Office: “File Type Blocked by Trust Center Settings”

You double-click a .doc a client sent, and Word stops before the page appears: “You are attempting to open a file type that is blocked by your File Block settings in the Trust Center.” The document is almost certainly fine. Office keeps a per-application list of formats it is willing to parse, and the one you just handed it is not on that list.

The message is a security gate, not a damage report. Once you know which gate it is, you can open the file in a couple of minutes — or decide it is not worth opening at all.

What the message actually means

File Block is a Trust Center feature that has been in Office since 2007. It is a grid keyed on file format, not on file content. A workbook can be byte-perfect and still be refused, because the decision is made before Office reads any of the body. That is why the dialog names a “file type” and never names your document.

Each application has its own grid. Word’s list governs .doc and .dot, Excel’s governs .xls, PowerPoint’s governs .ppt and .pps, and the macro-enabled variants sit on separate rows. A format blocked in Word stays perfectly openable in Excel if Excel’s list says so.

The grid has two columns — Open and Save — plus three radio buttons underneath that decide what happens to a ticked row: block it outright, open it in Protected View, or open it in Protected View with editing allowed.

Why a format ends up on the list

In a clean install of Microsoft 365, most legacy binary formats are still allowed. If you are seeing this message, something changed the default: a Group Policy object, an Intune security baseline, a hardening script from an IT vendor, or a colleague’s exported Office profile that got imported onto your machine.

Two neighbouring features get confused with File Block, and neither produces this sentence. Protected View shows a yellow bar and lets the file open read-only. Office’s blocked file types list is a hard-coded set of extensions Office refuses to touch under any setting. File Block is the only one that quotes itself in the dialog, so the wording is a reliable fingerprint.

Fix 1 — Allow the one format you need

Open the application that owns the file, then go to File → Options → Trust Center → Trust Center Settings → File Block Settings.

The grid lists formats by generation, for example “Word 97-2003 documents” or “Excel 97-2003 workbooks”. Click the row for the format you are opening, then choose Open selected file types in Protected View at the bottom of the dialog. Close everything and reopen the file.

Protected View is the right compromise for a file that arrived by email. You still get a banner and a click to enable editing, but the legacy parser runs behind a sandbox. Choosing “do not open” on the row for a different generation, such as the .docx row, will change nothing — read the row labels before ticking.

Fix 2 — Check whether a policy is overriding you

If the checkboxes are greyed out, or a bar reads “Some settings are managed by your system administrator”, the dialog is showing you a decision that was made elsewhere. The values live under HKEY_CURRENT_USER\Software\Policies\Microsoft\Office\16.0\word\security\fileblock, where 16.0 covers Office 2016, 2019 and 365 and 15.0 covers Office 2013. Each value is named for a format generation, and 0 allows the format, 1 sends it to Protected View, 2 blocks it.

Administrators can reach the same switch through gpedit.msc → User Configuration → Administrative Templates → Microsoft Word 2016 → Word Options → Security → Trust Center → File Block Settings. Deleting the registry value by hand only holds until the next policy refresh, so on a managed machine the honest fix is a request to whoever owns the policy.

Fix 3 — Make sure you are in the right application

A blocked .xls will not open through Word’s File Block list, and dragging the file onto a Word window or renaming it does not route around anything. Open it in the application that matches the extension: .doc and .docx in Word, .xls and .xlsx in Excel, .ppt and .pptx in PowerPoint. If several formats are blocked, each application needs its own row cleared.

Related but separate: a file whose extension does not match its actual container produces a different complaint entirely, covered in the file format and extension mismatch error. That one is about the file’s internal signature, not about policy.

Fix 4 — Convert the file instead of unlocking the format

If you need the content rather than the exact packaging, stop fighting the setting. LibreOffice opens .doc, .xls and .ppt without consulting Office policy and can save a fresh .docx or .xlsx. Google Docs and Word for the web accept legacy uploads and export modern formats.

Expect layout drift: tables with merged cells, footnotes, text boxes and embedded fonts all move during conversion. For a memo that is fine. For a signed contract or a print-ready brochure, conversion is not an acceptable substitute.

When it is not worth fighting

If the laptop belongs to an employer, the block is a security decision and asking for a permanent settings change is the wrong request. Ask instead for the file to be re-sent in .docx, or for a one-time exception on that single document.

If the layout has to survive intact and nobody will lift the block, that is a job for someone with the right policy — which is what our file repair service exists for; send the original and describe what has to be preserved.

One more check before you spend money: if the file fails on a machine where the format is allowed, the problem is not File Block. A file that opens and then closes, or one that reports unreadable content, points at a damaged package instead, and the steps there are different.

FAQ

Is my file corrupted? No. File Block is evaluated on the extension and the format generation before the file’s contents are parsed. A corrupted file usually produces “unreadable content” or a repair prompt, not a policy sentence.

Why did this start after an update? Security baselines tighten over time, and a baseline pushed by IT or applied with a new Office build can add legacy formats to the blocked list. The setting was always there; the update changed its value.

Does allowing the format make Office unsafe? It widens what Office will parse, and legacy binary parsers are a familiar target. Protected View is the compromise worth taking: the format opens, but with reduced trust and a visible banner.

Can I just rename .doc to .docx? No. The extension changes what Office expects, not what the file contains, and you will usually get a format mismatch error instead. Convert through an application that rewrites the package.