How to fix Error 1124 on Windows 11

by

Troubleshooting Guide: Error 1124 – Floppy Disk Controller Error Not Recognized by Driver

Why This Error Happens

Error 1124 occurs when the floppy disk controller (FDC) sends a status code or hardware signal that the legacy flpydisk.sys driver cannot interpret, typically because the controller firmware is outdated, malfunctioning, or conflicting with modern hardware abstraction layers in Windows 11. This is often triggered by a faulty physical floppy drive/cable, a virtualized floppy controller (common in VMs) sending unexpected signals, or corrupted/mismatched driver files following a Windows update. Since floppy hardware is legacy technology, Windows 11’s default drivers have minimal error-handling logic for controllers that deviate from expected ATA/FDC standards.

Step-by-Step Resolution Guide

  1. Check Physical Connections (Physical Machines Only)
    Power down the machine, and verify the floppy ribbon cable and power connector are firmly seated on both the drive and motherboard. A loose or reversed cable is a leading cause of unrecognized controller signals.

  2. Update or Reinstall the Floppy Disk Controller Driver

  • Press Win + X → select Device Manager.
  • Expand Floppy disk controllers (or check under Storage controllers if hidden).
  • Right-click the listed controller → Uninstall device (check “Delete the driver software for this device” if available).
  • Restart Windows 11; the system will attempt to reinstall a default driver automatically.
  1. Manually Update Driver via INF File
  • Navigate to C:\Windows\System32\drivers\ and confirm flpydisk.sys exists and isn’t corrupted (compare file size/date with a known-good system or Microsoft documentation).
  • If corrupted, run sfc /scannow in an elevated Command Prompt to restore the file from the Windows component store.
  1. Disable the Floppy Controller in BIOS/UEFI (If Unused)
  • Reboot into BIOS/UEFI setup (usually F2, Del, or Esc during boot).
  • Locate Integrated Peripherals or Advanced settings and disable the Floppy Controller if no floppy drive is physically installed. This prevents Windows from probing a non-existent controller.
  1. For Virtual Machines: Remove Virtual Floppy Device
  • In Hyper-V Manager or VMware/VirtualBox settings, remove the virtual floppy drive from the VM configuration.
  • Ensure no ISO or virtual floppy image is mounted, as this can send malformed controller signals to the guest OS.

Alternative or Verification Steps

  • Verify the Fix: Open Event Viewer (eventvwr.msc) → Windows Logs → System, and filter for Event ID 1124. Confirm no new instances occur after a reboot and normal system usage for 24 hours.
  • Alternative Fix: If the floppy drive is legacy/unused hardware, disabling the device entirely in Device Manager (rather than troubleshooting drivers) eliminates the error source without needing functional floppy support.