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?

5
  • What application are you using to copy the files? It also has to be long-path aware. Aug 22, 2019 at 3:02
  • Windows Explorer. Aug 22, 2019 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. Aug 22, 2019 at 19:04
  • I can create 280 char paths (including filename) on windows explorer so I'm assuming it does support it. Aug 22, 2019 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. Sep 6, 2019 at 23:50

0

You must log in to answer this question.

Browse other questions tagged .