Two systems: Surface Pro and HP dv6
Both running Win10 Pro
I've been fighting a battle over the last three weeks with my systems acting very strange. Here are some of the symptoms:
- CudaDrive has lost connection and then reestablishes connection.
- Wireless network drops and has to restart the MS Wireless service after a timeout.
- Various App titles stop working, like messaging, Cortana, WinMail, etc
- In Win10 Settings>System the links for Apps&Features and Storage stop responding.
- Tons of error messages generated in the event log.
I've spent almost three weeks trying to narrow this problem down. Searching the various forums I started exploring the registry and found a number of permission errors. Thinking it must be due to a MS patch I have rebuilt systems from ground up, disabling MS patches, editing registry, etc.
Then I did a methodical step by step build of a system. I would install Win10 clean, create a system restore, install a couple of applications, create a system restore. Checking during these steps if things worked or broke. If they worked, I created another restore point and installed a few more apps. If it broke, I did a system restore and split test the recent app installs to narrow down to the faulting application.
The net result of this is that I'm convinced CudaDrive is causing a lot of problems. It took sooooo long to find this as the problem symptoms don't appear to have anything to do with CudaDrive; I blamed the problem on everything other than CudaDrive, from MS Win10 updates, to Office365, my ISP, to whatever. But just a simple install / uninstall of CudaDrive causes the problems.
I've created a screencast at http://www.screencast.com/t/Xe0bBusD0Y.
CudaDrive "appears" to work... that is, it does sync files and show in explorer. However, it is causing so many other problems and constantly (every 5-10 minutes) kills the wireless driver in my systems that I can't use it.
Anyone else seeing similar symptoms (again, from the outside they would appear to have nothing to do with CudaDrive.) It's hard for me to believe that I'm the only one with these problems, occurring on two completely different systems and clean Win10 builds.