I was also having real issues with 2016.11; Crashing on opening projects, crashing on inserting a synth, crashing when doing Edit >> Undo insert synth, crashing inserting CA-2A etc.
 
Restarting Sonar seemed to give a temporary fix but after a reboot the issues returned.
 
It also caused major issues with my Novation Impulse midi keyboard/controller; anything output from the keyboard on midi channel 1 would not play or register in Sonar. Also, the faders in the control surface stopped working. The keyboard still worked OK in Sonar X3.
 
Tried rolling back to 2016.10 and then 2016.09 neither of which worked.
 
I only managed to fix the issues by doing a complete C drive restore (Sonar is installed on the C drive) from the day before the update to 2016.11.

I am also getting crashes. I have no instances of CA-2A but I loaded a previous project that I need to add a part in and it would crash after about 60 seconds every time I restarted it.  Reboots didn't seem to help. I rolled back then and still had the same problems.
 
I still have Pro installed (as I did an upgrade and didn't really need the SPLAT features last night) and it didn't crash but the audio engine stopped every 40 seconds or so without fail even after a reboot.
 
So what should have been about half an hour of adding a part I spent most of the time fighting with the crashes in the DAW. 
 

Yes.
 
I've narrowed down to 4 CW VSTs in a project with a single audio track and bus. 
 
Did an uninstall, registry cleanup, reinstall and VST Scan for the CA2A. 
 
> Seeing intermittent issues with VST Scan. Will sometimes hang, need to be restarted, will eventually complete the scan after a couple of tries.
 
I am then able to load and run the simple test project as well as client projects with the CA2A. 
 
However restarting the PC (i.e. power down when done working or soft boot) will undo everything and I'm right back to ground zero.  I've gone through this cycle 12-15 times over the last day or so. 
 
Please see CWBRN-61566 for further detail. 

Deleting AUD.INI on my system was one of the first thing I tried. 
 
No luck.
 
I can fix the problem, but in my case at least, something goes wrong after a PC Restart. 

@klauslix
 
Noting the exact same symptoms and issues, all very repeatable with the simplest of projects. 
 
I can get things working, but they only last until the PC gets restarted. 

I dug into the VST Scan issue. SONARPLT.exe was no longer set to "Run as Admin" (who knows why, possible either a Sonar rolling update or Win10 update issue?) I reset it and VST Scan ran much smoother ... for a while.
 
As I continue to trouble shoot this, I'm seeing it starting to hang again on the same CW VSTs. 
 
trying to pick out the red herrings in this one.

Noel. 
 
I was using 2016.10 quite successfully. 
 
I tend to believe the problems are most likely coincidental, but it's proving to be a bit of challenge to identify the root cause and correct them. 
 
The symptoms that can be repeatably observed on my PC are:
1. CA2A will crash any project with it in it. (AS will trying to insert RaptureSession. LP 64 EQ or MB)
2. Uninstalling and reinstalling seems to restore usability until the PC is restarted. 
3. VST Scan will hang on CA2A, RaptureSession and throw "Runtime Errors?" on the older LP 64 EQ and MB
 
Rolling back to 2016.10 did NOT solve the problem. 
 
System Restore did NOT solve the problem. 
 
There are several posts with very similar reports. 
 
Please feel free to take a look at CWBRN-61566 or suggest something to try. 
 
It would be appreciated. 
 
 
 
 
 
 
 
 

@stevesweat  
 
Roland drivers do not appear to be the most robust and in my case I need to restart the PC to get them back after "SONARPLT.exe has stopped working".
 
I've reinstalled the drivers a number of times as part of troubleshooting issues, and nothing has changed. Still need to reboot after a crash. 
 

Unfortunately, rolling back from Win10 to Win7 is not an option. 
 

32 bit is not the issue in my case.