Can't delete exe off my desktop

[Uranium-235]

I downloaded a MCaffee sdat update for a client computer and I executed it on my desktop to make sure it wasn't corrupt. Ever since then, I get a sharing violation (source of destination file may be in use) when I try and delete it. Even if I shut my whole computer down, and bring it back up, it gives me the same thing. anyone have ANY freaking idea what the hell is causing this?

[Tyler]

Weird, I've never had that happen to me before. You could try deleting it in DOS :)

[Uranium-235]

this is windows 2000, there is not dos, there's a console, and it gives me the exact same thing

[Jason425]

step 1) log on in safe mode...
step 2) run all the spyware-removal goodies and try to delete the file
step 3) don't use a 5+year old OS
:D

[Uranium-235]

this 5+ year old OS is better then any other windows OS out there

[Jason425]

that's debatable and opinion-based...

GL with the file anyway...

[Tyler]

I mean you could use a bootable DOS disk that supports NTFS.

[Uranium-235]

if I remember correctly, the only NTFS thing for dos only supports reading

[Tyler]

I saw this posted elsewhere and it worked for them...

"Try this - go to another folder, click file, new, text. Type in text the exact name /detail of the file in question. Then copy it to the folder containing the other file and it should overwrite it. Then it should delete."

[james]

I've suggested tyler's suggestion before for things in this matter, and it USUALLY works, but not always. There's a program, wholockme, which will tell you what process is locking what file. That might prove useful (kill the process, delete the file, restart the process if needed). However, explorer actually has a nasty habit of locking some files, which makes that not an incredibly useful methodology for deleting the file.

[Uranium-235]

ahhh. I got wholockme, and it was explorer that locked the file, so I killed it, it restarted (explorer), and it deleted fine. I was actually planning on killing explorer with the task manager, then starting CMD with the task manager and deleteing it from there, but it deleted anyways