At my wit's end and about to quit Reaper

Maybe some "Microsoft Visual C++" libraries (.DLLs) are missing?? (So then plugins which require those libraries do not work correctly and therefore cannot be scanned/used). (Also other, like C++ 2013 and C++ 2015 libraries may be required).

Never move the VST3 plugin folders. The VST plugins can go where you like. If say you want a single plugin folder you can do that for the standard VSTs. I call those standard but VST3 will replace VST/I Plugins over time. The most newly developed plugins or even starting to come through only as VST3. Check you've had all the Windows updates - but it sounds like you've done all that stuff. check you haven't got anything written in the Reaper plugins search box as that will limit you to whatever words you typed in.

Just to echo ... do NOT move your VST3 plugins, they are installed into a "standard" folder. On windows c:\program files\common files\vst3 or c:\program files (x86)\common files\vst3 Ideally, set up a folder structure of your own (I have C:\VST\) and in that have subfolders \64-bit\ and \32-bit\. Then if I simply have a .dll to drop in, I just dump it in the 64 or 32 bit folder. If the VST2 has an installer, then I let it install into its data into its "program folder" but direct the VST2 .dlls to go to the appropriate folders, ie 64-bit or 32-bit. This way I can keep track of my VST's easily, and also have a short search path in REAPER. Finally, keep a copy of your installers and registration codes on a memory stick or burn to a CD in case everything goes AWOL. HTH (just a little bit?) dB

Well, in case anyone else ever needs this thread. My solution appears to be working so far. I spent hours scrubbing my computer of every single Reaper file and every single file that had anything to do with a plugin. Documents, .dmg's, .dll's, .vst's, you name it. Gone. Now I am slowly reinstalling everything and so far, so good. Thank you to everyone who took time out of their day to help me with my issue and good luck!

Reaper must be blacklisting your plugins for some reason. Are you using a mix of x86 and x64 plugins? Is there anything in common among the missing plugins? Do they rely on iLok or other licensing software? When a plugin disappears in Reaper how does its entry in reaper-vstplugins.ini or reaper-vstplugins64.ini change? If you delete the entry, does the plugin appear again? Have you checked the Windows event viewer for faults related to the missing .dll's?

It's a PITA that VSTs that don't work because some component (such as the C++ library) is missing don't show any error message when Reaper does a "scan" and they don't work. I am not sure if Reaper can do anything about this. Anyway it's highly recommended to decently install all plugins on a new PC and not just move the (or in fact some of) the necessary files. This should take care of missing files and licensing issues, that also might occur and make such plugins unusable and/or unfindable. -Michael

To the OP ... I have had to add various C++ Redistributables over time to make some VST's work (and be recognised by Reaper). To date I have all the libs from 2005 to the present!!! That's 15 years worth of C++ libs! It's often not possible to work out which lib is required other than starting at the beginning and installing them one by one until the VST works! Glad you are getting back to some form of normal. Well done for persevering. The Forum is always keen to help, that's Reaper for you! dB

Portable Install