Windows 10: Windows File Explorer and Desktop isn't refreshing automatically.

Ive had this issue for a couple weeks now and wanted to help others since this is really frustrating.I found the solution for it in a random youtube video comment about this topic.UNPIN ANY NETWORK FOLDER from your Explorer and it will work again. Only fix which will persist. I hope this helps others as it did me.Cheers Everyone

:)

 

Automatic refresh doesn't work in File Explorer, Desktop, Recycle etc.


Same in the safe mode, no changes...

I have tried pretty much all those suggestions from various sites, but none of them worked for me.
What I have seems to be a major issue, they even call it WEDR bug.
The only thing that slightly changed recently... sometimes, a few times I managed to get automatic refresh for the Desktop, if I for example do the right click and create a new folder, it does create instantly and is visible straight away.... hoewever this never happens in Windows Explorer... I think I once got a file in C: to be processed automatically but thats it... and never had ANY automatic refresh for any of the folders and files on external drives.

 

Automatic refresh doesn't work in File Explorer, Desktop, Recycle etc.


And in safe mode? I don't think you've commented on that yet.

Solutions from a general web search:
What to do when Windows Explorer doesnt refresh | ITworld
- quite a list - note some of these would be covered by a test in safe mode.
http://www.thewindowsclub.com/deskto...ically-windows
Windows 7 Annoying Bug: Explorer doesnt refresh automatically when Create/delete/move any file/folder | Syed Jahanzaib Personal Blog to Share Knowledge !

 

Windows 10 File Explorer: No Automatic Refresh

After a few days, File Explorer stops automatically refreshing. Operations like:

• Adding or renaming a file
• Deleting a file
• Adding a folder
• Moving a file/folder
• etc.

complete successfully, but nothing happens visually until I manually press F5.

Some of you may realize that this question has
been asked several
times before, like this one nine
years ago. I've tried every single resolution step I can find that's been suggested. The problem always returns.

I think it's time someone from Microsoft answers this question properly. Why does a well documented bug like this go this long without a fix? Can you provide a solution that works and hasn't been blindly copied and pasted multiple times?