I typically run PortableApps from an external hard drive. Let's say I plug in one or two USB sticks after PortableApps is running. I run Explorer++ from the copy that is loaded on the hard drive. If I subsequently try to eject either of the USB sticks I get the "can't eject right now because a file is being used" or a similar nastygram. I get this message even when Explorer++ does not have its focus on either USB stick, but, for example, on the C drive. I need to close the copy of Explorer++ that is running in order to eject either USB stick without getting the nastygram. I have seen this on both XP and Win 7 machines.
I hesitate to label this post as a [bug] because perhaps this is PEBCAK.
It happens also with the default Explorer – definitely with Windows 7 and I also think with XP. My non-technical explanation would be that Windows Explorer keeps a copy of the disk structure or file structure in its memory, and therefore prevents ejection. I have often seen it happening with CF or SD cards (i.e. camera cards inserted in a reader), a USB key, or an external hard drive, with or without PortableApps on it.
With CF card, the problem may be "solved" by right-clicking on the card and selecting Eject. With other "non-ejectable" devices such as USB keys, it doesn't work and you have to close all Windows Explorer windows.
And since Explorer++, Total Commander and Free Commander use good chunks of the Windows Explorer code, the same problem exists.
Michel Gagnon
Montréal (Québec, Canada)
I also see this if I have a mounted TrueCrypt volume on a stick and try to dismount it with Explorer++ running. TrueCrypt complains and does not want to complete the dismount. BTW, I don't see this with TrueCrypt if I am running Windows Explorer. I attribute things like this to a gigantic conspiracy intending to drive me crazy. It's working ...