macOS 'The application could not be launched' – Fix for M1/M2 Macs

You just double-clicked that old app you downloaded—maybe a game, a utility from 2019, or some office tool. The icon bounces once, then stops. A dialog pops up: "The application could not be launched." No error code, no details. Just that cold dead-end.

On Apple Silicon Macs (M1, M2, M3), this usually means one of two things: the app is 32-bit (macOS hasn't supported those since Catalina), or the app needs Rosetta 2 and you don't have it installed yet. It can also happen with unsigned apps from small developers.

I know this is frustrating—you just want to use the software. Let's get you sorted.

Why this happens

macOS dropped 32-bit app support back in macOS 10.15 Catalina. If your app is old enough to still be 32-bit, it simply won't run on any modern Mac, M1 or Intel. The system won't even give you a clear warning.

If the app is 64-bit but built for Intel, your M-series Mac needs Rosetta 2 to translate it. Rosetta 2 is not installed by default on some Macs—especially if you didn't run any Intel app yet. You might have skipped the prompt when you first set up your Mac.

Another possibility: macOS Gatekeeper blocks apps from unidentified developers. That triggers a different error usually, but sometimes it falls through to this vague message.

Step-by-step fix

1. Check if the app is 32-bit

1. Open Terminal (from Utilities folder inside Applications).
2. Drag the app from Finder into Terminal to get its full path. Or type: file /Applications/AppName.app (replace AppName with the actual folder name).
3. Look at the output. If you see Mach-O 32-bit executable, it's 32-bit and can't run on any modern macOS. No fix will work.

If you see Mach-O 64-bit executable x86_64, it's a 64-bit Intel app. That's good. Move to step 2.

2. Install Rosetta 2 (if not already)

Open Terminal and paste this command:

softwareupdate --install-rosetta

You'll be prompted to agree to the license. Type A and press Enter. The installation is quick—maybe 30 seconds. Once it finishes, relaunch the app.

If it still fails, manually trigger Rosetta 2 installation by opening any Intel-based app (like GarageBand or a game) and letting it prompt you. But the command above is more reliable.

3. Try opening it via Terminal directly

Sometimes the Finder's launch mechanism fails silently. Use:

open /Applications/AppName.app

This bypasses some LaunchServices caching and may give you a more descriptive error message in Terminal (like "Library not loaded" or "code signing blocked").

4. Check Gatekeeper and quarantine attributes

macOS tags downloaded apps with a quarantine flag. Remove it with:

sudo xattr -d com.apple.quarantine /Applications/AppName.app

Then right-click the app in Finder and select Open (instead of double-clicking). That forces the Gatekeeper warning to show, and you can click "Open anyway."

5. Verify app architecture using System Information

If the app launched even once before, check its architecture in System Information > Software > Applications. Look at the "Kind" column. If it says "Intel," Rosetta is needed. If "Apple Silicon," the app is native and something else is wrong—possibly a damaged download or incompatible version.

What to check if it still fails

• Re-download the app. Corrupted downloads happen. Get the latest version from the developer's site, not a third-party mirror.
• Check macOS version compatibility. Some old apps only run on macOS 10.14 or older. Look at the developer's website or the app's Info.plist (right-click app > Show Package Contents > open Info.plist in TextEdit). Search for LSMinimumSystemVersion—if it's below 10.15, you're stuck.
• Try a free alternative. If the app is abandonware, there's often a newer, better option. For example, instead of an old FTP client, use FileZilla or Cyberduck.
• Use Activity Monitor. Launch it, then try opening the app. Watch for a new process that appears briefly then exits. That can give you a hint—like "not valid architecture" or "crash due to missing library."
• Run the app from a different user account. Create a new admin user in System Settings > Users & Groups. Log into that account and try launching the app. If it works, the problem is in your user Library (caches, preferences).

The ugly truth: some apps simply won't run on Apple Silicon. If it's 32-bit, there's no workaround. But if it's just Rosetta missing or a quarantine flag, you're back in business in under two minutes.

One last thing: if you see "The application could not be launched" on an app that used to work, check if macOS recently updated. Sometimes a system update resets Rosetta permissions or changes signing requirements. Reinstalling the app usually fixes that.