How to delete zero byte files (cmd commands don't work)

[Gondvanaz]

After typing cmd commands, i get "The system cannot find the file specified" messages. I tried commands like DEL /F /S /Q /A "D:\Torrents\*" (folder's name is Torrents) but nothing works so far. Files' type is file, size - 0 byte. They appeared after downloading torrent files.

 

[basroil]

Usually "0 byte" files are those currently being used for scratch or otherwise temporary sized files. To delete them, you need to close any software using them.

 

[Gondvanaz]

I tried to delete these files in safe mode, but still can't get rid of them. Help, please.

 

[Gondvanaz]

Also tried after shutting down windows explorer... still can't. Any suggestions?

 

[Alabalcho]

Download Process Explorer from Microsoft, and use "Find handle" to find out the process which keeps that file open. THen either close the handle, or kill the process.

 

[Gondvanaz]

Download Process Explorer from Microsoft, and use "Find handle" to find out the process which keeps that file open. THen either close the handle, or kill the process.

How to find out the process which keeps that file open? I typed file's name in "Find handle or Dll" (process explorer search) and it did find nothing.

 

[Alabalcho]

Are you sure the file you're trying to delete is open, or you don't have the rights to delete it?
Second - make sure you run PE showing all processes (File | Show all processes...)

 

[Tom Brock]

I had this same problem. The solution in my case was simple (though I needed help thinking beyond the obvious).

Windows could not delete the file and threw the same error seen in the original post. Likewise using cmd, I could not delete the file. Or so I thought.

The file name *appeared* to be "Re-".
- However "del Re-" failed.
- But... I noticed that there seemed to be a space in the filename, that is "Re- " (using properties) and not "Re-".
- However again, "del Re- " failed.
- Eureka! "del Re-*."

In my case there was some unknown character that appeared as a space that was confounding Windows and cmd. The wildcard "*" took care of it.