toastjam
I'm having the same crashing problems since the update. It's happening on both my studio DAW and my portable laptop DAW that i use for remote recording so it's got to be something in the update. I tried rolling back to October and that didn't work so I reinstalled the most recent update. I tried it again and it didn't work...but, for some reason I started up Sonar again (without rebooting the computer) and tried to open the same project and it worked. This also is consistent with the laptop DAW.
 
In summary, on both my laptop DAW and studio DAW, Sonar doesn't crash when it opens. It crashes when it tries to open a project. Like I mentioned above, if I start up Sonar again after the crash and try to open the same project it works. I have never had problems with Cakewalk programs or Sonar so this is unusual and I'm not happy that I have to go through this to get the program running but at least I'm not dead in the water....at the moment

Same here, Sonar crashes when I open a previous project only. However, I removed Waves RVerb VST3, and saved the project under a different name. The project no longer crashes when opened.

They have released a sticky in the forums:
http://forum.cakewalk.com/Instability-with-certain-Cakewalk-plugins-after-recent-Windows-10-updates-m3526221.aspx
 
Seems to be a windows 10 update issue with thread utilization and not a Sonar problem.
but you know how that goes..a problem is a problem and eventually becomes a Sonar problem.

I read it as exactly the opposite.
A Win 10 update exposed a decades old bug in Sonar code.
Since running a debug process (Procman via Bitflipper) fixes the issue, this means Win 10 has become faster and now exposes the Sonar bug.
This is preferable since it is fixable by the bakers and we don't have to wait for Microsoft.
It is all good.

microapp
I read it as exactly the opposite.
A Win 10 update exposed a decades old bug in Sonar code.
Since running a debug process (Procman via Bitflipper) fixes the issue, this means Win 10 has become faster and now exposes the Sonar bug.
This is preferable since it is fixable by the bakers and we don't have to wait for Microsoft.
It is all good.

I've read and reread the thread and can't find it being referred to as a decades old bug in Sonar.

mudgel

microapp
I read it as exactly the opposite.
A Win 10 update exposed a decades old bug in Sonar code.
Since running a debug process (Procman via Bitflipper) fixes the issue, this means Win 10 has become faster and now exposes the Sonar bug.
This is preferable since it is fixable by the bakers and we don't have to wait for Microsoft.
It is all good.

I've read and reread the thread and can't find it being referred to as a decades old bug in Sonar.

http://forum.cakewalk.com/FindPost/3526186
 

Its not a bug in SONAR - the problem is completely unrelated to SONAR itself. Its an issue in some of the plugins that apparently just became a problem with newer windows updates. The issue will even happen in a different DAW that uses these plugins - the symptom would be that they would fail to scan.

Yes, and I think it's not related to the new Sonar update since my VST scan started to freeze this last days and I'm still in the 10.2016 version...