This browser is no longer supported.
Upgrade to Microsoft Edge to take advantage of the latest features, security updates, and technical support.
![](data:image/svg+xml, %3Csvg xmlns='http://www.w3.org/2000/svg' height='64' class='font-weight-bold' style='font: 600 30.11764705882353px "SegoeUI", Arial' width='64'%3E%3Ccircle fill='hsl(128, 8%, 22%)' cx='32' cy='32' r='32' /%3E%3Ctext x='50%25' y='55%25' dominant-baseline='middle' text-anchor='middle' fill='%23FFF' %3EA%3C/text%3E%3C/svg%3E)
I am working on my dissertation and recently purchased Word 2010. Now, when I try to open my paper I get an error message that "Word found unreadable content in....." When I select yes, to recover that contents I then get another error message that says "we are sorry. We can't open ......because we found a problem with its contents." The details then state: "Operation aborted: max-element-depth constraint violated."
I have tried doing the open and repair and then saving but nothing works...help please?
A family of Microsoft word processing software products for creating web, email, and print documents.
Locked Question. This question was migrated from the Microsoft Support Community. You can vote on whether it's helpful, but you can't add comments or replies or follow the question.
Did you work on the file while it was located on some form of removable media?
Not at all. I was working on it from my desktop where I have originally saved it. Then I cut and paste it to my USB, and when I tried to move the file again from my USB to another laptop, it gave me the above error message.
Unfortunately, your file is irretrievably corrupted.
This file needs help in recovery. Can this be recovered? Thanks! I've already tried opening the file in Word 2010 (which it is originally saved) and Word 2016 both errors. I've tried renaming to .zip so I can view the xml and most of the item I click just shows 'archive is corrupt'.
Was the document located on some form of removable media when it was last worked on in Word?
Corruption of an archive as in the case with your file is usually caused by it having been worked on from removable media.