This allowed me to track down the cause to a plugin which created a drive mapping (to my P: drive) that has no ability to support files at the root (in P:/) because it fakes a bunch of non-windows network target file systems as sub-directories (i.e.
And it's a deep annoyance that this has made it impossible to investigate why the stalls are occurring so that I can track down whether there's a background program, service, or plugin involved.ĭoes anyone know of an alternate way to investigate, or else have any idea why starting ProcMon would prevent stalls from occurring?Īs an update, it turned out that while having ProcMon usually caused the stalls not to occur, I left it running (and restarted it whenever it crashed) all day, and eventually one of the stalls occurred with it enabled. While it is interesting that ProcMon "solves" my stalls, it is ugly and a bit impractical to try to leave it running all the time to get rid of the stalls (particularly as ProcMon reliably crashes in about an hour). After I close ProcMon, this effect seems to stick around for a little while (maybe as much as a minute), and then the stalls return. I took steps to clear the File Explorer cache, disable Quick Access, and various other recommendations, with no luck.Īfter that, I took the recommendation to look into the issue with Process Monitor (ProcMon) and made the very odd discovery that as long as ProcMon64.exe is running, the stalls stop occurring. The stalls aren't entirely consistent, but are a serious productivity issue when they are occurring.
I have been suffering from 30+ second File Explorer stalls when I open a new window as well as similar stalls when I open an Open File or Save File dialog from certain Windows 10 programs for a few months now.
0 kommentar(er)
