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?
Maximum path length is 260 in Windows Vista/7. I can recommend three solutions:
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.
Windows 7 and above:
NT 4/ Windows 2000:
Windows 95, or NT 3.5:
Windows 95, or NT 3.5 workaround:
Robocopy 'Jobs' and the 'Monitor source' option provide an alternative to setting up a Scheduled Task to run a batchfile with a Robocopy command.
You can access path lengths up to ~32K characters by prefixing with
This works from the command prompt and any other programs which use the Win32 Unicode Api methods, including .Net apps. It does require a file system that supports long paths (eg NTFS) but if you have a long path problem, that's a given.
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.
How does this suit you.
In Regedit browse to this folder
and set the following value to 0
Quickest fix I used in this situation was to rename the over-long name folders to something like "1".
Also, as a general practice, I try to explain all users not to put their life story into a file or folder name.
protected by slhck Sep 13 '12 at 13:13
Thank you for your interest in this question.
Because it has attracted low-quality or spam answers that had to be removed, posting an answer now requires 10 reputation on this site (the association bonus does not count).
Would you like to answer one of these unanswered questions instead?