Re:Why doesn't Windows recognize a USB device plugged into a...
by drzaiusapelord on Friday June 26, 2015 @01:04PM
(#9786108)
>if you take them out without using "eject" first.
That's not exactly true. That only happens if the NTFS volume has a dirty bit set. That happens when you corrupt something and some check fails. I pull drives in and out all the time without ejecting and almost never see the error you mention.
If you pull the drive when there's a write going on, then you'll activate the dirty bit and get that message.
That's not exactly true. That only happens if the NTFS volume has a dirty bit set. That happens when you corrupt something and some check fails. I pull drives in and out all the time without ejecting and almost never see the error you mention.
If you pull the drive when there's a write going on, then you'll activate the dirty bit and get that message.