Bug: Network search causes explorer.exe ntdll.dll to crash (1607 ver.)

This is happening on all computers with version 1607:


1- While searching for a keyword in a network drive, if the corresponding file resides deep in the folder tree (a very long path or a path close/above the windows character number limit), explorer crashes with event id 1000; 0xc0000374; explorer.exe caused ntdll.dll to crash.

2- After the first time the above bug happens, now everytime i try to click file explorer with the standard "go to quick access view", the same crash happens. When switching the standard view to "show this PC" instead, explorerl opens properly. I suppose the quick access memorized the path of my network search and it crashes as a result.





Important:
To rule out variables, I prepared a new computer with a fresh windows 10 install with nothing installed.
-Without windows updates (version 1511 IIRC), the problem does not exist.

-After installing the latest updates (version 1607) the problem appears immediately.



This is reproducible 100% of the time on fresh installs with nothing but update 1607 installed. How do I proceed to submit this bug to microsoft?


thanks

Hi, Did you have any luck resolving this? I can confirm that you're not alone with this issue and i am really surprised that there hasn't been a lot more people trying to get an answer to this. We have about 30 work stations accessing mapped network drives which have worked fine up until update 1607. Our temporary work around is to disable Quick Access and turn off preview pane, not really a workaround but it helps a lot of crashing.

NickGillam said:

Hi, Did you have any luck resolving this? I can confirm that you're not alone with this issue and i am really surprised that there hasn't been a lot more people trying to get an answer to this. We have about 30 work stations accessing mapped network drives which have worked fine up until update 1607. Our temporary work around is to disable Quick Access and turn off preview pane, not really a workaround but it helps a lot of crashing.

I had none. It does have to do with file path character limit.

I had to enable an option to start file explorer on a separate process (in folder options), so that when a crash happens, only explorer.exe closes and not the windows.

I will try your sugestions to see if it helps as well.


windows 10 is clearly not ready for businesses with this class of problems. Very concerning.

Hello,

I had a similar issue with some users, with the quick access, not the network search. I fixed it by clearing the file explorer history.
Right click on Quick Access -> Options -> Clear File Explorer history

yes but once the history gets populated with those very long network paths, it happens again.

This is a very big problem for my colleagues who have to search for files in network folders with very big paths.

I'm so glad to have found this post, I have exactly the same problem and had a suspicion it was related to long filenames/directories but couldn't find any other posts suggesting the same.

Has anyone logged this with Microsoft yet and if so is there a link to the thread I can follow?

Thanks to spyshagg for troubleshooting so far. None of the workarounds particularly help me, as my users frequently have to search our network drive for certain project names which is returning nested folders with long names, and then crashes their explorer window.

So the problem is resolved for me. In File Explorer go into View - Folder Options, then select the View tab and tick the option to Always show icons, never thumbnails.

I need thumbs to show (photography company).

In the mean time, old windows 10 versions reinstalled and windows updates disabled.