1

I have a Server 2016 file server and a Windows 10 client (fully patched) and even though I've enabled "NTFS long paths", I still get "the file names would be too long for the destination folder" error.

I can, however create files that are longer than 260 characters on the server. Is there another setting I need to modify in order to copy files with long path names?

  • What application are you using to copy the files? It also has to be long-path aware. – Harry Johnston Aug 22 '19 at 3:02
  • Windows Explorer. – user2629636 Aug 22 '19 at 14:04
  • And that works on the server? My understanding was that Windows Explorer doesn't support long paths at all, but my knowledge may be out of date. – Harry Johnston Aug 22 '19 at 19:04
  • I can create 280 char paths (including filename) on windows explorer so I'm assuming it does support it. – user2629636 Aug 22 '19 at 20:47
  • According to this 2016 post Explorer fakes long path support by "using the 8.3 shortname name for folders close to the root" so perhaps this is misleading you? Not sure why it wouldn't work just as well from the client though. – Harry Johnston Sep 6 '19 at 23:50
1

You can use the long path tool for this issue.

In using the long path tool you just have to click on the long path tool application icon and the tool will provide you a window that contains all your files. You have now the capability to move, delete rename and modify your files without getting error messages. It is a user friendly tool and it is a quick fix for this issue.

Not the answer you're looking for? Browse other questions tagged or ask your own question.