Windows 10: Win10 Home Explorer.exe Crashing with long file name folders

This is kinda funny but i need to post this. whenever i tried to browse map drive and all folders have different sub folders and it has a long filenames also. When i tried to browse and locate the files under each folders when i finally locate the file (pdf file) when i open it will refresh automatically (explorer.exe) and cannot open the file and i tried again but still same thing happened.

i need your help guys.

thank you

:)

 

Error 0xc0000374 (explorer.exe fault) after Anniversary Update

Can confirm seeing same behavior on multiple machines (various vendors). All anniversary and completely up-to-date.

Pre-anniversary update all works fine and/or an error message is displayed when working with long file names,
post anniversary update the experience is an explorer.exe crash, loss of all file explorer windows.

Experience can simply be replicated by mapping a network drive and accessing a long folder path, then trying to copy a file within the long path. As soon as interaction outside the folder takes place the explorer.exe crash occurs

Problem signature:

P1: explorer.exe

P2: 10.0.14393.0

P3: 57899981

P4: StackHash_5213

P5: 10.0.14393.0

P6: 578997b2

P7: c0000374

P8: PCH_CE_FROM_ntdll+0x00000000000A59A4

P9:

P10:

Faulting application name: explorer.exe, version: 10.0.14393.0, time stamp: 0x57899981

Faulting module name: ntdll.dll, version: 10.0.14393.0, time stamp: 0x578997b2

Exception code: 0xc0000374

Fault offset: 0x00000000000f73e3

Faulting process id: 0x1614

Faulting application start time: 0x01d1fd2b123e2953

Faulting application path: C:\WINDOWS\explorer.exe

Faulting module path: C:\WINDOWS\SYSTEM32\ntdll.dll

Report Id: c38c2f31-f9cf-4dba-87cb-004f71e90e55

Faulting package full name:

Faulting package-relative application ID:

Doing the long file/folder name fix using gpedit.msc or regedit has no impact, presumably file explorer is not yet manifest enabled to make use of this setting. Regardless, Anniversary behaves differently to pre-anniversary and it is clearly not desirable
that working with long file/folder names results in a crash, as opposed to a warning message!!

Please advise on suitable fix.

 

Quick Access Crashes Explorer

Same here. Windows explorer crashes and restarts when it comes to very long file names. Even just accessing the directory path where the the file with the long name is can cause it to crash. Sorting by columns, enabling preview pane or details pane, using
'Details' folder view or changing folder view type also crashes Explorer with long file names. Sometimes, it crashes when copying, moving or renaming files with long file names.

I enabled Win32 long paths but didn't make a difference. Does even Windows explorer support this? On Windows 7 this used to happen but very rarely. With Windows 10 it is very frequent and even more so with the Anniversary Update. With Free Commander
can access files with long file names without problems.