Keyboard drivers
Fix unrecognised keystrokes, macro keys, and RGB lighting communication.
You might also need
Keyboard drivers we cover
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.
Why keeping it updated matters
Keeping the keyboard stack current fixes concrete, reproducible faults rather than delivering vague speed-ups. A frequent example is the sticky repeat or double-typing problem, where one keystroke registers twice; this often traces to a debounce or HID report-parsing regression that a corrected kbdhid.sys or a vendor firmware update resolves. Another is the dead media row or backlight after a Windows feature update replaced a vendor filter driver with the generic one.
Updates also matter for laptops that suspend and resume. A stale i8042prt or ACPI keyboard driver can leave the internal keyboard unresponsive after the lid is opened, forcing a full reboot until the corrected driver restores wake handling. Security is a factor too, because keyboards are HID devices and a badly behaved filter driver can crash the input stack with a bugcheck, taking the whole session down.
Common warning signs of keyboard driver failure
- 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
How to fix keyboard driver problems
Confirm the fault is the driver, not the hardware
Plug the keyboard into a different USB port, ideally a rear motherboard port rather than a hub, and test in Notepad. Boot into the UEFI firmware setup: if the keyboard works there but fails in Windows, the hardware is fine and the driver or HID stack is the likely cause.
Reinstall the keyboard in Device Manager
Open Device Manager, expand Keyboards, right-click your keyboard entry and choose Uninstall device. Reboot; Windows redetects the HID keyboard and rebuilds kbdhid.sys and kbdclass.sys bindings from a clean state, which clears most double-typing and stuck-key faults caused by a corrupt install.
Let Windows Update refresh the HID driver
Open Settings, go to Windows Update, click Check for updates, then open Advanced options and Optional updates. If a driver for your keyboard or its HID controller is listed, install it and reboot. This is the supported way to obtain a maintained generic keyboard driver.
Install the vendor app for missing features
If typing works but macros, media keys or lighting are dead, install the companion software from your keyboard maker's support page for your exact model, such as G HUB, Synapse or iCUE. Reboot so its filter driver and service load and the extra HID collections become active.
Error codes linked to this hardware
Helpful guides
Should You Use Driver Updater Software?
Driver updater tools promise one-click fixes but add risk. Here's what they really do, when they cause problems, and the safe way to check drivers yourself.
DCH vs Legacy Drivers in Windows 10/11
DCH drivers split hardware support from control-panel apps in Windows 10/11. Why the change happened and how to tell which type you have.
How to identify unknown devices with hardware IDs
A practical walkthrough for naming every mystery entry in Device Manager using hardware IDs, driver details, and Windows' built-in tools.
Frequently asked questions
Why does my keyboard type the same letter twice on a single press?
Double-typing on one press is usually a debounce or HID report-parsing problem rather than a broken switch. Uninstall the keyboard in Device Manager and reboot to rebuild kbdhid.sys bindings cleanly. If it persists, check for a firmware update in your keyboard maker's companion app, since the microcontroller's own debounce timing may need correcting.
Why does my keyboard work in the BIOS but stop once Windows loads?
The firmware uses a simple built-in driver, while Windows loads the full HID or i8042prt stack. If it works in UEFI setup but dies at the desktop, the hardware is fine and a corrupt Windows keyboard driver is at fault. Uninstall the device in Device Manager, reboot to redetect it, and check Windows Update for a refreshed HID driver.
Why did my keyboard's media keys and backlight stop working after a Windows update?
A Windows feature update sometimes replaces a vendor filter driver with the generic HID keyboard driver, which handles typing but not the extra HID collections for media keys and lighting. Reinstall the companion app from your keyboard model's support page so its filter driver and service reload and those keys become active again.