Skip to main content
Inspiring
November 4, 2022
Answered

Problem continues: Updating to InDesign 2023 (v18.0), causes (all) files to open as "damaged"...

  • November 4, 2022
  • 1 reply
  • 2780 views

I'm about to loose my mind here!

I have made multiple resets of preferences, installed and uninstalled both 2022 and 2023 (same problem in both) and I have even done a reinstall of OS X Monterey. I have made a Repair run with Disk Tool, but no errors was found.

And the result is the same every time - I works just fine with the first couple of files, I open - then it starts with the "File is damages" and so on.

As strange as it sounds, I can (most of the time) bypass this error, by finding and double-clicking the indd-file in Finder and open it that way.

We have 3 other Macs working in the same environment/version OS X - none of those experience this problem.

Adding insult to injury, when opening a "damaged" file, it sometimes ignores the latest "save" and reverts to an earlier save - I don't have to tell you, that this is BAD (and that it has already cost us money!).

I just HAVE to fix this.
Right now I'm just about out of ideas and I'm thinking about another reset and then just try to work in an unadjusted environment - but I don't see, how that could possible change anything?
I'm getting to the point, where I'm desperate enought to try updating to Ventura, hoping that it might fix things!
Happy thoughts,
Jesper...

 

This topic has been closed for replies.
Correct answer Abaddonis

Hey

 

The link I provided gives different methods to resetting your preferences, into a deeper reset of preferences. It's worth checking out.

 

The Cleaner Tool might help - as it removes all the folders and reinstalls everything. 

 

Not everyone is having these issues, and we've seen 3rd party apps cause issues, corrupt user profiles, and various other things causing issues. 

 

If it's still persisting, I would suggest to start up in Safe Mode - and open InDesign and see if the problem is persisting. 


If it's ok it's likely a 3rd party app clashing. 

 

 


You mentioning "Corrupt user profiles" made me think about what settings I normally adjust.
Tried using a generic workspace - no changes.
Tried using default keyboard shortcuts - EUREKA - for now, at least, I can open documents without the "Damaged" error!!

Fingers crossed, that it holds - but what an absurd solution, if that was it??
Thinking positive thoughts - poooooositive thoughts...

1 reply

Community Expert
November 4, 2022

Try resetting your preferences:
The easiest way to reset everything is to delete the InDesign preferences: as soon as InDesign starts to boot hold down Shift, Alt, Ctrl (and Apple/Cmd if working on a Macintosh). A dialog will appear asking to delete the InDesign Preferences, select 'Yes' on this dialog.
Further info and instructions here if needed:
https://helpx.adobe.com/in/indesign/kb/indesign-preferences-support-file-locations.html

 

 

A complete reinstall

---

Reinstalling rarely fixes everything - you can do a complete reinstall using the
Creative Cloud Cleaner Tool https://helpx.adobe.com/creative-cloud/kb/cc-cleaner-tool-installation-problems.html

 

 

AbaddonisAuthor
Inspiring
November 4, 2022

As I wrote, I have already done the preferences-reset several times without any lasting results.
Okay, I will try the CC Cleaner, if my "reset preferences and work without changing any settings" experiment does not work.
But D*MN, this is an uphill battle - I think it would make even Sisyfos assume the fetal position!

Community Expert
November 4, 2022

Hey

 

The link I provided gives different methods to resetting your preferences, into a deeper reset of preferences. It's worth checking out.

 

The Cleaner Tool might help - as it removes all the folders and reinstalls everything. 

 

Not everyone is having these issues, and we've seen 3rd party apps cause issues, corrupt user profiles, and various other things causing issues. 

 

If it's still persisting, I would suggest to start up in Safe Mode - and open InDesign and see if the problem is persisting. 


If it's ok it's likely a 3rd party app clashing.