Unofficial archive. This is a read-only, community-run archive of the Apple Support Community. It is not affiliated with or endorsed by Apple Inc.

Logic Pro won't open after Ventura update: stalls on scanning audio unit plugins

this is INSANELY frustrating. I recently got a brand new M2 MacBook Air, and made the mistake of updating to ventura when it was released. Now, i cannot open Logic Pro. Logic will spend a long time scanning audio units and then when I restart it will hang on "updating information about audio unit plugins". It will not complete in any amount of time. I have tried EVERY solution suggested online. Removing all plugins from the plugin folder allows Logic to restart, but when replacing the plugins it once again hangs on rescanning them. Deleting the plugin cache seems to get you a little farther, since you can see the actual progress and arrive at the 'Incompatible Audio Units Found' pop up. This pop up tells you that there incompatible audio units and offers two buttons: 'Continue' and 'Start Plug-In Manager'. this is the most infurating part: clicking on either of those two buttons results in ANOTHER hang. The beachball immediately appears and no amount of time will allow Logic to start.


This is apple's OWN software on it's OWN update! It's so insane that with a brand new machine and the most recent OS i can't open the one program that i most use on a mac! I hate having to spend weeks googling and trying every tentative solution. If Logic identifies the incompatible units, WHY CAN'T IT DISABLE THEM AND START LOGIC PRO!!!

19 replies

RESOLVED!

I had the same issue with Waves plug-ins. I have the M2 and migrated from an i7. First go to the Go tab and select Computer/Library/Audio/Plug-ins and remove the Components Folder (place in the trash temporarily). Try to run Logic. It should start up. Now you know the issue is related to Plug-ins. Put back the Components folder and move all files in that folder, except the AppleAES folder to the trash. For myself I cleaned out everything as most was outdated. I was able to isolate the issue being the WavesShell- and for good measure I also placed the VST,VST3, and WPAPI folders in the trash. Then I opened up the updated Waves Central Application. Go to Settings and select Complete Waves Cleanup. Once Waves restarted I saw all my Waves Plug-ins were activated, but no longer installed. I selected the all box and proceeded to install all the Plug-ins on the computer. Once completed I started Logic and it worked. I went to the Plug-ins manager under Settings in Logic and saw the Waves Plug-ins. Most were successfully validated; however V14.12.90- CLA Guitars (s) effects, GTR Amp (m->s) and (s), GTR Amp 2cab (m), StudioRack (all) Midi-controlled effect all crashed validation and were isolated. And it works. My strategy was to remove everything old that I knew was Intel oriented, knowing it would be better to install from scratch. I suspect this process will work for other 3rd party Plug-ins as well. I had Waves V10 through V14 and just moved everything into the trash including Fabfilter, Izotope, CableGuy, Reason, etc...Now since I got Logic working with Waves I will proceed to install other 3rd-party Plug-ins. My system is the MacBook Pro M2 Max running Ventura 13.3.1 (a), Logic Pro 10.7.7, and Waves Central 14.1.1, and my Plug-ins are V14.

Hope this helps

Also, I deleted the trash.


When I was troubleshooting I first went to the Go/Library by pressing option. And noticed that the Components folder was empty. Then found a full Components folder under Go/Computer...


I believe the issues arise from the left over Intel based files on the new Mac. All that clutter should be deleted and 3rd-party software/apps reinstalled from scratch.

A few things to try…


If you disable Core Audio on launch (click on the Logic icon then press “Ctrl” on your keyboard) you’ll get the “Do you want to launch the Core Audio driver” - click “Don’t Launch”. If it’s a blank song, you’ll need to create an external midi track, if it’s an existing song, all your plugins will have an exclamation mark (being unavailable). Next go to “Settings > Audio” & re-enable Core Audio, (click “Apply”). You may get an error message saying “incompatible plugins/audio units”…. If Logic doesn’t crash, then go to “Settings > Plugin Manager” where you’ll see which plugins are causing issues (usually marked “Couldn’t be opened”).


If this doesn’t work, remove all plugins from your plugin folder. Make sure you remove all traces - some plugin manufacturers install their plugins in the Application folder (eg. Waves). If Logic is still trying to scan for plugins at launch, you still have 3rd party plugins on your system. Next, re-install plugins one by one (or vendor by v 00004000 endor) - make sure you download the latest versions, & check the vendors for compatibility. Launch Logic after every install, & if Logic stalls, you know you have a problem plugin, (& remove accordingly). Another issue that can cause the scanning process to trip is authorisation errors - make sure you have no expired demos etc.


