Guide · macOS

Audio plug-ins missing or not loading after a macOS update

You updated macOS, opened your session, and half your plug-ins are gone or greyed out. Here's what the update actually changed, and how to bring them back.

Why an update breaks plug-ins

A macOS update doesn't delete your plug-ins. It changes the rules for loading them. Two things happen:

The result: the plug-in file is still on disk, but macOS won't let it load, so your DAW hides it.

Fix it in the right order

1. Re-sign the plug-ins

This is the step that actually resolves the “damaged / can't be verified” failures. For each affected plug-in, clear stale attributes and apply a fresh ad-hoc signature:

sudo xattr -cr "/Library/Audio/Plug-Ins/VST3/YourPlugin.vst3"
sudo codesign --force --deep --sign - "/Library/Audio/Plug-Ins/VST3/YourPlugin.vst3"

Do this for anything that went missing. If a whole folder is affected (which is typical after an update), that's a lot of commands to type by hand.

An update usually breaks many at once

That's exactly what Plugin Medic is for. Drop a single plug-in for free, or unlock batch mode to drop your whole VST3 or Components folder and re-sign every plug-in in one pass, with a per-item result so you can see what got fixed.

Download Plugin Medic (Free) Batch mode is a one-time $5 Pro unlock · Universal · macOS 11+

2. Rescan in your DAW

Once the plug-ins are signed, force your host to re-validate them:

3. Clear the Audio Unit cache (AU only, if still stuck)

If Audio Units specifically won't reappear, resetting the AU validation cache forces macOS to re-examine them on next launch:

killall -9 AudioComponentRegistrar

Then reopen your DAW. It will re-validate the Components folder from scratch.

Prevent it next time

Before a major macOS upgrade, it's worth knowing your plug-ins may need re-signing afterward. It's routine, not a disaster. Keeping Plugin Medic around means the fix is a folder drop instead of an afternoon in Terminal.

Related: Why macOS says your plug-in is “damaged.”