How to make longer file names and paths in Windows 8

  • Thread starter Thread starter mech-eng
  • Start date Start date
  • Tags Tags
    File Windows
Join the discussion
Registration is free. Ask a follow-up in this thread, or start your own.
16 replies · 11K views
mech-eng
Messages
826
Reaction score
13
Hi. I try to copy long file names and paths from one source to another but there is a problem. Windows cannot do the operation and gives this error. "File name(s) would be too long for the destination folder"
So how can troubleshoot this problem?

Thank you.
 
Physics news on Phys.org
Vanadium 50 said:
You can shorten the filename and try again, or try a location that has a shorter path.

Yes, I could but I would like to change window's configurations so that I could copy them without changing their names. I do not want to change folder's names.

Thank you.
 
If the target directory is a subdirectory with a long path, you can define a drive letter that points directly to that target. If the source is also Windows, the destination file names will then be short enough to handle anything in the source path names.
 
Reply
  • Like
Likes   Reactions: jim mcnamara and QuantumQuest
mech-eng said:
Yes, I could but I would like to change window's configurations so that I could copy them without changing their names. I do not want to change folder's names.

The problem with this is that you are exceeding an internal Windows limit. If we somehow manage to bypass this limit to get the file where you want it, there is absolutely no guarantee that you will be able to use it there. (Or, for that matter, to even delete it, so you risk borking your system) Problems may be subtle - for example, it might be possible to force this file to be created, but the name may be too long for the Registry entry of the application that opens it, rendering it useless.
 
Try to determine if it's just a few files. I'm on Windows 7, and only have one problem file, a secondary installer update for Visual Studio express, 163 characters long, ...kb3110221.exe with a very long prefix apparently used as parameters.
 
I am Peter Brock

You should try out Long Path Tool program. I had the same problem, but this solved them all!
 
Reply
  • Like
Likes   Reactions: mech-eng
Peter Brock said:
I am Peter Brock

You should try out Long Path Tool program. I had the same problem, but this solved them all!

Today I tried to make a backup. The windows gave a notification : Too long files names for the source files. It didn't show which files they were so that I could have changed them. Is that program have a special name? How can I get it? Does it determines which paths are too long or it make windows accept long files?

Thank you.
 
To clarify: the limit in Windows NTFS for the ( name of a file + full device(4):folder name + trailing nul character) = 260. You will also see it referenced as 256 characters with no device name. It is a property of the filesystem. You may also see other numbers which purport to be limits. This is from msdn:
https://msdn.microsoft.com/en-us/library/aa365247(VS.85).aspx

So. If you cd to a directory with a long filename, then create a file in that directory with a long name, you now can get file too long errors when you reference the file from, for example, the c: directory.

Program to help with the problem: https://longpathtool.com/
 
Reply
  • Like
Likes   Reactions: berkeman and mech-eng
robphy said:
Could you use a zipped-up version or CD-image of the files?

Would you please explain what "CD-image of files" here is?

Thank you.
 
mech-eng said:
Hi. I try to copy long file names and paths from one source to another but there is a problem. Windows cannot do the operation and gives this error. "File name(s) would be too long for the destination folder"
So how can troubleshoot this problem?

Thank you.
I suggest you use LongPathTool for removing, renaming, coping and deleting files and folders with very Long Paths.

[Mentor Note: See post #12 for the URL for the LongPathTool software]
 
Last edited by a moderator:
Reply
  • Like
Likes   Reactions: berkeman