OSDev.org

BenLunt wrote:As far as I know, Rufus does not restore the USB drive so that Windows can access it. The indicator light on the thumb drive itself goes out, the instant Rufus is done with it, and it never comes back on. I also don't get the usual "beep beep" when you unplug a USB device.

Huh, that's interesting. What version of Rufus are you using? I use Rufus all the time, and I always can use the drive after it finishes.

nexos wrote:

BenLunt wrote:As far as I know, Rufus does not restore the USB drive so that Windows can access it. The indicator light on the thumb drive itself goes out, the instant Rufus is done with it, and it never comes back on. I also don't get the usual "beep beep" when you unplug a USB device.

Huh, that's interesting. What version of Rufus are you using? I use Rufus all the time, and I always can use the drive after it finishes.

Sorry, what I was trying to imply was that after Rufus is done with the drive, it does not restore the drive to allow Windows to see a connection and re-enumerate it. If I pull the drive, then re-insert the drive, as long as it is a valid FAT file system, Windows mounts it just fine.

Ben

If I pull the drive, then re-insert the drive, as long as it is a valid FAT file system, Windows mounts it just fine

On my Windows, Windows automatically remounts while Rufus is working. IIRC, you use XP, right? I believe that was before Autorun came into existence. That would explain it.

Windows behaves oddly when it finds something that resembles a valid filesystem. I had a flash drive with a leftover NTFS backup boot sector at the end of the drive, and none of Microsoft's own format tools could work with the drive until I used a hex editor to remove it.

nexos wrote:you use XP, right? I believe that was before Autorun came into existence.

AutoRun was first enabled for USB flash drives in Windows XP service pack 2, but it's been around since Windows 95.