Fix Audacity Crashing on Startup Due to VST Plugins

When Audacity crashes immediately upon launch, an incompatible, corrupted, or architecture-mismatched third-party VST plugin is typically the culprit. This guide provides a direct troubleshooting workflow to bypass the crash, locate and reset Audacity's plugin cache files, remove the offending plugin without opening the software, and isolate problematic files to restore stable operation.

1. Clear Audacity’s Plugin Configuration Files

Audacity scans and registers plugins during startup. If a plugin causes a crash, Audacity will continue to fail on launch until its plugin cache is cleared.

1. Ensure Audacity is completely closed (check Task Manager or Activity Monitor to ensure no background processes remain).
2. Navigate to the Audacity configuration folder on your operating system:
   • Windows: Press Win + R, type %appdata%\audacity, and press Enter.
   • macOS: Open Finder, press Cmd + Shift + G, enter ~/Library/Application Support/audacity, and press Enter.
   • Linux: Navigate to ~/.audacity-data/ or ~/.config/audacity/.
3. Locate the following files:
   • pluginregistry.cfg
   • pluginsettings.cfg
4. Delete both files (or move them to your desktop as a backup).

Deleting these files resets Audacity's plugin database without deleting your saved audio projects or main preferences.

2. Temporarily Move Third-Party Plugins

To prevent Audacity from immediately rescanning the problematic plugin when restarted, you must move your plugins from their scan directories.

1. Navigate to the standard VST directories on your computer:
   • Windows VST3: C:\Program Files\Common Files\VST3
   • Windows VST2: C:\Program Files\VSTPlugins or C:\Program Files\Steinberg\VSTPlugins
   • macOS VST3: /Library/Audio/Plug-Ins/VST3
   • macOS VST2: /Library/Audio/Plug-Ins/VST
2. Create a temporary folder on your Desktop (e.g., "VST_Backup").
3. Move recently installed or suspected plugins out of the system VST folders and into your backup folder.

3. Launch Audacity in a Clean State

1. Open Audacity. With the configuration files reset and the problematic plugins moved, the application should launch normally.
2. If Audacity opens successfully, the crash was definitively caused by one of the moved plugins.

4. Isolate the Faulty Plugin

To identify the exact plugin causing the crash:

1. Close Audacity.
2. Move one plugin (or a small batch) back into its original VST folder.
3. Open Audacity.
4. Go to Effect > Plugin Manager (or Audio Setup > Rescan Plugins depending on your Audacity version).
5. Enable the plugin and verify that Audacity remains stable.
6. Repeat this process one plugin at a time until the crash recurs. The last plugin added is the incompatible file.

5. Address Common VST Incompatibility Causes

Once the faulty plugin is identified, check the following factors:

• Bit Architecture: Modern versions of Audacity are 64-bit. Attempting to load older 32-bit VST plugins without a dedicated bridge (such as jBridge) will cause instability or failure. Ensure the plugin architecture matches your Audacity build.
• VST3 vs. VST2 Support: While modern Audacity supports VST3, certain complex plugins with proprietary copy-protection shells (like iLok or heavy OpenGL graphical interfaces) may fail to initialize properly in Audacity's open-source environment.
• Updates: Check the plugin developer’s website to ensure you are running the latest version of the plugin, as updates frequently resolve host DAW crashes.