Updated to Windows 10 1903 and now Explorer doesn't always refresh automatically!
By - akishore
I feel like it's never been guaranteed that folders refresh automatically. Between my PC running the most recent insider builds to the computers I use at work (both win7/10) that are quite behind the latest OS releases I feel like I've seen the issue on all of them at least once. Definitely not consistently but still.
I've not noticed any difference.
But F5 can be a bit more convenient to have it refresh.
Thanks for that keyboard shortcut. Much faster to refresh. Still amazingly annoying, but hopefully it gets fixed soon.
Hasn't happened to me ever since I updated manually to 1903.
Same thing here. Fresh 1903 and it only started happening after a couple weeks.
You're not alone.. I'm also actively looking for a fix on this annoying Windows 10 problem.
This is what I've tried which works
1. Added 'dontrefresh' on both 32-bit and 64-bit registry. (even I'm on Windows 10 x64)
2. File Explorer > File > Change folder and search options > Folder Options
Search tab > Check or uncheck ANY option > Restore Defaults > click Apply
3. Open Explorer > right click on Documents > Location tab > click Restore Default button > click Apply
4. Right click on desktop > Click Personalize > Themes > Desktop Icon Settings > Restore Default > click Apply
5. File Explorer > File > Change folder and search options > Folder Options
General tab > Restore Defaults > click Apply
NOTE1: Do this with only 1 File Explorer open
NOTE2: After 'Restore Defaults' you can revert to your own settings (on General tab)
After trials and error, this works for me on Windows 10 Pro 1903 version (Windows Update to the latest)
On my Downloads folder with below settings.
Sort by>Date modified
Now, all new downloads files will show on top in the list without pressing F5 refresh
This is truly a Windows 10 bug!!
\#WEDR – Windows 10 Explorer Doesn’t Refresh
\#FEDAR - File Explorer Doesn’t Auto Refresh
**Update**: After done all that, a reboot of Windows. I'm back to square one.
But this is what I've discovered. A little solutions.
Yes! I have this issue as well. However, I had it on a fresh install of 1803. Upgraded to 1903 about a week ago and still exists