Word: “Cannot Open the Document: Access Privileges”

You double-click a document a colleague sent you and Word refuses: Word cannot open the document: user does not have access privileges. The file sits in your Downloads folder, 300 KB, and opens on their machine with no prompt.

That sentence is not about a password. It is about which Windows account may reach the bytes, or which account Office thinks should own them. The checks below run from cheapest to most invasive.

Why Word reports “access privileges” and not “corrupt”

A single .docx can be blocked by three unrelated permission systems, and Word uses roughly the same sentence for all of them.

NTFS access control lists. Copy a document off a server or a colleague’s drive and Windows sometimes carries the original permissions along: the file lands on your desktop still owned by CORP\jdoe, with an ACL that gives your account nothing.

Encrypting File System. An EFS-encrypted file is bound to the private key of the account that encrypted it. Explorer shows the name in green, and the bytes are unreadable to everyone else — including you after a reinstall, because the key stayed in the old profile.

Information Rights Management. A protected document carries a use licence inside the package naming the accounts allowed to open it. No Windows permission you grant overrides that.

One distinction matters: Word opens files read-only without complaint when it cannot write, and raises this error when it cannot read. A file that is merely locked for editing is a different fault — the mechanics in Excel file locked for editing apply there.

Fix 1 — Move the file to a folder you own

Half of these reports come from the file’s location rather than its permissions. Copy the .docx to your Desktop and open the copy.

• Inside a .zip that was never extracted. Word receives a path in a read-only temp folder. Use Extract All first.
• The Outlook attachment cache. Opening from the preview pane hands Word a path under %LocalAppData%\Microsoft\Windows\INetCache. Use Save As.
• Read-only media, mounted ISOs, and shares where you can list a folder but not read the files in it.

If the copy opens, the document is healthy and only its old location was the problem.

Fix 2 — Unblock the file

Right-click the .docx → Properties → General. If the file came from the internet, Outlook or a chat app, there is a line near the bottom: Security: This file came from another computer… Tick Unblock → Apply.

That clears the Mark-of-the-Web, an alternate data stream called Zone.Identifier recording where the file came from. Office reads it and may route the file through Protected View; when that sandbox cannot reach the temp copy it needs, the failure surfaces as an access error instead of the yellow warning bar.

If Unblock is greyed out, the stream is absent and this is not your cause.

Fix 3 — Take ownership and grant yourself Full control

Right-click → Properties → Security → Advanced. The Owner line shows the account Windows thinks owns the file. If it is not you, click Change, type your account name, Check Names, OK, Apply.

Then on the Security tab click Edit → Add, enter your account, and grant Full control. Ownership alone lets you rewrite the ACL; it does not grant read by itself.

Expect two things: the ownership step needs an administrator account, and if the Security tab is missing entirely the file is on a FAT32 or exFAT volume, which has no ACLs — skip to Fix 4.

Fix 4 — Check whether the file is encrypted

A green file name means EFS. In a Command Prompt, run:

cipher /c "C:\Users\you\Documents\report.docx"

It lists the accounts that can decrypt the file and any recovery agent. If yours is not among them, the only route back is the original certificate: open certmgr.msc, find the old key under Personal → Certificates, export it as a .pfx with its private key on a machine that still has it, then import it here.

If that certificate died with a wiped profile and no recovery agent was configured, the ciphertext is intact and permanently unreadable. No repair tool decrypts EFS — they fail or hand back noise.

Rights-managed files behave similarly, but the fix is administrative: ask the sender to remove protection, or to have your account added to the IRM policy.

Fix 5 — Recover the content when the container stays locked

File → Open → Browse → arrow next to Open → Open and Repair rebuilds the package in memory and opens what it can parse. It cannot beat a permission error, but it does help the smaller group of files where a damaged permission table is what Word is complaining about.

Insert → Object → Text from File in a blank document pulls the body out through a different code path. Expect text, inline images and most tables; expect to lose section headers, footnotes, tracked changes and exact style definitions. Enough to keep working, not enough to send to a client.

If both fail and the file shows other symptoms, treat it as damage and work through Word document corrupted, which starts by copying the file so no tool writes over the original.

When it is not worth fixing

Three cases are genuinely closed. An EFS file whose certificate is gone and whose recovery agent was never configured. A rights-managed file tied to a tenant you no longer have an account in, such as a document from a former employer. And a file on failing media that returns read errors partway through, where every copy you make comes out a slightly different size.

In those cases the content exists but is not reachable with the credentials you hold, and the person who can unlock it is the one who locked it. That is a phone call, not a repair job.

What a repair service does is different: recover a document that opens but comes back empty, half-formatted or truncated. If that is your case, the assessment on the services page runs on a copy and tells you what survived before any work starts.

FAQ

It opens on my colleague’s PC and not on mine. What changed? Either the file carried their ACLs when it was copied, or it is encrypted to their key. Fix 3 answers the first, Fix 4 the second. Compare the file name colour in Explorer on both machines — green on one and black on the other settles it.

I reinstalled Windows and my old documents are green. Can I still open them? Only with the EFS certificate from the old installation, exported as a .pfx with its private key. If you never exported it and no domain recovery agent exists, those files cannot be decrypted — a limit built into the encryption, not into Word.