New
#1
MS forced updates with autoupdates disabled or what?
I have autoupdates is disabled in Services. I only update every month or so. I’m using a an audio recording program, Sonar Platinum. In our forum 4 weeks ago, it appears that MS did some forced updates to everyone’s computer even if autoupdates were disabled.
4 weeks ago many of us developed runtime errors form plugins whenever we opened song files. When this happened, I couldn't’ determine what the problem was so I reverted back to an image file from Oct.
Through much trial and error I found out that as long as I was disconnected from the internet I didn't’ develop the runtime errors, yet after connecting to the internet, after a few minutes or an hour of so I would again develop the runtime errors. At this point if I disconnected form the internet the errors wouldn't go away. So it appears that something from the internet altered my computer.
ON Tuesday 12/20 without me doing anything the runtime errors completely went away for many of us, the previous day I had the errors. So something from the internet was changed and everything was fine and has been since.
Normally when something goes haywire the quick fix is to revert to a known reliable image file and I can continue to work. IN this case it didn’t’ work. Cakewalk, the software developer has this general explanation.
“a recent Windows 10 update has introduced instability in a subset of our plug-ins and may cause SONAR or other Windows DAWs to crash. The problem is related to a change in the timing for thread initialization on Windows, which leads to intermittent crashing on project load, plug-in scanning, or adding these plug-ins to a project. We are able to reproduce the issue and it appears to only affect some systems since it is timing related.”
Most people were not affected the way I was, since I have lots of image files and was able to revert. Most used System Restore or a rollback method that went back to a previous Cakewalk version. These techniques didn’t’ work that well either and most that had this problem had just updated to the latest 2016.11 version, and the latest MS updates, and had more serious problems than I had since I developed a workaround. No one in the audio forum has any explanation of why this happened to my computer.
This forum has been excellent for understanding deep issues with Win 10 and MS in general. So I’m hoping someone can speculate what from the internet altered my computer without my knowledge. This software works fine disconnected to the internet, so it doesn't rely on a database or copy protection. MS is the likely suspect. I’ve never had a bug that reverting to a previous image didn't’ fix, so this Is unnerving.