Windows 10: 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

:)

 

Long Path Setting not working

Seems Enabling Win32 long path to overcome the 260 character restriction has not yet resolved the issue. I have enabled Win32 long path under group policy editor--> Filesystem and also the reg key D word setting but continue to receive error " The file
name would be too ling for the destination folder....."

 

Error 'Destination path too long' - File name would be too long for the destination folder.'

I'm using Windows 10 Enterprise, I set the 'LongPathsEnabled' to 1 using regedit, I also Enabled the option 'Enable Win32 long paths' using gpedit.msc.

Detail instruction can be found at this link:

https://www.howtogeek.com/266621/how-to-make-windows-10-accept-file-paths-over-260-characters/?

Unfortunately, the limit still applies in my windows PC even after re-boot, despite hopes of its limit removal.

Any other workaround?

(Shorten the file names is not an acceptable solution, as I work on code base.)

 

Windows long file name or path name has failed in the new windows

I have a windows 10 on my older computer and it has a group policy program that allowed me to set up windows 10 to allow for long file names/path names and I have no issues because the limit is no longer there. I bought a new PC with windows 10 and the group
policy and registry modification no longer is there (group policy app) and no longer allows for long file names/path names which is not acceptable. My work needs to have directories/folders several layers deep and windows no long has the fix to change your
windows system and explorer to allow for this to happen. There is no solution posted yet that solves this issue. There are lots of complaints about it though. I can delete files/folders ok by changing where the files are located but that is not the solution
needed by myself or many others. We need to be able to allow for long file names/path names! My old PC with window 10 (newer installs make a mess out of it and had to take them off as they are not good upgrades. Group Policy app in later upgrades of the windows
10 series which made it easy to allow for long file/path names no longer is on windows 10.

$1300 for a pc with windows now is a bad investment - I hate mac but windows continues to fail as to being my favorite system.

My and many others need is how can we modify the registry or get the group policy to do it to allow for long file/path names and not be restricted to the very small limits. If anyone has an answer on how to do this, then It would make life easier. Work around
answers for copying files closer to the root part of the drive are not valid answers. I found this article but have not used it as too many other suggestions have been posted and they wasted our time fixing this issue. Here is that articles summary which is
what our needs are:

In the past the maximum supported file length was 260 characters (256 usable after the drive characters and termination character). In Windows 10 long file name support can be enabled which allows file names
up to 32,767 characters (although you lose a few characters for mandatory characters that are part of the name). To enable this perform the following:

That article link is: Enable long file name support in Windows 10