I just installed the new Sonar Braintree update. First I updated Sonar, then downloaded Bark of Dog, and up till then Sonar seemed to be working. After I downloaded the new Craig Anderton Collection update, Sonar (Platinum) now crashes about 10 seconds after launch, before I can do anything. I tried reinstalling the Craig Anderton collection, but that didn't fix anything. My old Sonar X3 installation works fine. Is there a way to roll back the Craig Anderton stuff or reinstall Platinum? The Command Center doesn't seem to have any such options.
 
My system: Windows 7 Professional 64-bit
Mac Pro 2008 with Boot Camp
RME RayDat PCI-E sound card
6GB RAM
Thank you, Shayne

Just uninstalled Sonar Platinum via "Programs and Features" in Control Panel, rebooted system, reinstalled Sonar, and it still doesn't work.

You might have waited for some help. Craig's fx chains can't have any effect on Sonars code, it doesn't use or change any of it.

Perhaps there was something else at work. Shame you did all the uninstall processes as The Command centre allows you roll back to an earlier version.

Well I just found the setup file for the pre-Braintree version of Sonar Platinum still on my hard drive, rolled back and now everything is working again. I don't know what's wrong with the Braintree update, but I should probably let Cakewalk support know what happened....

Perhaps it's worth trying it again. I've been frantically following all the comments about the Braintree update and haven't seen anyone with your problem.

Now you know how to roll back relatively easily if need be and then notify Cakewalk.

Is it possible this has something to do with cancelling the AutoScan on startup mid-stream?
 
I had a case where I launched Sonar without my interface on. As soon as I realized it <got the message box telling me so> I switched it on, but as we all know, it's too late then. So as the scanner ramps up to scan my plugs, I kill Sonar to re-launch.
 
After relaunching, it did not re-scan and plugs as simple as Channel Tools showed up missing in the project.
 
After a restart of the PC, the scan kicked off and ran to the end smoothly. This fixed things for me.
 
Noel asks why you wouldn't have scan on startup enabled, and this is why for me. It's not worth the trouble if it can force you to restart your PC.

GS: I hate having scan at startup enabled.  It takes long enough to load in my projects (I use mostly VSTi's with large sample sets).  Therefore, scan VSTs at startup is a NO GO for me.
 
I do a manual scan after installing new VSTs and this works out fine.
 
Jim

mudgel
You might have waited for some help. Craig's fx chains can't have any effect on Sonars code, it doesn't use or change any of it.

That is correct. The FX Chains are basically just documents. So my update did not kill SONAR, but the thread title makes me look like a badass who can kill programs at will, so that's kinda cool 

The VST scanner works in the background and with well over a thousand plugs (Komplete Ultimate, Waves Horizon, FabFilter Total and a bunch of singles) it takes seconds. Not to mention you don't even have to wait for it. Just saying. Sorry you're having troubles.

jkleban
GS: I hate having scan at startup enabled.  It takes long enough to load in my projects (I use mostly VSTi's with large sample sets).  Therefore, scan VSTs at startup is a NO GO for me.
 
I do a manual scan after installing new VSTs and this works out fine.
 
Jim

If I have NOT installed any new VSTs the autoscan takes about 3-5 seconds on startup of SONAR