Help

Fixing the "app is damaged" warning on a Sunday

You downloaded it, you clicked it, and macOS told you the app is damaged and should go in the trash. It usually isn't damaged. The Mac is suspicious of a file that arrived from a browser, and it phrases the suspicion like a verdict. Here's what I do before I download the thing again.

The warning isn't a verdict

Gatekeeper keeps a note on files that came from the internet. That note is doing its job. The dialog just has a dramatic way of talking. If the download finished, the disk image opened, and the app copied into Applications, you are most of the way there. Trash is the wrong first move. It throws away the copy you were about to open the right way.

What I do first

1. Quit the dialog. Don't click Move to Trash.
2. Make sure the app is in Applications, not still sitting inside the disk image. Eject the image.
3. In Finder, right-click the app and choose Open. Confirm Open on the next dialog. The right-click path is allowed to trust this one file without you turning security off for the whole Mac.
4. If it opens, you're done. Use it on a test folder before the real one.

That sequence fixes the Sunday case more often than any terminal spell I used to forward to my cousin. I stopped forwarding the spell.

The quarantine flag

If right-click Open still bounces you back to the same warning, the flag is stuck. I clear it for that one app, not for everything on the machine. In Terminal, a single attribute command aimed at the app in Applications is the whole trick:

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

Replace the name. Don't point it at your home folder. Don't run a "fix all apps" script you found in a comment. One app, one flag, then try Open again. If Terminal isn't your Sunday plan, the right-click path above is the one to stay with, and you can write me instead of improvising.

When I do re-download

I download again only if the disk image never opened, or the copy in Applications is an obvious half file from a stalled browser. Six complete copies will not argue the Mac into a new opinion. One clean copy, in Applications, opened with the right-click, will.

Also check the chip. An Intel build on an Apple Silicon Mac, or the other way around, can fail in ways that look like damage and aren't. About This Mac, then the build labeled for that chip on the program page. Older versions are there for older systems. Use the line that names your macOS.

If it's a plug-in, not an app

A VST or an Audio Unit doesn't always get the same double-click life as an app in Applications. If the host says a plug-in failed to load after a fresh install, I rescan in the host first, then I look at whether the file landed in the plug-in folder the host actually reads. The damaged-app dialog is a different animal. Don't clear quarantine on a whole plug-in folder because one instrument was shy. One file, then a rescan, then a break for coffee.

If you're stuck after that, mail [email protected] with the program name, the version, and what About This Mac says. I read it on Sunday.