3 ms·
My issue with the 260 character limit is that it can easily be reached through normal usage, and can lead to some really strange behavior. * File cannot be mov
by MereInterest 4y ago
My issue with the 260 character limit is that it can easily be reached through normal usage, and can lead to some really strange behavior.
* File cannot be moved into a subfolder.
* Folder can be renamed, after which a file contained within it is inaccessible.
* File on a network drive may be accessible by some users, but not others. For example, one user may access the drive with the longer network name, while another has mapped the network drive as Z:\. A filename may exceed the 260 character limit for the first user, but not for the second.
* Cannot delete a folder, because it contains a file with a long name.
My experience may be biased due to using a program that recorded metadata in a filename, taking the majority of the 260 characters available in just the filename, but with the number of failure modes, I still don't think it is reasonable to have such a small limit.
- Tempest1981 4y agoExactly. I believe NTFS has supported 65535-char paths since, forever? But last I checked, even simple apps like Win10 Notepad will fail to open them. What is the point of the registry/gpedit setting to enable long paths system-wide -- when so much of Windows doesn't support it? File Explorer is really showing its age. Has any of this improved in Win11?