So every time I load a song I go through this constant ritual, "The following VST plugin CLSID could not be matched with an entry in the VST plug-in list" with every Waves plugin I own and the Softube Saturation Knob.  At the bottom of said window it offers a replacement location, I always select ok and yet the program never remembers the replacement selection.  I am running Sonar Platinum 2016.8 22.8.0.30.  Anyone know how to fix this?  or had the same issue & found a solution?
 
This has been a very frustrating issue to say the least.  I have searched online many times to solve the problem and nothing seems to quite match this problem.  Waves said it's a Sonar issue & of course no help at Cakewalk with a renewed membership only helpline. 
 
Thanks in advance!!
John
 
edit: added [Solved] to subject - sc

Same problem here with several waves plugs , I even went into the PIM and located the CLIDs that were mentioned for me and added them to my plug in profile, but didnt take either

Ham N Egz are you running the latest version of Sonar?  I'm wondering if in the last year Sonar fixed the issue since I am not running the latest version and not privy to bug fixes.

I think after choosing the other CSLID if you save the file it will remember.

bitman, one would think so but it does not remember.

Save the plugin's state as a preset, delete the plugin, save the project, re-insert the plugin, load the preset and re-save the project. It's a Waves thing.

dit_it_da_bidness
bitman, one would think so but it does not remember.

If you have the VST settings set to Scan at Startup (or maybe automatic) it's possible that it won't remember because it's going to re-scan every time you start, and so lose previous settings. 

Thanks for the reply bitflipper,  If I have no running Waves or Softube plugins in a song it still has the same issue regardless.

PhilW, thanks, I do no have an auto scan or the run in the background scan option on for plug-in scans, I only do that periodically when I add plugins or I am having issues.  
 

I, last night, open a "32 bit" project I have been trying to get to open without plugin drama in 64 bit sonar. Drama argely due to the unknowingly irresponsible use of dx effects in 32 bit land.
 
That aside, I was now greeted with a plethora of CLSID "choices" presumably due to the installation / uninstallation / reinstallation, reset and rescan things I had done of late. I thought of this thread and how, oh no, I'll guess n' choose the last of 3 possible CLSIDs for so 20 odd plugs and save but that won't fix it.
 
Well I finished my CLSID choosing chores and saved the file.
 
You know it open then with no errors? - Its a miracle!