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 agree. So I copied everything to 2 places. I leave the Stienberg folder alone. But Cakewalk because I have a few versions like you say, there was I think 3 vst folders. I put everything in one and deleted the others. Seems to all work just fine now. 

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.

Like SF_Green said, don't mess with your VST3 folders.
 
As far as the VST2s, it's fine to have many folders, as long as you include them all in Sonar VST locations.  The only thing I would advise is do keep your 32 and 64 bit plugins in separate folders.
 
The problem is your duplicate plugins.  You will need to go through and delete the duplicates (Maybe sort by date, and delete the oldest dated duplicates).

One thing I did to try to keep all my plugins organized (and easier to access) was just create root level directories for both 32 and 64 plugs.  Makes keeping track of things so much easier (plus it's easier to add when customizing your installs instead of searching around for folders 4 levels deep):
 
C:\VSTx32
C:\VSTx64
 
 

Thanks, Guys,
for now, the VST scanner is ok but I think that as soon as I reinstall RX6, I'm gonna have issues again. Let's see...
Atsuko

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).
 

Thanks, Scook! I was tired of searching a way to resolve the issues since the same plugins always scanned flawlessly. I don't know what happened, I think the errors started after installing the Waves' Brauer Motion but after uninstalling all Waves plugins, the errors were transferred to the iZotope plugins... 
Well, I'm now reinstalling all the Waves plugins I have then I'll try your suggestion disabling the 2 Rescan.

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.

scook
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.

I understand. Let's see what happens.
Thanks, Scook.