Home › Help
macOS calls the app or plug-in damaged
This note is the one I send when a plug-in or a small utility arrives from outside the App Store and macOS refuses it with the word damaged. It is the same dialog for an equaliser and for a menu-bar tool. The wording is dramatic. The cause is usually a quarantine flag, not a broken file.
What the dialog usually means
Gatekeeper marks files that came from the internet. The first launch then warns you. Damaged, in this particular sentence, often means the mark is there and the signature check stopped, not that the bytes are corrupt. If the download was cut off, you will usually see a different failure, earlier, when the disk image will not open at all.
Open it once from Finder
Before any terminal command, try the ordinary route. Find the app in Finder, control-click it, and choose Open. macOS then offers a button that the double-click dialog hid. Confirm it. After that one launch, a normal double-click is enough. This is the step I want people to try first, because it does not involve typing paths.
The quarantine attribute
If Finder still refuses, the quarantine attribute can be cleared for that one app. The command is specific. Replace the path with the app you actually downloaded. Do not point it at your whole Applications folder.
xattr -d com.apple.quarantine /Applications/Example.app
Run it, then try Open again. If the attribute was not there, the command will say so. That is fine. It means the problem is somewhere else, usually a signature the system does not accept, and clearing a flag that is not present will not invent one.
Plug-ins, not just apps
Audio plug-ins do not live in Applications. An Audio Unit sits in /Library/Audio/Plug-Ins/Components. VST3 sits in /Library/Audio/Plug-Ins/VST3. The same attribute can stick to the component. Logic and Reaper then skip it at scan time, sometimes with a quieter error than the damaged dialog.
- Rescan in the DAW before you delete anything.
- If you clear quarantine, clear it on that component, not on every file in the plug-in folder.
- A failed scan is not a reason to remove a different manufacturer's plug-ins to make room.
What I do not do
I do not install a tool whose only job is to turn Gatekeeper off. I do not run a command I found under a video. I do not delete the receipt database because one AU failed. If the developer did not sign the build, it stays off the studio Mac. A catalogue page is not a promise that every mirror is intact. Check the size against the page, and stop if the disk image will not open.
Accounts, favorites and comments are a separate matter. They are explained in the about page. They do not change how macOS treats a file.