Fix it now
Office decided not to open the file the ordinary way. Two separate rules produce that: the Mark of the Web, which puts a file from outside the machine into Protected View, and File Block, which refuses named formats outright. The file is usually fine; the rule is what is stopping you.
- Right-click the file in Explorer, choose Properties, and if an Unblock checkbox is offered on the General tab, tick it and click OK. That removes the Mark of the Web on your local device.
- Reopen the file. A yellow bar offering Enable Editing means you are in Protected View, and you may leave it if you trust where the file came from.
- If the file is refused outright with no bar and no Enable Editing button, you are in File Block territory. Open the application’s Options, go to the Trust Center, open Trust Center Settings, and find the File Block list.
- Change that format’s setting from not opening at all to opening in Protected View, click OK, and open the file. Then save it immediately in a current format so the block never applies to it again.
- If the File Block list is greyed out, a policy is enforcing it and only your administrator can change it. Ask them to look at the Trust Center branch of the Office administrative templates for that application.
- For a folder that receives such files routinely, add it as a Trusted Location instead. Office ignores the Mark of the Web check for files opened from one.
Convert the file rather than leaving the block open. Reopening a legacy format for one document and closing it again afterwards is a much better habit than leaving the list permanently permissive.
If the document opens, with or without the yellow bar, you are done. If it is still refused, the next section separates the two mechanisms and shows which one has you.
Why it happens
Anything that arrives from outside the machine – a download, an attachment, a file copied from another computer – carries a marker recording that fact. Microsoft calls it the Mark of the Web, and Office reads it before it reads the document. Files carrying it open in Protected View, a low-privilege sandbox with no editing and no active content, and their macros are blocked by default in Access, Excel, PowerPoint, Project, Publisher, Visio and Word on Windows. Removing the marker is the Unblock checkbox on the General tab of the file’s properties.
File Block is a different list and a harder stop. It names specific formats, mostly the legacy binary ones, and controls whether each may be opened normally, opened in Protected View, or refused. Nothing about the individual file is examined; the format is on a list. That is why File Block produces no yellow bar and no Enable Editing button – the document is never parsed at all – and why the fix is a setting change rather than a decision about trust.
The third possibility catches people out because the message looks identical. Office checks that a file is structurally what it claims to be before parsing it fully, and a file that fails is pushed into Protected View or refused. In practice that means files produced by a third-party generator that writes output close to, but not quite, the specification. If every file from one reporting system fails and ordinary documents open normally, that is where you are.
The file carries the Mark of the Web
You have this one if A yellow Protected View bar appears, or the file is refused, and Properties offers an Unblock checkbox.
- Tick Unblock on the General tab of the file’s properties and reopen.
- For many files at once, pipe Get-ChildItem into Unblock-File in PowerShell.
- For a folder that receives them routinely, add it as a Trusted Location, which makes Office ignore the check.
Unblock the archive before you extract it. Extracting first copies the mark onto every file inside, and you will be unblocking them one at a time.
File Block is refusing the format
You have this one if No yellow bar, no Enable Editing, the file simply does not open, and it is an old binary format or a converter format.
- Open the File Block list in the application’s Trust Center settings and find the row for that format.
- Change it from refusing the format to opening it in Protected View.
- Open the file and immediately save it in a current format, then put the setting back.
A policy is enforcing the block centrally
You have this one if The File Block settings are visible but greyed out, or they revert after a restart or a policy refresh.
- Confirm the machine is receiving policy and capture the report for your administrator.
- Ask them to review the Trust Center policies for that application. The relevant branch is User Configuration, Policies, Administrative Templates, then the application’s own Options or Application Settings, Security, Trust Center.
- Where a business process genuinely needs an old format, ask for a scoped exception rather than an estate-wide change.
The file was not written by Office
You have this one if Files from one export tool or reporting system always fail while ordinary documents from colleagues open normally.
- Open one on a machine that has never seen it, from a local folder, to confirm the file rather than the machine is at fault.
- Ask the vendor of the generating system whether their output has been updated for current Office builds.
- Have the generator produce a current format instead of a legacy one, which sidesteps File Block and the validation check together.
Full reference
The two gates, side by side
| Mark of the Web and Protected View | File Block | |
|---|---|---|
| What it examines | Where the file came from | What format the file is |
| What you see | A yellow bar offering Enable Editing | No bar; the file is simply not opened |
| Fix for one file | Unblock on the General tab of Properties | Change that format’s row in the File Block list |
| Fix for a folder | Add it as a Trusted Location | Nothing folder-based; File Block is about formats |
| Central control | Trust Center policy, per application | Trust Center policy, per application |
What Microsoft publishes about the macro half
- Macros in files carrying the Mark of the Web are blocked by default in Access, Excel, PowerPoint, Project, Publisher, Visio and Word, on Windows.
- Saving such a file to a Trusted Location makes Office ignore the Mark of the Web check and open it with macros enabled.
- Removing the mark on your own device is the Unblock checkbox on the General tab of the file’s properties.
- A signed macro from a source you have validated can be trusted by making that source a trusted publisher.
- The policies involved are named Block macros from running in Office files from the Internet, and VBA Macro Notification Settings.
Doing a migration of legacy files properly
Opening thousands of old binary documents during a migration is the one case where changing File Block estate-wide gets suggested, and it is still the wrong shape. Do it as a controlled exercise instead: a scoped policy change on a small number of machines, bulk conversion to current formats, then the policy reverted. Leaving the block open everywhere for the convenience of a one-off job leaves the estate permanently more exposed than it was, long after everyone has forgotten why.
Where each control lives
| Control | How to reach it |
|---|---|
| Unblock one file | Explorer, right-click, Properties, General tab |
| Unblock many files | Get-ChildItem piped into Unblock-File in PowerShell |
| Protected View settings | The application’s Options, under Trust Center, Trust Center Settings |
| File Block list | The same Trust Center settings dialog, in its own section |
| Trusted Locations | The same Trust Center settings dialog, in its own section |
| Central enforcement | Office administrative templates, under each application’s Security and Trust Center branch |
Do not switch Protected View off globally to make a message go away. It is the layer that contains a hostile document while Office parses it, and turning it off applies to every file from every source. Unblock individual files, or trust folders you control and users cannot write to.
Every code this article covers
| Code | What it points at | Source |
|---|---|---|
Office has detected a problem with this file |
Office opened the file in a sandbox or refused it because its trust or validation checks flagged it; Microsoft does not publish this wording as a defined error | not published by the vendor |
blocked by your File Block settings |
The format is on the application’s File Block list, so no individual file is examined; not published as a defined error | not published by the vendor |
You are attempting to open a file that is blocked by your registry policy setting |
The block is being applied by policy rather than by a local setting, so the local Trust Center will not move it; not published as a defined error | not published by the vendor |
Confirm the fix worked
- Open the file and confirm it appears without a Protected View bar, or that Enable Editing is offered and works.
- Check the file’s properties and confirm the Unblock checkbox is no longer offered.
- Save the document in a current format, reopen that copy, and confirm no block applies to it.
- If you changed a File Block row, reopen the Trust Center and confirm the setting is where you meant to leave it.
- Have a second user open the same file, to confirm the fix is not only on your profile.
Questions people ask about this
Is there anything I need to buy?
No. This costs nothing to fix. Every control involved ships with Office and Windows, and no licence, edition or subscription changes what File Block or Protected View do.
Why does the same file open on my colleague’s machine?
Because the Mark of the Web travels with the file and their copy may not carry one, or their Trusted Locations differ, or a policy applies to your group and not theirs. Compare where each of you got the file from first.
Is it safe to unblock a file from a known sender?
Reasonably, if you were expecting it and it is what you expected. Bear in mind that a compromised mailbox sends convincing attachments from a real colleague, so an unexpected document from a known sender deserves the same scepticism as one from a stranger.
We need to open thousands of legacy files during a migration.
Do it as a time-boxed exercise on a small number of machines: scope the policy change, convert in bulk to current formats, then revert. Leaving File Block open across the estate for a one-off job is the wrong trade and nobody remembers to close it afterwards.
The setting I need is greyed out. Can I change it in the registry instead?
You can usually make the value change and it will not last: policy reapplies on the next refresh. More to the point, a managed setting is greyed out because someone decided it should be, so the productive route is a scoped exception from whoever owns that decision.
