John

paul jenkins
.

Paul posting only a dot is not allowed. Its a violation of the rules. If you have something to say please say it. if you posted something and you wish to remove it a host can delete it. All you have to do is ask. 

Sorry i was testing something out, didnt know it was against the rules,please remove my dots

Since I had similar things to do to 15 old projects, I wasn't doing normal stuff. I was editing the tracks vs mixing polishing etc.
 
So when I tried to insert AmpliTube 4 on a guitar track, today, it's not there, though the Scanner shows all 502 of my plug ins. PSP is nowhere to be found either and if I weren't so frazzled, I could see what else is not showing up/available.
 YUCK
Michael
 
 

Having all sorts of VST scanning problems too.. When I try to scan, it hangs on random VSTs. And they're not Cakewalk VSTs.. The last one was the bx-Opto compressor.. I hope the bakers geb a quick fix in - well.. quick! I'm kinda dead in the water right now.. 

This issue reminds me why I take a system backup image each month.  I know I can roll everything back to it's last working state. 
 
That full image recovery option is always there if uninstalling a new version of software doesn't fix the issue I'm having. It also takes care of any conflicts with Windows updates or drivers too.  It's a complete snapshot of the entire system drive at the time that it was made.
 
Another option for use now, if you don't have a recent image from a known working state of your PC, is to look and see if you have a Windows system restore point that you can roll back to.  That should only take all of the Windows system files (and registry) back in time to the state they were in when that restore point was made.  Your personal folders don't get messed with.
 
You may need to re-install any software applications that were installed or updated since the date/time of that restore point.  The Windows registry gets rolled back as well.  There is a tool in Windows System Restore that allow you to scan for affected programs.  Just select the desired restore point, and click on "Scan for affected programs".
 
The way I would do it is to first uninstall the affected program(s), then run the restore, reboot, and re-install the version of the program that I wanted to run.  In the case of Sonar, maybe an earlier version ...
 
Example: last night I updated a program, that broke another program.  Just uninstalling the updated version and rebooting did not fix the problem.  I had to fall back to a Windows restore point from 7 hours earlier, followed by a reboot, to get running again.  Moral of this story: Windows is a tangled mess

Pragi
Thanks for your tips.
Another system recovery ( 11.2.16 ) and a rollback to Sonar 2016 10
gives the following new results .
Some smaller projects (arround 45 tracks ) are now working flawless, means I can open and edit
as expected ,
but the bigger projects (more than 70 tracks ) are now not opening at all -
no slow safe mode opening aso is working.
For the moment it´s okay to have the possibility to work on the smaller
projects .
Hope Cakewalk will manage a fix asap.
Don´t want to do a system backup cause it´s more then 3 months ago I did that.
Good reminder to do that monthly.
 

Another thing that occurred to me is maybe it's also a good idea to perform a complete clean uninstall of Sonar, before rolling back to a previous Windows restore point. There might still be a few things lurking from the newer Sonar version, even after the restore.  Windows restore only rolls back Windows files, not applications.  If the application un-installer leaves something behind, as most do, it could cause trouble.
 
There is this procedure on the Cakewalk knowledge base > https://www.cakewalk.com/...n-Install-Instructions
 
Also, what if maybe 2016-09 is the last stable release of Sonar?

brekus1
I just purchased a laptop win 10 home, 8 gig ram, 250 gig ssd, core i5 7th gen processor.  build 111 installed.  Instant crash when attempting to open any existing or new project.  No prior versions on this brand new laptop.  Any way to roll back to an earlier version?

Dang!  Sorry to hear that!  If it was mine, and I hadn't spent too much time setting up the new laptop, and all I had installed was Sonar I would probably do a factory reset and start over.  Probably go back to Sonar 2016-09 just to be safe. 
 
I have seen a few comments that rolling back Sonar has not been completely successful in some cases.  That said, there are probably ways to perform a clean uninstall of Sonar, then using Windows system recovery with a Windows system restore point taken before installing Sonar. But that could be hit or miss ... and  they are working on a fix, so maybe patience is the best strategy.

gmp

brekus1
I just purchased a laptop win 10 home, 8 gig ram, 250 gig ssd, core i5 7th gen processor.  build 111 installed.  Instant crash when attempting to open any existing or new project.  No prior versions on this brand new laptop.  Any way to roll back to an earlier version?

With Command Center you can choose to download all the files to your specified location. I do this and have every version of Plat, plus all the FX, etc. 2016.09 for me is the best most stable version. I always do verbose installs on everything, so I can control the installs better. I would think that you could download 2016.09 from Cakewalk. Check it out

If you log into your account, all of the prior versions of Sonar that existed since you owned the product are available.

brekus1
I just purchased a laptop win 10 home, 8 gig ram, 250 gig ssd, core i5 7th gen processor.  build 111 installed.  Instant crash when attempting to open any existing or new project.  No prior versions on this brand new laptop.  Any way to roll back to an earlier version?

You might have more luck opening the projects in safe mode, hold shift down when opening, then disabling the plugins - specifically Ca-2a and Rapture - as there is a known issue with them and a fix is in the works. My woes were relieved by disabling CA-2A and Rapture in my projects until the fix is in...
A lot of people have reported rolling back does not fix this as it is more of a Windows issue.
You say you can't open a new project, do you mean you can't start a new project or you can't open a very recent project?

Pragi

Bristol_Jonesey
Well the good news is that Cakewalk can reproduce the problem with CA2A and are currently working on a fix, so hang on in there!!

Thanks for your hinds.
My box is now working stable again after the following steps which were 
delivered by the members of this great forum :
 
- Win 10 update to the newest build
- Sonar rollback to version Sept. (9)16
- Deinstallation of Cake´s La 2a
 
- new start 
 
- refreshing vst 
- vst scan
-  opening a project - that didn´t open or crash -in safe mode
   pressing no to all- and (after some unrelevant  editing )don´t safe
 
- new start
 
Now all projects are opening in my box, no crashes ,glitches aso anymore.
 
Hope this helps 
regards
 
 
 

So did you re-install ca-2a at any point?? (or is de-installation a misspelling of re-installation?)

Bristol_Jonesey
I think there's more going on than just CA-2A issues

From what I read, yes. I would love to install the new update, but I'm finishing up some projects and don't want my Plat to go down in flames...
 
Walt

I'm experiencing a ton of crashing as well as failure to recognize my USB interface.  Here's one error I am seeing a LOT, and forces me to reboot my desktop computer:
 
Microsoft Visual C++ Runtime Library
Runtime Error!
Program: C:\Program Files\Cakewalk\SONAR Platinum\SONARPLT.exe
R6025
- pure virtual function call

I am experiencing crashes on every session. Usually I am just trying to move a plugin from one track to the next.
 
I get around 60 fault report windows open & only one of them sends the error report.
 
Takes me a good half hour of clicking to try and get to a point where I can close SPLAT down.
 
I haven't had any luck being able to view the mini dumps with the tools mentioned above.
 
Does anybody know how to open the SPLAT mini dump files???
 
Is there a way I can get Cakewalk to follow up on the error reports?

I have been checking on the status of theses reports for months now & it would appear they haven't been looked at.
 
Any advice would be appreciated.
 
 

+1 for the crazy behaviour of the Fault Reporter which is now adding to the horror of the all-too-frequent crashes which seem to occur around plug-in activity (moving, adding or deleting plugins etc.). The crashes now stimulate a non-stop loop of the Fault Reporter starting itself multiple times.
 
Close to despair. Has anyone found 2016.12 any better than 2016.11?