thornton
I had a problem with ca2a crashing inserted to the prochannel and GMP suggested to totally uninstall and reinstall. tried it and so far it has not crashed thank God.

You're right, uninstalling CA-2A and then reinstalling it, solved the problem. But it doesn't always solve the problem, sometimes it can create a worse problem, if for some reason VST scan gums up the works by stalling on CA-2A. I also got in a situation where I reset VST scan and then since it would stall on CA-2A it wouldn't' finish the scan and I lost many of my VSTi synths and VST FX.
 
Since I have saved a lot of image files I have the luxury of reverting back to a previous file when things go totally haywire. You can read about that from the several posts I've done in the past week all related to this issue.
 
As of now, I'm pretty pleased because I can get work done. I'm using 2016.09 and on 1st boot up, I open Plat and get a runtime error message, I'm careful not to close that window by hitting OK. I just move the window way out of the way and then everything works just fine. All the plugins and everything.
 
So I'd encourage everyone to at minimum do several system restores where you save the restore points or better yet make image files, which are a little more dependable. I’m glad to see someone at Cakewalk reporting that he’s found the problem and they’re actively working on a solution.
 

I just stumbled into to something...on my system if I go to platinum/preferences/vst settings and set to manual scan then select re-scan then select scan for failed plugins CA-2A and CA-2A vst 3 come up as well as Rapture Session. I leave setting on manual scan, open new project and now everything works as it should. If I close and re-open Sonar things are still fine. If I restart computer it's back to square one and I have to repeat all that manual scanning. This means there is a timing problem or something wrong with when plugins are scanned ..like some kind of conflicting thing.... I guess??? Almost like a fight to get all plugins running.  it's a workaround anyway..works here.

Just curious? Is this all a win 10 issue? Because I have dragged, dropped, inserted multiple (in some projects 5 instances) copies of CA2a, rapture, etc into several different projects and no issues at all. I am on win 8.1x64 though. I do have a pretty powerful machine, but not crazy. Just an i7.....Lots of ram though . 32gb. Hmmm. Hope everyone gets a fix asap
 
 
Edit: Not sure if it matters but I did notice I do NOT have a VST2 of CA2a, only the vst3 version?

Since some days several projects are not openeing, in my  box ,
others do . Don´t know why, but it  not only occurs
with the Ca2A aso,
The workarund working for me is to open this projects in safe mode 
pressing slowly the yes button, sometimes it´s crashing again ,
then I try a second time - with success .
Pragi

Stratman: I'm using windows 10, but I have heard that some windows 7  and others have been affected. I didn't see your comment about not having vst 2 version of CA-2A. Funny.. I'm having issues with Rapture Sessions as well and it has vst 2 and vst 3 version too. As a test I could temporarily remove dll for vst 2 versions...maybe worth a try. Many users are not having issues since last update. It's a system problem possibly, depending on individual configurations...the work around I stumbled into is a bit cumbersome..hope a fix is coming soon.   

I posted because I was curious about if it was just win10. I have literally (actually) put in many instances of CA2A VST3 only, rapture sessions, rapture pro and not a hiccup. I have done this in multiple projects, shut down. walked away.. Came back and reopened all without a problem. They all run fine. Just wondering why it is I am NOT touched by this thing?  I thought perhaps posting what I have done may help others and CW get to this issue. That's why I asked about the windows versions. Wish I had more to offer. All I can offer is I seem to be immune.

It appears to be related to a combination of the latest Win10 update and some obscure artifact in a few CW VSTs. A few Win7/8.1 users have checked in to say no issues, but there are also Win10 users who have not been affected. Or at least can get up and running after a couple of reboots. I did some checking on VST2 vs. VST3 with no useful conclusions, probably more of a red herring. 

If it helps, I've been running the MS tool ProcessMonitor before opening a project and turning it off once it's loaded. (big thx to bitflipper for this insight). Projects are running fine on 2016.11 and seem to load/run OK once the Sonar session has been started. Might be safer to start/stop it each time you open a project, but so far I have not needed to do this. 
 
I understand this particular issue appears to be a bit of an obscure corner case and this workaround may not work for everyone. In the meantime I'm back up and working while the experts address the root cause. 
 

Yesterday I bit the bullet and installed 2016.11 on my Win 7 machine. This is my primary DAW so I started by doing a full system backup and created a Restore Point in Windows "just in case"
 
The updates installed without a hitch.
 
After experimenting for a couple of hours, inserting synths, Midi Editing, drawing automation, tweaking Fx plugs, I 'm happy to report that NONE of the symptoms on display with my Win 10 computers manifested themselves.
 
I worked on several different projects with widely varying plugin configurations, including CA2A, Rapture Pro, Z3TA+2, LP64 etc.
 
So this, to my mind, firmly points the finger at a Win 10 problem.

when you say "crash" do you mean bluescreen or just Sonar?