If you have more than one Waveshell then perhaps. Even though the later versions supercede it might be worth checking.
 
I only install VST3 to my directory (C:\Program Files (x86)\Common Files\VST3)
 
VST 2.4 externally in it's on directory called C:\VST.
 
Another thing only 64-bit VST3 gets installed and Sonar is set to use VST3 where possible. I could be barking up the wrong tree but I hope it give some insight.
 

I had a similar problem. It's a lot of steps but it worked.
 
http://forum.cakewalk.com...m-Solved-m3626052.aspx

I would advise against adding all the 32bit paths to 64bit SONAR. You would be better off reducing the number of 32bit plug-ins being scanned. Most of them likely have a 64bit version later in the scan path which should be used in 64bit SONAR. You would be better off, copying the few 32bit plug-ins that have no 64bit option to a separate folder and remove the rest of the 32bit paths from the 64bit scan path.
 
Redundant scan paths should be avoided ALWAYS. This is a bad idea:

Studio Vheissu
C:\Program Files (x86)\Cakewalk\vstplugins
C:\Program Files (x86)\Cakewalk\vstplugins\cakewalk sound center

The scanner will go into "cakewalk sound center" folder because the parent folder is already in the scan path. Having both in the scan path causes the scanner to look in "cakewalk sound center" twice. In the past scanning a plug-in multiple times has been know to cause problems.
 
Are there any 32bit only VST3 plug-ins? If not, this

Studio Vheissu
C:\Program Files (x86)\Common Files\VST3

should not be in the 64bit SONAR scan path.
 

Btw I meant program files without the parantheses. One 32-bit directory and one 64-bit. Might be a couple more which are only cakewalk instruments and effects.

Sound Forge is a 32 bit application so it needs the 32 bit VSTs but as Scook said you shouldn't have all those redundant scan paths in Sonar. For all of Waves you only need the 64 bit VST 3 versions scanned. Obviously you'll have some other 64 VST2 plugins but with some good housekeeping they can all be placed in one folder.

Here's what worked for me:
 
From http://forum.cakewalk.com/Waves-nightmare-SOLVED-m3587657.aspx
See post #21
 
- I left my activations alone - they're on a USB stick
 
- uninstall everything via Waves Central
- delete everything (left) in C:\Program Files (x86)\Waves
- delete C:\Users\John\AppData\Roaming\Waves Audio
- reinstall everything via Waves Central (not the "easy" one)
- copy "WaveShell-VST 9.6_x64.dll" (or whatever version you have) from C:\Program Files\VstPlugIns to my location that I like. (C:\vst plugins\64 bit\Waves)
- open SONAR and run a vst reset

Before you do all that, try a clean rescan. Go to Preferences -> File -> VST Settings, click the "Reset" button followed by the "Scan" button. It may not solve your problem, but it's an easy step.
 
Do you have this issue when you attempt to insert a plugin into a new project, or only when you're opening previous projects that have Waves plugins in them?
 
FWIW, Waves plugins are working fine here. I have had them fail on three previous occasions (which is why I don't buy Waves products anymore), but each time it was a Waves licensing issue, not a SONAR problem.

I copied the c:\program files\common files\vst3\WaveShell-VST3 9.91_x64.vst3 to my cakewalk vst folder and re-scanned when I was having that problem. Have you tried?
 

Well after a frustrating week or so, it seems like some sort of miracle occurred and available instrument and FX plugins are playing nice with Sonar Platinum. Like Mike V said above a couple posts a little housekeeping can't hurt and I managed to get my list of vst paths down to three:
C:\Program Files (x86)\vstplugins
C:\Program Files\Common Files\VST3
C:\Program Files\vstplugins
 
For those of you with Native Instrument software, they have a neat little program used to put all of their 32 and 64 bit vsts in any folder you want. So with all the flotsam and jetsam left behind by the Department of Redundancy Department (old Firesign Theater fans may remember this little joke), it seems that every thing is running smoothly again. Waves AAS, NI, Izotope and the rest are all making nice-nice with Cakewalk. A huge thanks to those who took the time to try to help.

Probably should put a courtesy (Solved) in your thread title.