Why Won’t GarageBand Open? | Quick Fix Playbook

When GarageBand won’t open, the issue usually stems from plug-ins, audio devices, or a corrupt preference file.

If the music app stalls at launch, bounces once in the Dock, or hangs on “Initializing,” this guide shows fast checks and deeper fixes that restore a clean launch without losing projects. The steps start simple and move toward items that typically trip the app—third-party Audio Units, drivers, and damaged settings.

Fast Checks Before You Dig In

Confirm the basics first to avoid chasing ghosts. Reboot the Mac. Update the app from the App Store. Disconnect USB audio gear. Try the built-in speakers and mic. If the app opens only when hardware is unplugged, you’ve already found the culprit. Apple lists these early steps in its troubleshooting guide.

Symptom Likely Cause Quick Try
Icon bounces then disappears Corrupt preferences or plug-in scan crash Reset prefs; start without plug-ins
Stuck on “Scanning Audio Units” Incompatible Audio Unit Launch without Audio Units; rescan later
Hangs on “Initializing” Audio driver conflict Switch to built-in output/input
Opens, then beachballs on playback Outdated app or content download Update app; let extra sounds finish downloading
Works in one user, not another Account-level settings Create a fresh user to test

GarageBand Not Opening On Mac: Fixes That Work

Work from top to bottom. Try the app after each step. If one step solves it, stop there.

1) Update The App And macOS

Launch the App Store and install any updates for the app. New builds often include stability fixes, Audio Unit changes, and content delivery tweaks. Also apply macOS updates, which refresh audio frameworks and driver layers the app relies on.

2) Test With Built-In Audio Only

External interfaces and drivers can block a clean start. Unplug USB, Thunderbolt, and Bluetooth audio devices. Open the app. Then set output and input to “Built-in” in Preferences once it loads. If that works, reconnect gear one piece at a time to find the conflict.

3) Start Without Audio Units

Third-party plug-ins are the top reason for a launch hang. Hold the Control key while you click the app icon, choose “Launch Without Audio Units,” and try again. If the app opens, you’ve confirmed a plug-in issue. Later, re-enable plug-ins and rescan to isolate the bad one.

4) Reset The Preference File

The app stores global settings in a plist. If this file becomes damaged, the program may crash during startup. Removing it forces the app to recreate a fresh default copy. You won’t lose projects, presets, or patches; you’ll only lose custom preferences such as buffer size, metronome tweaks, or zoom settings. Apple notes this settings file lives in your user Library on your Mac and is rebuilt on next launch.

5) Safe Mode Boot

Safe Mode trims startup items and clears caches at boot. It’s a handy way to rule out system extensions and fonts that can interfere with audio apps. After a Safe Mode start, open the app, then restart normally and test again. Apple explains the steps in its Mac Help Safe Mode guide.

6) Create A New Mac User

If the program launches in a fresh account, the issue lives in the original user’s Library. That points you toward preferences, caches, or plug-ins installed per-user rather than system-wide.

7) Check Plug-In Compatibility And Rescan

Older Audio Units may not validate on newer macOS builds. If you recently updated the system, rescan plug-ins inside the app. You can also clear the Audio Unit cache so the next launch performs a clean validation. Reinstall any plug-ins that fail validation using their latest installers.

8) Reinstall The App From The App Store

If nothing else works, delete the app, empty the Trash, and download a fresh copy from the App Store. Projects in Music/GarageBand and custom samples remain unless you manually remove them, but it’s still smart to back up your user folder before a reinstall.

Step-By-Step: The Exact Fixes

Update The App

Open the App Store, search for the app, and click Update. Fresh builds often include stability and launch fixes. Apple maintains release notes that track those changes across versions.

Open With Built-In Audio

Connect no external interfaces. Launch the app. In Preferences > Audio/MIDI, set Output Device and Input Device to Built-in. Quit and relaunch to confirm a clean start with the default driver stack.

Launch Without Plug-Ins

Hold Control while clicking the app icon, then choose “Launch Without Audio Units.” If that works, open your project and remove third-party plug-ins from the channel strips one by one. Replace a suspect plug-in with a stock effect and test the launch again.

Reset Preferences (Plist)

Close the app. Open Terminal from Applications > Utilities, then run:

defaults delete com.apple.garageband10

If you ever upgraded from an older major version, also run:

defaults delete com.apple.garageband

