macOS Cannot Verify That This App Is Free From Malware: Here’s How to Fix It

You downloaded an app from a developer’s website, double-clicked it, and your Mac stopped you with a message: “macOS cannot verify that this app is free from malware.” It’s one of the more confusing warnings macOS throws at you — because it doesn’t actually mean the app is dangerous. It just means Apple’s Gatekeeper security feature couldn’t confirm the app’s identity before letting it run.

This guide explains exactly what causes the error, how to tell whether the app is actually safe to open, and four different ways to fix it — from a simple right-click to a Terminal command. We’ll also cover when not to bypass the warning.

What Is the “macOS Cannot Verify” Error?

When you download an app from outside the Mac App Store, macOS runs it through a security layer called Gatekeeper. Gatekeeper checks two things before letting the app open:

• Developer ID signature — confirms the app was built by a developer registered with Apple and hasn’t been modified since.
• Notarization — confirms Apple ran an automated malware scan on the app before it was distributed.

If either check fails, Gatekeeper blocks the app and shows the warning. This does not mean your Mac is infected. It means the app didn’t pass Apple’s automated verification process. The most common reasons this happens:

Is It Safe to Open? How to Check First

Before you bypass anything, take 30 seconds to verify the app’s source. Here’s a quick checklist:

• Did you download it directly from the developer’s official website?
• Does the file name and version match what the developer’s site shows?
• Can you verify the file using a checksum (MD5/SHA) if the developer provides one?
• Is the developer well-known or referenced by trusted sources?

If you answered yes to those questions, the app is almost certainly safe and the error is a false positive. Producers using DAW plugins, audio drivers, or tools like Ableton Max for Live devices frequently run into this — because many music software developers don’t go through Apple’s notarization process.

Fix 1: Control-Click to Open (Quickest Method)

This is the fastest way to open a specific app you trust without changing any system settings. It works on macOS Ventura and earlier. On macOS Sequoia (15), Apple changed this flow slightly — see Fix 2 below.

1. Open Finder and locate the app — usually in your Downloads or Applications folder.
2. Hold the Control key and click the app (or right-click if you have a two-button mouse).
3. Select Open from the context menu.
4. A warning dialog will appear again. Click Open to confirm.
5. The app will launch. macOS remembers this choice — you won’t need to repeat it next time.

This method allowlists the specific app without touching Gatekeeper or any system-wide security setting. It’s the recommended first step for producers opening a new VST plugin or third-party DAW tool.

Fix 2: Use “Open Anyway” in Privacy & Security Settings

If the Control-click method doesn’t work — or if you’re on macOS Sequoia (15) or later — Apple routes the override through System Settings instead. This is now the primary method on newer macOS versions.

1. Double-click the app. The warning will appear. Click Done (do not click “Move to Trash”).
2. Open System Settings from the Apple menu ().
3. Click Privacy & Security in the left sidebar.
4. Scroll down to the Security section. You’ll see a message that the app was blocked.
5. Click Open Anyway.
6. Enter your Mac administrator password when prompted.
7. The app opens. macOS will remember the exemption for future launches.

Fix 3: Remove the Quarantine Flag via Terminal

When macOS downloads a file from the internet, it attaches a hidden attribute called the quarantine flag (com.apple.quarantine). This flag tells Gatekeeper to run the verification check every time the app opens. Removing it with a Terminal command tells macOS to treat the app as if it were installed locally — bypassing the check entirely for that file.

Only do this if you are confident the app is legitimate. Here’s how:

1. Move the app to your Applications folder first (optional but keeps the path clean).
2. Open Terminal — go to Applications → Utilities → Terminal.
3. Type the command below, then drag the app icon directly into the Terminal window to auto-fill its path:

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

4. Press Enter. You may be asked for your administrator password.
5. Try opening the app again — the warning should be gone.

If the app is in a different folder, replace /Applications/YourApp.app with its actual path. You can also drag the app icon straight into Terminal after typing xattr -d com.apple.quarantine (with a space at the end) to fill in the path automatically.

Fix 4: Adjust Gatekeeper Settings (App Store & Identified Developers)

If your Mac is set to allow only App Store apps, every externally downloaded app will be blocked — even ones with valid signatures. Changing this to “App Store and Identified Developers” is a reasonable setting for most users who regularly install professional software.

1. Open System Settings from the Apple menu ().
2. Click Privacy & Security.
3. Under “Allow apps downloaded from”, select App Store and Identified Developers.
4. You may be asked to enter your administrator password.

This setting still keeps Gatekeeper active — it just widens the net of apps it accepts. You’ll still see warnings for truly unverified apps, but signed software from registered developers will open without issue.

Last Resort: Disable Gatekeeper Entirely (Not Recommended)

Some guides suggest disabling Gatekeeper system-wide using Terminal. This removes all verification checks and lets any app run without warning. We’re including it here for completeness, but it is the least safe option and should only be used as a temporary measure — if at all.

To disable Gatekeeper:

sudo spctl --master-disable

To re-enable Gatekeeper after installing the app (do this immediately):

sudo spctl --master-enable

Which Fix Should You Use?