Today I had one of the strangest Sonar experiences ever. I worked on a couple of songs today and then opened a 3rd song and got an error I’ve never seen 
 
Microsoft Visual C++ runtime error
SONARPLT.exe
R6025 - pure virtual function call
 
I was using 64 bit Platinum 2016.09 and every single CWP file I tried to open crashed in the same way. I then decided I had a serious OS or Platinum corruption and I reverted my C drive to an earlier image that I saved on 11/8. To my surprise I still had the problem. I shut down the computer and rebooted my AVB Ultralite audio box and rebooted the computer.
 
I then opened the default normal template and that opened fine. I then opened a song in the safe mode and after much testing I found that CA-2A and LP-64 EQ were both causing all the Runtime errors. Either one would cause the error. So I used Control Panel to uninstall CA-2A and reinstalled it from Command Center. Now only the LP 64 EQ would cause the crash.
 
I tried the do the same uninstall and reinstall  with LP-64 EQ. From Command Center I found out that it was part of the Engineering FX Suite, so I went to Control Panel and uninstalled it and reinstalled it using Command Center. For some reason it won’t install. I’ve tried to install it 3x from Command Center and it won’t install and so every CWP I open I get an error message saying it can’t find that plugin. In my templates for many months I’ve had Drum Bus Master which is an FX chain that I have in the FX rack of my Drum bus in the Bus pane. Drum Bus Master has LP-64 EQ as one the the FX in the chain, so this is why each song is looking for that plugin.
 
So here’s what’s baffling. I would think that if CA-2A and LP-64 EQ got corrupted in some way that reverting my C drive to an image from 11/8 when everything worked fine would solve a problem like this – it didn’t. Cakewalk Content is on my D dive, but I find no references to CA-2A and LP-64 EQ there.
 
Could it be that it’s some kind of internet connection to Cakewalk and that these 2 plugins were no longer getting the registration green light from Cakewalk to work? Like some kind of copy protection thing to prevent people pirating these plugins. And then there’s this lingering problem of why can’t I install FX Engineering Suite anymore. The other plugins in that suite are not showing up either – LP-64 Multiband, etc. Anyone have any clue about this puzzling problem?

@gmp
 
Please see my post on the exact same issue. "CA2A crashing every project + VST Scan Issues".
 
I've tried reinstalling the CA2A and Engineering FX via CCC as well as rolling back. Neither helped.
Have not done a System Restore yet, but per your post, this did not appear to solve the problem. 
 
It's a bit more than troubling. It's a showstopper. 
 
I'm continuing to troubleshoot, will post any progress on my thread. 
 
 
 
 

What do you mean by the Engineering FX Suite is not installing? Does the installer doesn't run or can't you find the plugin files it should have installed?
 
The LP-EQ is a file "LPEQ_64.vst3" and will be installed in the VST3 folder "C:\Program Files\Common Files\VST3" (or a subfolder of it). This folder must be listed as a VST folder in the Sonar preferences and you need to rescan VST folders after installation for Sonar to find it. Are LP EQ and LP MB listed in the VST3 effects section of Plugin Manager?
 
An Internet problem is unlikely, LP-EQ should not require any registration different from Sonar Platinum. Also, missing registration should not cause a crash, just the plugin would refuse to load. Some problem in the Windows Registry is more likely.

ralf
What do you mean by the Engineering FX Suite is not installing? Does the installer doesn't run or can't you find the plugin files it should have installed?
 
The LP-EQ is a file "LPEQ_64.vst3" and will be installed in the VST3 folder "C:\Program Files\Common Files\VST3" (or a subfolder of it). This folder must be listed as a VST folder in the Sonar preferences and you need to rescan VST folders after installation for Sonar to find it. Are LP EQ and LP MB listed in the VST3 effects section of Plugin Manager?
 
An Internet problem is unlikely, LP-EQ should not require any registration different from Sonar Platinum. Also, missing registration should not cause a crash, just the plugin would refuse to load. Some problem in the Windows Registry is more likely.

Engineering FX Suite did install as far as the install windows and such. Yet it didn't show up in plugin manager and I think you showed me why. I needed to run a VST scan. LP EQ and LP MB were showing up in plugin manager.
 
I was using 2016.09  I intended to revert back to my 2016.09 image and mistakenly reverted back to the 2016.10 image and I still had the crashing with CA-2A and LP-64 EQ. Uninstalling and reinstalling CA-2A fixed it.
 
