-Recklessly- remove hardware (from USB)

[SKesselman]

Hi,
Can someone please tell me what bad things will happen if I just unplug something from the USB, without "Safely remove"ing it?
Simply unplugging external devices/peripherals (a printer, a digital camera & a smartphone) doesn't seem to affect anything.
Does this apply only to certain types of hardware, or what?

Thanks.

[mouser]

wait for the experts to chime in, but i believe the real danger in prematurely unplugging a USB device is if it's a USB storage device of some sort that you have written TO (reading from shouldn't pose any risk).

in this case -- what you have worry about is that the operating system may not have actually finished writing to the drive even though it looks for all intents and purposes like it has.

other than that, it's hard to think what harm could really be caused.

[lanux128]

i concur with what mouser said. if you have to remove "recklessly", then at least enable the "Optimize for quick removal" option within your removable drive settings. you can read more about this option here.

[jgpaiva]

Here's a topic from 2007 about the dangers of not using the "safely remove" option. It's more directed at external disks, however.

[hpearce]

I use this now, so much easier http://for-free-on-i...nses-again-hurry-up/

[lanux128]

another "usb ejector" - USB Disk Ejector. this freeware also supports command-line parameters, can easily be run from Farr.

[f0dder]

Even with "optimize for quick removal", I'd still use "safely remove" to be 100% on the safe side. That will ensure all data is flushed and the filesystem is clean, and will notify you if there's programs still trying to access the device.

Do non-storage devices even show up on safely remove?

[SKesselman]

Do non-storage devices even show up on safely remove?

-f0dder (September 27, 2009, 11:57 AM)

Yes. All things USB show up. That's really why I'm asking - with my external drives, I'm happy to wait; with my printer or headset, it's so tedious...

[f0dder]

Hm, I don't think neither my printer nor my scanner shows up on the list - I always just yank those out anyway

[SKesselman]

Hm, I don't think neither my printer nor my scanner shows up on the list - I always just yank those out anyway

-f0dder (September 27, 2009, 12:16 PM)

  OK, question answered. Thanks!

[Innuendo]

If I recall correctly, the latest versions of Windows don't turn on a write cache for USB devices so they should be safe to just "yank out" unlike back in the Win98 days when doing so would surely corrupt your data.

I'm reading/writing from USB flash drives all day long & I'll confess that I'm a yank and run kind of person and never mess with "safely remove". I've been practicing this 'bad behavior' for a couple years now and data has never gotten corrupted.

But don't use my bad behavior as an excuse for you to act badly as well.

[Ehtyar]

Even with "optimize for quick removal", I'd still use "safely remove" to be 100% on the safe side. That will ensure all data is flushed and the filesystem is clean, and will notify you if there's programs still trying to access the device.

-f0dder (September 27, 2009, 11:57 AM)

Amen. However, it is extremely frustrating when Windows refuses to eject a device despite there being no open handles to it. I find that in this case, there are no adverse effects to simply yanking the device.

Ehtyar.

[f0dder]

Even with "optimize for quick removal", I'd still use "safely remove" to be 100% on the safe side. That will ensure all data is flushed and the filesystem is clean, and will notify you if there's programs still trying to access the device.

-f0dder (September 27, 2009, 11:57 AM)

Amen. However, it is extremely frustrating when Windows refuses to eject a device despite there being no open handles to it. I find that in this case, there are no adverse effects to simply yanking the device.

-Ehtyar (September 27, 2009, 06:24 PM)

I haven't experienced that?

However, I find that tortoisesvn's cache service often has a lock on an usb drive - killing the process fixes the problem

[lanux128]

if clicking/locating the 'safely remove' icon on the systray is tedious for you, then you can create a shortcut on the desktop with the following parameter.

[Select]

%windir%\System32\RUNDLL32.EXE shell32.dll,Control_RunDLL hotplug.dll

executing this shortcut will show the 'safely remove' dialog. plus you can also check the "Display device components" option which will display more info about the device, useful if you have more than one thumb drive plugged in at a time.

[4wd]

Even with "optimize for quick removal", I'd still use "safely remove" to be 100% on the safe side. That will ensure all data is flushed and the filesystem is clean, and will notify you if there's programs still trying to access the device.

-f0dder (September 27, 2009, 11:57 AM)

Amen. However, it is extremely frustrating when Windows refuses to eject a device despite there being no open handles to it. I find that in this case, there are no adverse effects to simply yanking the device.

-Ehtyar (September 27, 2009, 06:24 PM)

I haven't experienced that?

However, I find that tortoisesvn's cache service often has a lock on an usb drive - killing the process fixes the problem

-f0dder (September 27, 2009, 06:38 PM)

I used to get it a fair bit which I attributed to the "Shell Media Handler" in XP.  According to nlite info it can be responsible for keeping a lock on media files, (it's used for popup media file info and thumbnails of video files, IIRC).

However, ever since I started removing it and all the WMP components about the only thing that now holds a lock is Everything, (I should probably go through it's prefs and specify exactly which drives to only index....but it's so much easier to just exit it ).

[f0dder]

4wd: ah yes, shell media handler can be a lot of trouble - I haven't had that component installed for the last.. 5? years, so hadn't thought about it . It's especially a problem when you use 3rd party codecs; with unstable codecs (as those found in codec packs) and slightly corrupted media files, you get anything ranging from file locks to constant explorer crashes.