Computer Help forum

Question

error with long filename after file has already been renamed

Hi have a problem copying a folder from my computer to a 1.5 TB Passport external hard drive. The folder is 191 GB. After copying everything over, there are 3 errors for 3 files because the filename is too long. What drives me crazy though is that I have already renamed these 3 files with shorter filenames. The error message from the copied files lists the old names, not the new ones. The file in the error message does not even exist, because I have renamed it. What is even more perplexing to me is that I do not get the error message if I copy only the folder that supposedly has the files with the long filenames. I still don't get the error even if I create a bunch of folders on the hard drive to recreate the files location in the whole directory on the new drive.

I'm getting errors for files that don't exist! What should I do?

Discussion is locked
You are posting a reply to: error with long filename after file has already been renamed
The posting of advertisements, profanity, or personal attacks is prohibited. Please refer to our CNET Forums policies for details. All submitted content is subject to our Terms of Use.
Track this discussion and email me when there are updates

If you're asking for technical help, please be sure to include all your system info, including operating system, model number, and any other specifics related to the problem. Also please exercise your best judgment when posting in the forums--revealing personal information such as your e-mail address, telephone number, and address is not recommended.

You are reporting the following post: error with long filename after file has already been renamed
This post has been flagged and will be reviewed by our staff. Thank you for helping us maintain CNET's great community.
Sorry, there was a problem flagging this post. Please try again now or at a later time.
If you believe this post is offensive or violates the CNET Forums' Usage policies, you can report it below (this will not automatically remove the post). Once reported, our moderators will be notified and the post will be reviewed.
Collapse -
Clarification Request
Any chance of a screen grab?

In reply to: error with long filename after file has already been renamed

All Answers

Collapse -
Answer
Why not shorten names and paths?

In reply to: error with long filename after file has already been renamed

And as a pre-warning the spam about the usual tool will vanish without warning.
Bob

Collapse -
already did

In reply to: Why not shorten names and paths?

I already did, and that is the problem. I already renamed the file so it has a short name, but I still get the same error with the original long filename. A file with the long filename doesn't exist though. It is confusing.

Collapse -
There are other limits

In reply to: already did

Such as folder depth. Until we see full details, try less depth as well.
Bob

Collapse -
Answer
dates in error message not correct and short names worked

In reply to: error with long filename after file has already been renamed

I fixed the problem. . . if you want to see my notes as I was working through the problem, you can read below.

Okay I just tried to copy the folder of my files to an external hard drive once again. I obtained the same error and took some screen shots for the 3 errors.

error 1
https://drive.google.com/file/d/0B55PHkbittzieENuYkpCYThkMXM/edit?usp=sharing
error 2
https://drive.google.com/file/d/0B55PHkbittziOTVYS2IySkx1OVE/edit?usp=sharing
error 3
https://drive.google.com/file/d/0B55PHkbittziZ0NvZEttZk1KajQ/edit?usp=sharing

Each file contains the full name of the file inside of it, therefore I can find the file by searching the full name. Here is a screenshot of the search results for the first file shown in the first error as an example.

https://drive.google.com/file/d/0B55PHkbittziNFJ5OFhfZFJnVG8/edit?usp=sharing

From these search results, you can see that there is only one file with a date of "4/10/13 11:47 PM" and a size of about "4 kb". You can see that this file, which is the only file that matches the criteria of the error message, has the short filename. The name of the file is not the long filename in the error message.

The full path of the folder in which this file resides is
C:\Users\kurtw_000\Documents\kurt\storage\wikipad\KurtWhittemoreWiki\data\azim58 wikispaces download as of 8-10-13

What happens if I try to recreate the error without copying all 191 GB of my files? I tested this. On the external drive I create a Users folder, create a kurtw_000 folder inside of this, create a Documents folder inside of this, create a kurt folder inside of this, create a storage folder inside of this, create a wikipad folder inside of this, create a KurtWhittemoreWiki folder inside of this, and create a data folder inside of this. I then try to copy the azim58 wikispaces download as of 8-10-13 folder into the data folder, and then there are no errors! Very confusing.

Perhaps search cannot locate files with long filenames? Therefore, maybe I have never actually found the version of the file with the long filename? The fact that the error message is for a file with a size of 3.51 kB, and the file I found from search has a size of 4 kB may support this hypothesis even though the two files have the same date and time.

Ah! I found the problem. The file with a date modified of 12/27/13 2:11 PM seems to have been causing the problem. When I renamed the file, the date modified changed to 4/10/2013 11:47 PM for some reason. Perhaps the date modified was not displaying correctly since the name of the filepath for the file was too long. Whatever the reason. . . I shortened the names of the 3 files in that location even though the date did not match the date from the error message, and the problem was solved. I copied the 191 GB folder to my external hard drive, and there were no errors!

Collapse -
"search"

In reply to: dates in error message not correct and short names worked

After decades, Microsoft continues to blow the file search function in Explorer. I wrote that off years ago and use the command line instead. There are better search apps.

Microsoft also has never cured another issue with Explorer. I've seen it crash since about 1995 on files that are images (jpeg) where the jpeg image is corrupt. I've shared that one with Microsoft at some trade shows and the answer has always been "don't do that." They don't consider it a flaw. It's just a file and if you rename it from 1.jpg to 1.txt then it works, copies in Explorer fine.

Microsoft has been given a lot of rope and time.
Bob

Popular Forums

icon
Computer Newbies 10,686 discussions
icon
Computer Help 54,365 discussions
icon
Laptops 21,181 discussions
icon
Networking & Wireless 16,313 discussions
icon
Phones 17,137 discussions
icon
Security 31,287 discussions
icon
TVs & Home Theaters 22,101 discussions
icon
Windows 7 8,164 discussions
icon
Windows 10 2,657 discussions

SMART HOME

This one tip will help you sleep better tonight

A few seconds are all you need to get a better night's rest.