Keyboard drivers
Keyboard HID reports, scan codes, input stacks, macro interfaces, and lighting controls.
You might also need
Keyboard drivers we cover
Quick facts
- Hardware family
- Input Devices
- Works with
- Windows 11, Windows 10
- Last reviewed
- Aug 18, 2026
Reference scope
DriverUpdateMax documents driver purpose, architecture, terminology, and compatibility. It does not distribute driver packages or provide repair, installation, or technical-support services.
What does a keyboard driver do?
A keyboard driver sits between the physical keys and every application that expects text or shortcuts. When you press a key, the keyboard's onboard microcontroller detects which switch closed on the key matrix, applies debounce timing so a single press is not read as several, and sends a HID (Human Interface Device) report over USB. The driver receives that report, maps the raw usage code to a Windows scan code, and passes it up through the Win32k input subsystem to the focused window.
On contemporary Windows PCs the keyboard work is shared by a small stack of system components. Hidusb.sys and hidclass.sys handle the raw USB HID transport, kbdhid.sys translates HID keyboard usages into scan codes, and kbdclass.sys presents a single unified keyboard to the rest of Windows. A layout DLL such as kbdus.dll or kbduk.dll then decides which character each scan code produces, which is why the same physical key can type a hash or a pound sign depending on the selected layout.
Compatibility is model-specific
A driver is associated with hardware identifiers, an operating-system driver model, and a processor architecture. Devices in the same category can expose different controllers, firmware interfaces, and optional feature layers, so a category name alone does not establish package compatibility.
Where this driver fits in Windows
The keyboard driver sits between Windows, the applications you use, and the physical hardware. This layered view shows where the driver translates operating-system requests into device actions.
Observable keyboard device states
These observations can involve hardware, firmware, operating-system services, applications, or a driver. They are descriptive rather than diagnostic.
- A single key press registers twice or repeats without being held, pointing at a debounce or HID report fault
- Certain keys such as the media row, Fn combinations or backlight controls do nothing while ordinary letters work
- The keyboard works in the UEFI firmware setup but stops responding once the Windows desktop loads
- Device Manager shows the keyboard with a yellow triangle and an error code such as 10, 43 or 28
- The internal laptop keyboard is unresponsive after waking from sleep until the machine is fully rebooted
- N-key rollover fails so pressing several gaming keys at once causes ghosting or dropped inputs