Mac Apps Crashing at Launch? What to Check Before Reinstalling

TL;DR: A Mac app crashing at launch is almost never fixed by reinstalling alone, because the thing causing the crash usually survives the reinstall. Check your disk space, app permissions, and preference files first. One of those three solves it most of the time.

What you need

• A Mac running macOS (any recent version)
• About 10-15 minutes
• Access to Finder, Terminal (optional), and Console.app
• The app's name handy for searching logs

Step 1: Read the crash log first

Do not skip this. macOS writes a crash report every time an app dies. Open Console.app (find it in Applications > Utilities). Click Crash Reports in the left sidebar. Find your app's name and open the most recent report.

You do not need to understand every line. Look for words like SIGKILL, killed, disk full, permission denied, or a library name you recognize. That one clue tells you where to go next.

Step 2: Check available disk space

Apps need scratch space to launch. Some need a surprising amount. Go to Apple menu > About This Mac > Storage. If you have less than 10 GB free, that is almost certainly your problem.

Delete what you can. Move photos or large files to an external drive or cloud storage. Then try launching the app again before doing anything else.

Step 3: Check and repair app permissions

This one bites people constantly. Open System Settings > Privacy & Security. Scroll through the list: Full Disk Access, Files and Folders, Accessibility. If your app needs one of those and it is toggled off, it will crash silently on launch with no obvious error message.

Toggle the permission off, then back on. If the app is not listed at all, try launching it once manually and watch whether macOS prompts you to grant access.

Step 4: Trash the app's preference file

MacOS stores per-app preferences in ~/Library/Preferences/. That file can get corrupted after an update, a forced quit, or a power interruption. A corrupted pref file causes exactly the crash-on-launch symptom you are seeing.

Here is how to find and remove it:

1. Open Finder. In the menu bar, click Go > Go to Folder.
2. Type ~/Library/Preferences/ and press Enter.
3. Search for your app's name or developer name (e.g., com.adobe.photoshop.plist).
4. Drag that .plist file to your Desktop (do not delete it yet, just move it out of the way).
5. Relaunch the app.

If the app opens, the preference file was the problem. You can delete the old one from your Desktop. If the app still crashes, put the plist back and move on.

Computer acting up? Get a real diagnosis. Book a free diagnostic

Step 5: Check macOS and app version compatibility

macOS Catalina (10.15) and later dropped support for 32-bit apps entirely, affecting all Macs , including both Intel and Apple Silicon models. If your app is old and has not been updated, it may simply not run on your current macOS. (Yes, it will still crash silently. No, reinstalling will not help.)

Check the App Store or the developer's site for the app's system requirements. Compare them against your macOS version under Apple menu > About This Mac.

If there is a mismatch, your options are: update the app, find an alternative, or in rare cases run an older macOS in a virtual machine. Reinstalling the same incompatible version accomplishes nothing.

Step 6: Test in a new user account

This one is the real tell. Create a temporary user account under System Settings > Users & Groups. Log into that account and try launching the app.

• App launches fine in the new account: The problem is in your user profile. Corrupted cache, conflicting login items, or a bad preference file specific to your account.
• App crashes in the new account too: The issue is system-wide. Could be a bad install, a missing dependency, or a real compatibility problem.

This step tells you exactly where to dig next without guessing.

Step 7: Clear the app cache

If the new user test points back to your account, clear the app's cache. Go to ~/Library/Caches/ and look for a folder matching your app's name or bundle ID. Trash it. The app will rebuild it on next launch.

Do not clear all caches blindly. Just the one folder for the offending app.

Common mistakes

Reinstalling before diagnosing. A reinstall copies fresh app files but leaves your plist, cache, and permissions exactly as they were. If any of those caused the crash, reinstalling changes nothing.

Restarting macOS and calling it fixed. A restart clears RAM and sometimes resolves a one-off crash. But if the crash happens again on second launch, you have not fixed anything.

Updating macOS mid-troubleshoot. Major macOS updates can change permission behavior and sometimes break apps further. Finish diagnosing the current crash before running a major update.

Ignoring the crash log. Every answer is in there. People skip it because it looks intimidating. You only need to read the first 20 lines.

Decision table: which fix to try first

Bottom line

Nine times out of ten, a Mac app crashing at launch is a preference file, a permissions setting, or a full disk. Those take five minutes to check. Reinstalling is a last resort, not a first move, and it will not fix those underlying issues anyway.

If you have worked through all of these steps and the app still dies, there may be a deeper macOS problem: a corrupted system library, a failing drive, or a permissions issue at the system level. At that point it is worth getting a second set of eyes on it.

Our Mac repair service covers software diagnostics as well as hardware, and remote support is often the fastest way to get someone looking at your logs without hauling your machine anywhere. We work with customers across West Palm Beach, Royal Palm Beach, and Wellington from our Okeechobee Boulevard shop.

Computer acting up? Get a real diagnosis.

Fix My PC Store has repaired thousands of machines across West Palm Beach. Free diagnostics, honest pricing, no upsell games.

Book a free diagnostic