W
Wiborg
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):
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
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
36:28,5 explorer.exe 6676 FileSystemControl C:\Users\xxxxx\OneDrive NOT REPARSE POINT Control: FSCTL_GET_REPARSE_POINT
36:28,5 explorer.exe 6676 FileSystemControl C:\Users\xxxxx\OneDrive NOT REPARSE POINT Control: FSCTL_GET_REPARSE_POINT
36:28,5 explorer.exe 6676 FileSystemControl C:\Users\xxxxx NOT REPARSE POINT Control: FSCTL_GET_REPARSE_POINT
Which shows the inactivity of 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.
Any ideas to a fix or work around?
Continue reading...
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):
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
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
36:28,5 explorer.exe 6676 FileSystemControl C:\Users\xxxxx\OneDrive NOT REPARSE POINT Control: FSCTL_GET_REPARSE_POINT
36:28,5 explorer.exe 6676 FileSystemControl C:\Users\xxxxx\OneDrive NOT REPARSE POINT Control: FSCTL_GET_REPARSE_POINT
36:28,5 explorer.exe 6676 FileSystemControl C:\Users\xxxxx NOT REPARSE POINT Control: FSCTL_GET_REPARSE_POINT
Which shows the inactivity of 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.
Any ideas to a fix or work around?
Continue reading...