Answer the question
In order to leave comments, you need to log in
Setting the maximum length of the file server directory path - how to remove the restriction correctly? NTFS Long Path?
I came across too long cataloging, which exceeds 250+ characters, I need to do even more, but they don’t give a limit ....
On the WinSRV Domain, I changed the GPO here: Local Computer Policy > Computer Configuration > Administrative Templates > System > Filesystem > NTFS
Enabled long paths Updated the policy, still does not give.
I did the same on the file server, updated the policy does not give ...
I did the same on the PC, it does not help.
How to properly disable this restriction?
This is the maximum path I could create, but it is no longer editable, I can’t even increase it by 1 character.
"A:\IT\TestTestTestTestTestTestTestTestTest\TestTestTestTestTestTestTestTestTestTestTestTestTestTest\TestTestTestTestTestTestTestTestTestTestTestTestTest\TestTestTestTestTestTestTestTestTestTestTestTestTestTestTestTestTest\ZITTestTestTestTestTestDocument"
Answer the question
In order to leave comments, you need to log in
This is a limitation of winapi. So it’s just that it’s not removed for everyone. Only those programs that themselves know how to bypass it or new ones written for Windows 10 in which the corresponding special settings specified in the program manifest and registry work. In short, it is better to change the approach
1. OS versions on the file server and the client from which you are accessing the shared folder?
If Windows 10 and Server 2016 \ Server 2019 - and if this key is in gpedit.msc both there and there - then everything should work.
https://docs.microsoft.com/en-us/windows/win32/fil...
2. What does "WinSRV Domain changed GPO here: Local Computer Policy " mean? Can you explain what you wanted to achieve?
Try this
\\server\IT\TestTestTestTestTestTestTestTestTest\TestTestTestTestTestTestTestTestTestTestTestTestTestTest\TestTestTestTestTestTestTestTestTestTestTestTestTest\TestTestTestTestTestTestTestTestTestTestTestTestTestTestTestTestDocument\ZITTestTestTestDocument
I know that the problem of long paths is definitely solved by changing the system to ReFS, this restriction has been removed there.
255 characters is the standard. Yes, new Windows allow you to bypass it. but you need to understand that you are making an unportable system that is incompatible with anything. a competent decision is to correct the author's head, and not bypass the standard.
Didn't find what you were looking for?
Ask your questionAsk a Question
731 491 924 answers to any question