Pluging Folder Management!

Whenever presented a choice, I always have placed plugins in either C:\Program Files\Cakewalk\VST Plugins for x64 plugs, or C:\Program Files (x86)\Cakewalk\VST Plugins for x32 plugs.
 
All VST3 plugins go to C:\Common Files\VST3, and within Common Files there are also a small number of VST2 plugins in the VST2 folder.
 
I place collections of 3rd-party plugins into one of the 2 Cakewalk\VST Plugins folders, in a sub-folder for that collections, so within both of the Cakewalk\VST Plugins folders there would be a folder for Arturia, and one for Native Instruments, etc....
 
Anyways, the above is MY approach, and it works for me.  Just make sure the ones you want present for Sonar are present in the search paths in Sonar for VST plugins.
 
One more note, I happen to also have JBridge, for a small number of 32-bit plugins that just do not exist in a 64-bit format, that I want to continue to use.  THOSE plugins are within the 32-bit Cakewalk\VST Plugins folder, in a sub-folder called Bridged, so ONLY that set of 32-bit plugins has been added to my 64-bit Sonar's VST plugin search paths, so that I am not accidentally pulling in ANY random 32-bit plugin without knowing I am doing it.  Any additional 32-bit plugins that I want to try using get loaded into that Bridged sub-folder and removed if I find them problematic in 64-bit Sonar.  
 
By using ONLY 64-bit plugins whenever possible, and ONLY a small number of tested and contained in a separate folder of 32-bit bridged plugins, I really NEVER see any Sonar problems caused by plugins (before completely switching over to 64-bit plugins some years back, there were lots of problems from 32-bit plugins, specially the freeware ones.  Now - no problems for me - if any were to show up, from some new 32-bit plugin I was trying out - it would simply get removed from the Bridged sub-folder and that would be that.
 
Bob Bone