Restart the Mac and launch the app. A fresh settings file is created automatically.

Safe Mode Procedure

Shut down the Mac. On Apple silicon, hold the power button until “Loading startup options” appears, pick your disk, then hold Shift and click Continue in Safe Mode. On Intel, hold Shift during boot. Log in, test the app, then restart normally.

New User Account Test

Create a new Admin user in System Settings > Users & Groups. Log out of your main account and into the new one. Launch the app. If it runs here, the issue is in user-level data on the original account. Check that Library folder carefully: Preferences, Caches, and Audio Units.

Clear The Audio Unit Cache

Quit all DAWs. In Finder, press Shift-Command-G and paste ~/Library/Caches. Delete com.apple.audiounits.cache and com.apple.audiounits.sandboxed.cache. Restart the Mac and launch the app so it rescans plug-ins. Reinstall any plug-ins that fail validation using the latest installers from the developer.

For stubborn plug-ins, vendors provide rescan steps and cache reset paths. Follow the developer’s notes after you install the build.

Reinstall Cleanly

Drag the app from Applications to the Trash and empty it. Open the App Store, search, and reinstall. If you rely on legacy projects, keep a backup of your user Library so content packs and lessons remain available after the reinstall.

Common Error Messages And What They Mean

Message On Launch What It Points To Next Move
“Scanning Audio Units…” never finishes Bad or outdated plug-in Launch without Audio Units; clear AU cache; update plug-in
“GarageBand quit unexpectedly” at start Damaged preferences or plug-in Delete plist via Terminal; run with no third-party plug-ins
Beachball after opening a project Interface driver or massive content download Switch to built-in audio; let sound library finish
No input devices available Privacy permissions or driver issue Grant mic access in System Settings; try built-in input
Project opens in new user only Account-level corruption Migrate settings slowly; rebuild only what you need

Why Launch Problems Happen

Audio apps sit on a tall stack: macOS audio frameworks, drivers, hardware, and third-party code. A small mismatch can stop a launch. The most common triggers are plug-ins compiled for older SDKs, audio drivers that need an update after a macOS upgrade, and corrupted preference files. Large sound library downloads can also delay the first open while content caches build.

Spot The Plug-In That Breaks The Party

When the app opens only with plug-ins disabled, you can narrow the field fast. Open an empty project. Enable Audio Units. Add plug-ins in small batches. Quit and relaunch between batches. When the crash returns, remove the last batch, then add those items one by one. Keep a short list of plug-ins that failed validation so you can fetch fresh installers.

Check macOS And Model Compatibility

Running an older Mac or OS? Make sure your version of the app is compatible with your system. The App Store will offer the latest build your machine supports, but older plug-ins may not. If you’re on an Intel model that won’t receive major macOS updates anymore, expect more plug-ins to age out over time. Planning an upgrade removes a lot of friction here.

Privacy And Permissions Notes

If the app opens but recording inputs are missing, check System Settings > Privacy & Security > Microphone and grant access. Denied microphone permission can look like an audio device failure, which sends many users down the wrong path.

When You’ve Fixed It, Lock In Stability

Create A “Clean Boot” Project

Save a blank project with no third-party plug-ins and a single software instrument. If a launch issue returns, open this project first. If it loads, the problem likely lives in a specific project or plug-in, not the whole app.

Keep Plug-Ins Current

Subscribe to update emails from vendors. Many publish Apple Silicon builds and new notarized installers that fix launch-time crashes. Keep one folder with your current installers so you can roll forward quickly after a macOS update.

Back Up The User Library

Before big changes, copy ~/Library/Audio/Plug-Ins and ~/Library/Preferences. A quick restore saves hours if you need to revert a batch of plug-ins or recover a good plist.

Reference Steps From Apple

Apple’s official page walks through a clear order of operations—restart, update, test with built-in audio, open without Audio Units, try a new user, and reset preferences. Safe Mode instructions are documented in the Mac Help guide. These two links cover the exact sequences you’ll follow in this playbook.

FAQ-Free Troubleshooting Flow Recap

1) Update the app and macOS. 2) Test with built-in audio. 3) Launch without Audio Units. 4) Reset preferences. 5) Boot in Safe Mode. 6) Create a new user. 7) Clear the Audio Unit cache. 8) Reinstall from the App Store. Work from easiest to most invasive, and you’ll usually get a clean launch in short order.