How to Fix Apps Not Opening or Crashing After macOS Update (2026 Guide)

You updated to the latest macOS — Tahoe or Sequoia — and suddenly your favourite apps refuse to launch. They bounce in the Dock once or twice, then nothing. Or they open briefly before crashing with a cryptic error. This is one of the most common complaints after any major macOS update, and the frustrating part is that Apple's own error messages rarely tell you what went wrong. This guide walks you through every proven fix, from the quick one-liner to the deeper repairs that most guides never mention — including the Privacy & Security permission resets and preference file deletions that are the actual culprits in most 2026 Tahoe-related failures.

Why macOS Updates Break Apps (Root Causes)

Understanding why apps break helps you pick the right fix. A macOS update can break apps in several distinct ways:

• Permission revocation: macOS Tahoe tightened its privacy framework. Apps that previously had Accessibility, Full Disk Access, or Screen Recording permission may have had those permissions silently reset during the update.
• Corrupted preference files: The app's ~/Library/Preferences/com.developer.appname.plist file may have become incompatible with the new OS version, causing an immediate crash on launch.
• Launch Services database corruption: macOS maintains a registry of all installed apps. A broken entry in this database can prevent an app from launching entirely.
• Quarantine flags: Apps re-downloaded or sideloaded may have a quarantine attribute that macOS refuses to bypass post-update.
• Incompatible app version: The app simply hasn't been updated to support the new macOS runtime and is crashing at the framework level.

Quick Fix: Force Quit and Relaunch the App

Before anything else, force quit any stuck instance of the app and restart it cleanly.

1. Press Option + Command + Esc to open Force Quit Applications.
2. Select the problem app and click Force Quit.
3. Restart your Mac: Apple menu > Restart.
4. After reboot, try launching the app again.

If the app still refuses to open, move to the targeted fixes below.

Fix 1: Check App Compatibility with Your macOS Version

The first thing to verify is whether the app actually supports macOS Tahoe or Sequoia.

Check the app version

1. Locate the app in Finder > Applications.
2. Right-click (or Control-click) the app and choose Get Info.
3. Under General, note the version number.
4. Visit the developer's website or the App Store listing and confirm the latest release supports your macOS version.

Update the app

• App Store apps: Open the App Store, click Updates in the sidebar, and install available updates.
• Non-App Store apps: Open the app (if it opens at all), click AppName > Check for Updates, or visit the developer's download page directly.

If the developer has not yet released a Tahoe-compatible build, you may need to wait or use an older macOS-compatible version temporarily.

Fix 2: Reset App Permissions in Privacy & Security Settings

This is the most commonly missed fix after a macOS update. Tahoe's stricter permission framework can silently revoke previously granted permissions during the upgrade process.

Reset via System Settings

1. Go to Apple menu > System Settings > Privacy & Security.
2. Work through each relevant category: Accessibility, Full Disk Access, Screen & System Audio Recording, Files and Folders, and App Management.
3. Find the affected app in each category. If it's listed, toggle it off, wait 5 seconds, then toggle it back on.
4. If it is not listed, click the + button and navigate to /Applications/YourApp.app to add it.
5. Quit and relaunch the app.

Reset permissions via Terminal (more thorough)

The tccutil command resets specific permission categories system-wide. Open Terminal (Applications > Utilities > Terminal) and run the appropriate command for your app's issue:

# Reset Accessibility permissions
tccutil reset Accessibility

# Reset Screen Recording permissions
tccutil reset ScreenCapture

# Reset Full Disk Access permissions
tccutil reset SystemPolicyAllFiles

# Reset all permissions for a specific app (replace bundle ID)
tccutil reset All com.developer.appname

After running these commands, restart your Mac and re-grant the necessary permissions when the app asks for them.

Fix 3: Delete and Reinstall the App

If compatibility and permissions are not the issue, the app binary itself may be corrupted.

Remove the app completely

1. Drag the app from /Applications to the Trash — or use the App Store's delete option for MAS apps.
2. Empty the Trash: Finder > Empty Trash.
3. Remove leftover support files. In Terminal:

rm -rf ~/Library/Application\ Support/AppName
rm -rf ~/Library/Caches/com.developer.appname
rm -rf ~/Library/Saved\ Application\ State/com.developer.appname.savedState

Replace AppName and com.developer.appname with the actual folder and bundle identifier for your app.

Reinstall from a trusted source

• For App Store apps: Open the App Store, search for the app, and click Get / Install.
• For direct downloads: Go to the official developer website — never a third-party mirror — and download the latest build.

Fix 4: Clear App Cache and Corrupted Preferences

A stale or incompatible preferences (.plist) file is one of the top causes of post-update crashes that reinstalling alone does not solve, because the old plist survives a standard reinstall.

