Fix 'Word experienced an error trying to open the file'

Word chokes on .docx attachments because Windows marks them as blocked from the internet. Unblock the file, or kill Protected View, and it opens fine.

You double-click the .docx in your email and Word throws "Word experienced an error trying to open the file" instead of just opening the damn thing. Frustrating, and almost always a two-minute fix.

The fix (do this first)

Save the attachment to disk instead of opening it straight from Outlook. Right-click the saved file, pick Properties, and look at the bottom of the General tab. If you see a line that says Security: This file came from another computer and might be blocked to help protect this computer, that's your culprit.

Check the Unblock box, click Apply, then open the file. Done.

If you're doing this for a bunch of files, or you're on a server with no GUI, use PowerShell:

Get-ChildItem "C:\Users\you\Downloads\*.docx" | Unblock-File

That strips the Zone.Identifier alternate data stream from every file in the folder. Works on Windows 10 and 11, Server 2016 and up.

If Unblock isn't there or doesn't help

Sometimes the checkbox is missing because the file's already been unblocked, or because Group Policy stripped the option. Check the stream directly:

Get-Item "C:\path\to\file.docx" -Stream *

If you see a Zone.Identifier stream, the file's still flagged. You can remove it with:

Remove-Item "C:\path\to\file.docx" -Stream Zone.Identifier

Do that and Word will open it like any other local file.

Why this actually happens

When Outlook — or Teams, or Edge, or Chrome — saves a file from the internet, Windows attaches what's called the Mark of the Web. It's a hidden NTFS alternate data stream called Zone.Identifier that tags the file as coming from the Internet Zone. This has been around since XP SP2 and it's not going anywhere.

Word and the rest of Office see that tag and get cautious. They route the file through Protected View, which runs it in a sandboxed read-only mode. Usually that just shows a yellow bar at the top saying "Protected View." But certain document features — macros, embedded objects, some ActiveX controls, external data links — can't run in that sandbox. When Word tries to reconcile the request with the sandbox restrictions, it bails with "Word experienced an error trying to open the file." The error message is useless, but the underlying cause is very specific: the file is in the internet zone and Word won't fully trust it.

Unblocking removes the tag, Word skips Protected View, and the doc opens normally. No registry surgery, no reinstall, no prayer.

Less common variations

1. The file lives on a network share or OneDrive-synced folder

Same error, different trigger. Files in a Trusted Location skip Protected View entirely, but files in an untrusted network path don't. If you're opening from a mapped drive or a UNC path, add the path to Word's Trust Center. File > Options > Trust Center > Trust Center Settings > Trusted Locations > Add new location.

Don't check "subfolders" unless you actually need it. That widens the trust zone more than it needs to be.

2. Files from a specific sender always fail

If it's always the same person, they're probably sending you docs with embedded content — Excel objects, linked data, old-style macros. Even after unblocking, those can still blow up. Open the file with macros disabled (Word will prompt), then inspect with Developer > Visual Basic if you want to see what's inside.

3. The .docx is really a renamed .doc, .rtf, or corrupted

Happens more than you'd think. Rename the file to .zip and try to open it. A healthy .docx is a zip archive. If Windows says it can't open it as a zip, the file is corrupt or mislabeled and no amount of unblocking will save it. Ask the sender to resend.

4. Office Trust Center is locked down by policy

In managed environments, IT often disables Protected View entirely or forces it on regardless of the Mark of the Web. Check the registry:

HKCU\Software\Microsoft\Office\16.0\Word\Security\ProtectedView

Values like DisableInternetFilesInPV, DisableUnsafeLocationsInPV, and DisableAttachmentsInPV control this. If your org manages these via GPO, you're not changing them without a ticket.

5. Old Office or a bad install

Rare, but I've seen it on Office 2013 with missing updates. Run a quick repair: Settings > Apps > Microsoft Office > Modify > Quick Repair. If that doesn't do it, Online Repair. Don't waste time reinstalling from scratch first.

Prevention

Save attachments to a folder you've added as a Trusted Location. Then Word never touches Protected View for those files.
If your org allows it, uncheck Protected View for files originating from the internet: File > Options > Trust Center > Protected View. I don't recommend this on shared machines or anything handling sensitive data — the protection exists for a reason.
Don't open attachments directly from Outlook. Always save first, then open. Fewer surprises, and you keep a copy for your records.
If you're scripting this for users, hand them a one-liner shortcut that runs Unblock-File on whatever they drop into a folder. It beats walking them through Properties dialogs over the phone.

Nine times out of ten, unblocking the file fixes it. The other one time, it's a corrupt doc and the sender needs to resend. Don't overthink it.