Forum Discussion

Silvan Diem's avatar
Silvan Diem
Copper Contributor
Jul 13, 2018

Windows 2016 Server Long Path

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!

 

 

windows server

8 Replies

  • MarkPahulje's avatar
    MarkPahulje
    Brass Contributor
    Nov 04, 2020

    Silvan Diem  This is precise use case for the https://pathtoolongautofixer.blogspot.com/ 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.

    • Homeypet's avatar
      Homeypet
      Copper Contributor
      Sep 21, 2021

      MarkPahulje 

      This is similar to what https://myhomeypet.com/ saw Earlier on onhttps://myhomeypet.com/www-ess-compasssassociate-com-login-ess-compass-associate-paystub-online/ I support Your Stand.

  • freddavis's avatar
    freddavis
    Copper Contributor
    Apr 09, 2020

    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.

    • Shoptool's avatar
      Shoptool
      Copper Contributor
      May 07, 2020

      Dave Patrick  Windows 8 is now replaced with Windows 10https://shopfortool.com/gmail-sign-up-free-gmail-login-account-gmail-sign-in-on-www-gmail-com/ But all still work the samehttps://logingit.com/sign-office-365-office-365-login/ Just minor fixing.

    • Silvan Diem's avatar
      Silvan Diem
      Copper Contributor
      Jul 15, 2018
      Thanks for the rrply.
      We have a mixed environment witj Windows 7/10 Clients.
      Now we like to migrate our Fileserver W2K8 R2 to W2k16 . When we copied the filestructure 1:1 to a Winows216 Server: The Windows 10 Clients see and access Filepaths deeper 256 chars but not create/modify files in that path. Window 7 can't see files deeper 256 chars.
      With the old fileserver 2k8R2 we had not this Problem. Why? What has changed ? What is the recommended procedure to migrate a fileserver ! could someone help?
      Thanks in advance.

Resources