What is legacy USB support?

Legacy USB Support is a firmware-level (BIOS or UEFI) setting that allows USB devices—primarily keyboards, mice, and mass-storage devices—to be recognized and used before a modern operating system with its own USB drivers has loaded. It bridges the gap between older software and interfaces that were designed around legacy PS/2 ports and INT-based I/O, and the newer USB standard that requires a proper host controller driver stack.

The feature exists because the USB standard emerged in the mid-1990s, well after the PC BIOS and DOS-era software conventions were established. Programs written for those environments expected keyboard input through the legacy PS/2 controller (accessed via I/O ports 0x60 and 0x64) and interrupt calls such as INT 16h. Without a translation layer, a USB keyboard would be silent in these pre-OS scenarios.

Why It Matters

Legacy USB Support is essential in several situations where the full OS driver stack is unavailable:

Entering the BIOS/UEFI setup utility with a USB keyboard.
Using boot menus, boot managers (e.g., GRUB), or the Windows boot loader.
Running DOS, older diagnostic tools, or memory testers from a USB stick.
Operating a system in Safe Mode or a recovery environment that has limited driver loading.
Interacting with pre-boot execution environments and firmware shells.

If Legacy USB Support is disabled and no PS/2 ports exist, you may be unable to navigate the BIOS setup at all—since the USB keyboard won't respond before the OS boots.

How It Works

When enabled, the system firmware installs a small driver (often referred to as a USB SMM handler or a BIOS-level USB stack) that manages the USB host controller during the pre-boot phase. This handler performs several key jobs:

Enumeration: The firmware detects and initializes attached USB devices, assigning addresses and reading device descriptors.
Translation/Emulation: Input from a USB keyboard or mouse is captured and translated into the legacy interface the software expects—for example, emulating a PS/2 keyboard controller so that INT 16h calls return the correct scan codes.
System Management Mode (SMM): Many implementations use SMM, a high-privilege CPU operating mode, to intercept access to legacy I/O ports and redirect them to the USB device transparently.

Once a modern operating system loads its own native USB drivers, the OS typically takes ownership of the host controller, and the legacy emulation is handed off or disabled to avoid conflicts.

USB Legacy vs. Native OS Drivers

It is important to distinguish between firmware-level legacy support and the OS's native USB driver stack:

Legacy USB Support is limited, low-performance, and generally handles only HID (Human Interface Device) input and basic mass storage.
Native OS drivers provide full-speed, feature-rich access to every USB device class once the operating system is running.

BIOS/UEFI Configuration

The setting typically appears in the firmware setup under names such as:

Legacy USB Support
USB Legacy Support
USB Keyboard/Mouse Support
XHCI Hand-off or EHCI Hand-off (related handoff options)

Common values include Enabled, Disabled, and Auto. The Auto setting usually enables legacy support only when a USB device is detected at boot, disabling it otherwise for a marginally faster startup.

Common Use Cases

Server and workstation administration: Technicians configuring RAID controllers or firmware settings rely on USB keyboards working at the BIOS level.
Bootable USB media: Installing an OS, running antivirus rescue disks, or flashing firmware from a USB drive requires the drive to be visible pre-boot.
Legacy operating systems: DOS, older Linux distributions, or embedded systems that lack USB drivers.
KVM switches: Some KVM setups depend on legacy emulation to present devices to multiple machines.

Best Practices and Considerations

Keep it enabled on most systems unless you have a specific security or performance reason to disable it, especially if the machine has no PS/2 ports.
Security concern: Because legacy USB support can allow booting from USB mass-storage devices, organizations concerned about data exfiltration or unauthorized boot media may disable it (or disable USB boot specifically) and protect the setting with a BIOS password.
Troubleshooting: If a USB keyboard works in the OS but not in BIOS, verify that Legacy USB Support is enabled. Conversely, if a system hangs at boot with certain USB devices attached, toggling this setting can help.
XHCI hand-off: On modern systems using USB 3.x xHCI controllers, ensure the corresponding hand-off option matches your OS capabilities to avoid devices dropping out during boot.

Real-World Example

A CompTIA A+ technician receives a workstation that only has USB ports and no PS/2 connectors. The user reports they cannot press any key to enter the BIOS. The technician recognizes that Legacy USB Support has likely been disabled. By temporarily connecting the drive to another machine or using a PS/2-to-USB adapter with a legacy-capable device, they re-enable the setting, restoring full pre-boot keyboard functionality.

In summary, Legacy USB Support is a small but critical firmware feature that ensures USB peripherals remain usable in the many scenarios that occur before or outside of a fully loaded modern operating system.