inge
My feedback
2 results found
-
2 votesinge
supported this idea
·
-
53 votes
We are closely monitoring the KB previously shared by Microsoft for Windows 10 | Windows 11, and we see that the issue status is marked as resolved (Resolved: 23 Jan 2026, 14:00 PT).
- Windows 11 - Resolution: This issue is resolved in the out-of-band (OOB) update released on January 24, 2026, (KB5078127), and updates released after this date.
- Windows 10 - Resolution: This issue is resolved in the out-of-band (OOB) update KB5078129, released on January 24, 2026, and available via the Microsoft Update Catalog, as well as in updates released after this date.
We have validated the fix on Windows 11 and are seeing the issue resolved. Kindly install the latest update and confirm whether it resolves the issue for you.
Thanks and Regards
Sanyam Talwar (he/him) | Adobe InDesign | Linkedin | Twitter
inge
supported this idea
·
An error occurred while saving the comment
I am experiencing repeated file corruption and save failures in Adobe InDesign when working with documents stored in cloud-synced folders (previously iCloud, currently OneDrive).
When saving an existing .indd file, InDesign displays the error message:
“Cannot save ‘[filename].indd’. The file is damaged (Error code: 2).”
After this occurs, the document can no longer be saved reliably. In some cases, only Save As IDML works. A normal Save or Save As (.indd) fails.
This issue occurs even though:
The file opens normally
There are no missing fonts
Links are valid
Disk space is sufficient
I have found that InDesign only saves reliably if the file is stored outside of cloud-synced locations (e.g. in the local Downloads folder). Saving inside iCloud or OneDrive causes the issue.
Steps to reproduce
Create or open an InDesign document (.indd)
Save the document inside a cloud-synced folder (iCloud Drive or OneDrive)
Work on the document (multiple pages, images, guides, margins)
Attempt to save
InDesign returns:
“Cannot save… file is damaged (Error code: 2)”
Expected result
The document should save normally, regardless of whether it is stored in a cloud-synced folder.
Actual result
Save fails with “file is damaged (Error code: 2)”
File may become partially corrupted
Only IDML export sometimes succeeds
InDesign lock files (~filename) remain behind
Workaround
The only reliable workaround is:
Saving and working only on local folders (e.g. Downloads or Documents outside cloud sync)
Using IDML to recover corrupted files
Additional notes
This has happened multiple times on different projects
The issue appears related to cloud sync interfering with InDesign’s save process
File sizes increase after IDML recovery, suggesting internal rebuild
This is a serious workflow risk for professional users relying on cloud backups