Windows 10: Microsoft Removes 260 Characters Path Length Limit in Windows 10 RS

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.)

 

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).

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.

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. *Eek

 

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).

 

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

 

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.

 

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.

 

Well, it doesn't take a rocket scientist to realize that support for long path names is still a work in progress. It is not even enabled by default.

We stopped asking such questions after the infamous recent blunder with Regedit, which crashed during Search operations because of exceedingly long registry key names.

 

It's not great... Explorer uses hard-coded buffers in various places that don't allow paths greater than 256 characters and there are a bunch of shell extensions (including some in Windows) that are affected.

You would be better off finding an alternative file browser.

Rumor you say? *Wink

https://i.imgur.com/pgASs0x.png

 

It's rumor that it will be in RS2, not that they're working on one (one never knows when or if it will actually make it into the build, or if it will replace the desktop File Explorer)

 

If only there were some developers at Microsoft.