File Explorer Preview Warns a File Could Harm Your Computer: Check Its Origin
By ON Lab · Sources checked November 8, 2026
If File Explorer shows a warning that a file could harm your computer instead of a preview, first check whether this is the documented internet-origin protection. Microsoft changed this behavior with Windows security updates released from October 14, 2025. A missing preview under that warning is not, by itself, evidence that a PDF viewer is broken.
Identify the exact symptom and file origin
Record the warning, your Windows version, where the file came from and whether it is local or on a network share. Do not begin by changing preview handlers or reinstalling a PDF application. Those actions address different causes of a blank pane and do not establish why this warning appeared.
Microsoft’s current notice describes files carrying Mark of the Web from the Internet security zone, and files on an Internet Zone share. The change protects against a preview-related credential-leak risk. A public January 2026 question described the same warning interrupting document review after the October update; that is a concrete workflow problem, not proof of a paid-software need.
Keep three states separate
| Observed result | Useful interpretation |
|---|---|
| The documented warning appears for a downloaded file | Check the internet-origin restriction and your trust decision for that exact file. |
| A pane is empty without this warning | The notice alone does not explain it. Record the file type, viewer and comparison result. |
| The warning occurs for files on a shared location | Record the share address for your administrator; a share-wide zone change has a broader effect. |
For example, a locally created document previewing while a downloaded PDF shows the warning is a useful comparison. It is not proof that the downloaded PDF is safe. Do not copy, rename or repeatedly redownload a questionable file to try to make the warning disappear.
The official per-file route is conditional on trust
If you are confident in both the file and its source, Microsoft documents selecting the downloaded file’s Properties in File Explorer and choosing Unblock. This removes its internet security block. The notice says the change may only take effect after the next login.
Before doing that, establish which exact file you intend to trust. A familiar-looking filename or extension is not a source check. Keep the original source information and use the organization’s existing review process for unexpected attachments. If trust is unresolved, leave the block in place and ask the sender or your administrator to verify the file through an established channel.
On a managed device, do not try a different mechanism if the expected control is unavailable. Record that absence along with the file’s location and the warning. A missing checkbox does not establish that a registry edit is the appropriate substitute.
A network-share change is a different decision
The official notice also describes security-zone configuration for an Internet Zone share. That affects files from the listed share, so it is broader than trusting one downloaded document. Give the share address and examples to the administrator responsible for the policy. This guide does not supply a blanket registry bypass or recommend changing an entire zone for one preview.
A useful handoff contains: “This exact warning appears for [file type] at [local download or approved share]. A harmless locally created comparison [does/does not] preview. The device is [Windows version]. The problem began [observed date, or unknown].” Leave private filenames and network addresses out of a public forum post.
Verify the result after an approved change
- Return to the same file and confirm its identity; a different copy is not the same test.
- Record whether the security block is still present in the file’s properties.
- Check the preview again, allowing for the notice’s next-login caveat.
- If the warning disappears but content still does not preview, record that new state separately.
Removing one restriction does not promise that the file type has a working preview handler. Conversely, being able to preview content does not certify that a file is safe. The verification is limited to the observed warning and preview behavior.
The current Microsoft notice and original support answers are free to read. There is no demonstrated need here for a paid preview utility. For a PDF that opens but fails only during printing, use the separate PDF printing comparison; that guide starts at a different failure stage.
Method: Microsoft’s current notice with all FAQ sections expanded, plus a public user report and an editorial diagnostic/handoff example. No Windows device, properties dialog, unblock action, network-zone change or repaired preview was reproduced. Follow the linked notice for the current supported scope.