Deleting files with VERY long file names

[J. P. Gilliver (John)]

Variations in that appear when you get past the counting number of 9, or
the first few characters include some not allowed in an 8.3 name (fewer
characters are allowed than in long names - spaces for example), or if
the extension has more than three characters, or ...

Yes, that's correct or close to correct, AFAIK. Still, the safest thing
is to use dir /x in a command window, so as not to accidentally use the
wrong name. Dir /x shows both names, which makes correct identification
easy.

Agreed.

 

[Gene E. Bloch]

Another method is to map a drive letter to a folder just above the problem
file. To do this share the folder to everyone and then map the folder as a
network share. Disconnect the drive when done and remove sharing
permission. Saves a lot of messing about with renaming

[]
Does SUBST no longer work in 7? (It works in XP; I think XP tries to dissuade
you from using it, but I haven't experienced any ill-effects, provided you
know you're using it.)

Mapping drive letters - and SUBST if available - are (possible) solutions to
the problem of too long a name including the path; if the path is not
involved, then use of the short name is better.

On this Windows 7 computer, subst /? in a command window gives a brief
help message. I would guess that means it works in Win 7.

Subst /help gives an error message

 

[Zaphod Beeblebrox]

Another method is to map a drive letter to a folder just above the problem
file. To do this share the folder to everyone and then map the folder as a
network share. Disconnect the drive when done and remove sharing
permission. Saves a lot of messing about with renaming

[]
Does SUBST no longer work in 7? (It works in XP; I think XP tries to dissuade
you from using it, but I haven't experienced any ill-effects, provided you
know you're using it.)

Mapping drive letters - and SUBST if available - are (possible) solutions to
the problem of too long a name including the path; if the path is not
involved, then use of the short name is better.

On this Windows 7 computer, subst /? in a command window gives a brief
help message. I would guess that means it works in Win 7.

Subst /help gives an error message

(-;

--
Zaphod

Adventurer, ex-hippie, good-timer (crook? quite possibly),
manic self-publicist, terrible bad at personal relationships,
often thought to be completely out to lunch.

 

[Zaidy036]

In message<[email protected]>, Bob I<[email protected]>
writes:
Another method is to map a drive letter to a folder just above the problem
file. To do this share the folder to everyone and then map the folder as a
network share. Disconnect the drive when done and remove sharing
permission. Saves a lot of messing about with renaming
[]
Does SUBST no longer work in 7? (It works in XP; I think XP tries to dissuade
you from using it, but I haven't experienced any ill-effects, provided you
know you're using it.)

Mapping drive letters - and SUBST if available - are (possible) solutions to
the problem of too long a name including the path; if the path is not
involved, then use of the short name is better.

On this Windows 7 computer, subst /? in a command window gives a brief
help message. I would guess that means it works in Win 7.

Subst /help gives an error message

(-;

subst /? works but /help gives an error on my Win7 64bit

 

[Gene E. Bloch]

On 3/09/2012, J. P. Gilliver (John) posted:
In message<[email protected]>, Bob I<[email protected]>
writes:
Another method is to map a drive letter to a folder just above the
problem
file. To do this share the folder to everyone and then map the folder as
a
network share. Disconnect the drive when done and remove sharing
permission. Saves a lot of messing about with renaming
[]
Does SUBST no longer work in 7? (It works in XP; I think XP tries to
dissuade
you from using it, but I haven't experienced any ill-effects, provided
you
know you're using it.)

Mapping drive letters - and SUBST if available - are (possible) solutions
to
the problem of too long a name including the path; if the path is not
involved, then use of the short name is better.

On this Windows 7 computer, subst /? in a command window gives a brief
help message. I would guess that means it works in Win 7.

Subst /help gives an error message

(-;

subst /? works but /help gives an error on my Win7 64bit

That's no surprise to me, since that's what I just reported two posts
up...

In this post, that's 4 and 6 lines above your comment.

 

[J. P. Gilliver (John)]

On 3/09/2012, J. P. Gilliver (John) posted:
In message<[email protected]>, Bob I<[email protected]>
writes:
Another method is to map a drive letter to a folder just above the problem
file. To do this share the folder to everyone and then map the folder as a
network share. Disconnect the drive when done and remove sharing
permission. Saves a lot of messing about with renaming
[]
Does SUBST no longer work in 7? (It works in XP; I think XP tries
to dissuade
you from using it, but I haven't experienced any ill-effects, provided you
know you're using it.)

Mapping drive letters - and SUBST if available - are (possible)
solutions to
the problem of too long a name including the path; if the path is not
involved, then use of the short name is better.

On this Windows 7 computer, subst /? in a command window gives a brief
help message. I would guess that means it works in Win 7.

Subst /help gives an error message

(-;

subst /? works but /help gives an error on my Win7 64bit

Before we get too far down this road: I mentioned subst because I find
it a lot easier to use, when just working within existing drives, than
using the mapping network drive method.

 

[atillarist]

Alf wrote on 02/13/2011 05:20 ET

I have picked up a few files with very long names that Windows 7 will no
delete (error message indicating that file names are too long). So far I hav
tried (1) rebooting, (2) moving or changing th
files names--will not work because I get a Windows error sound by jus clickin
on the files, and (3) using CMD to try to delete the files with old DO
commands--still get an error message re lengt
of the files

I would appreciate any suggestions. TIA. --Al


Posted with NewsLeecher v5.0 Beta
Web @ http://www.newsleecher.com/?usene

After days of searching I finally found solution for unlocking, managing an
renaming long named files. Get your problem solved fro
http://longpathtool.com/

 

[Gene E. Bloch]

Alf wrote on 02/13/2011 05:20 ET :
After days of searching I finally found solution for unlocking, managing and
renaming long named files. Get your problem solved from
http://something.something/

It looks to me like an old spammer is back with a new nym.

Any other opinions?

 

[Char Jackson]

It looks to me like an old spammer is back with a new nym.

Any other opinions?

I randomly see 'helpful' posts like the one above, all pointing to the
same utility, in most of my subscribed text groups. Like the one
above, they are usually replies to posts that are 1-4 years old.

 

[Tony Luxton]

I randomly see 'helpful' posts like the one above, all pointing to the
same utility, in most of my subscribed text groups. Like the one
above, they are usually replies to posts that are 1-4 years old.

So what? People might still want the information, even if it's been
answered before in a post that's long been deleted from the server.

 

[Char Jackson]

So what? People might still want the information, even if it's been
answered before in a post that's long been deleted from the server.

Replying to 4 year old posts, and basically spamming at the same time,
isn't really helpful.

 

[Bravesoul]

Solution For Excessively Long File Names in Windows 7

Ok after I had a problem deleting several files that have excessively long file names, I came to this forum and searched for a solution.
Some sounded a little to complicated to attempt.
Then it dawned on me like a light switch went off in my head.
I have wifi setup on my laptop, and from time to time send files and receive files from my phone.
I use an application called ES File Explorer which is a free application on the Android Market.
So I decided to delete the files using ES File Explorer.
Steps I took to delete file.
1. Shared out the drive with the problem in my case it was drive: K
---> note: I don't suggest you share your computer on a public network that would open your computer to risks. <----
2. Using ES File Explorer select Lan (search for computers on private wifi)
3. Logged into my computer through ES File Explorer (on my private wifi network)
3. Navigated to the file with the problem and told ES File Explorer to delete it.

Since my phone's operating system is based on linux I was able to delete it with no problem.
This solution should also work for extremely long directory names.

Hope this helps

 

[Retseem]

I just used the file explorer from 7-zip.
This explorer doesn't seem to care about file name lenght, path lenght\depth or whatsoever.

 

[lyf4ce]

CMD Prompt Solution

I just had this problem and used this in order to delete the files:

for /f "tokens=5* delims= " %g IN ('dir /x') DO (del "%g% /f /q /s)

Didn't delete directories, but deleted all files in them and then the directories could be deleted.

 

[wagu]

this worked for me, without a 3rd party tool

When I tried to delete it directly using the shortname, I still got the name is too long error. But when I renamed it first using the shortname, I was able to delete it using the new name.

STEPS:
1. dir E* /x (to find the short name of my long file name that started with letter "E")
2. ren EVIL001~1 deleteMe (renamed it to "deleteMe" using the short name)
3. del deleteMe (bye-bye evil long name file!!)

 

[Kellynim]

how to delete long path file

There are several reasons why Windows might not allow you to delete a file:

• The file might be in use in which case you can't delete the file until the program using it gives it up.
• The file might be marked read-only.
• The file name might be so long that Windows can't handle it. File names with more than 260 characters in them are often difficult to delete.

There are also several reasons why Windows might not allow you to change the name of a file; particularly its extension. All above apply here; as well as...

• Your system may not be showing file extensions by default.

We'll cover that one first and the others in turn.

 

[mramsden]

Simple solution .... works for same prob in Windows 8

It's not just the filename length .. it's also the path length.

I just created a folder in the root directory, moved the folder containing the offending files with the very long names into that single level deep folder, and deleted it there.

The shorter path length did the trick.

 

[daveq]

Thanks for the help. Been years I've had such files!

Thanks for the help. Been years I've had such files!

On 2/13/2011 4:20 AM, Alf wrote:
> I have picked up a few files with very long names that Windows 7 will not delete (error message indicating that file names are too long). So far I have tried (1) rebooting, (2) moving or changing the
> files names--will not work because I get a Windows error sound by just clicking on the files, and (3) using CMD to try to delete the files with old DOS commands--still get an error message re length
> of the files.
>
> I would appreciate any suggestions. TIA. --Alf
>
>
When in DOS or the Command Prompt as Windows 7 calls it did you try
deleting the file with the long name by using the short name as shown
with a dir /x while in the directory with the bad file?

The short name shown with the /x option will be a form of the long name
but limited to 8 characters.

 

[alexiusnor]

Alf bro have you ever used Long Path Tool, if not then i will suggest you to download this and use it..You will get solution of your problem shared here.

 

[bmiranda]

I have picked up a few files with very long names that Windows 7 will not delete (error message indicating that file names are too long). So far I have tried (1) rebooting, (2) moving or changing the
files names--will not work because I get a Windows error sound by just clicking on the files, and (3) using CMD to try to delete the files with old DOS commands--still get an error message re length
of the files.

I would appreciate any suggestions. TIA. --Alf


--
--------------------------------- --- -- -
Posted with NewsLeecher v5.0 Beta 1
Web @ http://www.newsleecher.com/?usenet
------------------- ----- ---- -- -

Had a similar problem before. I just used the Long Path Tool and it worked. The software can be downloaded for free. Very helpful!