Crash when NTFS long paths are enabled

[jonzy]

xplorer2 version: 3.2.0.2 [Unicode] x64 4/21/2016
Windows 10 version: 1607 (OS Build 14393.447)

I enabled long paths on my Windows 10 Home machine by editing this registry key (change from 0 to 1):
HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\FileSystem > LongPathsEnabled

After signing out, xplorer2 crashes immediately when it is opened.

Disabling LongPathsEnabled again fixes the issue.

I emailed a crash log already, but I thought I'd post this here for the benefit of the community as well. Is there a fix for this?

Thank you!

[nikos]

I believe yours crashes because you left xplorer2 browsing a very long path. It shouldn't crash but hey!?
I tried to enable huge paths on my win10 using LongPathsEnabled registry tweak, and somehow it doesn't turn them on as it should
so for the time being I cannot comment any further

[jonzy]

Thanks for your work, and for looking into this, Nikos. I'm a big fan of xplorer2.

I'm not sure why that hack wouldn't work... Afaik if you're on a Windows build > 14352 it should. I didn't spend much time with it myself yet, but so far I didn't get any of the usual "path too long" errors anymore, so that part seems to be working for me.

[nikos]

I am on 14393 (anniversary) so it should be working. I tried it in a VM, I don't want to risk my main working environment
anyway long paths are going to be addressed before long no matter how hard work it's going to be (for next to nothing)

[nikos]

as it turns out, windows explorer AND everything based on windows shell (read xplorer2) still cannot use very long file names for most file operations. I have updated the blog article. So nothing much has changed, back to square 1
www.zabkat.com/blog/long-8.3-path-names.htm

[RightPaddock]

The 260 character limit is/was a legacy of HPFS, the native OS/2 file system (circa 1989) ==> High Performance File System

When I first saw reference to "Windows 10 AU" I wondered if MS were producing country specific versions