TheSteven

Kamikaze

TheSteven
Sorry I was editing my previous reply and you had already answered.
In thinking it over I doubt if the problem is the location of the VSTs.
Yes they should fix the problem..

Thta's a shame, you had me considering changing it once and get a chuck of time for a tidy up/SSD

Below is my current approach in setting up my VST2 plugins and it's been working really well for me.
It optimizes scanning, eliminates most dupes and it works across multiple DAWS.
All my VST2s are easy to locate and backup.
Plus I never have to run Sonar/Cakewalk** in Admin mode - except for when registering a new Sonar installation.
**or any of my DAWs

C:.
├───Audio
│   ├───VST32
│   │   ├───32Main
│   │   └───Has 64 bit version
│   └───VST64
│       ├───64Main
│       └───Has VST3 version

For Cakewalk my scan path is:
C:\Audio\VST32\32Main
C:\Audio\VST64\64Main
C:\Program Files\Common Files\VST3

For other DAWS just select the appropriate paths.
 
Whenever I get a new plugin I always run it first in SaviHost or ImageLine's MiniHost before I run a VST scan.
That way I can handle any registration or activation issues upfront and don't risk the plugin getting marked as bad or get corrupted info in the VST scan.
 
Hope you find the info useful.
 
...Steven
 

Kamikaze
Thank again for the info
 
So if it has an installer, use the installer to set the paths, but if it desn't, just move them.