Microsoft Removes 260 Characters Path Length Limit in Windows 10 RS

swarfega · 02 Aug 2016

So is this a good thing because the restriction has been remove? Are we now unlimited?

Brink · 02 Aug 2016

swarfega said:

So is this a good thing because the restriction has been remove? Are we now unlimited?

Not unless you enable it first. :)

https://www.tenforums.com/tutorials/5...dows-10-a.html

swarfega · 02 Aug 2016

Only time I'd need it I guess would be for music files.

pokeefe0001 · 02 Aug 2016

swarfega said:

So is this a good thing because the restriction has been remove? Are we now unlimited?

Not necessarily a good thing. You will be able to create longer path names now. Programs that check path length will now choke on the long path names but would work fine with a shorter path name. Is that good or bad? Worse, a program that just assumes max 260 length might copy the name without checking and possibly overlay something. (I don't actually know if that is possible.)

lehnerus2000 · 02 Aug 2016

pokeefe0001 said:

It would be nice if a "Warning" option (logging or otherwise notifying when a previously too long name is created) were available with this feature, but I suspect that's too much to wish for.

Agreed.

Given how much stuff is in modern operating systems there are quite a few useful features missing (e.g. time outs on file copying).

pokeefe0001 said:

The only time I've run into the length limitation has been when copying files from a directory with a short path name to a directory with a long path name.

I've had it occur when I've unzipped an archive which has ridiculous file structure inside it (e.g. Android Studio projects).

I've also seen a message saying that a file must be deleted because its path would be too long if moved to the Recycle Bin.

swarfega said:

Only time I'd need it I guess would be for music files.

I've experienced that when I was trying to rip a Pavarotti CD.
The filename included all of the performers, the orchestra, the opera name and track title.

BahBoh · 03 Aug 2016

I enabled long file paths using the policy editor but then I could NOT BELIEVE that File Explorer - Microsoft's File Explorer - in 2016 does NOT support long file paths !
How can Microsoft do that ?!

Can anyone tell me if the manifest hack above works for File Explorer ?

Mystere · 03 Aug 2016

BahBoh said:

I enabled long file paths using the policy editor but then I could NOT BELIEVE that File Explorer - Microsoft's File Explorer - in 2016 does NOT support long file paths !
How can Microsoft do that ?!

Can anyone tell me if the manifest hack above works for File Explorer ?

Most likely, they didn't bother to update Explorer yet because rumor has it that the next release (Redstone 2) is going to have a new Universal File Manger application (which will support the long paths).

jimbo45 · 03 Aug 2016

Hi there

It fails in file explorer so no good if copying / restoring in particular Music files where this restriction will be encountered most. Also some HYPER-V VM's have mega long file / directory names.

Cheers
Jimbo

Berton · 03 Aug 2016

I've seen part of the problem is confusing the distinction between LFN/Long File Names and Long Name File Path where Path includes the files with LFN. When needed I try to run file compression within a Folder and save in that Folder then move the resultant compressed file to a drive or Folder where I want it, bypass the Path issue.

AndreyT · 03 Aug 2016

swarfega said:

Only time I'd need it I guess would be for music files.

Not really.

A full path name includes a chained sequence of folder names that lead to the actual file. Which means that absolutely any file might end up with a path name that is too long once it is somehow gets placed too deep in the folder hierarchy. One Windows 8 blunder everyone is well aware of is related exactly to that: Windows 8 generated some internal folder names inside user profiles, which were too long for Windows itself to handle. And it was impossible to do anything with that data, unless one used some inelegant tricks.