Hilda Signal Chain

Notes on plugins, drivers and setup, and the slow craft of the remix, written from one small room.

Renaming and Rescanning: How I Got 400 Missing Plugins Back After a Path Change

The session opened with the kind of dialog box nobody wants to see at 11pm: 412 plugins missing. Not “some plugins failed to load.” Four hundred and twelve. The Hilda Garman remix project I had been rebuilding from the archive, all those old electro stems and disco edit sessions, suddenly had more holes than a reel of tape left in the sun.

The cause was boring. I had reorganised my sample and plugin drives a few weeks earlier. Moved the VST2 folder, renamed the VST3 path, swept a bunch of old installers into an archive directory. The DAW had been pointed at the old locations via its plugin paths list, and somewhere along the way those paths had been rewritten or dropped entirely. Every plugin the host couldn’t find at its cached location went to the missing list. Four hundred and twelve of them.

First, confirm it’s a path problem and not a dead install

Before touching anything, I closed the session without saving and reopened a tiny test project. That matters. If a project is half-loaded with missing plugins, saving it can bake the missing state into the file. Open something disposable first.

Then I checked the obvious: were the .dll and .vst3 files actually still on disk? On Windows the VST3 folder lives at C:\Program Files\Common Files\VST3 by default, and VST2 files are wherever the vendor decided to drop them, which is usually the wild west. On macOS, VST3 is /Library/Audio/Plug-Ins/VST3 and the user-level equivalent is ~/Library/Audio/Plug-Ins/VST3. If the files are there, it’s a path or cache problem. If they’re gone, you reinstalled into a folder you then deleted, and no amount of rescanning fixes that.

Nine times out of ten it’s the cache.

Rebuild the plugin path list before you rescan

A rescan is only as good as the paths it’s scanning. So the order is: fix paths, then clear cache, then rescan. Not the other way round.

  • Ableton Live: Preferences, then Plug-Ins, then check “Use VST Plug-In Custom Folder” and set the path explicitly. Live also has a “Rescan” button and a “Rescan Plug-Ins” option. Hold Alt (Windows) or Option (macOS) when you click Rescan to force a full deep scan instead of the quick incremental one.
  • Reaper: Options, Preferences, Plug-ins, VST. Add the folder paths, then hit “Clear cache/re-scan.” Reaper is the most forgiving of the bunch here. If a plugin loads in Reaper but not your main DAW, that tells you the plugin is fine and the other host’s cache is stale.
  • FL Studio: Options, Manage Plugins, then the plugin search paths list. Hit “Find more plugins” and let it run. FL keeps its own database and can lag behind reality.
  • Cubase/Nuendo: Studio, VST Plugin Manager. Use “Update” after adding paths, not just “Rescan.”

I keep a plain text file listing every plugin folder path, updated whenever I install something. It sounds obsessive. It took ten minutes to build and it has saved me from this exact situation twice now.

The VST3 trap nobody warns you about

Here’s the annoying part. VST3 plugins, unlike VST2, are supposed to find themselves. The spec says the host scans the standard locations and you’re not meant to move things around. So when you rename a parent folder that contains VST3 files, some hosts just give up on the whole subtree until you clear the cache.

My VST2 folder had been renamed. That was the main culprit. Plugins like the free classics in my chain, Valhalla Supermassive for the ambient tails on the old disco edits, TDR Nova for surgical EQ, the TAL-Chorus-LX for that Juno-ish widening, all of them lived under a renamed parent. The host had cached the old path, couldn’t resolve it, and marked every single one missing. Renaming the folder back to its original name restored most of them instantly, before I even rescanned.

That’s the fastest fix I know: if you can remember the original folder name, put it back. Rename first, rescan second.

Clearing the cache: the real work

When renaming wasn’t enough, I cleared the cache properly. This deletes the host’s plugin database, so on next launch it rescans everything from scratch. It’s slow. It can take five to fifteen minutes depending on how many plugins you own. Do it once, not five times.

For Live, the plugin database lives in the user Library under Preferences. Trashing or renaming it forces a clean rebuild. Reaper stores its VST cache as a .ini file in the resource path. FL Studio keeps its database in the user data folder. Cubase rebuilds when you clear its plugin cache from the Plugin Manager. I won’t pretend I remember every exact filename. The point is that each host has a cache file, and deleting it is the nuclear option that actually works.

One thing to do before you nuke anything: take note of which plugins are 32-bit. If a plugin was a 32-bit VST2 and you’re on a 64-bit-only host now, it will show as missing no matter how many times you rescan. The archive had a couple of old 32-bit oddities that I had to bridge or retire. Don’t waste a rescan cycle chasing those.

When the rescan finds everything but the session still complains

Rescanning got all 412 back into the plugin list. The session opened with the same 412 still flagged as missing. This is the moment people give up and reinstall everything.

What happened: the session stores the plugin’s unique identifier, not just its name. If the plugin is reinstalled into a different path, or a different version number, the host can sometimes match by name and sometimes not. The fix is to use the host’s “replace missing plugin” or “substitute” feature. Most DAWs let you point a missing slot at the newly found plugin, and all settings transfer if the plugin version matches. It’s tedious at 412 items. It’s still faster than rebuilding the chains by hand.

Where it really hurt: my plugin chains on the Garman sessions aren’t one-off. The compression, EQ, saturation order matters. A compressor before or after the saturation changes the whole character of those old drums. Losing a slot in the middle of a chain doesn’t just break a plugin, it changes the sound. So I rebuilt one chain, saved it as a preset, and dragged it into the rest. That’s the only reason I finished before 2am.

Preventing the next 412

Three habits, none clever.

First, never rename or move a folder that contains installed plugins. Move the installer archives, not the installed files. Second, before any drive reorganisation, export your plugin path list from your host and save it somewhere outside the drive you’re touching. Third, do a test rescan after any move, before you open a real session.

And if you use multiple hosts, test in the most forgiving one first. Reaper will find almost anything. If Reaper can’t see it, the plugin is genuinely broken or missing on disk, not a path issue. That single test saves an hour of flailing.

The archive is loading clean again. Four hundred and twelve missing plugins, one renamed folder, and an evening I would rather have spent on the disco edits themselves. But the plumbing had to be fixed first. It always does.