How to rescan my plug-ins?

If the plug-in doesn't appear in the Logic Pro Plug-in manager, make sure to try to reset all the Audio Units as explained below:

Please note that resetting Audio Units in Logic Pro also resets them for MainStage.

• Choose Logic Pro > Preferences > Plug-In Manager

• Click on “Full Audio Unit Reset”
• Close Logic Pro, then reopen it. Logic Pro rescans all installed Audio Units plug-ins
• You can now check if your plug-in is available both in the Logic Pro Plug-in manager and when trying to insert it on a track

If the plug-in appears in the Plug-in Manager but still isn't available in Logic Pro or MainStage, make sure to try to rescan the faulty plug-in itself:

• In the plug-in Manager, locate the plug-in you want to check. To filter by manufacturer, click manufacturer's name in the left column
• “failed validation” appears in the Compatibility column for the plugin, select the plug-in in the list, then click Reset & Rescan Selection

Important Note:

If using a previous Logic Pro version (Below 10.7), you may have to manually delete the following files to reset the Audio Unit cache and force a plug-in rescan:

• First, please close Logic Pro &/or Mainstage
• In Finder, click on Go then Go to Folder in the menu bar at the top
• Copy-paste the following path then click Go : ~/Library/Caches
• Delete any folder named AudioUnitCache
• Delete any file named com.apple.audiounits.cache
• Reboot the system (mandatory) and then open Logic Pro once again

The rescan process may take several minutes depending on the amount of AU components installed.

When opening Cubase, all the VST plug-ins installed into it’s “Default VST plug-in paths” should be automatically scanned and available.

installed in a Custom folder, you’ll have to first add that in the VST Plugin Manager for them to be scanned.

To do so:

• Navigate to the Studio menu and click VST Plug-in Manager

• Click on the cog icon located on the bottom left of the window, and then click the + icon

• Select the folder where the VST plug-in(s) are located, and click Select Folder.
• Click the Refresh icon located next to the Search bar to begin scanning

Depending on the amount of plug-ins installed, it may take more or less time for the plug-ins to be scanned.

Important Note:

In case some plug-ins may have been blacklisted at some point, make sure to check the “Blocklist” tab:.

If you find any plug-in here you’d like to use make sure to select the plugin and then to click on “Reactivate”

If you have difficulties to have your plug-ins detected in Ableton LIVE, please refer to the steps below:

On Windows:

• Launch Ableton LIVE with a right click > Run as administrator
• Open the 'Preferences' menu > 'Plug-Ins' tab and click on ‘Rescan’.
• If the plugin is still not detected and in case you would have located your VSTs in a separate Custom folder:
• Make sure to enable the ‘Use VST2 / VST3 Custom folders’ options and to select the appropriate VST folder to rescan.

In case any problem persists, you can try the following steps:

• Reach your VST folder through your File Browser and move it out of its current location, reopen LIVE to force a rescan.
• Now, move the VST folder back in place and open LIVE once again to have it rescan your folder

This may sometimes help resolving some detection issues.

On Mac OS:

• Launch Ableton LIVE
• Open the 'Preferences' menu > 'Plug-Ins' tab
• In the 'Plug-Ins Sources' section make sure that the 'Use VST PlugIn System Folder' is set to 'On'
• If the button is already set to 'On', please, click on Rescan
• If the plugin is still not detected and in case you would have located your VSTs in a separate Custom folder:
• Make sure to enable the ‘Use VST2 / VST3 Custom folders’ options and to select the appropriate VST folder to rescan.

• If the plug-in still do not appear as a VST, make sure to also try to enable the Audio Units to see if the Audio unit version is from there available in the ‘Plug-ins browser’ > Audio Units section.

This may sometimes help resolving some detection issues.

• Reach your VST folder through your File Browser and move it out of its current location, reopen LIVE to force a rescan.
• Now, move the VST folder back in place and open LIVE once again to have it rescan your folder

This may sometimes help resolving some detection issues.

The newly installed AAX plug-ins should be normally automatically scanned and accessible through Pro Tools if properly installed.

If for some reasons, you can find your plug-ins as expected, make sure to delete the Pro Tools preferences files which will force a plug-in rescan on next opening. To do that, please follow the steps below:

On Mac OS:

• First, close Pro Tools and reach the MAC OS Finder top bar
• Then, click Go and select Go to Folder

• Type in (or just copy/paste to avoid any mistake) the following path (with the tilde) before clicking on “GO”: ~/Library/Preferences/Avid

• Delete or Move the two following files you will find within the Pro Tools folder to another temporary location: InstalledAAXPlugins > Pro Tools Prefs

• Restart your computer and launch Pro Tools which should now rescan your plug-ins.

You should now be able to instantiate your plug-ins properly.

