[...]count to ten, then unplug.
Aaaaahhhh! So that's the trick!

Also, if you get the "device busy, cannot unmount" error, try using the handle tool from sysinternals - it will often show you which program is the sinner. Doesn't always work though, which puzzles me; I'd really like to know what has the device locked in those situations.I've had a Command Prompt do that to me a few times, if it's open on that drive letter with nothing running for awhile.
A tool I have not used recently, but which I think would also help is the free utility Unlocker which can be found here: http://ccollomb.free.fr/unlocker/Unlocker, truly one of my favorites and it works on x64.
Unlocker, truly one of my favorites and it works on x64.It works for you?
Does unlocker work on Windows XP 64 or Vista 64? Not yet, I am working on it.I tried it some time ago, and it didn't work on my system (vista 64). Would it be that it was updated and now works? That'd be great

Unlocker, truly one of my favorites and it works on x64.It works for you?Quote from: from unlocker's webpageDoes unlocker work on Windows XP 64 or Vista 64? Not yet, I am working on it.I tried it some time ago, and it didn't work on my system (vista 64). Would it be that it was updated and now works? That'd be great
@jgpaiva:I've been using process explorer's "find handle"/"close handle" feature, and it works great. I just wanted the simplicity of Unlocker, a few clicks and you're done
If Unlocker doesn't do it for you and your 64-bit system...there is always: file-assassin. If memory serves me well, there is a 64-bit version.
http://www.malwarebytes.org/fileassassin.php


Original address: https://www.donationcoder.com/forum/index.php?topic=8088.0