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

This indicates that this runtime error should not even be happening, because nothing really is wrong. Otherwise Sonar would not be working properly after that.

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.

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. 
 

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.

@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.  
 
 

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

@gmp
 
Thx for the feedback, much appreciated. I'm blocking out time this Thur to do more troubleshooting and will try both an earlier System Restore as well as rolling back to an older SONAR update. I've only tried 2016.10 because it had been rock solid for me. 
 
I still suspect it's a wider, more complicated issue. I plan to dig deeper into potential configuration changes as the result of a Win10 update but also thinking/hoping CW might have noted something as it is a fundamental system requirement. "Do you have the latest update?" seems to be a standard troubleshooting response.  
 
Will post any insight on the thread I started. 

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

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

My computers running windows 10 both agree the last update available for windows 10 was 11/9/2016