macOS 'You don't have permission to open the application' fix

macOS Errors Beginner 👁 1 views 📅 May 28, 2026

This error pops up when macOS Gatekeeper blocks an app from an unidentified developer. Fix it by removing the quarantine attribute or manually allowing the app in Security & Privacy.

What triggers this error

You download an app from outside the Mac App Store — maybe a DMG from GitHub or a direct download link. Double-click it, and instead of launching, you get a dialog: "You don't have permission to open the application." The app icon sits there mocking you. This almost always happens with apps from developers Apple hasn't vetted, especially on macOS Catalina and later (10.15+). I've seen it most with open-source tools, beta builds, or older apps that haven't been updated for Apple's notarization requirement.

The culprit here is almost always a single file attribute called com.apple.quarantine. macOS slaps this on any app downloaded from the internet (any browser, email attachment, chat download). It's a security flag that tells Gatekeeper: "Check this app before letting it run." If the app isn't signed by an Apple-identified developer or notarized by Apple, Gatekeeper blocks it with that permission error.

Why this happens (the short version)

Apple's security model since macOS Catalina has gotten stricter. Gatekeeper checks two things:

  1. Is the app signed with a valid Developer ID certificate?
  2. Has the app been notarized by Apple (scanned for malware)?

If either check fails, macOS throws that permission error. The quarantine attribute is the trigger — it tells the system to perform the check. Remove the attribute, and the app runs. Simple.

Step-by-step fix

Option 1: The quick fix (remove quarantine attribute)

  1. Open Terminal (Finder > Applications > Utilities > Terminal).
  2. Type this command, but don't hit Enter yet:
    xattr -d com.apple.quarantine 
  3. Drag the offending app from Finder into the Terminal window. This will add the full path to the command. It should look like:
    xattr -d com.apple.quarantine /Applications/SomeApp.app
  4. Press Enter. You won't see any output if it works.
  5. Try opening the app again.

What if xattr says "No such xattr"? That means the quarantine attribute isn't present. That's weird — it usually is. Skip to Option 2.

What if xattr says "Operation not permitted"? You don't have write permission to the app's location. Move the app to your Applications folder first, then run the command again.

Option 2: Allow via System Settings (when xattr doesn't fix it)

  1. Open System Settings (or System Preferences on older macOS).
  2. Go to Privacy & Security.
  3. Scroll down to the Security section.
  4. Look for a message that says something like "[App Name] was blocked from opening because it is not from an identified developer."
  5. Click Allow Anyway.
  6. Enter your admin password (or use Touch ID).
  7. Close System Settings. Open the app again — this time macOS will ask you to confirm you want to open it. Click Open.

Note: This option works even if you already removed the quarantine attribute. It's the fallback when Gatekeeper still says no.

Option 3: The nuclear option (disable Gatekeeper entirely — not recommended)

  1. Open Terminal.
  2. Run:
    sudo spctl --master-disable
  3. Enter your admin password.
  4. Now any app will open without checks. To re-enable Gatekeeper later, run:
    sudo spctl --master-enable

I only suggest this for power users who install tons of unsigned apps and understand the risk. For everyone else, stick with Option 1 or 2.

What if it still fails?

Two things to check:

  • The app is damaged or incomplete. Redownload it from the source. A corrupted download won't open no matter what you do.
  • You're on a managed Mac. If your work or school issued you this Mac, your IT department may have MDM profiles that block specific apps. Check System Settings > Privacy & Security > Profiles. If you see profiles, talk to your admin.
  • The app is an older PowerPC or 32-bit Intel app. macOS Catalina and later dropped 32-bit support entirely. Check the app's system requirements — if it requires an older OS, it won't run on modern macOS.

I've fixed this exact issue for dozens of users. The quarantine attribute removal works 90% of the time. The other 10% it's either a permissions issue (which Option 2 solves) or a dead app that needs an update. Good luck.

Was this solution helpful?