After High Sierra Update all files report "damaged and can't be opened"

"file damaged can't be opened move to trash" Same here. On a mid 2010 15" MacBook Pro os 10.13.1.

Now if I return to my studio I can open it from my late 2012 mac mini os 10.13.1 from the iCloud desktop. When I re save it will become openable again from the MacBook Pro. Really killing my work flow. BTW the files are SketchUp Pro 2018. Seems to be related to iCloud. Ideas?

I had the same issue but had kept all my old files on my previous Mac - so simply copied them over again and they seem to be working ok now. However, I cannot download software and install - my system preferences keeps reverting to "apple only" even though I keep unchecking it. Trying the gatekeeper disable to see if that helps. Am on 10.13.2, only had this new MBP 5 days and hating this OS already - nothing but problems (wi-fi keeps dropping too, yet another fix)

I utilized the migration assistant and still am getting the errors on files that are downloaded, even .zip files being opened by the default Mac app.

I am not sure if it is related, but I also cannot change the General Security settings to accept Apps downloaded from App Store and identified developers. I can change the radio button but it will revert back to App Store only when I pull up the screen again.

I have the same problem. I can't even open a PDF. System preferences keeps reverting to App Store only, even though I changed it to App Store and identified developers. MacOS 10.13.1. Yes, previewing the file works perfectly. A fix is urgently needed.

I have same issues; I also used Migration Assistant to move files; it corrupted the permissions on my .ssh/ directory and on the encryption keys inside there. It complains that PDFs that are openable on my wife's older MacBook or on my Late 2012 MBP running the latest version of software.

This is the most annoying bug I've encountered in the 30 years I've been a Mac User...

Facing the same issue. This is what I did :

• bought a new MBP 2017 with pre-installed 10.12.x
• clean installed 10.13.1 after erasing Macintosh HD
• As a last step of clean install, transferred data from old MBP (mid-2010) using migration assistant

Now, when I click on a transferred file, first time it opens as expected. If I close it and try to re-open it by clicking on it again, it shows a message saying this file is damaged and move it to trash.

What is the solution? I can't use my new MBP without the data!

Everything is getting worse suddenly.

Some two days old pdf became unreadable. And also pngs or keynote file.

It seems to be random. Foto library seems to be ok at the moment, but who knows...

What's happening Apple?

Every helps appreciated!

I'm on 10.13.2 after migrating from my previous iMac. The same problem. Can't even change the security option "Allow apps downloaded from" to "App store and identified developers"

It got "unchecked" after each reboot :-(

I'm so dissapointed with Apple - their software is getting worse with each release. I have spent HUGE amount of money on a new iMac 2017 because the old one (2009) was suppose to have problems with High Sierra.

Migration was a nightmare for the first time and now this problem.

APPLE what the ... has happened to you !

Can confirm this fixed my issue.

Used migration tool to move from 2013 13" Macbook Pro Retina to New 2017 Macbook Pro 15.4" and files were all damaged etc. Actually got the error when after dowloaded the newest Parallels, tries to install and it said the same thing, I was worried but thanks for this advice!

I did the same exact thing as you have described and have the same problem. On hold w Applecare now. This is beyond frustrating.

I can confirm that this fix works!!

Hopefully Apple will fix this soon so we can get back to having just the checkbox for opening apps from Apple Store and known developers checked.

I just found that I can no longer update IntelliJ IDEA or its plugins. It cannot access the files for update. This app isn't bought through the app store.

Seems fixed for me too, but not sure what exactly caused the problem. Didn't see anything relevant in the release notes.

At least there was a simple fix - reinstalling your whole d-m machine

Had to do the same thing and i downgraded to Sierra ...