Will Win 10 support a 3.5 floppy drive?

The BIOS senses and identifies the drive correctly.

I have the latest BIOS.

I've got a Linux CD somewhere, I'll try that and see what happens.

fireberd said:

The BIOS senses and identifies the drive correctly.<snip>

Run a LiveCD w/USB3 support but also (as not clear from last post) check if any BIOS updates if you haven't done that yet too

Just booted up UBUNTU Linux and the floppy drive works OK in Linux. I was able to display the contents of a diskette.

The BIOS, as previously noted is up to date. This is a new installation and a BIOS update was done shortly after the build (mid December). ASUS Z170 ROG Maximus III Hero with an i7 6700K (Not OC'd) and 16 GB RAM.

What is a "LiveCD"???

fireberd said:

What is a "LiveCD"???

Generic term to any CD/DVD that boots to a working OS . (Started with CDs though now most need DVDs) I think "LiveCD"s originally came w/ Linux OS. Essentially same as a Rescue CD/DVD

You can also try a windows based rescue. i often use Gandalf's ISO boots to windows PE and packed with tools (4.3gb download). Handy to have around in any case. Burn to dvd or create bootable flash drive.

The latest x64 version is "Gandalf’s Win10PE x64 Redstone build 14393 version 11-10-2016"

The Linux DVD that I booted is a "LiveCD" and as noted the floppy drive was detected and works OK in Linux.

I have a Macrium WinPE disc, not sure if the floppy will be detected in that but will try it in the morning.

Thanks/Jack

fyi.... I just noted Redstone build 14393 is also insider preview. anxious to hear how macrium works. I imagine its based on a standard WinPE build

ComputerGeek said:

fyi.... I just noted Redstone build 14393 is also insider preview. anxious to hear how macrium works. I imagine its based on a standard WinPE build

Version 1607 Build 14393.693 [RS1] is the current iteration of the Released Win10 I have installed while my test computer with Insider Preview is at Version 1607 Build 15002.1001 with Build 15007 now downloading. Macrium worked fine with 14393 last week in cloning a Notebook HDD>

Berton said:

Version 1607 Build 14393.693 [RS1] is the current iteration of the Released Win10 I have installed while my test computer with Insider Preview is at Version 1607 Build 15002.1001 with Build 15007 now downloading. Macrium worked fine with 14393 last week in cloning a Notebook HDD>

I just downloaded Macrium Free, built a rescue image (after initial build an "Updated Macrium Files Found" pop-up appeared, I accepted it and rebuilt to flash drive)

• Booted into Macrium
• Connected my USB floppy to a USB3 port (i do have both USB2 and USB3 ports on mine)
• When Macrium window appeared, I minimized it
• At command prompt typed ver, Windows said 10.0.14393
• Opened Macrium window, selected "Browse for image" and my floppy drive appears

My floppy drive did not appear when I booted Macrium PE. I have a paid version of Macrium, shouldn't be different from yours but I never got the display you have.
I'll have to try it again.

UPDATE: Tried the Macrium rescue CD again. I found the display you have but it came up different than yours. The floppy drive was not listed.

So, back to it works in Linux but not Windows on this PC. I've tried the BIOS options for the floppy drive, Auto, FDD, Force FDD and it makes no difference.

I updated my Insider version to the latest version this morning. After updating the Insider version I tried the floppy drive and it failed with the Code 10, connected to a front panel USB port. I have a USB 2.0 powered external hub that I use for some printers and I plugged it into the external hub and it came up working. I restarted the PC with the Insider version and the floppy drive still connected to the external hub but it again came up with Code 10.

I had tried the external hub with my production Win 10 Pro installation before and it didn't work. I've tried it in two other rear I/O panel USB ports (on different internal USB controllers/hubs) and the same there, Code 10. I tried all the options available in the BIOS for the USB connected floppy drive and the three options - Auto, FDD, Forced FDD make no difference. The three options make no difference in Linux either - it recognizes the floppy drive in all 3 options.

The fact it worked one time, says its "close". Nothing else I can find in the BIOS for USB or the floppy drive. Thus it suggests something In Windows - maybe a registry entry?