Fix it now
Word is refusing the document for one of two unrelated reasons: it does not trust where the file came from, or it cannot read what is inside it. Settle which before you repair anything, because the two fixes have nothing in common and the repair one rewrites the file.
- Right-click the file in Explorer, choose Properties, and look at the General tab. If an Unblock checkbox is offered, tick it, click OK and reopen. That is the whole fix for most documents that arrived by email or download.
- Copy the file to a short local path such as C:\Temp and open it from there, which rules out a long path, a network location and a sync folder in one move.
- If it still refuses, work on a copy from here on. Use File > Open, select the file, click the arrow beside the Open button, and choose Open and Repair.
- If that fails, open the same dialog, set the file type list to Recover Text from Any File (*.*), and open the document again. You lose the formatting and usually keep the words.
- If every document fails rather than this one, start Word with its default settings by running winword.exe /a, which is the switch Microsoft documents for exactly this test.
Take the copy before the first repair, not after the first failure. Open and Repair and the text recovery converter both rewrite what they open, and a half-successful repair can leave you with less than you started with.
If the document opens and its content is intact, stop here. If it opens with holes in it, or will not open at all, the next section separates the trust problem from the damage problem.
Why it happens
A document that arrived from outside the machine carries a marker recording where it came from. Microsoft calls it the Mark of the Web, and Office reads it before it reads the document: files carrying it open in Protected View, and their macros are blocked outright. Nothing is wrong with the file; a rule is being applied to it. Clearing the marker is the Unblock checkbox on the General tab of the file’s properties, and putting the file in a Trusted Location makes Office skip the check altogether.
Damage is a different animal. Microsoft’s own list of what a damaged document looks like is mostly not “will not open”: pages that renumber themselves, page breaks that keep redoing themselves, wrong layout and formatting, unreadable characters on screen, errors during processing, and a machine that stops responding on open. A document that opens badly is as damaged as one that will not open, and has more recovery routes available.
0x80070570 sits below both of those. It is Windows error 1392, ERROR_FILE_CORRUPT, published as “The file or directory is corrupted and unreadable”, and it comes from the file system rather than from Word. Seeing it means the storage layer could not hand over the bytes, so the useful next move is to fetch a fresh copy from the source and look at the disk, not to run a document repair against a copy that was never read correctly.
The file is marked as coming from outside
You have this one if It arrived by email, download, chat or a copied USB stick, and Properties offers an Unblock checkbox.
- Tick Unblock on the General tab of the file’s properties, apply, and reopen.
- For a batch, run Get-ChildItem over the folder and pipe it to Unblock-File in PowerShell.
- If your team receives such documents constantly, add the folder as a Trusted Location instead of unblocking one file at a time.
Only trust a folder you control and that ordinary users cannot write to. A Trusted Location makes Office ignore the Mark of the Web for everything placed in it, including anything an attacker manages to drop there.
The document itself is damaged
You have this one if It fails on every machine, or it opens with the symptoms above, and other documents from the same source behave.
- Try Open and Repair first, then Recover Text from Any File.
- Open a new blank document and use Insert > Object > Text from File to pull the body of the damaged one into it.
- Save the recovered content out to Rich Text Format and back, which rebuilds the structure, and check File > Info > Manage Document > Recover Unsaved Documents for an autorecover copy.
The location is the problem, not the file
You have this one if It opens from the desktop but not from its usual home, and that home is a deep folder tree, a WebDAV or SharePoint path, or a folder a sync client is working on.
- Copy the file to a short local path and open it there.
- Count the full path length. Anything near the classic limit of about 260 characters fails unpredictably, and # % and & in the name break WebDAV and SharePoint paths.
- If the folder is synchronised, let the client finish and make sure the file is downloaded rather than an online-only placeholder.
The storage is failing
You have this one if 0x80070570, other files from the same volume or device also misbehave, or the file came from optical media or a USB stick.
- Copy the file again from the original source rather than repairing the copy you have.
- Run chkdsk against the volume, read the System log for disk warnings around that time, and restore from backup or a previous version if the source is damaged too.
Word itself is starting badly
You have this one if Every document fails, not just this one, and winword.exe /a opens them all.
- Change the template: File > Options > Add-ins, set Manage to Templates and click Go.
- Disable COM add-ins from the same dialog with Manage set to COM Add-ins, and change the default printer to a driver-free target, which is one of Microsoft’s documented steps.
Full reference
Recovery routes, in the order Microsoft puts them
| If the document will not open | What it does |
|---|---|
| Open in Draft view with automatic link updating turned off | Skips the work that a broken link or picture makes Word do at open time |
| Insert > Object > Text from File | Pulls the body into a healthy container without opening the damaged one directly |
| Paste-link into a rescue document | Builds a link to the damaged file and then changes the source, recovering content the direct open cannot reach |
| Recover Text from Any File (*.*) | Reads whatever readable text remains and ignores the structure |
| If the document does open | What it does |
|---|---|
| Copy everything except the last paragraph mark into a new document | Leaves the damaged final mark, which carries much of the document’s stored state, behind |
| Change the template | Separates a fault in the document from a fault in the template it is attached to |
| winword.exe /a | Starts Word using default settings, so add-ins and stored settings are out of the picture |
| Change the printer driver | Word lays out against the printer; a bad driver produces symptoms that look like document damage |
| Force a repair with Open and Repair | Rebuilds what it can from the parts that survive |
| Save to Rich Text Format and back | Round-trips the content through a format that discards the damaged structure |
Telling trust from damage in one move
Open the file on a second machine that has never seen it, from a local folder, with a fresh copy taken from the original source. If it opens there, you have a trust or location problem on the first machine and nothing needs repairing. If it fails there too, the file is damaged and the recovery routes above are the whole of your options.
Doing it for more than one file
- Clear the Mark of the Web across a folder with Get-ChildItem piped into Unblock-File rather than opening each file’s properties.
- Where documents arrive continuously into one folder, make that folder a Trusted Location and stop unblocking altogether.
- Unblock a downloaded archive before you extract it. Extracting first copies the mark onto every file inside.
- Do not turn Protected View off across the estate to save the clicks. It is the layer that contains a hostile document while Office parses it.
When there is nothing left to recover
If the container cannot be read at all, the text recovery converter is the last route inside Word and it returns words without formatting, tables or images. Before you go looking for third-party recovery software, check the autorecover files, the previous versions on the volume, the copy in the sender’s Sent Items, and any backup taken since the document was last known good. Those four turn up a clean copy far more often than a recovery tool does.
Do not repair the original. Every one of these routes writes to the file it opens, and a failed repair is not reversible. Work on a copy and keep the original untouched until you have a result you are happy with.
Every code this article covers
| Code | What it points at | Source |
|---|---|---|
Word experienced an error trying to open the file |
Word declined the document; the wording covers both a trust refusal and a file it could not read, and Microsoft does not publish it as a defined error | not published by the vendor |
The file is corrupt and cannot be opened |
Word could reach the file but not read its contents; not published as a defined error, though Microsoft does document the symptoms and the recovery routes | not published by the vendor |
0x80070570 |
Windows error 1392, ERROR_FILE_CORRUPT: the file or directory is corrupted and unreadable | Microsoft Learn |
The document name or path is not valid |
The location rather than the document was rejected – length, characters or a path that no longer resolves; not published as a defined error | not published by the vendor |
Confirm the fix worked
- Open the document normally and confirm no Protected View bar appears at the top.
- Scroll to the end and check that tables, headers, footers and images survived, which matters most after a repair.
- Save the result under a new name, close it and reopen that copy, to confirm the rewritten file is clean.
- Open two or three other documents from the same source, to confirm the fault was specific rather than general.
- If you unblocked the file, confirm the Unblock checkbox is no longer offered in its properties.
Questions people ask about this
Do I need to buy repair software?
We would not start there. Word’s own routes – Open and Repair, the text recovery converter, insert as file, and the Rich Text round trip – recover most documents that are recoverable at all, and they are already in the product. No licence in Arco’s range makes a damaged file readable.
Why does the same file open for a colleague?
Because the Mark of the Web travels with the file and their copy may not carry one, or their Trusted Locations differ from yours. Compare where each of you is opening it from before you assume the document is at fault.
Can I turn Protected View off entirely?
You can, and you should not. It is the sandbox that contains a malicious document while Office parses it, and switching it off applies to every file from every source for ever. Trusting one folder you control is a far better trade than removing the layer.
Is there anything to recover if the file will not even open as an archive?
Sometimes. The text recovery converter reads whatever text remains and ignores the structure, so expect the words without the formatting, tables or images. Check autorecover files and previous versions first, because either is a better outcome.
Word crashed while saving to a share and now the document is unreadable. What should I do first?
Fetch the file again from wherever a second copy exists before you touch this one – the sender, a backup, a previous version, or the autorecover file. Repairing is a one-way operation, and a clean copy beats a repaired one every time.
