• SONAR
  • VST scan still hanging on CW synths even after installing 2016.12 (p.2)
2016/12/15 20:24:54
chuckebaby
Noel addressed this in the 5 page thread that was started last week. it appears the problem is with Windows and not Sonar. how this is possible is beyond me, but I can believe it, I don't think Cakewalk is going to re write the code and work backwards to help out Microsoft.
2016/12/15 20:37:55
RSMCGUITAR
chuckebaby
Noel addressed this in the 5 page thread that was started last week. it appears the problem is with Windows and not Sonar. how this is possible is beyond me, but I can believe it, I don't think Cakewalk is going to re write the code and work backwards to help out Microsoft.


Does that mean all other DAWs are also hooped?
2016/12/15 20:41:45
RSMCGUITAR
I just remembered that I have Reaper. Tried opening it... it also crapped out and wouldn't start. It stalled out on the Cakewalk plugs that most here are struggling with too (ie. ca2a, rap pro/session, zeta+2)
 
2016/12/15 20:52:50
promidi
Looks like "Patch Tuesday" is turning into "Crash Wednesday"
2016/12/15 21:29:22
bitman
promidi
Looks like "Patch Tuesday" is turning into "Crash Wednesday"


Ouch.
2016/12/16 13:44:58
bitflipper
Sometimes, identifying the problem can be far easier than implementing a fix. Especially when mitigation requires rewriting foundational code that will likely destabilize the application in unexpected ways.
 
My guess is Microsoft could alleviate the need for drastic action by either reverting to the previous method or offering it as an alternative for developers. CW is probably waiting to see what MS is going to do, while simultaneously working up contingency plans in case MS drags their feet. Traditionally, MS prioritizes problems based on how many users are affected. To put it into perspective, that same Windows update that broke CA-2A also made it impossible for millions of users to obtain an IP address via DHCP. Guess which one got an emergency strike force assembled in Redmond?
 
2016/12/16 15:14:34
Hatstand
There were four windows 10 updates between December 9th and 13th on my rig
Security Update for Adobe Flash Player for Windows 10 Version 1607 (for x64-based Systems) (KB3209498)
Cumulative Update for Windows 10 Version 1607 for x64-based Systems (KB3206632)
Windows Malicious Software Removal Tool for Windows 8, 8.1, 10 and Windows Server 2012, 2012 R2, 2016 x64 Edition - December 2016 (KB890830)
Cumulative Update for Windows 10 Version 1607 for x64-based Systems (KB3201845)
 
any one of these could seem innocuous on the face of it, until you look at the list of effected files of which there are 15,000 entries in one of the releases.
I am guessing there will be quite a lot of investigative work to determine which one has caused the headaches.
I guess we could help if one of us has not installed certain updates but is experiencing the problems. It might assist the CW guys in narrowing down the cause. My guess is it is not the flash player update but I have been known to have been wrong
12
© 2026 APG vNext Commercial Version 5.1

Use My Existing Forum Account

Use My Social Media Account