Safelyremove kills explorer.exe and I'm left without a desktop
Posted: Mar 23rd, 2008, 5:48 am
How nice...
Safelyremove tells me that explorer is accesing the drive (actually, the only "access" is a FOLDER VIEW of drive h:\somedir open.
So I see the "process" and I say "ok, I'll let safelyremove kill it", and it proceeds to KILL THE WHOLE DESKTOP (instead of closing the folder view), so... the desktop never comes back. I'm left with the applications already open and that's it.
Suggestions/questions:
1. Is this working as intended?
2. If it's going to kill the whole desktop and it never comes back (XP SP2 here, FWIW), why not show a warning of some kind?
3. Why not close the folder view, rather than the whole desktop
4. Why does the "scanning" trying to find the process which is accessing the drive take so darn long? I'd use WinXP's built-in util, it takes about the same time to tell me it can't unplug the device.
FC
Safelyremove tells me that explorer is accesing the drive (actually, the only "access" is a FOLDER VIEW of drive h:\somedir open.
So I see the "process" and I say "ok, I'll let safelyremove kill it", and it proceeds to KILL THE WHOLE DESKTOP (instead of closing the folder view), so... the desktop never comes back. I'm left with the applications already open and that's it.
Suggestions/questions:
1. Is this working as intended?
2. If it's going to kill the whole desktop and it never comes back (XP SP2 here, FWIW), why not show a warning of some kind?
3. Why not close the folder view, rather than the whole desktop
4. Why does the "scanning" trying to find the process which is accessing the drive take so darn long? I'd use WinXP's built-in util, it takes about the same time to tell me it can't unplug the device.
FC