SYMPTOMS
The macOS installation can sometimes fail with the error Nuke [version] is damaged and can’t be opened. You should move it to the Bin. This issue has been reported by macOS users, and the error looks something like the image below:

CAUSE
When installing Nuke, there is a potential conflict with security features that invoke the Nuke is damaged... message when launching the software. From further investigations, it looks like macOS’s Gatekeeper security application appends an attribute to Nuke, suspending it from opening at launch and displaying the aforementioned error.
RESOLUTION
If you’ve received the above error message when launching Nuke after installation on macOS, please follow the steps outlined below.
Temporarily override your Mac security settings to open the software:
In macOS an application can fail to install or launch because it hasn’t been notarized, or is from an unidentified developer. This failed application will appear in the Gatekeeper security settings: Apple Menu > System Preferences > Privacy & Security > Security section. Click the Open Anyway button to confirm wanting to open or install the application, as shown below:NOTE: If you're prompted to open Finder, command-click the app in Finder, choose Open from the menu, and then clickOpen in the dialog that appears. Enter your administrator name and password to open the application.
Nuke should now be saved as an exception in your security settings, and you can open it in future instances by double-clicking it, just as you can any authorized application..Alternatively, you can use Terminal to temporarily disable all the security features of Gatekeeper. Please keep in mind that disabling the security software will leave your machine open for intrusion by unwanted software, such as malware.
If you’d like to continue in disabling Gatekeeper, please run the following command in Terminal:
sudo spctl –master-disable
sudo spctl –master-enable
Disabling or removing specific extended attributes to launch Nuke:
WARNING: The following information is not a recommended process because modifying extended attributes may have unintended or unforeseen consequences. Performing the steps below is at your own risk.1. As an Administrator, please run the following command in Terminal to view any extended attributes of the application (with Nuke installed to the default location):
sudo xattr /Applications/Nuke16.0v4/Nuke16.0v4.app
Running the above command should give results similar to the following:
com.apple.quarantine
should be present for Nuke, and will prevent the application from launching. If this line is present for the Nuke application, please proceed to the next step to remove it.2. As an Administrator, run the following command in Terminal to remove the quarantine extended attribute:
sudo xattr -d com.apple.quarantine /Applications/Nuke16.0v4/Nuke16.0v4.app
Alternatively, if you’d like to remove all extended attributes of the application, please use the following code:sudo xattr -cr /Applications/Nuke16.0v4/Nuke16.0v4.app
NOTE: The -c flag removes all attributes, whereas -r applies recursively for the entire targeted .app directory contents. More information on these flags can be found with the xattr -h flag in Terminal, or by viewing content in the Further Reading section below.
After removing the
com.apple.quarantine
extended attribute that was assigned by Gatekeeper, Nuke should now be able to launch without the Nuke is damaged error.FURTHER READING
- Please review the following for more information on the macOS Gatekeeper application
-
For further understanding of the Gatekeeper command, please review this link
-
Additionally, please view more information of the xattr command attributes
FURTHER HELP
If you are still experiencing issues when launching Foundry software after performing the steps above, please open a Support request and let us know the exact issue encountered and the troubleshooting steps that have been taken.
For more information on how to open a Support request, please refer to this article: Q100064: How to raise a support ticket
We're sorry to hear that
Please tell us why