There’s probably very few plugin developers that have official Ventura qualified plugins - particularly smaller developers, but many are already silicon compatible, so “may” work without issue. - ymmv. Being at the cutting edge of Mac OS updates has it’s disadvantages… & backups provide a simple way to revert - but hindsight is not much help other than being a helpful reminder…


Last resort is to roll back to Monterey, & re-install everything : How to reinstall macOS – Apple Support (UK) (Make sure you backup first)!


Had same problem with M2 chip. My problem was Waves plugins, versions V10, V11, V12. After I completely removed all Waves content, the problem did not occur anymore. Previously I also got stuck in the startup plugin scan and Aborting did only freeze the system.


After I went to Applications-folder, right clicked Logic Pro and chose "Get info" and ticked box "Open using Rosetta", I got to find out that reason was Waves plugins as it said which one were incompatible and could then skip.


Hope this helps.

The most recent version of waves is v14.

Check your Application folder for “Antares Technologies” - should be an uninstaller included there (there is in mine). Running the uninstaller should uninstall both the plugin & any trial authorisations. Other than that, my only other suggestion is to contact Antares Support…

Mine turned out to be a powered midi converter that just hadn't liked all the rebooting, turn it off and plug it in again and it was all happy. I did learn on my journey not to use the disk utility in recovery to wipe a drive, use the erase disk in reinstall Ventura otherwise it leaves crap on the drive at a low level, in my case out of date UAD drivers.

Check with the vendors of your third party plugins, make sure they're Apple Silicon compatible.

Hi,

This is not as frustrating as you may believe. My mentor Edgar Rothermich says "80% of your problems happen because of 20% of your plug-ins". If you remove the Au files from the components folder. I believe everything should go back to normal. One or more of your plugs in incompatible. Simply go through each plug-in (or each manufacturer) and load them back into the Components folder, re-start Logic, and eventually you will get to the root of the problem. Best of luck! Cheers! - Eddie G.

Remove ur plugins. It’s the FX n actress you have added. They may not have been updated to function with the New Version. I had to pull the whole external effect folder off. On stock would upload.

Check with the developers, they should have instructions for that in their support pages.

AWESOME, I will Try every single one of these solutions today. But I think My exact problems stems from an expired plugin Trail for "Anteras Auto-Tune Pro/Auto-Tune Slice".


I've tried deleting all the existing files for every single 3rd party plug in because I ONLY use stock plugins/live recordings for my Process. So if theirs a way to Remove every single 3rd party plug in on my Laptop, that'd be great.


Anyways, When I Try and Open My Plugin Manager, It says "This menu Item in disabled Because CoreAudio is disabled"


But when I go to check/uncheck to enable my CoreAudio, I get the beachball/Never Ending Spinning ball...

so absolutely frustrating

I ran my Antares uninstaller and it didn’t do the trick. Now I’m trying to uninstall Auto-Tune Slice specifically (because that’s the error message preventing Logic from opening) and it’s asking me for a password for which I cannot enter anything into the window. I opened a ticket with Antares 8 hours ago and haven’t heard anything in response.

I'm the same M2Pro Mac Mini, I've wiped it 4 times now, this time was just Ventura and Logic Pro installed, nothing else, no drivers, no plugins ONLY Ventura and Logic Pro. Hangs every time after the Logic splash screen. Apple software on Apple silicon, this should not be happening. Having to go back to my i7 to work and proper livid

Yes, I know, but V12 (and maybe also V11) worked on Monterey on Intel chip. I still used some of them, but have moved already while ago to UAD, so I don't have to pay constantly to Waves to keep my plugins working. But that's another story.

I am stuck on this EXACT same problem, is it possible to just Delete my 3rd party Plug-ins Altogether ?

The plugin I was Using was a 14 day free trial of, Anteres "AtuoTune Pro/Auto-Tune Slice"

I thought I was the only one

it’s been weeks and they don’t provide any solutions


Did you find a solution?

Same here, brand new M2 MBP. Logic scanning my plug-in every time then crashing on the spash screen. I need this to work, what's the solution here?


Hi! I have the EXACT same issue. Same plugins. Same error message. Did you figure it out? Much appreciated!