Running Windows 8.1 and trying to rename a file using the Navigation Pane in File Explorer (the left hand panel aka folder view) is a game of beat the clock for me at the moment.
That's because every few seconds something is iterating over the folders in that panel. So a folder in rename/edit mode quickly either has all text selected (so next key press overwrites all previous key presses) or focus is lost.
If i just use the context menu and select rename, and watch, i can see a flash of arrows just briefly (like when you hover over with the mouse tho I've moved my mouse away previously) and a flicker of the text before all text is selected and focus is lost.
This only happens in the Navigation Panel, not in the Details panel... which consequently has become the workaround. And it happens on any drive or folder.
Nothing appears to be iterating when a folder is not in rename mode. No flickers or flashes. No excessive CPU or memory usage.
I've turned off all usual suspects:
- Windows Search
- Windows Defender
- Killed all processes down the point of just what's needed to keep the OS stable.
I'd like to be able to use "some utility" point it at a folder and then have it report every process that accesses that folder.
To iterate is to read, yes?
I've tried process explorer but it doesn't seem to be showing anything useful though I'm not necessary using it in an advanced manner. I'm just listing all processes and filtering for directory accesses.
How can I intercept this iteration?
Update 1 :
Ok so it helps to be using the proper tools. Mine were hopelessly outdated (Process explorer 2012). By updating to ProcMon 3.1, as per comments, I can get a much better handle on this via improved filtering:
So it seems the Nav Panel IS being iterated even when a folder is not in rename mode. However it is only being iterated when the drive is expanded and if I collapse the drive then it stops iterating.
When it is iterating it is generating exactly 20 events every 7 seconds as below:
Does this pattern look familiar to anyone?
Note: The drive and folder is irrelevant. This happens for any combination of drive and folder. Also PID 6084 is explorer.exe and that this is aberrant behaviour as a quick test on other pcs tells me they don't iterate / keep polling in this way.