With all due respect, Waves has the plug-ins I like, and use often. I know they're not the only game in town, but I'm prefer to be more pragmatic after an investment. Do I discontinue use of thousands invested in a plug-in chain of effects? It seems the best advice would be to get a definitive answer or maybe a few recommendations as to how to work around such an issue, vs. just dump them.
 
I've had my experience with Waves' cold nature, but they've improved quite a bit since 2 years ago. In fact, they helped me out with a licensing/discovery issue on a Sunday, and the tech-support agent knew exactly how to make the right things happen in Sonar to see the IR-1. That was way more handy than the support I've not had from EastWest for Quantum Spaces, who have yet to get back with me.
 
I've got some incredible non-Waves plug-ins that I also paid quite a bit of money for. They have yet to welcome 64-Bit DAWs without bridging (which I personally refuse to do, as bit-bridging seems to cripple the DAW for those plug-ins, IMO). 
 
Does anyone know a better way to work around such an issue?

Something to add here. I don't have this problem with Wavelab 7. Does that bring this issue back a little closer to Cakewalk? FWIW, I did also submit a ticket to Waves about this. 

I apologize, Brian. As soon as I wrote that post I had second thoughts about it. What if he's bought one of the expensive kitchen-sink bundles, I thought. And although I do feel a duty to warn others, your post should be warning enough. So as Deckert said to Rachel, "forget it, bad joke"...I'm sure Waves support will fix you right up.

brconflict
The only fix I found was to re-install the older release version, re-scan/reset all plug-ins, manually save each and every Waves plug-in settings for each project in my Sonar history, uninstall the old version of Waves, install the new, re-scan, replace each Waves plug-in in each Sonar .cwp. then, manually and individually re-import the previously saved settings for each Waves plug-in.

Yep! That was/is basically my work-around. :-( However, my old DAW is still around so I do not need to uninstall/reinstall ...

Waves did respond, and says there shouldn't be an issue, so I'm hoping maybe they know some hack I don't. heh.
 
Thanks, bitflipper. I know you aren't the apathetic type.
 
No response yet from Cakewalk Support, tho. Could be they're talking about it internally before responding. Unfortunately, I can't call in during the day, when they're most likely able to help.

Cakewalk Support hasn't responded yet to my email support request from Friday, but Waves said they'll work with me. They claim it should not have this issue, but I've not had one update that went without this problem. Perhaps they have the correct procedure/fix/workaround for this. I'll report back here what we find.

This was the response I received from Cakewalk support:
 
"SONAR is looking for your previously saved instances of the plugins with a specific plugin ID value. If installing the update from Waves forces SONAR to see your plugins as new ones, then unfortunately there is no way to have it automatically switch them over in your project."
 
Has nobody else called this issue in before me? I'm still planning to work with Waves on this, who claim there should be no issue.

brconflict
Did you ever solve this issue? I am hopeful you did as I have this same issue after Installing X3.
 
Thanks

This seems to have been fixed in X3c. Although I still recommend "hiding" 32-bit versions of the plug-ins, and not to mix VST2/VST3 versions in the same FX Chain or bin, but otherwise, I've not experienced the problems in X3c. For those waiting on DMG to fix theirs from crashing the VST SCanner. This should be fixed as of v1.22 of EQuality.

Still having issues with X3c where I keep getting the CLSID missmatch. I called Waves Tech Support today and here is how we fixed my issues.
 
X3 32bit...

1. Create a new folder in Program Files x86 called, Waves VST2.
2. Move, WaveShell-VST 9.2.dll from C:\Program Files (x86)\Cakewalk\Vstplugins to the new folder Waves VST2.
3. Add a new path for new folder "Waves VST2" to the X3 Plug-In Manager.
4. You will now only see Waves Plug-ins in VST3 Plugin Category in the Plug-IN Manager and none in VST Audio Effects.

 
I no longer get the CLSID error. We did this with 32bit and 64bit X3.