Last night I discovered what I did and first saved an image of this problem and then this time reverted to 2016.09. Well thankfully all the CA-2A and LP-64 EQ problems are gone without any reinstalling or uninstalling.

False alarm - I now have the same problem with 2016.09 - a newly restored image file. Last night it worked fine with loading 1 song, but today it crashes. I uninstalled and reinstalled CA-2A and uninstalled Engineering FX suite. Now I have no audio, I have to shut down and reboot my AVB Ultralite. I'm still wondering if something frothe internet is doing this. It makes no sense at all. Or is Command Center doing something strange.
 
CA-2A is not showing up after a few reboots, so I did a VST scan both check boxes and it's stuck on CA-2A. Close and reopen Plat and this time hit reset and then scan, Stuck on Rapture. Since I hit reset now it can’t find crucial plugins like Ivory, etc.
 
I’ll revert back to the 2016.09 image and this time disconnect the internet and won’t open Command Center. Cakewalk needs to give us some kind of explanation. This is really weird.

I did seem to determine the problem with mine is associated with the ASIO driver which is Roland Octa-Capture. However I have been using this driver and version for almost a year, which means it's brought on by cakewalk. You might want to check this if you haven't already.

robert@gmwmusic.com
I did seem to determine the problem with mine is associated with the ASIO driver which is Roland Octa-Capture. However I have been using this driver and version for almost a year, which means it's brought on by cakewalk. You might want to check this if you haven't already.

I have an AVB ULtralite for my audio not a Roland, so I'm not following what you're suggesting. Please explain
 
thanks,

Want I meant is checking your USB interface driver. ASIO is the driver you would use with todays USB 3.0. This appears to be the root of my problem which by the way I still haven't resolved.

I'm having exactly the same problem on Sonar Platinum running on Windows 10. Reinstalling the latest C+++ redistributables and reinstalling Sonar did not help. I did find a workaround that enables me to use Sonar (including using LP-64) until such time as a real fix appears. 
a. Start Sonar
b. Open a project that has LP-64 installed (I've installed it on an aux bus--I don't know if it would work if it was on a channel bus).
c. When the project loads you should see the R6025 error—just ignore it (if you click on OK, sonar will crash and you’ll have to reboot to unload it). For me, even with the error window open, Sonar still works
d. Delete LP-64 and save the project (I think you have to save it, maybe not)
e. Exit Sonar via File/Exit
i. After Sonar closes, the error message box should close on its own. If not, select OK to close it manually.
f. Restart Sonar: It will now work, including being able to loading projects with LP-64 (until the next reboot and then you have to go through this again)


This has worked for me so far. I hope it works for others. And of course I hope this gets fixed soon!
 

boblev
I'm having exactly the same problem on Sonar Platinum running on Windows 10. Reinstalling the latest C+++ redistributables and reinstalling Sonar did not help. I did find a workaround that enables me to use Sonar (including using LP-64) until such time as a real fix appears. 
a. Start Sonar
b. Open a project that has LP-64 installed (I've installed it on an aux bus--I don't know if it would work if it was on a channel bus).
c. When the project loads you should see the R6025 error—just ignore it (if you click on OK, sonar will crash and you’ll have to reboot to unload it). For me, even with the error window open, Sonar still works
d. Delete LP-64 and save the project (I think you have to save it, maybe not)
e. Exit Sonar via File/Exit
i. After Sonar closes, the error message box should close on its own. If not, select OK to close it manually.
f. Restart Sonar: It will now work, including being able to loading projects with LP-64 (until the next reboot and then you have to go through this again)


This has worked for me so far. I hope it works for others. And of course I hope this gets fixed soon!
 

Brilliant solution. Man it’s good you think out of the box. I had no idea I could leave that error screen open and Plat wouldn't’ close. I did just what you said and deleted the LP-64 FX and saved it and now I don’t’ get that error when I reboot and open that file and get no error when I open CWP files after that.. You may want to check out my recent post that was clearly computer hell.
 
Well since then, I went ahead and reverted again to my 10/23 image and this time before opening Plat I got all the latest Win updates and now when I open a CWP I get the runtime error for the 1st song, I was letting it close. Then fortunately I was able to open a 2nd CWP and it never happens again. Only on the very 1st file that I open from a fresh boot. So that’s quite an improvement. Yet your new method is even better.
 
My usual way of working is whenever I have a new Plat version to install I 1st do all the Win updates, and then install the new version. I don’t’ like the auto updates, because I want to have a chance to try out the new version without throwing another variable of constantly changing OS updates.