On Windows:

• Go to your file explorer.

The folder and related files may be hidden, so make sure to first go to “View” section and to select “Show Hidden Items” if not already done.

If more convenient, you can also directly copy/paste the path below in your file explorer address bar to reach it.

• You’ll find the needed file to delete in the following location:

C\:Users\*Username*\AppData\Roaming\Avid\Pro Tools

• From here, you can move or delete the following file:

InstalledAAXPlugIns

• Now, restart your computer and launch Pro Tools which should rescan your plug-ins

You should now be able to instantiate your plug-ins properly.

The default system folder should be automatically scanned on opening and your plug-ins properly detected.

If not working, make sure to refer to the steps below

These steps apply both to Windows and Mac OS:

• Open Reaper
• Go to Options > Preferences > VST
• Set your VST Plug-ins path which should be the following:

/Library/Audio/Plug-Ins/VST

/Library/Audio/Plug-Ins/VST3

• In some situations, you may have to add the following paths to your User Library:

/Users/Username/Library/Audio/Plug-Ins/VST

/Users/Username/Library/Audio/Plug-Ins/VST3

All of them should be separated with a “;” to avoid any troubles. “Username” has to be of course replaced in the path with your own Username.

• Now click "Re-scan" (In some situations, using the “Clear cache/rescan" option may be needed)
• Reboot Reaper and your Plug-ins will be re-scanned.
• Now check if your Plug-ins are correctly listed in your Plug-ins List

Audio Unit plug-ins (Mac Only) should be scanned by default on launch.

When opening Studio One, the default system VST folders should be automatically rescanned and your newly installed plug-ins detected.

In case they wouldn’t be detected, make sure to check your VST Plug-ins folders and to force a rescan.

To do that, please refer to the steps below:

On Mac OS:

• Open Studio One
• Go to Studio One > Preferences > Locations > VST Plug-Ins

• Make sure the following paths are present:

/Library/Audio/Plug-Ins/VST

/Library/Audio/Plug-Ins/VST3

If using any specific VST Custom folders, make sure to click on “Add” and to select the folder(s) containing your VST files.

• Once done, make sure “Scan at Startup” is checked.
• Then, click on “Reset Blocklist”
• Restart Studio One which should now find your plug-ins and let you enjoy using them.

On Win:

• Open Studio One
• Go to Studio One > Preferences > Locations > VST Plug-Ins

• Make sure the following paths are present:

C:\Program Files\Vstplugins

C:\Program Files\Common Files\vst3

If using any specific VST Custom folders, make sure to click on “Add” and to select the folder(s) containing your VST files..

• Once done, make sure “Scan at Startup” is checked.
• Then, click on “Reset Blocklist”
• Restart Studio One which should now find your plug-ins and let you enjoy using them.

Your plug-ins should be usually properly scanned and detected when opening Bitwig, however in case anything would be wrong, make sure to refer to the steps below and if needed to try to delete the VST cache file.

These steps apply both to Windows and Mac OS:

• Launch Bitwig Studio.
• Go to File > Settings > Locations and check if the following paths are displayed under VST plug-in folders (If needed, make sure to add them):

Windows:

C:\Program Files\Vstplugins

C:\Program Files\Common Files\vst3

Mac OS:

/Library/Audio/Plug-Ins/VST

/Library/Audio/Plug-Ins/VST3

E.G on Mac OS below:

• Make sure also to click if needed on the small arrows icon next to the defined VST locations to ensure these folders to be properly monitored and your plug-ins automatically detected.
• If needed, close Bitwig and open it once again for your plug-ins to be properly detected
• If any problem persists, you may have to possibly trash the Bitwig VST cache as explained below by deleting the mentioned Folder/File(s):

On MacOS:

/Users/”Username”/Library/Application Support/Bitwig/Bitwig Studio/ index (folder)

/Users/”Username”/Library/Caches/Bitwig/vst-metadata (file)

On Windows:

C:\Users\”Username”/AppData/Local/BitwigStudio/index (folder) C:

\Users\yourusername/AppData/Local/BitwigStudio/cache/vst-metadata

“Username” has to be of course replaced in the path with your own Username.

Once done, on next Bitwig opening, all the VSTs should be then rescanned and properly detected.

Because of the way FL Studio works, there might be a conflict between the different versions of the same plug-in.

Following the steps below should help you have the latest version opening and running as expected:

• In the FL Studio Plug-in manager, untick the "Combine VST and VST3 versions of the plugin".
• Tick both "Rescan plugins with errors" & "Rescan previously verified plugins".
• On the top of the view, tick "Verify plugins"
• Finally click on the "Find more plugins" button.

Once done it should be fully rescanning the plugins and properly dissociate the different VST versions, which should be then be working fine.