Most “App Cannot Be Opened” alerts on a Mac come from Gatekeeper checks, missing permissions, or a broken install, and you can fix them fast.
You click an app, and macOS throws the app cannot be opened mac message. Maybe it says the app is “damaged,” or it can’t be checked for “malicious software,” or it’s “from an unidentified developer.” It isn’t personal.
macOS is doing its job: it’s trying to stop new, untrusted software from running until you confirm it’s safe. The trick is knowing which warning you’re seeing and using the safest override that fits.
What The Message Usually Means
Most blocked-app messages fall into a few buckets. Some are normal first-run checks. Others point to a download that got altered, an app that doesn’t match your Mac’s chip, or a file that landed in the wrong place.
Before you start flipping switches, read the wording.
| Message You See | Likely Cause | Fix To Try First |
|---|---|---|
| “… cannot be opened because it is from an unidentified developer” | Gatekeeper blocked the first launch | Use Finder > Open, then approve in Privacy & Security |
| “… cannot be opened because Apple cannot check it for malicious software” | Not notarized, altered, or quarantined download | Confirm source, then use Open Anyway or remove quarantine |
| “… is damaged and can’t be opened” | Corrupt app bundle or failed update | Re-download from the maker, then reinstall clean |
| App bounces once, then quits | Missing access, plugin crash, or bad settings | Check Privacy permissions, then reset app settings |
| “You can’t open the application” on Apple silicon | Intel-only app without Rosetta or outdated build | Install Rosetta if prompted, or get a universal build |
Quick Safety Checks Before You Override Anything
If the app came from a random file mirror, pause. A safe fix starts with a safe download. If you got the app from the Mac App Store, the blocks below rarely apply.
- Download From The Publisher — Use the maker’s site or the Mac App Store, not a repackaged copy.
- Compare The File Name — If the name has extra words like “cracked” or “free,” delete it.
- Scan The Installer — Use your Mac’s built-in malware checks and any trusted security tool you already run.
App Cannot Be Opened Mac On First Launch
This is the common “I just installed it” moment. You double-click, you get a warning, and you want to open the app once without turning your Mac into an open door.
Start with the least invasive route. It leaves Gatekeeper on, it logs your approval, and it avoids wide system changes.
Use Finder’s Open Command
macOS treats “Open” from Finder as an explicit user choice. That small difference often turns a hard block into a one-time confirmation.
- Find The App In Applications — Open Finder, click Applications, and locate the app you installed.
- Open The Context Menu — Control-click the app icon, then choose Open.
- Confirm The Prompt — Click Open again on the dialog, then enter your Mac password if asked.
Approve The App In Privacy And Security
If you tried to open the app and it was blocked, macOS adds a short-lived approval button in Settings. You’ll usually see it for about an hour after the block.
- Open System Settings — Click the Apple menu, then choose System Settings.
- Go To Privacy & Security — Scroll until you see the Security section.
- Click Open Anyway — Confirm you want to run the app, then authenticate.
After you approve it once, the app should launch like normal. If the warning returns every time, skip ahead to the quarantine and permissions section.
Fixing An App That Cannot Be Opened On Mac Safely
Sometimes you need more context than a single dialog gives you. This section helps you tell a safe one-time override from a broken install that will keep failing.
Match The Warning To The Right Fix
- Unidentified Developer — Use Finder Open or the Open Anyway button. Don’t disable Gatekeeper for this.
- Cannot Check For Malicious Software — Treat it as a trust check. Confirm the source, then approve or remove quarantine.
- Damaged — Don’t force it. Re-download and reinstall, since the app bundle may be corrupted.
Confirm The App Is Signed Before You Trust It
If you’re comfortable with Terminal, you can ask macOS what it thinks about the app’s signature. This does not “fix” the app by itself, but it can keep you from approving a sketchy copy.
- Open Terminal — Use Spotlight, type Terminal, and press Return.
- Run A Gatekeeper Check — Type
spctl -a -vv /Applications/AppName.appand press Return. - Read The Result — Look for lines that mention a valid developer ID and notarization status.
If the path is tricky, drag the .app from Finder into the Terminal window after the command, then press Return.
Check Compatibility, Updates, And Install Location
An app can be “fine” and still refuse to open on your Mac. Chip type, macOS version, and install location can block launches in ways that look like security warnings.
Verify Your Mac’s Chip And The App Build
Apple silicon Macs can run Intel apps through Rosetta 2. Many apps install Rosetta on demand. If you see a prompt to install Rosetta, that’s the intended path.
- Check Your Chip — Apple menu > About This Mac shows Apple silicon or Intel.
- Update The App — Grab the newest build from the publisher, since older builds can fail to launch.
- Install Rosetta When Prompted — Open the Intel-only app and accept the install prompt if it appears.
Make Sure The App Lives In Applications
Running apps from Downloads, a zip preview, or an external drive can keep the quarantine flag in place and can break helper tools. Copy the app into /Applications, then try again.
- Drag The App To Applications — From Finder, move the .app bundle into Applications.
- Eject Disk Images — If the app is inside a .dmg window, copy it out first, then eject the .dmg.
- Try A Fresh Launch — Quit the installer window and open the app from Applications.
Refresh macOS And Restart Clean
Updates include security data, certificate updates, and bug fixes that affect app checks.
- Restart The Mac — A full reboot clears stuck helper processes and login items.
- Install macOS Updates — System Settings > General > Software Update.
- Update Built-In Security Data — Let the Mac sit online for a few minutes after updating so background updates can finish.
Use Terminal For Quarantine And Permission Fixes
If you trust the app and the safe UI approvals still fail, the culprit is often a quarantine tag left on the file or a permission issue inside the app bundle. Terminal can fix that without turning off macOS protections across the board.
Remove The Quarantine Attribute From A Trusted App
Downloads often carry an extended attribute that marks them as “quarantined.” Gatekeeper uses it to decide when to show warnings. Removing it from a trusted app can stop repeat blocks.
- Move The App To Applications — Don’t run this on a copy sitting in Downloads.
- Run The Quarantine Removal — Type
sudo xattr -r -d com.apple.quarantine /Applications/AppName.app. - Enter Your Password — Terminal won’t show characters as you type; press Return when done.
If you see “No such file,” check the path. The easiest fix is to type the command, add a space, then drag the app into Terminal to fill the path.
Fix Execute Permission When An App Bundle Was Altered
Some apps arrive inside archives that change execute bits, or the app gets modified by a cleanup tool. If the app opens once and then refuses, permissions can be the reason.
- Locate The Binary — Many apps store the executable in
AppName.app/Contents/MacOS. - Restore Execute Bits — Try
chmod +x /Applications/AppName.app/Contents/MacOS/*. - Launch Again — Open the app from Applications and watch for a different error message.
Reset Gatekeeper The Safe Way
You’ll find old advice that says “disable Gatekeeper.” On newer macOS releases, those Terminal toggles are restricted or require extra confirmation. A safer habit is to keep Gatekeeper on and approve only the app you trust.
- Prefer Open Anyway — It’s per-app and leaves system checks intact.
- Delete Suspicious Copies — If an app needs wide bypass steps, treat that as a red flag.
- Reinstall From A Clean Source — A fresh download can remove the need for Terminal tweaks.
When It Still Won’t Launch
When nothing above works, stop trying random tricks. You want a clean diagnosis: does the app fail for your user account, for the whole Mac, or only in one working setup?
Try Safe Mode And A New User Account
Safe Mode starts macOS with fewer extras. A new user account isolates settings. Together, they tell you whether a login item, font, plugin, or permission is blocking the app.
- Boot Into Safe Mode — Restart and hold Shift on Intel, or hold the power button on Apple silicon until startup options show, then choose Safe Mode.
- Test The App — Open the app from Applications and note what changes.
- Create A Test User — System Settings > Users & Groups, add a fresh user, then try the app there.
Repair The Disk And Check Free Space
Apps fail to open when the disk is full or the file system has errors. You don’t need to guess. macOS includes Disk Utility for this job.
- Free Up Space — Leave at least several gigabytes available so the app can write caches and updates.
- Run First Aid — Open Disk Utility, select the startup disk, and run First Aid.
- Reinstall The App — Delete the app, empty the Trash, then install again.
Clean Reinstall Without Leftovers
A drag-to-Trash uninstall can leave settings behind. If a bad preference file is crashing the app at launch, a clean reinstall is the fix.
- Remove The App — Drag it from Applications to Trash.
- Remove Related Files — In Finder, use Go > Go to Folder and check
~/Library/Preferences,~/Library/Caches, and~/Library/Containersfor related files. - Install Again — Download a fresh installer and run it, then open the app once from Applications.
Know When To Stop And Ask The Developer
If you’ve verified the download source, checked signatures, and the app still refuses to open, the build may be broken on your macOS version. Grab the exact error text and the app version number, then send it to the developer.
If you’re writing a help article for others, tell readers to share the exact wording and macOS version. That single line often points straight to the fix.
If you landed here after searching “app cannot be opened mac,” start again with the message table at the top, then follow the matching path. Often.
