Guide

AU validation failed in Logic Pro: how to fix it

Logic Pro will not use an Audio Unit until it passes Apple's validation, and a plugin that fails is disabled and drops out of the list. It looks like the plugin vanished, but Logic found it, tested it, and held it back on purpose. Here is what that means and how to get the plugin validating again.

This one is Logic-specific. Logic loads Audio Units only, so it is the only host that runs this test, and the steps below use Logic's own menus. Paths shown are macOS.

What does AU validation failed mean?

It means Logic tested the plugin, the plugin did not pass, and Logic disabled it, so it will not appear in your instrument or effect list even though it installed.

Logic Pro loads Audio Unit (AU) plugins only. Whenever it finds a new or changed Audio Unit, it runs Apple's validation tool, called auval, on it before it will let you use it. The test checks that the plugin loads and behaves the way an Audio Unit is supposed to. A plugin that passes is enabled and shows up in the menus. One that fails is marked failed and switched off, so it goes missing with nothing on the track to explain it.

So a failed validation is not Logic losing your plugin. It is Logic testing the plugin and keeping it out of the way until it passes, which is good news: you usually have one plugin to fix, not a broken install of Logic.

Only Audio Units are validated

Logic uses Audio Units and nothing else. It does not load VST, VST3 or AAX at all, so those formats are never validated and are never affected by this. If a plugin only came as a VST or VST3, Logic will not show it whether or not it would validate, and that is a different problem covered in why a plugin does not show up in your DAW.

Why does a plugin fail AU validation?

Because the plugin did something the test would not accept, and it is usually one of a short list of reasons. The failure itself rarely tells you which, but these are the common ones.

  1. An old version with a real bug. The plugin has a fault that the validation catches, and an update from the maker usually clears it.
  2. Not updated for your macOS or Logic. A plugin built for an older system, or a Logic and macOS that have moved on past the plugin, can fail where the two no longer agree.
  3. An Intel-only plugin on Apple Silicon. On an Apple Silicon Mac, Logic normally runs natively, and an Intel-only Audio Unit has to run under Rosetta or it is blocked. That mismatch can show up as a failed validation.
  4. Unsigned or quarantined. If the component is not signed, or macOS quarantined it through Gatekeeper because it was downloaded, the system can block it before it ever passes.
  5. A corrupt or incomplete install. An interrupted download or install can leave the component damaged, so it fails every scan until you reinstall it.

The table below maps each cause to the fix that clears it.

Why it failedWhat fixes it
An old plugin version with a bug Update the plugin to its current release, then re-run validation
Not updated for your macOS or Logic Update Logic and macOS to a supported combination and install the matching plugin build
Intel-only plugin on an Apple Silicon Mac Install a Universal or Apple Silicon build, or run Logic under Rosetta as a temporary workaround
Unsigned or quarantined by Gatekeeper Install a signed, notarized build from the maker, and install only plugins you trust
Corrupt or incomplete install Remove the .component and reinstall a fresh download cleanly

How do you fix a failed AU in Logic?

Work down this list in order and stop the moment the plugin validates. The steps run from the most common and least disruptive to the last resort.

  1. Update the plugin and Logic. A version mismatch is the most common cause, so bring the plugin to its current release and update Logic and macOS to versions the maker lists as supported, then test again.
  2. Re-run validation in Logic's Plug-in Manager. Open the Logic Pro menu, choose Settings (or Preferences on older versions), then Plug-in Manager. Find the plugin, select it, and click Reset & Rescan Selection. Logic runs the test again and shows whether it passed this time. The exact steps are in the next section.
  3. Reinstall the component cleanly. Remove the plugin's .component file from /Library/Audio/Plug-Ins/Components, or the same folder inside your home ~/Library if it installed there, then download a fresh copy and install it again in case the first install was damaged.
  4. Check native or Rosetta. If the plugin is Intel-only it will not validate while Logic runs natively on Apple Silicon. A Universal or Apple Silicon build from the maker is the real fix. As a temporary workaround you can run Logic under Rosetta: quit Logic, find Logic Pro in Applications, right-click and choose Get Info, and tick Open using Rosetta. Note that this affects every plugin, not just the failing one.
  5. Clear the AU cache and relaunch. macOS keeps a cache of the Audio Units it has scanned in ~/Library/Caches/AudioUnitCache. Quit Logic, remove that cache, and reopen Logic so it rebuilds the list and tests the plugin fresh.
  6. Contact the plugin maker. If it still fails after all of this, send the maker your Logic version and your macOS version and tell them it fails validation. A plugin that fails auval on a system it says it supports is theirs to fix.

If you want the exact reason it stopped, Apple's auval tool can be run from Terminal against a single Audio Unit and it prints where the test failed. That output is optional and is mostly useful to pass on to the maker. For everything else about Audio Units in this host, see audio plugins in Logic Pro.

How do you re-run AU validation?

In Logic's Plug-in Manager, with Reset & Rescan Selection. This is the one place in Logic that re-tests a plugin and shows you the result.

  1. Open the Logic Pro menu at the top left of the screen.
  2. Choose Settings. On older versions of Logic this is Preferences.
  3. Open Plug-in Manager.
  4. Find the plugin in the list. A failed one is shown with a failed status.
  5. Select it and click Reset & Rescan Selection.
  6. Logic runs the validation again and updates the status to passed or failed.

If it passes, it returns to your instrument or effect menus straight away. If it still fails, rescanning on its own will not change that, because it only re-tests what is already there. The fixes above, updating, reinstalling, checking Rosetta or clearing the cache, are what actually change the result, and then a rescan confirms it. If the plugin is not in the Plug-in Manager list at all, rather than listed as failed, that is a slightly different problem: see why a plugin does not show up in your DAW.

If you would rather not fight it

Most of this page is about one plugin that will not pass a test the rest of your setup passes fine. While you sort it out, it helps to have an instrument you know validates cleanly, so you can keep making sound in Logic instead of chasing a failed scan.

One of ours, since you are here

Our Audio Unit is signed and notarized, and it passes Logic's validation cleanly on the first launch, so none of the steps on this page apply to it. You can also try it in a browser first, with no install and no account. The Collection is three instruments: ARGISH, SILT and REHEAT.

Every one ships as AU, VST3, AAX and a standalone app on macOS, signed and notarized, and a VST3 on Windows. So the Audio Unit lands in the right folder and validates in Logic on the first launch, rather than adding to the trouble on this page.

Try one free in your browser first, no install and no account. The whole Collection is one purchase.

More guides like this

We write these when there is something worth writing down. One email when a new one lands or a new Tunary instrument ships. No newsletter, no schedule.

See all guides