Windows 10: enable win32 long paths but not work

Dear support TeamI have changed the following two settings in order to be able to open long-path files with more than 260 characters in file explorer, but I still can’t open long-path files even after restarting the computer after the changes. Please help me find out why. 1. opening the Registry Editor regedit.exe and navigating to HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\FileSystem. Look for the value "LongPathsEnabled" and make sure it is set to 2. Open the Group Policy Editor gpedit.msc and navigate to Local Computer Policy > Computer Configuration > Administrative Te

:)

 

GPO: enable win32 long paths

I saw that the Windows 10 Anniversary Update was supposed to address the limitation of long file paths and names. According to what I found, the new GPO entry of "enable NTFS long paths" was supposed to be added, but I didn't see it. Upon further research,
I did find the "enable win32 long paths" option one level up in the GPO.

Question: Was this supposed to address the problem? After I enabled it, rebooted the computer and confirmed that the setting was still enabled, I tried to copy a file (via File Explorer) from a local hard drive (G:\*.*) to a server share (\\SERVER\SHARE),
but it failed for the same old reason that the pathname was too long. Does this only work locally, or does it only work with specific capabilities, like PowerShell?

 

Enable Win32 long paths GPO not working

For work I frequently receive zip archives from other companies that contain deep trees of folders and documents. If I expand them into my own folder structure I often hit the 260 character path length limit. I'm dealing with large numbers of files and folders
and it is extremely time-consuming too reorganize and shorten names.

Since the Anniversary Update there is a group policy setting "Enable Win32 long paths" and I have enabled that. But it doesn't seem to work. I still get the filename or path too long errors when copying or creating folders in Windows Explorer that cross
the 260 limit. Are there other factors that influence this? I know the OneDrive synchronization app that is part of Office 365 als has problems with long paths, but it isn't working outside OneDrive and SharePoint folders either.

My system is Windows 10 Pro 64bit.

I don't think I had this limit in Windows 7, but I'm not 100% sure.

 

Enable Win32 long paths GPO not working

Hmm, bad news I'm afraid. In this thread I see replies from
apparently well-informed people claiming that even though Windows 10 is ready for long paths, Windows Explorer is not. It is suggested that a 3rd party fileviewer "One Commander" does support long paths.