Jul 13 2018 01:40 AM
We would like to migrate from Windows 2008 R2 File Server to Windows 2016 Server (Version 1607 OS Build 14393.2363).
Now we recognized that there must be a new limitation on the path length in Windows 2016 Server.
On the Windows 2008 Server we could access path longer than 260 characters whitout any problem. (Shared folder over the network or on the server with explorer. )
We enabled the GPO Setting : "Enable Win32 long paths" - without success.
Is there a workaround or is it impossible to move data with long path without substitute the path with shortnames ?
Any kind of help is highly appreciated
Thanks in advance!
Jul 13 2018 08:16 AM - edited Jul 13 2018 08:19 AM
What client OS has the problem?
https://www.howtogeek.com/266621/how-to-make-windows-10-accept-file-paths-over-260-characters/
Jul 15 2018 08:53 AM
Jul 15 2018 09:01 AM
I'd review the settings on the client. Also for the windows 7 clients this one might help.
Jul 16 2018 04:37 AM
Hi,
Found the Solution here: https://www.pelegit.co.il/enable-long-path-windows-server-2016/
Have to activate shortnames on tthe server on the apropriate volume:
fsutil 8dot3name set d: 0
After i copied the Data again from the Source Fileserver, everything works as expected with all the Windows Clients!
Thanks To all for your help!
Apr 09 2020 12:05 AM
I suggest you try Long path tool is the very good
program for easily delete, copy & rename long path
files, error, unlock solution.
Try it and solve your problem.
May 07 2020 09:28 AM
@Dave Patrick Windows 8 is now replaced with Windows 10, But all still work the same. Just minor fixing.
Nov 04 2020 08:38 AM
@Silvan Diem This is precise use case for the Path Too Long Auto Fixer tool I built, it's the st tool that discovers, reports and auto corrects filenames and paths that are too long to fit under the MAXPATH 260 character limit.