GarageBand Won’t Open? | Fast Fix Guide

If the music app stalls on launch, you’re not stuck. This guide gives clear fixes that work on real Macs, from quick updates to deeper cleanups. Start at the top and work down; your project files stay safe with these steps.

Fix A GarageBand Startup Freeze: Step-By-Step

Work through these actions in order. After each one, try opening the app again.

Start With Updates

Bugs that block launch often vanish after a patch. Open App Store, click Updates, and install the newest build. Also apply the latest macOS point release, then reboot. Many users see the app spring back to life after this alone. Then test launch once more again.

Confirm You Have Space

The workstation needs working room for temp renders and sound libraries. Keep at least 10–15 GB free on the system drive. If you’re tight, move bounces off the disk, clear Downloads, and empty Trash. Then try launching again.

Reset Preference Files Safely

Corrupted settings can block the splash screen. You can reset them without touching projects. Quit the app. In Finder, press Option and open the Go menu, choose Library. Head to ~/Library/Preferences/ and drag com.apple.garageband10.plist to the desktop. Launch the app; it builds a fresh plist. If the app opens, delete the old plist.

Rule Out Third-Party Plug-Ins

Many launch stalls trace back to an Audio Unit failing validation. To test, move third-party AUs out of these folders: /Library/Audio/Plug-Ins/Components/ and ~/Library/Audio/Plug-Ins/Components/. Put them on the desktop temporarily. Open the app. If it launches, add components back in small batches to find the offender. Update or replace any plug-in that triggers the crash.

Restart The Audio Engine

The system audio daemon can get stuck. Open Activity Monitor, search for coreaudiod, select it, and click the Stop button to quit. macOS respawns it in a second. Try launching again.

Check Microphone Permission

On macOS Mojave or later, the app needs mic access to record. If the first-run permission prompt failed, it can hang at launch. Go to System Settings → Privacy & Security → Microphone and enable access for the app. Then relaunch.

Test In Safe Mode

Safe Mode boots macOS with only Apple extensions, clears caches, and blocks login items. That makes it perfect for isolating flaky drivers and helper tools. Use Apple’s steps to boot into Safe Mode for Apple silicon or Intel models, then try opening the app. If it works here, a third-party add-on on normal boots is the likely cause.

Create A New User For Comparison

A fresh macOS user account removes profile-level tweaks, odd launch agents, and stale preference bundles from the picture. If the app opens under the new account but not under yours, focus on items in your original user Library, not system-wide files.

Why This Works, Backed By Official Guidance

Apple’s own guide groups fixes into three buckets: update software, test the sound library and plug-ins, and reset settings. That aligns with the steps above. Safe Mode testing and new user checks are classic Apple methods for separating system issues from account issues.

For reference, see Apple’s troubleshooting guide for GarageBand and the Mac Help page on starting in Safe Mode. Both walk through update checks, permissions, and plug-in isolation with clear platform steps.

Deeper Fixes When The App Still Won’t Launch

Rebuild Audio Units Cache

If the splash screen stalls on “Scanning Audio Units,” clear the AU cache. Quit all audio apps. In Finder, go to ~/Library/Caches/AudioUnitCache/ and remove the files inside. Next, visit ~/Library/Preferences/ and remove com.apple.audiounits.cache. Reboot, then try opening again. macOS will rescan plug-ins on the next launch.

Reset The Sound Library

Missing instrument content can block loading. Open the app’s Sound Library manager when possible and redownload the base library. If you can’t reach the manager, reinstall the app from the App Store to fetch a clean content set.

Clear App Sandbox Containers

Corruption inside the app container can stop the UI from appearing. Quit the app. In Finder, open ~/Library/Containers/ and look for folders beginning with com.apple.garageband10. Move them to the desktop, then launch. If the app opens, sign back into the sound library and rebuild content as needed.

Reset MIDI Drivers And Surfaces

Bad MIDI device bundles can crash the audio engine before the window shows. Unplug controllers and interfaces. Then check /Library/Audio/MIDI Drivers/ and ~/Library/Audio/MIDI Drivers/ for third-party files. Move them out, reboot, and test. Add devices back one at a time.

Fix Permissions On The Music Folder

If the Music folder lost write access, the app won’t create temp assets or the library. Open Finder, select the Music folder, press Command-I, and grant “Read & Write” to your user. Click the gear → Apply to enclosed items. Try launching again.

Delete Autosave Crash Files

A corrupt autosave can loop load on start. Visit ~/Library/Autosave Information/ and remove files with the app name. Projects remain intact in your standard project folders.

Reinstall The App The Right Way

Drag the app from Applications to the Trash and empty it. Open App Store and install fresh. After install, open once before restoring any third-party plug-ins or custom templates. If it launches, add extras back slowly.

Common Symptoms And Likely Causes

Match what you see on screen to the table, then jump to the right fix.

Exact Steps For Key Fixes

Find And Remove The Preference File

Quit the app. In Finder, hold Option and choose Go → Library. Open Preferences. Drag com.apple.garageband10.plist to the desktop. Launch the app. If it opens, delete the old plist. If not, move it back.

Move Plug-Ins Out Safely

In Finder, go to the two Components folders listed earlier. Create a folder on the desktop named “AUs-Temp.” Move third-party .component files into it. Try opening. If the app opens, put components back in small sets. When a set blocks launch, split it again to find the single plug-in at fault.

Grant Mic Access Manually

Open System Settings → Privacy & Security → Microphone. Toggle the switch for the app on. If the switch is missing, quit System Settings, reboot, then try toggling again. The Apple page linked above shows the exact menu path.

Boot To Safe Mode

Shut down. For Apple silicon: press and hold the power button until “Loading startup options” appears, pick your disk, hold Shift, click Continue in Safe Mode. For Intel: power on and hold Shift at the chime. Log in; you’ll see “Safe Boot” in the menu bar. Now open the app.

Create A Clean Test Account

System Settings → Users & Groups → Add User. Pick Administrator. Log out of your main account, log into the new one, and try launching. If it works, your original profile holds the problem, not macOS.

Prevent A Repeat

Keep Plug-Ins Current

Old AUs break after macOS upgrades. Check each vendor for Apple silicon builds, notarized installers, and Sonoma or Sequoia compatibility notes. Update before you upgrade macOS.

Leave Headroom On The System Drive

Keep double-digit gigabytes free so renders and caches have space. Bounce finished sessions to external storage and trim large sample packs you don’t use.

Back Up Templates And Presets

Save custom channel strips, patches, and templates outside the app container in a cloud folder. If you need to wipe caches or containers, you can drop them back in minutes.

Audit Login Items

Go to System Settings → General → Login Items. Remove audio tools you no longer need. Fewer background helpers means fewer launch surprises.

When To Ask For Help

If none of the steps work, gather a spin report and crash log so Apple can pinpoint the blocker. Open the Console app, filter for the app name, and copy the latest crash entry. Share that with Apple Support or the plug-in vendor. You can also post details on the Apple Support Communities with your macOS version, the app version, plug-in list, and what you tried from this page.

Send us your feedbackTell us what you thought about this post

Name * Email *

Your comment *

Quick check — what is …? *

Send feedback