This is really to just share another possible solution to when you find Windows File Explorer going slow which it less well known and does not show up in many of the lists of solutions to try when you experience this behaviour.
I don’t know about you but I always find it annoying when my computer’s behaviour changes drastically enough to affect work and a while back, whenever I opened File Explorer or used an application used File Explorer to look for a file. File Explorer would take ages, relatively speaking, to what I was used to. We talking about a change from about a few seconds (almost instantaneous) to about 1 a minute or more to display all the folder options, in the left-hand pane. The slow loading was also often accompanied by the progressive search indication in the address bar. And this happened every time the machine started up. So it was not something a ‘shut-down’ and ‘restart’, that is often the first thing to try and useful, would sort out. While the slow file searching did not stop work, it was seriously hindering and downright annoying.
This slowdown confused me as I could not think what might be the cause of it, but I had a sneaking suspicion File Explorer was looking for devices or networks no longer connected to the computer, but even when all network drives were connected the behaviour persisted. Frustratingly all the possible solutions that I was coming across were not resolving it and I spent a LONG time trying to find a solution to it. That’s ‘long time’ as in many short forays spread over time searching online.
The fix in this case was “Delete automatic destinations” found on The Geek Page (https://thegeekpage.com/file-explorer-is-opening-too-slow/)*. The process of resolving it is easy enough.
- Open the run command box by pressing the Windows key + R together
- Into the text field copy and paste the following code, then run.
- Select all files in the folder and delete them.
No promises that this is a fix for you, and if it does not work it is probably worth browsing and working through the possible fixes mentioned by The Geek Page.
* I’m not affiliated with them in any way, but happy to give a shout-out for mentioning this as a possible solution.