Take the 2-minute tour ×
Super User is a question and answer site for computer enthusiasts and power users. It's 100% free, no registration required.

I need to make backups of some files on a network share. However, I need to copy those files to my local drive before burning the disks because those files might be in use. Some of the files won't copy because the file path is too long. Is there any workaround other than changing the file structure?

share|improve this question
1  
See also Window 256 characters path name limitation. –  Gilles Dec 1 '10 at 0:59

4 Answers 4

up vote 8 down vote accepted

Maximum path length is 260 in Windows Vista/7. I can recommend three solutions:

  • (if the path is too long) First copy the folder to upper levels in windows explorer and then move it to your local computer
  • (if file names are too long) First try to zip/rar/7z them with an archive application and then copy the archive file to your local computer and then extract the contents.
  • Use third party apps.

All of these suggestions assume you have some sort of write access on the network shared folder/computer. If you can't do any of these then you might need help from your administrator.

share|improve this answer
4  
zipping the files worked! –  Brian Sturm Nov 30 '10 at 21:19
    
@BrianSturm, Well, assuming they are 3rd party apps –  Pacerier May 16 at 0:24
robocopy /E source destination

Robust File and Folder Copy.

share|improve this answer
1  
This is the solution. If you want to turn OFF support for paths with length greater than 256, pass in the /256 flag. Thanks a lot! I have struggled with this all day. –  Cort3z Apr 26 at 0:40

You can access path lengths up to ~32K characters by prefixing with \\?\. This works from the command prompt (and some programs which use the Win32Api Unicode methods).

\\?\C:\Some\Really\Long\Path

Note that certain applications and a lot of native tools (like Explorer) will have problems with these paths so use this to get yourself out of a hole, not into one.

share|improve this answer
1  
This is a really great tip. I also works to get around handling com1, com2 etc filenames. –  Andreas Reiff Jan 6 at 11:58

How does this suit you.

In Regedit browse to this folder
HKEY_LOCAL_MACHINE\System\CurrentControlSet\Control\FileSystem

and set the following value to 0
NtfsDisable8dot3NameCreation

share|improve this answer
3  
Can you elaborate? –  Imray Aug 26 '13 at 5:41
    
@Joe, Are you sure this works? –  Pacerier May 16 at 0:24

protected by slhck Sep 13 '12 at 13:13

Thank you for your interest in this question. Because it has attracted low-quality answers, posting an answer now requires 10 reputation on this site.

Would you like to answer one of these unanswered questions instead?

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