You open a .docx that worked fine yesterday, and Word throws "The file is corrupt and cannot be opened" — annoying, and it's almost never actually the file. Most of the time an Office update flipped a security setting or broke your Protected View config, and Word is now refusing to parse documents it was fine with 24 hours ago.
Fix 1: Unblock the file (try this first — it's 10 seconds)
If you downloaded the docx from email, Teams, SharePoint, or a browser, Windows tagged it with a Mark-of-the-Web zone identifier. Word treats those as hostile, and after certain Office builds the check got stricter. The fix:
- Right-click the .docx in File Explorer.
- Click Properties.
- At the bottom of the General tab, look for Unblock next to the security warning.
- Check it, click Apply, then try opening it again.
If Unblock isn't there, the file wasn't downloaded — skip to Fix 2.
For a whole folder, PowerShell is faster:
Get-ChildItem "C:\Your\Folder" -Recurse | Unblock-File
Fix 2: Disable Protected View for trusted locations
This is the culprit behind 8 out of 10 of these tickets. Office updates sometimes reset or aggressively reapply Protected View, so files sitting in network shares or mapped drives get sandboxed and fail to open with that corrupt error.
- Open Word → File → Options.
- Go to Trust Center → Trust Center Settings.
- Click Protected View on the left.
- Uncheck all three boxes: Internet files, Files located in unsafe locations, and Outlook attachments.
- Then go to Trusted Locations and add the folders where your docs live (network shares included).
Don't leave Protected View off for the whole system if these are shared machines. Add the specific folders to Trusted Locations instead — that's the clean fix.
Fix 3: Repair Office
If the above didn't work, the update may have left a half-broken install. This is common on machines that got interrupted mid-update or are running old cached MSI remnants from Office 2016/2019 alongside a 365 click-to-run.
- Settings → Apps → Installed apps.
- Find Microsoft 365 (or Office 2019/2021), click the three dots → Modify.
- Choose Quick Repair first. If that fails, run Online Repair — it takes 15-20 minutes but actually replaces the binaries.
Fix 4: Registry — kill the file validation block
Office File Validation got bolted onto 2010 and still lingers in some templates. If Word is blocking files specifically from a network path, this is often why. On a test machine first:
HKEY_CURRENT_USER\Software\Microsoft\Office\16.0\Word\Security\FileValidation
ExtensionHardening = 0 (DWORD)
You can also disable it via Group Policy under User Configuration → Administrative Templates → Microsoft Word 2016 → Word Options → Security → Trust Center → File Block Settings. Set the file types you actually use (docx, docm) to "Open" instead of "Block."
Why any of this works
That error message is a lie. Word isn't detecting corruption — it's refusing to even attempt parsing because a security layer said no. Protected View, Mark-of-the-Web, and File Validation all run before the OOXML parser ever touches the file, and when any of them trips, Word reports the most generic failure it has: "corrupt." Because an Office update can silently rewrite Trust Center defaults, add new file-block rules, or change how zone identifiers are evaluated, you get exactly the pattern you're seeing: everything worked, update installed, nothing works. The fixes above turn off the right gate.
Less common variations
- Only one specific file fails, others in the same folder open fine: the docx really is damaged. Try Open and Repair — File → Open → browse → click the arrow next to Open → Open and Repair.
- Error appears when double-clicking but not when opening from inside Word: broken file association. Run this from an elevated command prompt:
winword.exe /r— it re-registers Word's file types in the registry. - Comes back after every reboot: a Group Policy or Intune baseline is re-pushing Protected View settings. Check
gpresult /h report.htmland look under User Configuration → Administrative Templates → Microsoft Word. - Add-in conflict: start Word with
winword.exe /a. If files open fine, one of your add-ins is the problem. Disable them from File → Options → Add-ins one at a time. - Normal.dotm is corrupted: close Word, rename
%appdata%\Microsoft\Templates\Normal.dotmto Normal.old, reopen Word. It rebuilds the template automatically.
Prevention
You can't stop Office from updating, and you shouldn't try. But you can stop this from recurring:
- Push Trusted Locations via Group Policy across the fleet instead of setting them per user. One policy beats 200 help desk tickets.
- Pin Office updates to the Monthly Enterprise Channel if you're on 365. Semi-Annual Channel if stability matters more than features.
- Test the current channel build in a ring of 5-10 users before the full rollout. Every one of these incidents started with "we just pushed the latest update."
- Keep a copy of any critical docx in .rtf or .doc format on a file share. If Word's validation layer is having a bad day, a legacy format will still open.
And write the fix down. The next time Microsoft ships a Trust Center change, you'll be the one getting the call at 4:45 PM on a Friday.