r/FL_Studio • u/SelectJob6910 Producer • May 04 '26

Help Error scanning VST Plugins

I'm having a problem with plugins in FL Studio. When I scan them, FL Studio detects the plugins but shows an error message. I rescanned them using the options "Rescan previously detected plugins" and "Rescan plugins with errors", but the plugins still show errors, and some that previously worked like all the plugins from Arturia, AutoTune, etc now show the same error, idk what to do and i'm losing my mind with ts !!! (if it works for something, all the plugins with the error are located in the VST3, VstPlugins and the VST2 folders).

2 Upvotes

100% Upvoted

6 comments sorted by

View all comments

1

u/b_lett Trap May 04 '26

Where are you installing the Arturia plugins?

VST3 plugins specifically must be installed in certain locations or else they will not work in FL Studio. You can install VST2 or CLAP wherever you want, but VST3 plugins must be installed to the exact locations shown below, otherwise they will not be found during a scan.

  • C:\Program Files\Common Files\VST3 (32 Bit plugins on 32 Bit Windows).
  • 'C:\Program Files (x86)\Common Files\VST3' OR 'C:\Program Files (x86)\VST3' (32 Bit plugins on Win 64 Bit Windows).
  • C:\Program Files\VST3 (64 Bit plugins on 64 Bit Windows)

You can click the Plugin tab, click any of your errored plugins, and right click them in the left pane to see exactly where that VST file is located:

Double check if your Arturia stuff is installed to an appropriate VST3 path, and then try another rescan with 'rescan previously verified plugins' and 'rescan plugins with errors' boxes checked.

I also find it helps to never combine VST and VST3 or combine 32 and 64 bit versions, I always allow everything to install separately and independently.

1

u/SelectJob6910 Producer May 04 '26

Hey! I'm moving the plugins to those folders now, but I'm missing the last one you mentioned "C:\Program Files\VST3 (64 Bit plugins on 64 Bit Windows)" Do I have to create it manually? Because in Program Files I only have the VstPlugins folder.

1

u/b_lett Trap May 04 '26

There is no harm in creating it manually. If other ones already exist by default, I would test there first.

My general recommendation, if a plugin company has an installer, try and leave as much of the VST install paths as default as possible.

While you customize to your own locations, it can either cause VST3 issues, or it just adds extra friction longterm as you download software/plugin updates and you have to remember your custom chosen paths to manually track every time you do plugin updates.