could the analytics be helpful here? identify differences between the crashes and crash-nots?

Zargg

John
Now I feel left out. 

Maybe we should go to the back of the room
I'm not having these issues either..

Come on back here guys. Everything's just fine at the back wall.

So I rebooted and start sonar, check for audio devices, everything looks fine. start a new blank project and it does let me. First thing I masochistically do is open the pro channel and insert ca-2a and crash! I think I'm going to devote this week to practicing instruments and keep an eye on the forum... 

I've had several problems since the update.
 
1. In one project, I was using Session Drummer for a click track (don't want to argue about the Metronome right now). After the update, Session Drummer started playing back one of its canned MIDI sequences along with the click when I started to track, at very high volume. (This was compounded by my not being able to find the Synth Rack, but that's my fault for not reading the e-zine.)
 
2. While opening a project containing Rapture Pro, I got a message reading "Failed to locate resource", then a MS crash message (0xc...05). I uninstalled and reinstalled Rapture Pro, which seemed to fix it.
 
3. Trying to open some projects from the Start Menu or from the File menu led to "SONAR.PLT has stopped working". They opened OK from Windows Explorer, and behaved normally after saving.
 
I'm sure all this is going to get worked out.

I also am experiencing very odd behaviour. The odd thing is that I don't keep my music computer connected to the Internet. Yet when I turned it on Sonar was behaving with almost all the problems listed in previous threads.

Sonar claims that I must re authorize plug ins and that others don't exist. It is very weird. I hope they have a fix soon.

I just checked a project that has no plug ins and it loads and plays fine. So I presume, as has previously been said that it is caused by the plug in manager.

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. 
 

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. 

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.

@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. 
 

32 bit is not the issue in my case. 
 

Interesting Stevesweat and Jackson white...
 
I have the Roland Octacapture and am seeing the same thing.  Any Sonar crash (CA2A or Melodyne, or anything else) causes ASIO drivers to vanish from my machine.  The only way to get them back is to restart DAW.
 
Now a days I always check a standalone VST like EZkeys to make sure my ASIO drivers are alive on the machine.
 
I have disabled and reinstalled the drivers a few times and it seems to help for a little while.
 
Do you also have super slow project loading times ?  I sometimes have 7 - 10 minute times loading projects.  Not sure if it is Roland ASIO driver related ?
 
I will start a new thread and see how many others are seeing issues with their Roland ASIO cards in the last little while.
 
JR

Was David Blaine on the build team for CA-2A?? I think there is a time bomb in it.

I'm reaching way out on a limb here, but is there a pattern in common to a specific brand of audio interface and their ASIO drivers, that is now having issues with the plugins?  I ask this because not everyone has seen the issues in 2016.11.
 
Just wondering, because several folks have said that Sonar crashes for them upon inserting certain VST plugins, or starting up an existing project that contains them.
 
Noel mentioned that nothing has changed specifically relating to VST handling.
 
But, is it possible that the changes in 2016.11 to enhance the WASAPI drivers could be at play here?  I believe that some VST's interact with the Sonar audio engine as soon as they are inserted into a project.
 
See this related thread: http://forum.cakewalk.com/Calling-All-Roland-Sound-Card-Users-Quad-and-Octa-m3524639.aspx

@abacab
 
The Roland xCapture drivers have always been a bit shaky in my experience but only a minor inconvenience for some time. Easily recoverable with a PC restart, which in my case trashes any "fixes" I made to get the CW VSTs working. 
 
@klauslix reported what sounds like identical symptoms and issues as mine but with a different interface (Steinberg) so I suspect the driver is likely more of a red herring. 
 
However, I am wondering about the recent WASAPI drivers feature as my CPU core balancing now looks considerably more unbalanced than with the previous update. Certainly a "core enough" change to consider the potential impact on any drivers. I've also noted CW very recently updated two of the FX suites with the problematic VSTs before the latest update. 
 
IME, it has only, but very consistently, been the same select CW VSTs that can be associated with the problem. Noel Borthwick stated in another thread that no changes were made to the VST Scan and I believe him, -but- something must have corrupted/changed with the noted CW VSTs to crash Cakewalk VST Scan. 
 
I will try looking into system cfg, Win10 changes, VST3? this Thursday for additional clues. 

@bitflipper
 
Agreed on the driver comments, believe it's a bit of a red herring.
 
> Have you noticed any changes on the appearance of your CPU core balance? 
 
Mine were remarkably low and well balanced -until- the latest update. I've only had to time to run a few  larger projects since the latest issues but noting large discrepancies across the cores with #1 spiking considerably higher than all the rest.