silvercn
Has anyone had problems loading / scanning in Waves plug ins to plug in manager?

Has anyone ever had a drunken one-night stand that ended badly? Pretty much everybody who uses Waves products has experienced installation, authorization or initialization problems at some time.
Sure, some will say "not me!", but their time will come. They'll swap out a network card and the Waves plugins will stop working. Or the plugins will just decide on their own that you don't have a license for them. Or they'll just vanish from your VST inventory. No other vendor has these issues with such regularity. It's a Waves specialty.
Locate a file called WaveShell-VST {version}.dll. This is what SONAR actually scans. It's a generic front-end for Waves plugins, which actually reside elsewhere. Make sure it's in the scan path(s) for Plugin Manager. If it is, and still not being picked up in the scan, make sure you're running SONAR as Administrator.
When the shell fails to initialize during the scan, it's intentionally obtuse about the reason for the failure. You won't get any kind of message, because Waves is so paranoid about copy-protection they don't want to provide any clues as to why the scan failed. After all, the top priority of any software vendor is to get paid. Delivering something useful for the money is secondary.