mettelus
I am pretty sure that is accurate. Additionally, registry entries added will also remain. The best method to "rollback" is a system restore prior to installation. These days restore points prior to installations is good practice for any software.

unfortunately that seems to be the case - which makes the entire Sonar rollback functionality less relevant

Rob[atSound-Rehab]

mettelus
I am pretty sure that is accurate. Additionally, registry entries added will also remain. The best method to "rollback" is a system restore prior to installation. These days restore points prior to installations is good practice for any software.

unfortunately that seems to be the case - which makes the entire Sonar rollback functionality less relevant

This is why I use image files of my C drive, so I know I've really rolled back to a previous state. Sometimes even system restore doesn't work right. Very strangely in this case even when I revert back to a previous image, I'm still getting this runtime error, making me believe there must be an internet database involved, either Cakewalk or MS

Rob[atSound-Rehab]

mettelus
I am pretty sure that is accurate. Additionally, registry entries added will also remain. The best method to "rollback" is a system restore prior to installation. These days restore points prior to installations is good practice for any software.

unfortunately that seems to be the case - which makes the entire Sonar rollback functionality less relevant

it would be useful for cake to clarify what gets rolled back, and what not

Copy here :
I can exactly point the moment this problem occured .
I Installed Sonnar X3 on a fresh laptop only 1month ago.It has only X3 and audacity on it, no extra VST's 

Last week W10 had a big install, after this install I opened Sonar and had it crashed on a project I have been working on every day of the week before.
So my best guess ; it is a W10 issue.

PatrickGo
Copy here :
I can exactly point the moment this problem occured .
I Installed Sonnar X3 on a fresh laptop only 1month ago.It has only X3 and audacity on it, no extra VST's 

Last week W10 had a big install, after this install I opened Sonar and had it crashed on a project I have been working on every day of the week before.
So my best guess ; it is a W10 issue.

 
I have auto updates turned off, so even though this cropped up for me last week also it had nothing to do with updates. In fact even if I revert back to my 10/23/16 image file, I now have the problem with that also. I definitely did not have this problem with that image in OCT.
 
 
In fact I did some extensive testing with several different image files and none of them have this problem as long as I am disconnected to the internet. And the problem shows up about 30 min after I connect to the internet. This has got to be the strangest bug I've ever experienced
 

UPDATE after some systematic troubleshooting today. 
 
1. I can open a project with a CA2A in it ONLY if I;
> uninstall it (Control Panel | Programs & Features > Uninstall CA2A)
> delete all registry keys
> reinstall it using the CCC.
This works only as long as the PC is NOT restarted. 
 
2. -EVERY- time I restart the PC, CA2A will crash the program on project load.  
- Actually inserting CA2A, LP 64 EQ or MB, or RaptureSession in any project will also crash SONAR, but I only use the CA2A. 
- All of the noted CW VSTs would cause VST Scan to hang or stop working. 
 
3. The comments about being able to ignore the "Runtime Error!" flags or it's only the first instance and all is fine afterwards do not work for me. Most likely because the Roland drivers seem to require a reboot after a crash. 
 
4. I was able to get VST Scan to run smoother be making sure SONARPLT.exe was set to "Run as Admin". I know to do this but it appears to have been reset as a result of a Win10 or SONAR update (will look into that).
Thx to abacab for the reminder, but it did not solve the problem with the CW VSTs.
 
5. My Win10 updates are set to "deferred" which means I schedule them when I have time to address any potential issues, but the system is up to date as of a week ago before the problems with the CW VSTs.
 
6. Only other activities I can recall are the Melodyne 4 Studio update to 4.1 and possible a Pace Ilok update. 
 
7. Even though I was able to open a client project after the uninstall/del/reinstall, I'm noting the CPU cores are much less balanced and the #1 core is spiking. They have been remarkably well behaved up til now.
 
8. The test project has a single audio track and a single master bus with only the PC EQ and one instance of the CA2A. Could hardly be simpler.
 
9. Still thinking it must be some core system issue as the rollback did NOT solve the problem. And per gmp, System Restore did not work either. That's more than a bit unsettling, looking for some help from CW at this point. 
 
10. Problem report filed as CWBRN-61566.
 
The other reports in the log are the result of the Problem Reporter flaking out and dumping as I was trying to enter the steps to reproduce the problem. I will add messages and further updates to this one only. 
 
I'm done for now until Wed, will be looking for something else to try. Limping along, but losing confidence.
 
 
 
 
 

Having same problems here.I think it has something to with windows 10 updates and or Microsoft Visual C++. appears I got 2 updates Dec 1 and Dec 4... restore points automatically created, right after I did Melodyne update, After testing today I found that the following plugins are crashing Platinum when loading existing projects that contain them: CA-2A, LP64 LP64 Multiband and Rapture...there may be more. If I try to load plugin I get runtime error. I'm wondering if I should try to do system restore prior to Dec 1st...

Don't have time for further testing until Thur, but that's worth a try. 
 
Becoming more curious as to why it seems to be -only- certain Cakewalk VSTs. Everything else in use (UAD, BFD, NI, TH3) is working fine. 
 
Please let us know if you try this and if it helped. 

I just tried system restore prior to visual c++ updates  and same behaviors as before. Before I updated sonar and again after... same behaviors. Thought I had a clue what caused this..it is funny that only certain vst's and one synth are affected.

Noting they are all Cakewalk VSTs though. I haven't noted any issues with any 3rd party VSTs (UAD, NI, Fxpansion, Nomad Factory, Melda, Overloud, etc.)
 
Working through a couple of projects due on Wed and also wondering why my CPU core balancing now appears to be all wacky. Or considerably "less evenly balanced" than before.