-
-
Notifications
You must be signed in to change notification settings - Fork 2.3k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Feature: Add full support for \\?\
(256 character limit bypass)
#14865
Comments
FYI https://learn.microsoft.com/en-us/windows/win32/fileio/maximum-file-path-limitation |
I made a relevant comment about this issue under #9531 It's not enough to disable this limitation in WIndows, though. The app has to implement this feature for it to work. |
Is this being worked on? I am looking for a new file explorer and long file paths is the main reason why I am looking for an alternative file explorer. |
Not yet |
For network path you would need to use : \?\UNC\ . I will see If I can find some time to work on it. |
@samcarrier Are you thinking about working on this? I have a need to support long pathnames and was thinking about tackling this as well. Was a software developer a long time ago but perhaps I can make a go of it, or work with you |
Either way, I'll help you out understand the codebase and how storage access works if you have questions when working on. |
Any news on this? Thanks a lot |
It's available if anyone wants to work on it. |
What feature or improvement do you think would benefit Files?
\\?\
can be used to bypass the 256 characters limit windows has. Files however doesn't interact with it fully only being able to read the folder files and nothing else.Can be tested using
Requirements
\\?\
to path (This could probably be hidden to users as it doesn't change anything with smaller paths once the below is also fixed)/
would have to be converted to\
before parsingFiles Version
3.2.4.0
Windows Version
10.0.22621.3155
Comments
No response
The text was updated successfully, but these errors were encountered: