It's in preferences somewhere.
Start sonar in safe mode. Control on start;right?

jackson white
@jemodu
Have not seen any issue with any other VSTs. From your list I only have the Aria and AAS players but they're scanning, loading and playing as before. Issues were reported with the BT Trackbox, but I'm not able to duplicate them either. 

It seems this problem causes the system to "teeter on the edge." Sometimes things fall off, sometimes not. I can do multiple sessions in a row and everything works fine, then opening up the same project later can cause a crash. 
 
Lance, thanks for the update. Much appreciated. FYI - I'm also having anomalies with 2016.10 on my desktop, and these issues started at the same time as the anomalies with 2016.11. This supports your saying the issues are due to changes in Windows, and are not specific to 2016.11.

My Sonar Platinum crashed today during VST scan. On attempting again, the next crash came up with a message indicating a problem related to my new keyboard (Nektar LS-88+). Crash report to send to Cakewalk. Since it was also during the VST scan, very possible that the "timing" issues are the problem.  After rebooting the computer and attempting to open Sonar, I got a message from Sonar that there is no audio device and that I'll need to indicate one in preferences. At least no crash this time. Outside of Sonar, computer plays sound fine. Inside Sonar, edit preferences no longer shows my Edirol UA-101 device, so nothing available to select. Just about as bad as a crash to have a music program unable to make sound. Since this also is during startup, I'll assume the Windows update issues are contributing. Since Cakewalk works closely with Microsoft, I hope the bakers will let Microsoft know how disruptive their involuntary "updates" have been.

Shortly after I typed my message here, Windows popped open a message that it would need to schedule a restart. I closed open applications, rebooted, watched the messages about Windows installing yet another update, then watched the reboot happen. Just for fun I tried opening Sonar again. It opened normally. No issue with VST scan. No issue with missing audio device. I opened my recent project to find it working just fine again. Here's hoping this new update actually patched the underlying issue (although I understand the issues have been inconsistent for others, so I won't celebrate too strongly until the improvement clearly persists).

Hey - just checking in.  Haven't done the 2016-11 update yet, but am running with an offline machine (Windows 7 Home Premium and i7-970 processor). 
 
Anyone with Win 7 seen issues with this update?
 
I'm up for doing the install but can easily way for a more stable update, if that it what is necessary.
 
By the way, I tried doing the Screenset install (with 2016-6, I think) and it failed (I think due to my machine being at the Windows 7 baseline level), I reported it, but just want to shout out that a few of us have remained with that OS version, so please consider that when you move forward.
 
Much appreciated.
 
Best,
Jim 
 

rwheeler
Shortly after I typed my message here, Windows popped open a message that it would need to schedule a restart. I closed open applications, rebooted, watched the messages about Windows installing yet another update, then watched the reboot happen. Just for fun I tried opening Sonar again. It opened normally. No issue with VST scan. No issue with missing audio device. I opened my recent project to find it working just fine again. Here's hoping this new update actually patched the underlying issue (although I understand the issues have been inconsistent for others, so I won't celebrate too strongly until the improvement clearly persists).

 
I can confirm the new cumulative update (KB3201845) fixed the Plugin Scanning issues for me.

FWIW, I just received a Microsoft update, KB3201845 on Win10.
I did not have the crash issues before (last update from Microsoft that I received before this was Nov. 9) and I don't have any afterwards.
Just tested a new project with multiple insertions of Z3TA +2, CA2A, LP EQ and LP MB.

soundtweaker

rwheeler
Shortly after I typed my message here, Windows popped open a message that it would need to schedule a restart. I closed open applications, rebooted, watched the messages about Windows installing yet another update, then watched the reboot happen. Just for fun I tried opening Sonar again. It opened normally. No issue with VST scan. No issue with missing audio device. I opened my recent project to find it working just fine again. Here's hoping this new update actually patched the underlying issue (although I understand the issues have been inconsistent for others, so I won't celebrate too strongly until the improvement clearly persists).

 
I can confirm the new cumulative update (KB3201845) fixed the Plugin Scanning issues for me.

That is odd that Microsoft shipped out a cumulative update for Windows 10, version 1607, on a Friday before patch Tuesday.
http://news.softpedia.com...kb3201845-510849.shtml

oy when it rains it pours. Following this I noticed I had Win updates that didn't go in right, now I'm upstream problem solving. What is this, the 90's?
 

Symptoms did not change for me after the KB3201845 update. My test case is inserting CA-2A into a new project after rebooting, which consistently raises a stack overrun exception.