How do I delete a corrupt zombie file in Win 10?

I can’t delete it, move it, rename it or do anything with it. I tried using cmd, no joy there either. It’s like the file exists but it doesn’t. So I tried deleting the whole folder, nope can’t do that either. Somehow the file got renamed, not sure if Win did it or how it happened. The file got renamed “~tmp~(file name) (file size) (date).pdf” Somehow the file size and date got included as part of the file name but the .pdf extension is correct.

I had this problem and had to boot up in safe mode, command prompt and delete by navigating to the folder with dir commands and then either del the file or rmdir the folder. I’m not even sure rmdir is the command, but easy to google that part.

Try using the command prompt, but execute “dir /X” first. You’ll see a listing that includes lines like:
10/12/2019 11:38 PM 1,185,684 SPURGE~1.STL Spur Gear (48 teeth).stl

Note the “SPURGE~1.STL” name in there. That’s the old 8.3 short filename. You may be able to delete that instead of the long filename version.

Thanks, that gives me a few things to try, if those fail would there be any use in booting up with a linux live disc? I was never comfy with linux but I can probably muddle my way through it.

Good news is that I have multiple backups so if I hose something I’m not gonna lose any data.

Here’s a long-shot idea.

Using CMD, navigate to the containing directory and do an >attrib *.*

That will list all the files and their attributes. You might also try >attrib *.* /L in the off chance that somehow you’ve got a symlink, not an actual file, on your hands.

It sounds like you’ve got the skill to interpret what you’ll find and solve your problem if this reveals any new / unexpected info. If not, post what you find and the rest of us will tackle it.

Thanks @Dr.Strangelove, that did the trick! Also thanks to @What_Exit and @LSLGuy!

If that worked, then it is likely that the long file name somehow acquired a none printable character that you could not see or input. That happened to me some time ago.

I’ve always been a fan of FileAssassin.

Agreed. Especially since the Windows file APIs are littered with bugs when it comes to Unicode support. It would not shock me at all if it’s possible to have a filename with a special character that cannot be expressed (or converts to something wrong) when it goes though whatever file deletion API that it’s using.

Anyway, glad the trick worked!