macOS 'The application can't be opened' error fix

1. Gatekeeper's blocking the app (most common)

You just downloaded that new app, double-clicked, and — nothing. Or you get “The application can’t be opened” with a note about an unidentified developer. I’ve seen this dozens of times on macOS Ventura, Sonoma, and Sequoia. The fix is simple, but Apple hides it well.

Here's what's happening: macOS has a security feature called Gatekeeper. It checks if an app is signed by an Apple-approved developer. If it’s not, or if it was downloaded from the web (not the App Store), Gatekeeper stops it from opening. This tripped me up the first time too.

Fix:

1. Open System Settings (or System Preferences on older macOS).
2. Go to Privacy & Security.
3. Scroll down to the Security section.
4. You’ll see a message like “App was blocked from opening” with an Open Anyway button next to it. Click that.
5. Enter your admin password when prompted.
6. Try opening the app again. It should work now.

Real-world scenario: I saw this with Macs Fan Control after a clean install of macOS Sequoia. The app downloaded fine, but the Gatekeeper alert only shows up for a few minutes after the first failed launch. If you missed it, re-download the app and try again quickly — or use the Terminal method (next section).

Pro tip: If the Open Anyway button didn’t appear, or you waited too long, you can manually clear the quarantine attribute via Terminal:

xattr -d com.apple.quarantine /Applications/YourApp.app

Replace YourApp.app with the actual app name. This tells macOS, “Yeah, I trust it.” Works every time.

2. The app is damaged or incomplete

Sometimes the error says “The application can’t be opened” without any Gatekeeper mention. That usually means the app file is corrupt or the download got cut off. I see this a lot with large apps like Adobe Creative Cloud or Final Cut Pro when the download’s interrupted.

Fix:

1. Delete the app from your Applications folder. Drag it to Trash.
2. Re-download the app from the official source. Don’t use a third-party site.
3. If it’s a DMG file, re-mount it. Sometimes the DMG itself is corrupt — redownload that too.
4. Check the file size: if it’s way smaller than expected (e.g., a 500 MB app shows 50 MB), the download failed.

Quick test: Open Terminal and run:

file /Applications/YourApp.app

If it says “cannot open” or “empty”, the app is hosed. Re-download.

Why this happens: Spotty Wi-Fi, VPN interruptions, or browser download managers that pause mid-transfer. I’ve also seen this on macOS Monterey when downloading via Safari — sometimes it just drops part of the file. Use a wired connection or a download manager like Folx if you’re on unreliable networks.

3. Permissions or cache corruption

Less common, but I’ve hit it: the app’s permission settings are messed up, or your macOS launch services cache is stale. This can give you the same “can’t be opened” error even when the app is fine and Gatekeeper isn’t involved.

Fix — Reset launch services database:

1. Open Terminal from Applications > Utilities.
2. Run this command:

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

3. Enter your admin password when asked.
4. Quit Terminal and try opening the app again.

Why it works: The lsregister tool rebuilds the database that Mac uses to figure out which app opens what. After a failed app install or a weird update, that database can get confused. This clears it out. I do this every time I install a new macOS version — it prevents tons of weird app-opening errors.

Still stuck? Check the app’s permissions — right-click the app in Finder, choose Get Info, and make sure your user account has Read & Write under Sharing & Permissions. If not, click the lock icon, add yourself, and set it.

Quick-Reference Summary Table

One last thing: If you’re running macOS Catalina or older, the “Open Anyway” button is in System Preferences > Security & Privacy > General. Same fix, slightly different layout. And if you’re on a corporate Mac with managed profiles (like Jamf), you might need IT to whitelist the app. That’s a whole different headache — but the steps above cover 95% of the cases I’ve handled.

Got another error? Hit me up in the comments. I’ll help you sort it out.