How to Rescan Plugins in Popular DAWs

After installing a plugin, your DAW may need to refresh its plugin database before the new instrument or effect appears.

Quick guidance: Back up important projects, use legally obtained installers and valid licenses, confirm operating-system and DAW compatibility, and change only the folders or settings relevant to the affected plugin.

Before Rescanning

Close the DAW during installation, verify the correct plugin format and note any custom VST2 folder. Complete legitimate authorization and restart the computer if the installer requires it.

Ableton Live

Open Settings or Preferences and choose Plug-Ins. Enable the required VST2, VST3 or Audio Unit source. Set the correct VST2 custom folder, then use Rescan. If the plugin was previously rejected, consult Ableton’s supported full-rescan method for your Live version.

FL Studio

Open Options and Manage Plugins. Add the correct VST2 folder to Plugin search paths if needed, then select Find installed plugins. Review the scan report for errors or duplicates.

Cubase

Open Studio and VST Plug-in Manager. Cubase normally scans standard VST3 locations. Review the blocklist when a compatible plugin does not appear and follow the developer’s instructions before attempting reactivation.

Studio One

Open Options on Windows or Preferences on macOS, then Locations and VST Plug-ins. Add the correct custom VST2 folder, reset the blocklist only when appropriate, and restart or scan at startup.

Logic Pro

Logic uses Audio Units. Open Plug-in Manager, locate the developer or plugin, and check its validation status. Use Reset & Rescan Selection for the affected legitimate plugin when compatible.

Why Rescanning May Not Work

The wrong plugin format was installed.
The DAW is scanning a different folder.
The plugin architecture does not match the DAW.
The operating system or DAW version is unsupported.
Authorization or required components are missing.
The plugin is blocked after a failed validation.

Keep scans focused: Add only actual VST folders. Scanning entire drives or system folders can slow startup and generate false failures.

When to Reinstall

Reinstall only after checking format, path, compatibility and scan status. Use the publisher’s uninstaller and current installer. Protect existing projects before removing an older version.

Frequently Asked Questions

Do I need to rescan after every plugin update?

Many DAWs detect updates automatically, but a rescan can help when a new version is missing.

Why is my plugin on a blocklist?

It may have crashed, failed validation, lacked authorization or been incompatible during scanning.

Should I scan my sample-library folder?

No. DAW plugin scanners need plugin binaries, not large sample-content folders.

Related PluginXpert guides:

Need Remote VST Installation Support?

Send your Windows or Mac version, DAW, plugin name and error screenshot. PluginXpert will review the requirement and explain the available paid installation service.

Chat on WhatsApp

Explore more installation and troubleshooting guides or contact PluginXpert.