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: Most helpful
  1. K István 5 Reputation points
    2025-11-07T08:02:11.0633333+00:00

    Control Panel-> Intrnet Options->Security Tab
    Trusted Sites->Sites

    Add your network drive Z: (or something), uncheck Require https.... box

    Screenshot from 2025-11-07 08-56-43

    Was this answer helpful?

    1 person found this answer helpful.

  2. Nic J 15 Reputation points
    2025-11-07T02:26:03.96+00:00

    This is related to files downloaded - but it's from my server. Its really inconvenient and slows down my work. I do not like messing with settings as I'm not an IT pro -- I think MS could fix this option in a way that a travelling professional can view files without an issue. MS is meant to help us become more efficient while protecting our systems ... they should have put a few more hours into developing this feature... That's a FAIL from me MS.

    Was this answer helpful?

    1 person found this answer helpful.

  3. M_HERMAN 60 Reputation points
    2025-11-06T14:55:42.04+00:00

    (1) I am going to share my solution to this problem in this post, and just know that I'm using a non-networked laptop at home, but first

    (2) THANK YOU to everyone who shared so many varied solutions.

    (3) I also want to point out that this is NOT ONLY HAPPENING TO PDF FILES because I have had the exact SAME PROBLEM with downloaded CSV FILES as well.

    (4) MY SOLUTION PART 1: I constructed the following .ps1 file and saved it at C:\ which is the root of my one and only laptop drive. It is named "UnblockFiles_from_C_down.ps1".

    User's image (5) MY SOLUTION PART 2: Whenever needed, I launch the following .bat file from my desktop. It is named "UNLOCK ALL DOWNLOADED FILES.bat".

    User's image (6) I'll just add that I like the interactive pieces, like the ECHO and PAUSE commands because it helps me see that the fix is running and not getting stuck or crashing. I didn't want to unlock every darn file on my drive, but having discovered that my CSV files are also locked, I have the .ps1 script set up to do 2 different types of files, and there is the template for adding additional loops if and when more file types get bungled up in this dreadful new "feature".

    I still do not understand why doing a preview is so dangerous, but blatantly opening the whole file in an app is somehow gloriously safe. What am I missing here?

    Was this answer helpful?

    1 person found this answer helpful.

  4. Kim Nance 5 Reputation points
    2025-11-05T17:58:02.04+00:00

    Hi everyone - for network users like myself who weren't having any luck with some of the other suggestions in this thread - here's what worked for me:

    Control Panel > Internet Options > Security Tab > Local Intranet > Sites > Click "Automatically detect intranet network". Then OK, then Apply, then OK. After I did this I could preview files again, including PDFs.

    User's image

    Was this answer helpful?

    1 person 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.