I had to do about the same. Best of luck!
 
Peace
 

bits2tubes
This is something I've wondered about for a while.  Every software developer seems to have a different idea of where their plugins should go.  This has got me confused more than once. I which there was a standard location for plugins to go and all developers installed then there. That would end a lot of headaches for me. 

 
 For me it's the opposite.  Some developers still think plugins should go Steinberg\VST Plugins.
 
 Waves installers are a PITA. I've had where I accidentally removed all of them except for the most recent purchase, I personally do not like the multiple VST installers.  Sometimes you end up with a lot of demos.  VST installation is something I pay more attention to.
 
 

Thanks so far for the responses. I've contacted Waves support.
Thanks TheSteven - I'm not using a dongle, my licenses are all on the PC.
I have often thought of rationalising the vst paths, but you know how it is .. it wrecks the current projects so you need to find all the plugs again, etc.  My scan path at the moment must have a dozen or so folders in it. But as you say - it may be inherent to the recent Waveshell 9.91 itself.
 
Cheers
Jerry

You can move your plugins any time you want. It won't break old projects - as long as they can still find the plugins.

For Waves, SONAR just as to know where the waves he'll dll is - and this points other all the actual plugins. You can copy the waveshell dll anywhere you want to (from c:\program files (x86)\vst plugins) and it still works fine.

I have all my plugins in one place - c:\vst plugins\64 bit - in various sub folders. Then sonar only has to scan here, the vst3 folder and there's another one for "c:\program files\cakewalk\shared plugins" (or something like that)

jbraner
... You can copy the waveshell dll anywhere you want to (from c:\program files (x86)\vst plugins) and it still works fine...

Actually, you can't.  But you can move  the waveshell dll anywhere you want.  Copying the file will only confuse Waves, even if you tell Sonar the new path.

I still have one in the original location, but SONAR doesn't scan there - then I have a copy in my preferred location - and it works fine :-)

jbraner
I still have one in the original location, but SONAR doesn't scan there - then I have a copy in my preferred location - and it works fine :-)

I do this also without issues. You just put the path to it in the DAW your using.

Mosvalve

jbraner
I still have one in the original location, but SONAR doesn't scan there - then I have a copy in my preferred location - and it works fine :-)

I do this also without issues. You just put the path to it in the DAW your using.

My mistake then, apologies.  I could have sworn I tried it and got grief (Must have been a different VST).  It's especially surprising knowing how "quirky" Waves can be with some installs.
 

Ok, I'm fixed now. I went back through the process of deleting the cache and all the waveshells (again) and reinstalling and all the plugins are now picked up. 
 
jdf

Mosvalve

jbraner
I still have one in the original location, but SONAR doesn't scan there - then I have a copy in my preferred location - and it works fine :-)

I do this also without issues. You just put the path to it in the DAW your using.

The problem comes when they change the version of waveshell. Then you have to be sure that SONAR only sees the one version, and you have to rescan all your VSts.
(listen to me - a few weeks ago, I didn't know how any of this worked, but I got burnt when upgrading some Waves stuff. Now I know how it works, and it's not *that* bad...)