Delete the preferences file

1. Open Terminal.
2. Run the following (replace the bundle ID with your app's):

defaults delete com.developer.appname
rm ~/Library/Preferences/com.developer.appname.plist

If you don't know the bundle ID, browse to the preferences folder manually:

open ~/Library/Preferences/

Look for a .plist file that matches the app name and delete it.

Clear the app cache

rm -rf ~/Library/Caches/com.developer.appname

Relaunch the app. It will regenerate a clean preferences file on first launch.

Fix 5: Repair Disk Permissions with Disk Utility

Disk Utility's First Aid feature repairs filesystem errors and permission problems on your startup volume that can silently prevent apps from launching.

1. Open Disk Utility (Applications > Utilities > Disk Utility).
2. In the left sidebar, select your startup disk — typically named Macintosh HD.
3. Click First Aid in the toolbar, then click Run.
4. Wait for the process to complete. If errors are found and repaired, restart your Mac.

Rebuild the Launch Services database via Terminal

A corrupted Launch Services database can make macOS unable to find or register an app. Rebuild it with:

/System/Library/Frameworks/CoreServices.framework/Frameworks/LaunchServices.framework/Support/lsregister -kill -r -domain local -domain system -domain user

This command kills and rebuilds the entire app registry. It can take a minute to complete. Restart your Mac afterwards.

Bonus Fix: Remove Quarantine Flags

Apps that were re-downloaded or transferred from another Mac may carry a quarantine attribute that macOS blocks post-update. Check for it and remove it:

# Check for quarantine attribute (drag the .app into Terminal after the command)
xattr -l /Applications/YourApp.app

# If you see com.apple.quarantine, remove it:
xattr -d com.apple.quarantine /Applications/YourApp.app

If macOS says the app "can't be opened because it is from an unidentified developer", go to System Settings > Privacy & Security, scroll down, and click Open Anyway next to the app's name.

How to Prevent Apps Breaking After Future Updates

• Wait 1–2 weeks before updating: Let the early-adopter wave report problems first. Critical bugs typically get a point release (e.g., macOS Tahoe 15.0.1) within two weeks.
• Check app compatibility before upgrading: Search "[App Name] macOS Tahoe compatible" before hitting the update button.
• Back up with Time Machine first: A full backup lets you roll back if an update causes widespread breakage. Go to System Settings > General > Time Machine and run a manual backup.
• Keep apps updated: App developers release Tahoe-ready updates around the same time Apple ships the OS. Apps updated within a few weeks of the macOS release are far less likely to crash.
• Use a separate admin account for testing: Create a second macOS user with admin rights and test problematic apps there first — permission issues on the main account often don't appear on a fresh profile.

Need expert help? CloudHouse Technologies offers Pay-Per-Ticket Support — get a specialist to fix this for you.

Frequently Asked Questions

Why do apps stop working after a macOS update?

macOS updates frequently revoke app permissions, update security frameworks, and change system APIs. Apps that rely on older frameworks or were granted permissions that the new OS version now handles differently will fail to launch or crash immediately. The most common culprits in 2026 Tahoe upgrades are silently revoked Privacy & Security permissions and stale .plist preference files that conflict with the new runtime.

How do I find the bundle ID of an app to use with tccutil or defaults?

Open Terminal and run: mdls -name kMDItemCFBundleIdentifier /Applications/YourApp.app. Replace YourApp.app with the actual app filename. The command returns the bundle ID in the format com.developer.appname, which you can use with tccutil reset All com.developer.appname or defaults delete com.developer.appname.

The app was working fine before the update — do I really need to reinstall it?

Not necessarily. Start with Fix 2 (reset Privacy & Security permissions) and Fix 4 (delete the preferences file). These two steps resolve the majority of post-update crashes without requiring a reinstall, because the app binary is usually fine — it's the permissions or the now-incompatible plist that causes the failure. Only reinstall if those steps don't work.

Can I downgrade macOS if an app is permanently broken?

Yes, if you have a Time Machine backup made before the update. Boot into macOS Recovery (hold Command + R on Intel Macs, or hold the power button on Apple Silicon until startup options appear), select Restore from Time Machine, and choose a snapshot from before the upgrade. This is a last resort — exhaust all app-level fixes first and check whether the developer has released a compatibility update.

My app shows "damaged and can't be opened" after the update. What does that mean?

This error usually means the app's code signature has become invalid — either because a macOS update changed the signature verification rules, or the app binary was modified or incompletely downloaded. Fix it by removing the quarantine flag: run xattr -d com.apple.quarantine /Applications/YourApp.app in Terminal. If that doesn't work, delete the app and download a fresh copy from the official developer source.