Skip to content
Logic ProFilesLogic ProFiles

Fix Problems

Audio Unit failed validation in Logic Pro — how to fix it

Logic Pro tests every Audio Units plug-in before it lets you use it. A plug-in that fails the test is marked in the Plug-in Manager and left out of your menus. A rescan fixes many cases. When it doesn't, the plug-in usually needs an update, an authorisation, a clean reinstall or Rosetta.

Owen Hartley Owen Hartley Updated Checked for Logic Pro 13
Plug-in box on a checklist with a red cross where the validation tick should be
Incompatible Audio Units found

Applies to: Logic Pro 13, 12 and 11 for Mac (alert wording as documented by Native Instruments).

Most likely causes

  1. Outdated plug-in after a Logic Pro or macOS update (most common)
  2. Plug-in not authorised or a damaged activation file (common)
  3. Intel-only plug-in on Apple silicon without Rosetta (common)
  4. Damaged Audio Units cache (occasional)
  5. 32-bit plug-in or a 32-to-64-bit wrapper (occasional)

After clearing the cache

Finder-style folder path from Library to Caches to AudioUnitCache with two cache files marked for removal
Clearing the AudioUnitCache makes Logic Pro scan every plug-in again.

When you reopen Logic Pro after clearing the cache, it scans all your plug-ins again. Apple says this scan can take 10 minutes or more after an update, so give it time before deciding Logic Pro has frozen. If it does hang, see Logic Pro keeps crashing.

If the plug-in passes but still isn't in your Insert menu, check the Hide and Ignore columns described in plug-ins not showing.

Fixes, in order

  1. 1. Rescan the plug-in

    When the alert appears, Native Instruments says to click Start Plug-In Manager. Or open Logic Pro > Settings > Plug-in Manager yourself, select the plug-in and click Reset & Rescan Selection.

  2. 2. Update the plug-in

    Install the latest version from the maker's installer or app (for example Native Access for Native Instruments).

  3. 3. Authorise it

    Apple's article says a plug-in marked "not authorised" needs the maker's activation steps first.

  4. 4. Reinstall cleanly

    Akai's steps: authorise the plug-in, delete its .component file from the Components folder, reinstall the latest version and restart Logic Pro.

  5. 5. Clear the Audio Units cache

    Arturia says to delete com.apple.audiounits.cache and com.apple.audiounits.sandboxed.cache from ~/Library/Caches/AudioUnitCache, then reopen Logic Pro.

  6. 6. Give Logic Pro Full Disk Access

    Native Instruments lists this for some of its plug-ins: System Settings > Privacy & Security > Full Disk Access.

  7. 7. Install Rosetta for Intel-only plug-ins

    On Apple silicon, Intel-only Audio Units work only with Rosetta installed.

  8. 8. Remove wrappers and 32-bit plug-ins

    Apple says 32-bit plug-ins aren't compatible and advises against 32-to-64-bit wrappers.

Sources

Checked November 2026. Logic ProFiles is independent of Apple; menu names can differ slightly between Logic Pro versions.

Frequently asked questions

What does "failed validation" mean in Logic Pro?

+

Logic Pro's Audio Units test found a problem with the plug-in, so it isn't offered in your menus. Rescanning, updating or reinstalling the plug-in usually clears it.

Why did a plug-in fail validation after updating macOS?

+

Usually the installed version doesn't support the new macOS or Logic Pro. Apple asks you to check third-party Audio Units compatibility after every update, then install the maker's latest version.