CA-2A + LP 64 EQ causing Runtime errors

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?

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.

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.

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,

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!
 

Gerry,
 
So glad this worked for you, too. I was able to do a full day's work yesterday after going through the workaround. No reoccurrences of the error message, LP-64 worked fine, and so did everything else. Fingers crossed!
 
Bob

I just ignore it. It first occured after the latest W10 install.
Took me 3 days to figure out that you just can ignore the message.


X3 / Octapad. 
Intel I5 notebook.

jackson white
Not sure I agree. I tried ignoring these and get; 
 
"SONARPLT.exe stopped working"
 
every single time I tried to insert one. Not that I needed them, but there is definitely something wrong. 
 

It looks like there are a few variations of this same runtime error problem. Most of us can simply not click on ok when the runtime error window comes up. If you click on ok then it closes and then it closes Platinum.
 
I've done a lot of experimenting with this and I've had some more severe times when it seemed I couldn't' do anything except start over with a new image file. I still don't understand why I'm all of a sudden having this problem and I haven't ever updated to 2016.11. Thanks for keeping us updated.

jackson white
@gmp
 
Can you please confirm that you did not update to 2016.11 and that you are seeing these problems with 2016.10? 
 
It's quite possible that (at least in my case) the issue was just coincidental with the update to 2016.11. I rolled back to 2016.10 which did NOT fix the problem, but wondering if something core had been corrupted that was not covered in the rollback. 
 
If you are seeing the problems on 2016.10 (which was rock solid for me) then we might to look a bit deeper into any Win10 updates.  
 
 

 
I did not update to 2016.11 after seeing several complaints I was leery. I used 2016.10 for about a week and it had a few problems for me, but not the runtime problem, so I reverted back to my 10/23 image of 2016.09 on 11/17. The last Win updates I did were on 10/23. Then last week this crazy runtime error problem cropped up.
 
 
Since last week 2016.09 hasn't worked well for me until I started over by reverting again back to the 10/23 image and then did all the Win updates. Now at least things are manageable, all I have to do is ignore the runtime error screen, being careful not to hit ok and then no other projects cause a problem. All the plugins work fine.
 
 
The most baffling thing is if I disconnect from the internet, then revert back to my 10/23 image, I don't get the runtime errors at all. So for me this is all triggered by something with the internet, I assume either something with Cakewalk or MS, like an internet database. My guess is MS is doing something that's causing my unique problem, and possibly everyone's problem with these runtime errors.
 
My post below has my detailed account of this:
 
http://forum.cakewalk.com...VST-scan-m3523271.aspx

I haven't had a Win10 update since Nov. 18th and I'm not seeing any of these crashes on my daw or laptop.
 

Having the same crash issue as above. Using safe mode pinpointed the LP-64 as causing the crashes, runtime error etc.
Just upgraded to the latest Sonar Platinum with lifetime updates, LP-64 still makes it crash.
 
Latest Windows 10 build