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
Click For Summary

Discussion Overview

The discussion revolves around the challenges of copying long file names and paths in Windows 8, particularly the error message indicating that file names are too long for the destination folder. Participants explore potential solutions, workarounds, and software recommendations related to this issue.

Discussion Character

  • Technical explanation
  • Debate/contested
  • Exploratory

Main Points Raised

  • One participant describes encountering an error when attempting to copy long file names and seeks troubleshooting advice.
  • Some participants suggest shortening file names or using a location with a shorter path as a workaround.
  • Others express a desire to change Windows configurations to allow copying without renaming files, questioning the feasibility of such changes.
  • Several participants assert that it may not be possible to bypass the internal limits imposed by Windows or other file systems.
  • A participant recommends a Microsoft cumulative update (kb 2919355) that claims to address related issues, though they have not personally tested it.
  • Another participant proposes defining a drive letter for a long path as a potential solution.
  • Concerns are raised about the risks of bypassing Windows limits, including potential issues with file usability and system stability.
  • Some participants inquire about software solutions, specifically mentioning the Long Path Tool and asking for recommendations for free alternatives.
  • There is a suggestion to use zipped versions or CD-images of files as a workaround for the problem.

Areas of Agreement / Disagreement

Participants express a mix of agreement and disagreement regarding the feasibility of changing Windows configurations and the effectiveness of proposed solutions. Multiple competing views remain on how to handle long file names and paths, and the discussion does not reach a consensus.

Contextual Notes

Participants reference the character limit for file names in Windows NTFS, noting that the limit is commonly cited as 260 characters, which includes the full device and folder names. There are also mentions of potential discrepancies in reported limits.

Who May Find This Useful

This discussion may be useful for users experiencing difficulties with long file names and paths in Windows, as well as those seeking technical solutions or workarounds for file management issues.

mech-eng
Messages
825
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.
 
Computer science news on Phys.org
You can shorten the filename and try again, or try a location that has a shorter path.
 
  • Like
Likes   Reactions: QuantumQuest
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.
 
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.

I don't think that is possible in Windows or any other file system that I know of.
 
I would recommend what Vanadium 50 suggests. Alternatively you would try kb 2919355 from Microsoft, here https://support.microsoft.com/en-us/kb/2919355. This is a cumulative update for Windows RT 8.1, Windows 8.1, and Windows Server 2012 R2. I haven't used it but it claims that one of the issues it fixes, is the one you describe.
 
anorlunda said:
I don't think that is possible in Windows or any other file system that I know of.

Absolutely correct and it is an issue of Windows Explorer itself and not of the NTFS file system.
 
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.
 
  • 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.
 
  • #10
I am Peter Brock

You should try out Long Path Tool program. I had the same problem, but this solved them all!
 
  • Like
Likes   Reactions: mech-eng
  • #11
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.
 
  • #12
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/
 
  • Like
Likes   Reactions: berkeman and mech-eng
  • #13
Do you know free programs of this sort?
 
  • #14
Could you use a zipped-up version or CD-image of the files?
Could you use a live linux CD to perform the operation?
 
  • #15
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.
 
  • #17
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:
  • Like
Likes   Reactions: berkeman

Similar threads

  • · Replies 19 ·
Replies
19
Views
5K
  • · Replies 16 ·
Replies
16
Views
5K
  • · Replies 35 ·
2
Replies
35
Views
6K
Replies
6
Views
2K
Replies
10
Views
3K
  • · Replies 2 ·
Replies
2
Views
2K
  • · Replies 30 ·
2
Replies
30
Views
3K
Replies
12
Views
5K
Replies
2
Views
3K
  • · Replies 3 ·
Replies
3
Views
2K