Problem with "is damaged and can’t be opened. You should move it to the Trash."

[padaxax]

Hello guys,

I have following problem with my brand new MBP 15 late 2016:

Since I updated the OS to 10.12.3. I receive the following message whenever I open any file on my Mac:

"document1.pdf is damaged and can’t be opened. You should move it to the Trash."

It is equal what kind of file I open, let it be .pdf .docx .jpeg - I always receive the message from above. However I can view the files by using preview with the blank key.

I figured out, that it has to do with gatekeeper settings. When I change the settings from "App Store" to "App Store and verified developers" first the system does not save my selection and second I still can not open any file on my mac.

I then found a way to disable gatekeeper by using following terminal command sudo spctl --master-disable and I am now able to open any of my files just like normal.

But this is not a long term solution, since I want my mac to stay safe.

Does anyone know what else I could do?

 

[Sanpete]

Have you used any unusual software, beyond the software that comes on your machine and other standard software? There have been reports of particular programs causing this issue.

You may not need to use terminal, by the way, but you probably don't want to do the following for each file.

https://support.apple.com/kb/PH21769?locale=en_US

 

[keysofanxiety]

Had this issue on an almost new delivered Mac (just a couple of days old). Nothing else was installed following its delivery, simply because they weren't able to due to the problem. Updating the OS from 12.2 to 12.3, a repair install (not wiping first) through Recovery OS, PRAM/SMC reset, Safe Mode boot, or 45 minutes to Apple Support didn't resolve the issue. Problem persisted every single time.

That's the one and only time I've encountered this problem on a Mac – where anything you download from the Internet comes up with that damaged error. No matter what type of file it is: dmg, pkg, zip, app, docx, pdf...

Backing up the user data and wiping/reinstalling the OS fixed the problem. Whilst I appreciate that the nuclear option isn't much of a 'fix' – granted, it's almost always the final desperate troubleshooting step – I can only assure you I spent ages trying to permanently solve it without any luck. So it may be best to cut your losses now and go that route. Sorry it's not the resolution either of us wanted.

 

[Mindinversion]

I would download Onyx and do an automated cleanup [which fixes permissions among a great deal of other things]

Sometimes it's better to do a system analysis before taking off and nuking the site from orbit... Even if you KNOW that it's the only way to be sure

 

[padaxax]

Thanks for the replies. I just reinstalled macOS and it is now working okay.