The Cakewalk Vstplugins folder

Hi, guys, I'm having problems with the VST scan. It was working fine until it started to show an error with iZotope RX6 that was installed a long time ago with no problems; I uninstalled it, then, the scan stuck in Z3ta+2 so I uninstalled it too; then the issue came to Ozone 7; I uninstalled it... 
After several installing/uninstalling actions, I think I have a clue of the issue.  I realize I have 3 cakewalk's Vstplugins folder: C:\program files\Cakewalk\Vstplugins; C:\program files (x86)\Cakewalk\Vstplugins and M:\program files\Cakewalk\Vstplugins - this is the one I chose the DLLs to be installed but what I see is that I have a mess in my computer with lots of duplicated, triplicated DLLs in several folders. I also have in C:\program files\common files\VST2 and VST3 - C:\program files (x86)\common files\VST3.  It seems too much folders for me.
It seems to be related to the iZotope products.  I don't know what started the issue because I didn't install anything new from iZotope. I resolved the issue with Z3ta+2 simply removing its VST3 folder from the scan so that it only scans my M:\program files\Cakewalk\Vstplugins; it's ok for me.
At this very moment, I have uninstalled some iZotope plug-ins (RX 6; Neutron; RX Final mix) and the VST is fine even though the existence of the several folders I stated. I can live without the others but RX 6 is very important for me and I already have Neutron 2 and Ozone 8 that were scanned ok.
I'm affraid to reinstall RX 6 and all the process I'm passing come back again and I have lots of plug-ins I purchased this last year like a lot of Waves products and T-Racks 5.  I don't know if it's healthy to have so many Cakewalk's Vstplugins folder with duplicated DLLs. Do you guys have any ideas?
Thanks, Atsuko

I don't think you should have to add or mess with VST3 at all.  Part of the VST3 standard is that there is a common universal folder and you shouldn't have to add it and you shouldn't change it like we are used to doing with VST2.  Try deleting any VST3 folder references you have added and leave the default in the scan path and try that.  The default VST3 path is:  C:\Program Files\Common Files\VST3
That should be your only VST3 path.  If you really, really want to store your VST3 files elsewhere for some reason, I would suggest figuring out how to use junction points and create one in that folder to wherever you want to store your VST3 files.

If you are hanging on previously scanned plug-ins while NOT running a reset, chances are the scanner is setup to perform unnecessary work. Make sure both
Rescan Failed Plug-ins
and
Rescan Existing Plug-ins
are NOT enabled. Typically these two options are rarely needed and are disabled by default. Go to Preferences > File > VST Settings to confirm the state of these options. NOTE: the check boxes are disabled when automatic background scan is selected. In that case, change to another scan option, disable the options then restore the background scan setting.
 
Should the scanner fail during a reset, temporarily move the offending plug-ins or directories containing the plug-ins out of the scan path. Once the scan completes, put the plug-ins and directories back. The next scan should pick up the restored plug-ins without rescanning the existing plug-ins (assuming the Rescan options are turned off).
 

Sometimes the plug-in in the error message is not the cause of the problem. It may be plug-ins scanned sometime before the plug-in in the error message. Regardless, temporarily moving the plug-in mentioned in the error message usually solves the problem. Once a scan manages to complete without errors it should be possible to put the "bad" plug-ins back and scan one more time to get the "bad" plug-ins added. This technique only works if the rescan options are disabled. The rescan options are part of the problem.

Rather than delete the duplicate .dll and .vst3 files, I'd recommend simply renaming them to .dll.old / .vst3.old - that way it's much easier to recover if you make a mistake.
 
Sonar will ignore anything other than .dll or .vst3, so having .old at the end will mean Sonar will skip these files in the scan.
 
M.

in managing .vst files I haven't had a problem with Sonar but when I do occasionally jump over to Ableton Live I do have problems as apparently Live only looks at one or two folders for vst files. I like how SF_Green stated he just created two root level directories.  If I wanted to better organize my vst files into central locations can I just copy (or move) them over, or do I need to reinstall them to those new locations?