I hope the above helps me!!
I just bought Waves plugs and am having the issue with VST2/3 I think.  I am also getting told my licenses are not there and see the rescan popup.
 
Funny thing is, when I installed the plugins (I have uninstalled/reinstalled twice) they work when I first launch X3c.  When I close it and re-open none of the Waves plugs work.

Meno, it seems Waves may have misguided you. VST2 doesn't mean 32-bit, because you can have VST2 64-Bit plug-ins, I believe. Anyway, here is a procedure I posted that should take care of 99% of your Waves woes (it still won't renew your WUP, unfortunately, but hey...)
 
http://forum.cakewalk.com...Try-this-m2944841.aspx
 
This procedure starts fresh. Sonar's Plug-In Manager should be able to correctly separate VST2 from VST3, making that much easier. Or, you can simply "hide" VST2 plug-ins in Edit Preferences=>File=>VST Settings.

I wonder if they have an explanation of why this happens on some systems and not on others. I can't remember ever having any of these issues. Just the don't mix VST2/3 thing. I have my license on a USB stick, don't know if that makes any difference.

brconflict
Meno, it seems Waves may have misguided you. VST2 doesn't mean 32-bit, because you can have VST2 64-Bit plug-ins, I believe. Anyway, here is a procedure I posted that should take care of 99% of your Waves woes (it still won't renew your WUP, unfortunately, but hey...)
 
http://forum.cakewalk.com...Try-this-m2944841.aspx
 
This procedure starts fresh. Sonar's Plug-In Manager should be able to correctly separate VST2 from VST3, making that much easier. Or, you can simply "hide" VST2 plug-ins in Edit Preferences=>File=>VST Settings.

brconflict
I don't think I said anything about VST2 being 32bit only. All I did was describe how to correct for 32bit Version of X3. I use both Sonar 32bit and 64bit. I did follow the directions that X3 gives on how to hide/replace but this did not work and I kept getting the Waves CLSID errors.
 
Waves did good by me. The latest versions of my Waves plug-ins are all VST3. The conflict is having both versions showing in Sonar plug-in manager. I had VST2 plugs showing in Sonar's "VST Audio Effect Category" and the "VST3 Audio Effects Category". Having both is what was causing the issue. So the work around removes all of the VST2 plugins and keeps all the VST3 in the Plug-IN Manager.
 
I was going to take a look at your advice "procedure" but I can't get that link to work.

To fix my issue with Waves on a fresh install was to move the WaveShell 32-bit and 64-bit versions to different folders and make sure Sonar 32-bit only saw the 32-bit version of WaveShell.
This seemed to fix the issue in both X1 and X3 that I use often.

I've seen issues with 64-Bit Sonar, but never with 32-bit. So that's interesting you ran into the case of the CLSID errors there.
 
Meno, I just wanted to point that out since Waves may have told you to create "VST2" folders, instead of "32-bit" folders in Program Files(x86), which is the 32-bit Program Files folder, and your header for these steps said, X3 32-bit.. just wanted to make sure you and others who read your instructions knew those weren't hand-in-hand the same (VST2 and 32-bit). I'm sure you knew that, Waves should have known that, but possibly other may not. Sorry for not assuming you knew that.   And yes, Waves support helped me work this out early on as well, even at 9PM at night on a call-back! WUP costs money, but IMO it can be worth it in a pinch.
 
So, there were three separate issues overall that caused problems for me with Waves plug-ins:
1) Mixing 32-bit and 64-Bit plug-ins in Sonar X1/X2. Crashes (maybe fixed in X3). The procedure I have fixes this in particular.
2) Mixing VST2 and VST3 in X3. GUI Glitches and possible crashes (avoid mixing these Waves plugins).
3) CLSID issues from sub-versions (i.e. 9r7 to 9r13, etc.) in Waves plug-ins (seems to be fixed in X3).
 
Hope this helps!!