I hope thay are making some progress, as in finding the solution to these problems. Mine crashes on first start then after one or two tries I can get it going. I guess it just depends on what plugin your using in your project.

Frequent crashes with a wide variety of plug-ins on different systems - certainly not confined to those mentioned so far. Is there any advice on roll-backs or whether 2016.11 is any better? (I'm on Platinum 2016.10). Never experienced anything even remotely like this before in all years I've been with Sonar.  Are we sure rolling updates was a good idea?

rjeynes
 Are we sure rolling updates was a good idea?

Since this was caused by Microsoft and not Cakewalk, I would say yes, rolling updates was/is a good idea.

Ok, but the fact remains what
You bought doesn't work. So it's the vendors responsibility to make it work. And I'm sure they will, Hopefully soon.

gustabo
Since this was caused by Microsoft and not Cakewalk,

i'm not sure this is actually confirmed as the case, there's been no real explanation yet?

Here's an interesting thread on the Microsoft Community page that discusses this Windows update issue and the effect it may be having on us all.

gustabo

rjeynes
 Are we sure rolling updates was a good idea?

Since this was caused by Microsoft and not Cakewalk, I would say yes, rolling updates was/is a good idea.

The one thing I did this morning was change my WiFi connection to a "metered" connection to allow me to control when Windows updates are installed. Going forward, when the Sonar update is released I'm going to:
 

1. Create a restore point
2. Allow Windows to install the cumulative update
3. Install the Sonar update

I hope this strategy avoids the mess I'm in right now (i.e. unable to use Sonar in any useful way)
 
I hope the bakers release a hot-fix soon! But I'm under the impression this is a complicated fix and they want to thoroughly test it before releasing it.

The "Thread" Mentioned above is from 2013. As of today, we still have received NO explanation from Cakewalk about these MASSIVE problems and NO prognosis as to when this is going to be fixed (and by whom). In other words, how long are we going to be out of business?

ok, here's some more fwiw
 
i had not experienced any of the issues reported by others
i just got a windows update, with KBs 2565063 and 3206632
i think ah ok here we go
let it do its thing
do an extra restart for good measure
opened test projects in sonar and another host
i still don't have any crashing with sonar or the ca2a (both latest versions, the ca2a is the from the recent freebie but vst3 only, sonar is the steam edition, and i'm assuming the shared components are the same for all versions, pim & vst scanner)
 
win10 pro x64, 8g, asio4all(!), nothing special, always online, etc
 
hth

dlesaux
Here's an interesting thread on the Microsoft Community page that discusses this Windows update issue and the effect it may be having on us all.

That thread is from 2013. Windows 10 was not out then.