Anderton
Do you save the project in X3 before closing it?

No , just open it without saving.

Hi all. Thanks for the supportive replies. I'm sure they are working on the fix, but surely as customers we and our customers deserve to be updated. The silence is obviously a tactical which is sad. I'm starting a new customer project this morning and will be using Reaper.
 
Come on Cakewalk, get together and review your communication here, you need to take a more active approach to your customers when you have problems, not just when you want to market something.

bitflipper
The easiest workaround is to start SONAR and close it. For me, at least, the problems do not reoccur after SONAR has been opened once. They reappear after a reboot, however.
 
It would be nice if Noel would give us a little information, though. I'm sure he already knows what the problem is, but the fix is likely going to be very difficult. I'm also sure he's deep into it and hasn't seen a 40-hour workweek since this all began.

Unfortunately this workaround does not work on my system. 

@jimo
 
Have you tried running Procmon before opening a project? 
 
That's been the only consistent way for me to keep rolling. 

eltonechris
Come on Cakewalk, get together and review your communication here, you need to take a more active approach to your customers when you have problems, not just when you want to market something.

They obviously are. I found these in two minutes by using search.
 
http://forum.cakewalk.com/Instability-with-certain-Cakewalk-plugins-after-recent-Windows-10-updates-m3526221.aspx
http://forum.cakewalk.com/FindPost/3530698
http://forum.cakewalk.com/FindPost/3530429
http://forum.cakewalk.com/FindPost/3530426
http://forum.cakewalk.com/FindPost/3524975
http://forum.cakewalk.com/FindPost/3524877
http://forum.cakewalk.com/FindPost/3524873
http://forum.cakewalk.com/FindPost/3524877
http://forum.cakewalk.com/FindPost/3524916
http://forum.cakewalk.com/FindPost/3524919
http://forum.cakewalk.com/FindPost/3524750
http://forum.cakewalk.com/FindPost/3524787
http://steamcommunity.com/app/380080/discussions/2/1843493219431348830/#c1843493219431590250
http://steamcommunity.com/app/380080/discussions/2/1843493219431348830/#c1843493219432235253
http://steamcommunity.com/app/380080/discussions/2/1843493219431348830/#c154643795211614585
 
 

Craig, I already read I think, all the posts you listed. Many are Cake asking for more info or dumps. The ones on the steam forum provide the most actual content. Bob Kellogg stated that he had isolated the issue within a few days of the issue appearing. Not much has been said since then.
I was VERY surprised to see 2016.12 preview made available so early without any mention of this problem.
I think what the OP wants to see is maybe an official sticky post up top saying something like...
 
We are in contact with MS regarding this problem and are waiting for a reply stating whether they intend to revert the offending code changes. In the event they do not, we have identified the problem and are proceeding with a fix to the failing VST plugins. We apologize to our users, especially those who are completely down. Here are some things that may mitigate this issue.... list rollback to 2016.10, procmon, run X3 then Plat, etc, etc.
We hope to have updates to CA-2A and Rapture available with <x> weeks.
 
 
 
 

Lots of crashes here as well.
Especially when exporting track templates which I cannot do at the moment because SONAR will crash 
 

microapp
Craig, I already read I think, all the posts you listed. Many are Cake asking for more info or dumps. The ones on the steam forum provide the most actual content. Bob Kellogg stated that he had isolated the issue within a few days of the issue appearing. Not much has been said since then.
I was VERY surprised to see 2016.12 preview made available so early without any mention of this problem.
I think what the OP wants to see is maybe an official sticky post up top saying something like...
 
We are in contact with MS regarding this problem and are waiting for a reply stating whether they intend to revert the offending code changes. In the event they do not, we have identified the problem and are proceeding with a fix to the failing VST plugins. We apologize to our users, especially those who are completely down. Here are some things that may mitigate this issue.... list rollback to 2016.10, procmon, run X3 then Plat, etc, etc.
We hope to have updates to CA-2A and Rapture available with <x> weeks.

 
I realize a lot of people just skip past the stickies, but doesn't the following sticky pretty much say the same thing? I'm not sure it's necessary to tell people they can roll back, isn't that common knowledge? The one thing the stick doesn't have is an estimate on the time frame, but that seems to be out of Cakewalk's control to some extent given Seth's post about waiting to see if Microsoft is going to fix the issues that caused this. I can only imagine the code chaos that would happen if Cakewalk does a release to get around a Microsoft bug that no longer exists by the time the release hits...
 
Instability with certain Cakewalk plugins after recent Windows 10 updates
 
It has come to our attention that a recent Windows 10 update has introduced instability in a subset of our plug-ins and may cause SONAR or other Windows DAWs to crash. The problem is related to a change in the timing for thread initialization on Windows, which leads to intermittent crashing on project load, plug-in scanning, or adding these plug-ins to a project. We are able to reproduce the issue and it appears to only affect some systems since it is timing related. We are actively working on a resolution and will release fixes to the affected plugins as soon as possible.

Plug-ins that may be affected:

• CA-2A
• Rapture Pro
• Rapture Session
• Z3TA+2

We appreciate your patience while we work to resolve this issue,
- Cakewalk
 

Lance Riley
Product Manager

I doubt MS will revert their code since I have seen nothing in the tech press about the new thread intialization causing problems elsewhere. Cake has already said the problem has existed for years and that it is a Cake bug. The MS change only exposed the bug. It sounds like the MS change was an improvement (i.e. faster). If Cake fixed this and MS reverted, the fix still should work, otherwise many programs running on Win 10 would be having problems and this is not the case.
Cake has stated the bug is in the affected plugins and not the Sonar core. The problem has been identified and apparently it is known how to fix it. I don't think it is unreasonable to expect at least a general time frame estimate for this to be resolved. Something like 'we expect a solution in the 2016.12 release' or 'in the 2017.01 preview'.

I was also puzzled by the explanation... I have tried to google for "the timing for thread initialization", but nothing useful appears. I must admit I have never used threads in Windows, but if such "thing" exists there, I guess it should be documented. If MS has introduced an issue in the core thread creation procedure, I am sure the Internet will explode immediately. Except this forum, I do not observe any reports...
I have always thought that user should never predict the "time" when new thread is created.