How to copy files that have too long of a filepath in Windows?
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?
windows-7 windows copy-paste
add a comment |
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?
windows-7 windows copy-paste
1
See also Window 256 characters path name limitation.
– Gilles
Dec 1 '10 at 0:59
add a comment |
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?
windows-7 windows copy-paste
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?
windows-7 windows copy-paste
windows-7 windows copy-paste
asked Nov 30 '10 at 13:44
Brian SturmBrian Sturm
563269
563269
1
See also Window 256 characters path name limitation.
– Gilles
Dec 1 '10 at 0:59
add a comment |
1
See also Window 256 characters path name limitation.
– Gilles
Dec 1 '10 at 0:59
1
1
See also Window 256 characters path name limitation.
– Gilles
Dec 1 '10 at 0:59
See also Window 256 characters path name limitation.
– Gilles
Dec 1 '10 at 0:59
add a comment |
5 Answers
5
active
oldest
votes
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.
8
zipping the files worked!
– Brian Sturm
Nov 30 '10 at 21:19
@BrianSturm, Well, assuming they are 3rd party apps
– Pacerier
May 16 '15 at 0:24
Although I really hate this about Windows...the zip solution really saved my day. Thanks!
– Bas Slagter
Sep 18 '15 at 8:43
add a comment |
robocopy /E source destination
Robust File and Folder Copy.
Windows 7 and above:
Robocopy XP027 is a standard command on Windows 7 and above.
NT 4/ Windows 2000:
The Windows Server 2003 Resource Kit Tools include Robocopy XP010,
which can be run on NT 4/ Windows 2000.
Windows 95, or NT 3.5:
Robocopy does not run on Windows 95, or NT 3.5. (Robocopy is a Unicode application).
Windows 95, or NT 3.5 workaround:
The Microsoft Robocopy GUI will install Robocopy XP026 to C:Windowssystem32,
this version can run on older OS's,
and includes some features from XP027 (/BYTES) but has competely broken errorlevel handling.
Robocopy 'Jobs' and the 'Monitor source' option provide an alternative to setting up a Scheduled Task to run a batchfile with a Robocopy command.
6
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.
– Automatico
Apr 26 '15 at 0:40
1
amazing! Solution i never know until now this bult-in solution.
– SIslam
Oct 12 '15 at 8:01
2
Great solution - couple of further notes: (1) destination should include the folder name if copying the folder - e.g. if copying C:Windows to D:Windows the command would berobocopy /E C:Windows D:Windows
(i.e. not robocopy /E C:Windows D:). (2) Can move files instead of copying them by using the/MOVE
option.
– Steve Chambers
Jul 31 '17 at 8:57
On Windows, this is a reliable solution for NAS usage. You can start a copy of millions of files, and if the transfer is interrupted half-way through, it will pick up where it left off, not re-copying all files that have already have been transfered. It's really valuable when you have a Wifi connection that drops intermittently, and still want to be able to move large numbers of files with guaranteed completion.
– user19496
May 1 '18 at 10:54
This doesn't work for files that have invalid names on windows. Is there a flag for this that will help?
– Richard
2 days ago
add a comment |
You can access path lengths up to ~32k characters by prefixing with \?
.
\?C:SomeReallyLongPath
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.
2
This is a really great tip. I also works to get around handling com1, com2 etc filenames.
– Andreas Reiff
Jan 6 '15 at 11:58
add a comment |
FastCopy is open source C project written by SHIROUZU Hiroaki and is "The Fastest Copy/Delete Software on Windows." It supports UNICODE and over MAX_PATH (260 characters) file path names.
If you have hundreds of paths that are too long to fix, use "Path Tool Long Auto Fixer" Tool
2
FastCopy is really quite excellent. In particular, unlike RoboCopy it does useful things with directory junctions/soft links.
– rlpowell
May 16 '17 at 23:52
Excellent. Alternately, there is a SO answer that lists similar fast-copy programs that are also usually extended-path compliant.
– ingyhere
Dec 25 '17 at 19:00
add a comment |
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.
Any decent file manager can handle longer than 260 character file names.
add a comment |
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?
5 Answers
5
active
oldest
votes
5 Answers
5
active
oldest
votes
active
oldest
votes
active
oldest
votes
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.
8
zipping the files worked!
– Brian Sturm
Nov 30 '10 at 21:19
@BrianSturm, Well, assuming they are 3rd party apps
– Pacerier
May 16 '15 at 0:24
Although I really hate this about Windows...the zip solution really saved my day. Thanks!
– Bas Slagter
Sep 18 '15 at 8:43
add a comment |
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.
8
zipping the files worked!
– Brian Sturm
Nov 30 '10 at 21:19
@BrianSturm, Well, assuming they are 3rd party apps
– Pacerier
May 16 '15 at 0:24
Although I really hate this about Windows...the zip solution really saved my day. Thanks!
– Bas Slagter
Sep 18 '15 at 8:43
add a comment |
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.
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.
answered Nov 30 '10 at 14:08
Gani SimsekGani Simsek
2,4601718
2,4601718
8
zipping the files worked!
– Brian Sturm
Nov 30 '10 at 21:19
@BrianSturm, Well, assuming they are 3rd party apps
– Pacerier
May 16 '15 at 0:24
Although I really hate this about Windows...the zip solution really saved my day. Thanks!
– Bas Slagter
Sep 18 '15 at 8:43
add a comment |
8
zipping the files worked!
– Brian Sturm
Nov 30 '10 at 21:19
@BrianSturm, Well, assuming they are 3rd party apps
– Pacerier
May 16 '15 at 0:24
Although I really hate this about Windows...the zip solution really saved my day. Thanks!
– Bas Slagter
Sep 18 '15 at 8:43
8
8
zipping the files worked!
– Brian Sturm
Nov 30 '10 at 21:19
zipping the files worked!
– Brian Sturm
Nov 30 '10 at 21:19
@BrianSturm, Well, assuming they are 3rd party apps
– Pacerier
May 16 '15 at 0:24
@BrianSturm, Well, assuming they are 3rd party apps
– Pacerier
May 16 '15 at 0:24
Although I really hate this about Windows...the zip solution really saved my day. Thanks!
– Bas Slagter
Sep 18 '15 at 8:43
Although I really hate this about Windows...the zip solution really saved my day. Thanks!
– Bas Slagter
Sep 18 '15 at 8:43
add a comment |
robocopy /E source destination
Robust File and Folder Copy.
Windows 7 and above:
Robocopy XP027 is a standard command on Windows 7 and above.
NT 4/ Windows 2000:
The Windows Server 2003 Resource Kit Tools include Robocopy XP010,
which can be run on NT 4/ Windows 2000.
Windows 95, or NT 3.5:
Robocopy does not run on Windows 95, or NT 3.5. (Robocopy is a Unicode application).
Windows 95, or NT 3.5 workaround:
The Microsoft Robocopy GUI will install Robocopy XP026 to C:Windowssystem32,
this version can run on older OS's,
and includes some features from XP027 (/BYTES) but has competely broken errorlevel handling.
Robocopy 'Jobs' and the 'Monitor source' option provide an alternative to setting up a Scheduled Task to run a batchfile with a Robocopy command.
6
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.
– Automatico
Apr 26 '15 at 0:40
1
amazing! Solution i never know until now this bult-in solution.
– SIslam
Oct 12 '15 at 8:01
2
Great solution - couple of further notes: (1) destination should include the folder name if copying the folder - e.g. if copying C:Windows to D:Windows the command would berobocopy /E C:Windows D:Windows
(i.e. not robocopy /E C:Windows D:). (2) Can move files instead of copying them by using the/MOVE
option.
– Steve Chambers
Jul 31 '17 at 8:57
On Windows, this is a reliable solution for NAS usage. You can start a copy of millions of files, and if the transfer is interrupted half-way through, it will pick up where it left off, not re-copying all files that have already have been transfered. It's really valuable when you have a Wifi connection that drops intermittently, and still want to be able to move large numbers of files with guaranteed completion.
– user19496
May 1 '18 at 10:54
This doesn't work for files that have invalid names on windows. Is there a flag for this that will help?
– Richard
2 days ago
add a comment |
robocopy /E source destination
Robust File and Folder Copy.
Windows 7 and above:
Robocopy XP027 is a standard command on Windows 7 and above.
NT 4/ Windows 2000:
The Windows Server 2003 Resource Kit Tools include Robocopy XP010,
which can be run on NT 4/ Windows 2000.
Windows 95, or NT 3.5:
Robocopy does not run on Windows 95, or NT 3.5. (Robocopy is a Unicode application).
Windows 95, or NT 3.5 workaround:
The Microsoft Robocopy GUI will install Robocopy XP026 to C:Windowssystem32,
this version can run on older OS's,
and includes some features from XP027 (/BYTES) but has competely broken errorlevel handling.
Robocopy 'Jobs' and the 'Monitor source' option provide an alternative to setting up a Scheduled Task to run a batchfile with a Robocopy command.
6
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.
– Automatico
Apr 26 '15 at 0:40
1
amazing! Solution i never know until now this bult-in solution.
– SIslam
Oct 12 '15 at 8:01
2
Great solution - couple of further notes: (1) destination should include the folder name if copying the folder - e.g. if copying C:Windows to D:Windows the command would berobocopy /E C:Windows D:Windows
(i.e. not robocopy /E C:Windows D:). (2) Can move files instead of copying them by using the/MOVE
option.
– Steve Chambers
Jul 31 '17 at 8:57
On Windows, this is a reliable solution for NAS usage. You can start a copy of millions of files, and if the transfer is interrupted half-way through, it will pick up where it left off, not re-copying all files that have already have been transfered. It's really valuable when you have a Wifi connection that drops intermittently, and still want to be able to move large numbers of files with guaranteed completion.
– user19496
May 1 '18 at 10:54
This doesn't work for files that have invalid names on windows. Is there a flag for this that will help?
– Richard
2 days ago
add a comment |
robocopy /E source destination
Robust File and Folder Copy.
Windows 7 and above:
Robocopy XP027 is a standard command on Windows 7 and above.
NT 4/ Windows 2000:
The Windows Server 2003 Resource Kit Tools include Robocopy XP010,
which can be run on NT 4/ Windows 2000.
Windows 95, or NT 3.5:
Robocopy does not run on Windows 95, or NT 3.5. (Robocopy is a Unicode application).
Windows 95, or NT 3.5 workaround:
The Microsoft Robocopy GUI will install Robocopy XP026 to C:Windowssystem32,
this version can run on older OS's,
and includes some features from XP027 (/BYTES) but has competely broken errorlevel handling.
Robocopy 'Jobs' and the 'Monitor source' option provide an alternative to setting up a Scheduled Task to run a batchfile with a Robocopy command.
robocopy /E source destination
Robust File and Folder Copy.
Windows 7 and above:
Robocopy XP027 is a standard command on Windows 7 and above.
NT 4/ Windows 2000:
The Windows Server 2003 Resource Kit Tools include Robocopy XP010,
which can be run on NT 4/ Windows 2000.
Windows 95, or NT 3.5:
Robocopy does not run on Windows 95, or NT 3.5. (Robocopy is a Unicode application).
Windows 95, or NT 3.5 workaround:
The Microsoft Robocopy GUI will install Robocopy XP026 to C:Windowssystem32,
this version can run on older OS's,
and includes some features from XP027 (/BYTES) but has competely broken errorlevel handling.
Robocopy 'Jobs' and the 'Monitor source' option provide an alternative to setting up a Scheduled Task to run a batchfile with a Robocopy command.
edited Dec 28 '15 at 10:40
answered Jan 28 '12 at 7:34
user19496user19496
91021018
91021018
6
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.
– Automatico
Apr 26 '15 at 0:40
1
amazing! Solution i never know until now this bult-in solution.
– SIslam
Oct 12 '15 at 8:01
2
Great solution - couple of further notes: (1) destination should include the folder name if copying the folder - e.g. if copying C:Windows to D:Windows the command would berobocopy /E C:Windows D:Windows
(i.e. not robocopy /E C:Windows D:). (2) Can move files instead of copying them by using the/MOVE
option.
– Steve Chambers
Jul 31 '17 at 8:57
On Windows, this is a reliable solution for NAS usage. You can start a copy of millions of files, and if the transfer is interrupted half-way through, it will pick up where it left off, not re-copying all files that have already have been transfered. It's really valuable when you have a Wifi connection that drops intermittently, and still want to be able to move large numbers of files with guaranteed completion.
– user19496
May 1 '18 at 10:54
This doesn't work for files that have invalid names on windows. Is there a flag for this that will help?
– Richard
2 days ago
add a comment |
6
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.
– Automatico
Apr 26 '15 at 0:40
1
amazing! Solution i never know until now this bult-in solution.
– SIslam
Oct 12 '15 at 8:01
2
Great solution - couple of further notes: (1) destination should include the folder name if copying the folder - e.g. if copying C:Windows to D:Windows the command would berobocopy /E C:Windows D:Windows
(i.e. not robocopy /E C:Windows D:). (2) Can move files instead of copying them by using the/MOVE
option.
– Steve Chambers
Jul 31 '17 at 8:57
On Windows, this is a reliable solution for NAS usage. You can start a copy of millions of files, and if the transfer is interrupted half-way through, it will pick up where it left off, not re-copying all files that have already have been transfered. It's really valuable when you have a Wifi connection that drops intermittently, and still want to be able to move large numbers of files with guaranteed completion.
– user19496
May 1 '18 at 10:54
This doesn't work for files that have invalid names on windows. Is there a flag for this that will help?
– Richard
2 days ago
6
6
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.– Automatico
Apr 26 '15 at 0:40
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.– Automatico
Apr 26 '15 at 0:40
1
1
amazing! Solution i never know until now this bult-in solution.
– SIslam
Oct 12 '15 at 8:01
amazing! Solution i never know until now this bult-in solution.
– SIslam
Oct 12 '15 at 8:01
2
2
Great solution - couple of further notes: (1) destination should include the folder name if copying the folder - e.g. if copying C:Windows to D:Windows the command would be
robocopy /E C:Windows D:Windows
(i.e. not robocopy /E C:Windows D:). (2) Can move files instead of copying them by using the /MOVE
option.– Steve Chambers
Jul 31 '17 at 8:57
Great solution - couple of further notes: (1) destination should include the folder name if copying the folder - e.g. if copying C:Windows to D:Windows the command would be
robocopy /E C:Windows D:Windows
(i.e. not robocopy /E C:Windows D:). (2) Can move files instead of copying them by using the /MOVE
option.– Steve Chambers
Jul 31 '17 at 8:57
On Windows, this is a reliable solution for NAS usage. You can start a copy of millions of files, and if the transfer is interrupted half-way through, it will pick up where it left off, not re-copying all files that have already have been transfered. It's really valuable when you have a Wifi connection that drops intermittently, and still want to be able to move large numbers of files with guaranteed completion.
– user19496
May 1 '18 at 10:54
On Windows, this is a reliable solution for NAS usage. You can start a copy of millions of files, and if the transfer is interrupted half-way through, it will pick up where it left off, not re-copying all files that have already have been transfered. It's really valuable when you have a Wifi connection that drops intermittently, and still want to be able to move large numbers of files with guaranteed completion.
– user19496
May 1 '18 at 10:54
This doesn't work for files that have invalid names on windows. Is there a flag for this that will help?
– Richard
2 days ago
This doesn't work for files that have invalid names on windows. Is there a flag for this that will help?
– Richard
2 days ago
add a comment |
You can access path lengths up to ~32k characters by prefixing with \?
.
\?C:SomeReallyLongPath
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.
2
This is a really great tip. I also works to get around handling com1, com2 etc filenames.
– Andreas Reiff
Jan 6 '15 at 11:58
add a comment |
You can access path lengths up to ~32k characters by prefixing with \?
.
\?C:SomeReallyLongPath
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.
2
This is a really great tip. I also works to get around handling com1, com2 etc filenames.
– Andreas Reiff
Jan 6 '15 at 11:58
add a comment |
You can access path lengths up to ~32k characters by prefixing with \?
.
\?C:SomeReallyLongPath
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.
You can access path lengths up to ~32k characters by prefixing with \?
.
\?C:SomeReallyLongPath
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.
edited Jan 10 at 21:44
answered May 30 '14 at 9:53
BasicBasic
65511129
65511129
2
This is a really great tip. I also works to get around handling com1, com2 etc filenames.
– Andreas Reiff
Jan 6 '15 at 11:58
add a comment |
2
This is a really great tip. I also works to get around handling com1, com2 etc filenames.
– Andreas Reiff
Jan 6 '15 at 11:58
2
2
This is a really great tip. I also works to get around handling com1, com2 etc filenames.
– Andreas Reiff
Jan 6 '15 at 11:58
This is a really great tip. I also works to get around handling com1, com2 etc filenames.
– Andreas Reiff
Jan 6 '15 at 11:58
add a comment |
FastCopy is open source C project written by SHIROUZU Hiroaki and is "The Fastest Copy/Delete Software on Windows." It supports UNICODE and over MAX_PATH (260 characters) file path names.
If you have hundreds of paths that are too long to fix, use "Path Tool Long Auto Fixer" Tool
2
FastCopy is really quite excellent. In particular, unlike RoboCopy it does useful things with directory junctions/soft links.
– rlpowell
May 16 '17 at 23:52
Excellent. Alternately, there is a SO answer that lists similar fast-copy programs that are also usually extended-path compliant.
– ingyhere
Dec 25 '17 at 19:00
add a comment |
FastCopy is open source C project written by SHIROUZU Hiroaki and is "The Fastest Copy/Delete Software on Windows." It supports UNICODE and over MAX_PATH (260 characters) file path names.
If you have hundreds of paths that are too long to fix, use "Path Tool Long Auto Fixer" Tool
2
FastCopy is really quite excellent. In particular, unlike RoboCopy it does useful things with directory junctions/soft links.
– rlpowell
May 16 '17 at 23:52
Excellent. Alternately, there is a SO answer that lists similar fast-copy programs that are also usually extended-path compliant.
– ingyhere
Dec 25 '17 at 19:00
add a comment |
FastCopy is open source C project written by SHIROUZU Hiroaki and is "The Fastest Copy/Delete Software on Windows." It supports UNICODE and over MAX_PATH (260 characters) file path names.
If you have hundreds of paths that are too long to fix, use "Path Tool Long Auto Fixer" Tool
FastCopy is open source C project written by SHIROUZU Hiroaki and is "The Fastest Copy/Delete Software on Windows." It supports UNICODE and over MAX_PATH (260 characters) file path names.
If you have hundreds of paths that are too long to fix, use "Path Tool Long Auto Fixer" Tool
answered May 16 '17 at 23:30
MarkusMarkus
593
593
2
FastCopy is really quite excellent. In particular, unlike RoboCopy it does useful things with directory junctions/soft links.
– rlpowell
May 16 '17 at 23:52
Excellent. Alternately, there is a SO answer that lists similar fast-copy programs that are also usually extended-path compliant.
– ingyhere
Dec 25 '17 at 19:00
add a comment |
2
FastCopy is really quite excellent. In particular, unlike RoboCopy it does useful things with directory junctions/soft links.
– rlpowell
May 16 '17 at 23:52
Excellent. Alternately, there is a SO answer that lists similar fast-copy programs that are also usually extended-path compliant.
– ingyhere
Dec 25 '17 at 19:00
2
2
FastCopy is really quite excellent. In particular, unlike RoboCopy it does useful things with directory junctions/soft links.
– rlpowell
May 16 '17 at 23:52
FastCopy is really quite excellent. In particular, unlike RoboCopy it does useful things with directory junctions/soft links.
– rlpowell
May 16 '17 at 23:52
Excellent. Alternately, there is a SO answer that lists similar fast-copy programs that are also usually extended-path compliant.
– ingyhere
Dec 25 '17 at 19:00
Excellent. Alternately, there is a SO answer that lists similar fast-copy programs that are also usually extended-path compliant.
– ingyhere
Dec 25 '17 at 19:00
add a comment |
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.
Any decent file manager can handle longer than 260 character file names.
add a comment |
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.
Any decent file manager can handle longer than 260 character file names.
add a comment |
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.
Any decent file manager can handle longer than 260 character file names.
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.
Any decent file manager can handle longer than 260 character file names.
edited Aug 20 '18 at 12:13
answered Oct 12 '15 at 10:16
OvermindOvermind
7,91831631
7,91831631
add a comment |
add a comment |
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?
1
See also Window 256 characters path name limitation.
– Gilles
Dec 1 '10 at 0:59