So are we sure that all the recent issues are due to Microsoft? I don't think there's anything conclusive. I was under the impression that a MS update uncovered a flaw in the Sonar code. Code that was very old. At least that's what I recall from a very early post from the bakers.

ampfixer
So are we sure that all the recent issues are due to Microsoft? I don't think there's anything conclusive. I was under the impression that a MS update uncovered a flaw in the Sonar code. Code that was very old. At least that's what I recall from a very early post from the bakers.

 I saw that post. I agree we need more info from Cakewalk. It is a fact that MS is doing forced updates. Do an internet search.
 
Right now a few of us, including myself,  are speculating with educated guesses. I'd prefer definite facts also. Hopefully Cakewalk will respond soon.

It's Putin, I'm sure of it.
 
That Commie Putin has been ComPutin.

I think it's more cakewalk just based on my on observations. I mean I have other DAW software I tested with no problem. Just to name one instance. What I want is for cakewalk to give us some kind of feedback. I believe it's over due.

robert@gmwmusic.com
I think it's more cakewalk just based on my on observations. I mean I have other DAW software I tested with no problem. Just to name one instance. What I want is for cakewalk to give us some kind of feedback. I believe it's over due.

Agreed.

robert@gmwmusic.com
I think it's more cakewalk just based on my on observations. I mean I have other DAW software I tested with no problem. Just to name one instance. What I want is for cakewalk to give us some kind of feedback. I believe it's over due.

agreed

it's being clearly blamed on ms over at the steam forums, "We're likely going to have to rebuild and publish updates for the plugins to fully address the issue Microsoft created."
http://steamcommunity.com/app/380080/discussions/2/154643795213913095/
 

gmp
I’ve never used 2016.11. I was using 2016.09 when this all started about 2 weeks ago. All of a sudden out of the blue, I got a runtime error, which I've not seen as far back as I can remember. I reverted my C drive back to a previous image file from 10/23 and to my surprise, the problem resurfaced again.
 
After much time and testing,  I traced it back to me having an internet connection. When I disconnected the internet and reverted back to an old image, I wouldn't get the runtime error. After reconnecting to the internet, I got the runtime error about 30 min later. Once you get the runtime error it’s like a virus, the only fix is to revert to an old image and stay off the internet.
 
Last Saturday and Sunday I did lots of extensive testing with some old image files and never had any runtime errors, even though I was connected to the internet. Yet on Monday the runtime errors came back. I have Win autoupdates turned off. What is MS doing to our computers?

This is certainly the most interesting clue I've seen so far!
 
Using 2016.09, which appears to be a very stable Platinum release.  That rules out the most recent Sonar updates, at least in this case.
 
He Rolled back to an October image,  which rules out the Microsoft updates from November.
 
Folks started seeing issues two weeks ago.
 
He has updates disabled, but apparently "something" is updating when connected to the net.
 
What is updating?  Is there another application or driver updater or something running under the radar here?
 
For example, some security software silently updates it's program versions in the background, in addition to updating daily virus signature files. 
 
I don't have any other Microsoft programs on-board, but I wonder if MS Office can do silent updates?  ... or browsers???

I can run rapture and dimension pro 64 bit stand alone using my ASIO driver in my windows 10 pc with no problems. I can't run my ASIO in sonar at all. Just a not to ponder.

abacab

gmp
I’ve never used 2016.11. I was using 2016.09 when this all started about 2 weeks ago. All of a sudden out of the blue, I got a runtime error, which I've not seen as far back as I can remember. I reverted my C drive back to a previous image file from 10/23 and to my surprise, the problem resurfaced again.
 
After much time and testing,  I traced it back to me having an internet connection. When I disconnected the internet and reverted back to an old image, I wouldn't get the runtime error. After reconnecting to the internet, I got the runtime error about 30 min later. Once you get the runtime error it’s like a virus, the only fix is to revert to an old image and stay off the internet.
 
Last Saturday and Sunday I did lots of extensive testing with some old image files and never had any runtime errors, even though I was connected to the internet. Yet on Monday the runtime errors came back. I have Win autoupdates turned off. What is MS doing to our computers?

This is certainly the most interesting clue I've seen so far!
 
Using 2016.09, which appears to be a very stable Platinum release.  That rules out the most recent Sonar updates, at least in this case.
 
He Rolled back to an October image,  which rules out the Microsoft updates from November.
 
Folks started seeing issues two weeks ago.
 
He has updates disabled, but apparently "something" is updating when connected to the net.
 
What is updating?  Is there another application or driver updater or something running under the radar here?
 
For example, some security software silently updates it's program versions in the background, in addition to updating daily virus signature files. 
 
I don't have any other Microsoft programs on-board, but I wonder if MS Office can do silent updates?  ... or browsers???

Well the plot thickens. I opened Control Panel Programs and looked at my updates. It shows that the last MS updates were on 10/9 and then it shows an Adobe Reader update on 12/10 - hmmm. I looked in my startup groups and see it doesn't show up, so there must be a setting in the program about autoupdates.
 
I uninstalled Adobe Reader and I still have the runtime error. So I just reverted back to my 10/23 image, opened Plat – no error. I then uninstalled Adobe Reader. Rebooted the computer and opened Plat and to my surprise, I again have the runtime error.
 
So maybe it’s not Adobe after all. I wonder if it’s MS Defender? This my DAW, so I try not to do much internet work, except those related to my DAW. So I dot[‘ have any virus software installed, since I’m careful. So what could be updating without my permission?