Windows 10: Will Win 10 support a 3.5 floppy drive?

Two OSes on one computer with the same problem? Could be a hardware issue. Another test I use is to boot to a Linux LiveDVD [Linux Mint 17 or 18] with the problem hardware plugged in, see if it works that way.

 

yea, I had added an edit to last post as forgot that fact. Check BIOS. Booting from LiveDVD good suggestion as well

 

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.

 

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"???

 

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

 

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?

 

Some good additional test info. I'd like to get some more info and test each controller one at a time

1. Look at Property->Details tab again for the floppy. This time look for Inf section? My floppy installs using Inf section USBSTOR_CBI.NT. Is yours the same?

2. By default the USB Mass Storage driver file usbstor.sys is started on demand. It's started when you connect a flash drive as well as when you connect the floppy. So probably won't make a diff (but can't hurt). I want to start the driver on system startup and let stay running.

• Download Serviwin. Install 32 or 64 bit version.
• Right click, Run as admin
• Click View->Drivers
• Scroll to name: usbstor
• Right click->Change Startup Type to Automatic (Verify the Startup Type changes to Automatic. If it doesn't, you didn't run as admin)
• Reboot and try again

3. Finally, I know you said you tested the different controllers. Not sure how you did it so consider testing as follows. In post #26 I can see your m/b has 2 USB controllers

• One Asmedia 3.1 controller and
• One Intel 3.0 controller

I want to test by disabling one controller at a time to test the other. (Apologies, don't remember if you said it before, but assume you latest Intel and Asmedia drivers installed?). I don't think this approach should be a problem, but to be safe I'd create a disk image before we start. Once we disable the controller your USB mouse/keyboard is attached, they'll stop working. But upon reboot it Windows should connect them to the enabled controller.

Don't know if you did it this way already but I'd like to test controllers by disabling one at a time then rather by plugging into an external port. Based on internal h/w connections, sometimes Windows is constrained by choice of controller. But often Windows is free to dynamically choose whichever controller it prefers for the job. fyi.... You can see the current parent/child realtionships of your devices in DevMgr click View->Devices by Connection to see which controller your floppy was ultimately connected to

/* EDIT */
Oh. And while at it, connect the floppy to each port for both controller tests. And do you happen to know which controller was connected to for the case of hub where it worked the one time?

 

inf section has the same USBSTOR_CBI.NT

I got it figured out (or as Jethro would say "ciphered out").
I connected it to the front panel USB 3.0 port and failed.
I connected it to a port on the external (powered) USB 2.0 port that is connected to a USB 3.0 controller port and failed.
I connected it to a port on a PCIe USB 2.0 expansion card and it works! Tried it several times/boots and its solid.

I don't have any open USB 2.0 ports on that expansion card, it has 5 ports and I have 5 USB connected CD/DVD burners connected to the card (for my audio CD Production). I may have to install another PCIe USB 2.0 expansion card to get the needed port. The case I have only has two USB 3.0 front panel ports, no USB 2.0.

Here is what I tried. First one is attached to the front panel port.




This one is attached to a port on the USB hub




Finally, the PCIe USB2.0 port card.

 

Good find.

As you said you only had 3.0 ports, I only noticed the usb3 controllers on glance at Device Manager snapshot. Good to learn you also had extension cards with USB 2.0 ports.

Interesting to note neither the Asmedia or Microsoft USB3 drivers worked with the floppy. Yet Linux drivers did.