File Explorer not previewing pdf files since 25H2 update

Paul Nicholson 560 Reputation points
2025-10-15T08:07:37.1033333+00:00

Since installing the 25H2 update to Windows 11, the preview for pdf files is not working.

I just get the following message "The file you are attempting to preview could harm your computer. If you trust the file and the source you received it from, open it to view its contents"

I have tried everything to restore the preview without success.

Any help would be much appreciated!

Windows for home | Windows 11 | Files, folders, and storage

Answer recommended by moderator
Vivekanandan Tiwari 210 Reputation points
2025-10-20T03:18:02.11+00:00

Here is a simple solution that worked for me -

in the file explorer, just disable this check box as shown in the image, this simply worked for me

(This happened on windows 10 as well!)
Screenshot 2025-10-20 084655

Was this answer helpful?

90+ people found this answer helpful.

103 additional answers

Sort by: Oldest
  1. Randy Baroja 20,775 Reputation points Independent Advisor
    2025-10-15T08:48:02.98+00:00

    Hi,

    Most of the time, making sure your preferred PDF app, like Adobe Reader or Edge, is set as the default fixes it, because File Explorer needs that to show previews. Also, double-check that the Preview pane is turned on (View > Show > Preview pane) and see if selecting a PDF brings the preview back. If it’s still not working, sometimes just repairing or reinstalling the PDF app does the trick, since that restores the preview handler that the update might have messed with. This usually gets things back to normal pretty quickly.

    Kind regards,

    Was this answer helpful?


  2. Mark Zuber 185 Reputation points
    2025-10-15T09:35:21.4533333+00:00

    Hey everyone,

    Just wanted to chime in – I’ve been running into the same issue with PDF previews in File Explorer since the 25H2 update. Some PDFs show the preview just fine, but others throw this message:

    "The file you are attempting to preview could harm your computer."

    After digging around a bit, I realized it’s related to the Mark of the Web (MOTW). Windows tags files downloaded from the internet, and apparently the preview handler now treats those more strictly.

    As a workaround, I ran this PowerShell command to unblock the files in a folder:
    Get-ChildItem -Path "C:\Users\Username\Documents\PDF" -Recurse | Unblock-File

    That actually fixed the preview for those PDFs – but it’s not really a proper solution. I’d rather not have to run this manually or script it every time. Would be great if Microsoft gave us a way to trust certain folders or disable this check for local files.

    Anyone else found a cleaner fix?

    Kind regards,

    Was this answer helpful?

    50+ people found this answer helpful.

  3. Ramesh 181.2K Reputation points Volunteer Moderator
    2025-10-15T10:08:04.63+00:00

    Hi Paul,

    In that case, here are some options that I can think of.

    After saving the PDF from email to a folder, right-click on the PDF file, click Properties, select "Unblock", and click OK.


    -or-


    Create a scheduled task that executes the above PowerShell command at regular intervals to bulk unblock PDFs.


    -or-


    Create a scheduled task that executes the Streams.exe tool (from Sysinternals) at regular intervals to bulk unblock PDFs.

    Streams - Sysinternals | Microsoft Learn

    How to Bulk Unblock Files Downloaded from Internet

    Streams command-line example:

    c:\tools\streams.exe -s -d %userprofile%\downloads\
    

    The above command unblocks all files in the Downloads folder and subfolders.


    -or-


    Or, put all those PDFs in a FAT or exFAT partition. This may not be a feasible option for many users due to lack of security, but posting it anyway.

    Was this answer helpful?

    1 person found this answer helpful.
    0 comments No comments

  4. TheodorJosef Eisenring 15 Reputation points
    2025-10-15T17:13:19.6633333+00:00

    Same problem after installing the final update KB5066791 in Windows 10 Version 22H2. The bug seems also to exist in Windows11 24H2 Update KB5066835 (Oct. 14)

    Was this answer helpful?

    4 people found this answer helpful.

Your answer

Answers can be marked as 'Accepted' by the question author and 'Recommended' by moderators, which helps users know the answer solved the author's problem.