Windows 10: Unable to truly enable Long Paths >260 chars

I have a project environment that has many recursive folders, entire folder/file path of which eventually is more than 260 characters which is a standard limit set by windows.What I Tried:1. Updated 'LongPathsEnabled' registry key2. Updated Group Policy Editor -> File System -> Enable win32 long paths3. restart of the machine & gpupdate /forceCurrent Status:Now, I'm allowed to create new files/folders in a long path >260 but ONLY FROM CLI. When I try the same thing from GUI, it prompts the error "Destination Path Too Long"Why I need to be able to create folder/file from GUI:I'm

:)

 

Enable or Disable Win32 Long Paths in Windows 10


Even with this setting enabled,
explorer will not let me move a long filename file + long folder name path greater than 260 chars?

So what is the point of enabling this setting?

What is the alternative software to Explorer that I can use to manage my files then?

 

Long Directory + File names > 256 chars --any sign of support yet

Hi there @clam1952

Appreciate your reply -- been there, seen it, done it (didn't get the T-shirt though !!!) Doesn't work. At least not with my servers : NAS (CENTOS 7.4 and RHEL Enterprise 7.4). File sharing system -- SAMBA / CIFS. Windows OS - W10 PRO X-64.

This is still a MEGA problem for a lot of people with Windows / Non Windows (Unix type server) connections.

Not sure how MAC shares these files with Windows either --I'm sure on the MAC there's no problem with the file names --be interesting to see how Windows accesses long file names from a MAC server.

Any offers to post shots of Mac source / server with Windows share showing file length etc > 260 chars.

File name + directory name + path must be > 260 chars in length on the MAC though.

Cheers
jimbo

 

Long path names (>260) works with some file browsers

Hi folks

Some file browsers now work with the long file names but "bog standard file explorer" plus applications based on the old explorer api will still fail. - You set long file names via reg key -- it's in the tutorials.

Anyway for example FILEZILLA (an FTP client) running on Windows can show correct files on a NAS server. File explorer fails.

Here's the screenshot





Files transferred successfully no names lost and can be seen with FILEZILLA on the LOCAL (windows machine) properly






After transfer the files can still be viewed correctly also in File explorer because the path length is shorter than 260 but it's a start to at least transferring files with long path names from a NAS server to windows. Files also play correctly.





Note : the basic problem is that the path name on the NAS server could well be quite long -- this NAS server has 20TB of HDD on it - around 4 - 5 TB of music. The destination path on windows won't include the whole NAS path length but you probably want the folder and music files which will pretty well always be <260 chars in path name lengths)

File explorer breaks down if you merely use it for copying these files vis "Connect Network drive" as it can't display the NAS directory properly as shown.



C'mon Ms can't you FIX file explorer please instead of getting involved in things like icons and live tiles . !!!!!!

Cheers
jimbo