Cakewalk recognizes Waveshells x64, but isn't able to load it properly

Hey y'all -

I have a problem with my Waveshells 64x Plugin. Even tough the 32bit Version runs properly, Cakewalk fails to scan the 64x Plugin. While it scans the VST Plugins, it says: "The following plug-in caused an error during load: Waveshell1-VST 10.0_x64 - The failure point was reported as: Open".

I already contacted waves support and re-installed everything, but the Waveshells into the right folders - but still, it fails. They offered me a remote installation (even tough Cakewalk isn't a supported DAW by now), but for some job-related reasons (classified documents) I am not allowed to let someone remote control my computer and I think that this is maybe a Cakewalk error?

Thanks -
Julian.

I had the same issues with V9.
 
I run Win 10 Pro (64bit) on an AMD Six Core (3,5 GHz), 8 GB Ram

Done both yesterday, still the same error.

V9 is completely deinstalled.

It's not a Cakewalk issue. Each plugin provides its own installation/initialization routine, and the DAW's scanner merely invokes that code and hopes the plugin knows what to do. If that routine fails, all the scanner can do is report it and move on. At least Cakewalk no longer hangs when that happens, thanks to its recently-implemented sandbox mode.
 
Try starting Cakewalk as Administrator and then running the scanner manually (from the Preferences dialog). Make sure the "scan in sandbox" and "generate scan log" options are checked. The scan log may provide an additional clue for Waves support to figure out how their code is failing. You'll find the log file in %appdata%\Cakewalk\Logs, named "VSTScan.log".

Ok, thanks y'all I'll try that administrator thing.

I spent the better part of yesterday on the phone with a very nice young guitar playing Waves tech while he remotely tried to fix a problem that just cropped up for me...to no avail.  I had re-wupped all my plugins up to version 10 but since then had purchased two new ones.  First, Abbey Road Chambers...installed and activated no probs.  Second, Waves Tune...easy installed and activated with no probs...BUT...Sonar will not see it after scanning AND what's worse now Codex and Grand Rhapsody Piano no longer will load.  All other Waves instruments and plugs seem to be working fine. He did several uninstalls, re-installs and scans but no love.  But did discover some new clues...Codex and GRP will open standalone fine and they will also open as vst instruments with no problem in Studio One.  So...looks like a Sonar scanning issue.  When I look at the properties in Sonar's VST dialog those two plugins are not showing their correct id numbers...maybe that has something to do with it.  But I can't seen to force Sonar to change the wrong id numbers (1 and 0) to the correct ones (89 and 196).  If anyone here has any suggestions I'd be more than happy to hear them.
 
Will do as Bit suggests and take a look at the scan logs in Sonar.
 
Sorry Bit but there wasn't a Logs folder anywhere after %appdata% Cakewalk on my box...