Forum Discussion
File Explorer ignoring UNBLOCKED file status with 24H2
FILE EXPLORER IGNORING UNBLOCKED FILE STATUS AFTER DOWNLOAD AND UNBLOCK
I updated to Win 11 23H2 --> 24H2 some days ago.
Yesterday I used Mark Russinovich tool "Streams" to manually remove from CMD prompt the "file comes from another computer..." warning, e.g.:
Today I noticed I have a problem with Zone.Identifier ADS files: File Explorer is extremely slow to update file status "unblocked" after I unblock it, and still reports the file is coming from another PC. When I try to unblock it again, I get this error ("can't find file". I suppose it is correct since Zone.Identifier ADS files should have been removed:
The problem remains: File Explorer is ignoring the unblocked file status. Even after 5 mins the file is still "coming from another PC..." (???) when I choose Properties. Sometimes randomly, after a while, when I check again the unblocked status it is finally acknowledged by File Explorer.
dir /r on the previously unblocked files from File Explorer shows the SmartScreen:$DATA is still there... Zone.Identifier:$DATA is gone instead. Which is OK I guess.
Quick test: download a file from Edge with SmartScreen enabled, then with right-mouse-button select Properties and unblock the file. Now re-open Properties for that file...
Reproducible also from Safe Mode (!).
Is it a new File Explorer bug in 24H2?
C:\Windows\Explorer.exe 6.2.26100.2454
Edge Browser 131.0.2903.99
Windows 11 24H2 26100.2605
Can't see other reports about this bug on the net...
24 Replies
- _Bparker_Brass Contributor
Fixed now on my system too, version 26100.6725.
- HexaaeBrass Contributor
August 29, 2025 - KB5064081 (OS Build 26100.5074) should finally fix it, but it's a "gradual rollout" so it can take some time...
I got it installed (Win 11 24H2 26100.5074), but at the moment the bug is still reproducible for me (feature still locked).- HexaaeBrass Contributor
Finally fixed (unlocked from previous KB?) with KB5065426 (26100.6584). 09/09/2025
- _Bparker_Brass Contributor
Still not fixed in build 26100.5074.
- _Bparker_Brass Contributor
Still not fixed in build 26100.4946.
- _Bparker_Brass Contributor
Still not fixed in build 26100.4770.
- _Bparker_Brass Contributor
Still unfixed in build 26100.4652.
- _Bparker_Brass Contributor
Still unfixed in build 26100.4484.
- HexaaeBrass Contributor
26100.4351 still affected.
Confirmed still unfixed since roll-out of 24H2 (after 8 months...) 😖
- _Bparker_Brass Contributor
Still not fixed in build 26100.4351.
- ElaoineCopper Contributor
Roll back to Windows 11 23H2