Now all we have to do is figure out what the difference is between those who have it running fine and those who don't.
 
I guess I fall in the middle, had problems until after rebooting a couple times and then all was well.

If anything glad I bookmarked this forum location, LOL, I haven't ventured into the "kitchen" yet. 

Is there an easy and reproducible recipe for a crash, preferably starting from a blank project?
 

OK, also did the MeldaProduction upgrades sometime after getting the LUFS Meter and today did the Cableguys updates..  Thought I had something amiss from all that, with more crashes and the audio engine stopping frequently. If things don't smooth out tomorrow, will roll back..

I have the rescan problem too, and mine stalls at the first Cakewalk Plugin on my list - the LP64.
 
I rolled back, and the manual scan still stalled at the LP64.  But I only rolled back the Platinum update, not the Boutique Effects update (there was a Cakewalk Instruments update too).

I was never able to get Sonar to work with Windows 10. I'm still using 7, and haven't had any issues.

PeterMc
Is there an easy and reproducible recipe for a crash, preferably starting from a blank project?

For me, it's easy and reproducible. All I have to do is 1) reboot the machine and 2) insert CA-2A into an FX bin (or open a project that already contains CA-2A in an FX bin).
 
Not everyone's experiencing the same symptoms, though. For example, I have no problem doing a scan.
 

I rolled back to 2016.10 and still am having the same problem. One project (which was created in 2016.11) in particular always crashes sonar while loading the first time, but then will load the second time. If I put ca-2a in the pro channel (or fx bin - just checked) sonar crashes.
 
I'm not getting crash report offers - not sure if they need to be enabled - I've gotten them at the studio before but not here at home. I'm referring to Sonar asking if you want a dump report etc. upon crash.
 
Once they open everything seems fine, and a simple midi project I created after rolling back opens and runs fine. But try to insert ca-2a in anything and crash...
 
Against my better judgement I will try to open the project I created in 2016.11 that still crashes the 2016.10 rollback at home, up at the studio today on my main rig which has yet to be 2016.11'ed but IS windows 10 current.

I have had Sonar crash on startup a few times, but it always starts the second time.

This didn't happen before the update. It happens whether I am opening a project, or starting Sonar "blank".

I have not investigated the ca2a problem, but will try tonight. I have worked on projects that contain the PC.ca2a, and loaded PC presets that use it, but have not inserted it on its own.

No problems with scan.

Windows 10 x64.

Is there any difference in behaviour for those that installed the anniversary update and those that didn't?

bitflipper
For me, it's easy and reproducible. All I have to do is 1) reboot the machine and 2) insert CA-2A into an FX bin (or open a project that already contains CA-2A in an FX bin).
 
Not everyone's experiencing the same symptoms, though. For example, I have no problem doing a scan.
 

Same results here.
 
(FWIW) Plugin count significantly increased after update.  Discovered the "C:\Program Files (x86)\Cakewalk\Vstplugins" had been added to VST scan path after update.  Deleted path, rescanned, plug count as expected.