
Usually I just delete anything that gets put into "C:\32VST" but I may want to use or test something (Sylenth1 32 bit is on my "to-do" list because 64 bit won't run on my updated Win10 ) There are a couple of VSTs that had problems with their VST3 versions, so I just move them to my ".\Common Files\VST3 HOLD\" folder. I also have the same setup for "C:\Program Files\Common Files\VST3\". So, I created a "C:\Program Files (x86)\VST Plugins HOLD\" folder and move them there, where they are not scanned. I avoid any 32bit plugins, and create "hold" folders for anything that gets put in (x86) folders.įor example, things get put into "C:\Program Files (x86)\VST Plugins\" folder, but I do not use them. This might give you some idea of what you can do to check out scanning problems or manage VSTs: "C:\Users\*user*\Documents\Image-Line\FL Studio\Presets\Plugin database\Installed"


Or as said, delete the "Installed" folder. You might try "unchecking" any paths you are able to uncheck, and recheck them as you go forward.
