0

When starting File Explorer the explorer.exe process attempts to cache information about files under the Desktop-root including network shares found on the network.

The operation used is called "FileSystemControl" and the method uses opportunistic locking "FSCTL_REQUEST_OPLOCK" to attempt caching information. If caching fails after a few attempts, FileExplorer pauses for 30 seconds until retrying - and finally giving up the attempt. Only when the final attempt fails - after more than 30 seconds, File Explorer is released to the user-interface.

Extract from SysInternals ProcMon filtered on process:explorer.exe and operation:FileSystemControl shows (xxxx is the username):

min:sec: 34:04,0 Explorer.EXE 9792 FileSystemControl C:\Users\xxxxx\AppData\Roaming\Microsoft\Internet Explorer\Quick Launch\User Pinned\TaskBar\File Explorer.lnk CANCELLED Control: FSCTL_REQUEST_OPLOCK

min:sec: 34:04,1 Explorer.EXE 9792 FileSystemControl C:\Users\xxxxx\AppData\Roaming\Microsoft\Internet Explorer\Quick Launch\User Pinned\TaskBar\File Explorer.lnk CANCELLED Control: FSCTL_REQUEST_OPLOCK

min:sec: 36:28,5 explorer.exe 6676 FileSystemControl C:\Users\xxxxx\OneDrive NOT REPARSE POINT Control: FSCTL_GET_REPARSE_POINT

min:sec: 36:28,5 explorer.exe 6676 FileSystemControl C:\Users\xxxxx\OneDrive NOT REPARSE POINT Control: FSCTL_GET_REPARSE_POINT

min:sec: 36:28,5 explorer.exe 6676 FileSystemControl C:\Users\xxxxx NOT REPARSE POINT Control: FSCTL_GET_REPARSE_POINT

Which shows the inactivity of 2 min 24 seconds until FileExplorer user interface is displayed.

If the user logs in to the network shares, FileExplorer will start without delays, but the user may have security and other reasons for not wanting to stay logged in all the time.

DISM and SFC reports no problems. I am looking for a solution that addresses the sympthoms not a generic repair/reinstall - pls.

Any ideas to a fix or work around?

  • 1
    Clear out your quick access list or disable it all together. Network drives in your quick access that are not available cause significant hang ups. – Appleoddity Nov 8 at 22:09
  • Relevant comment - my QuickAccess list is with local drive attached links only - no refs to network shares. – Wiborg Nov 8 at 23:02
  • Recent files? Seems to do the same thing. – Appleoddity Nov 8 at 23:06
  • Relevant comment - but my QuickAccess list is with local drive attached links only - no refs to network shares. The Desktop branch - build by Windows - refers to a Network node with reference to my network share - which as far as the ProcMon log shows causes this problem. Think this is where the root cause of this problem is. Windows cannot differ correctly between a drive that is visible and one that is available for use, then trying to access gets hung up somewhere in the storage driver system. – Wiborg Nov 8 at 23:08
  • Regarding recent files: Frequent and pinned files/folders are showed in the right-click pop-up - recent files I do not get when launching the file explorer. Can you be specific on the recent files clue? – Wiborg Nov 8 at 23:13

Your Answer

By clicking “Post Your Answer”, you agree to our terms of service, privacy policy and cookie policy

Browse other questions tagged or ask your own question.