Keyboard Not Working After a Windows Update: How to Roll Back the Driver and Fix It

Published on 2026-11-08 ยท 7 min read ยท By MiniTestLab Engineering Team ยท Category: Keyboards

Launch Companion Diagnostic Tool

Test your hardware right now in your browser with zero install:

Open Keyboard Tester

A Windows update broke your keyboard driver, and the fix is a targeted rollback through Device Manager, not a reinstall. Windows Update routinely pushes generic HID or chipset driver packages that overwrite vendor-specific keyboard firmware interfaces, particularly on USB hubs using an Intel or AMD USB 3.x host controller. The result is that the keyboard enumerates on the bus but the HID descriptor handshake fails silently, leaving the OS with no usable input device. On some machines a secondary culprit is the Filter Keys accessibility flag, which Windows 11 22H2 and 23H2 updates have been known to toggle on without user action.

Confirm the Keyboard Is Actually Dead, Not Just Misconfigured

Before you touch Device Manager, rule out a software-layer false alarm. Open Keyboard Test in a second browser tab. If keypresses register there but not in your application, the fault is application-specific or an input method editor conflict, not a driver issue. If nothing registers at all, proceed below.

Next, check Filter Keys. Go to Settings > Accessibility > Keyboard. If "Filter Keys" is toggled on, disable it immediately. Filter Keys sets a default ignore window of 1000 ms between repeated keystrokes, which makes the keyboard appear dead under normal typing cadence. This single setting has accounted for a large share of keyboard-not-working-after-Windows-11-update reports since the 23H2 rollout.

Also check Settings > Time & Language > Typing > Advanced Keyboard Settings. Confirm the input language is not set to a layout that remaps your keys to unexpected characters. A stray language pack pushed by Windows Update can silently swap your active layout.

Driver Rollback: Exact Path Through Device Manager

This is the primary fix when a keyboard stopped working after an update. Use a USB mouse to navigate if your keyboard is fully unresponsive, or use an on-screen keyboard (Win key > type "on-screen keyboard" > Open).

  1. Right-click the Start button and select Device Manager.
  2. Expand "Keyboards". You will see one or more entries. A generic Windows update typically installs "Standard PS/2 Keyboard" or "HID Keyboard Device" over a vendor driver.
  3. Right-click your keyboard entry and select Properties.
  4. Click the Driver tab. Note the Driver Date and Driver Version fields. If the date matches your last Windows Update installation date, this is your culprit.
  5. Click "Roll Back Driver". If the button is greyed out, Windows has already discarded the previous driver package. Skip to the manual INF section below.
  6. Select "Previous version of the driver performed better" when prompted, then click Yes.
  7. Restart the machine. Do not let Windows Update run immediately after boot.

If Roll Back Driver is greyed out, you need the vendor INF. For Logitech keyboards, the driver package is inside the Logitech Options+ or G HUB installer. For Corsair, it is bundled in iCUE. For Keychron, Ducky, and most tenkeyless mechanicals using a USB HID-only interface, the generic Microsoft HID driver is actually correct and the fault is elsewhere, usually the USB host controller driver described in the next section.

USB Host Controller Driver Rollback

If your keyboard enumerates in Device Manager but still produces no input, expand "Universal Serial Bus controllers" in Device Manager. Look for an Intel USB 3.x eXtensible Host Controller or AMD USB 3.10 eXtensible Host Controller entry. Windows Update frequently pushes a new version of these drivers, and the new version can break HID polling on downstream ports.

Right-click the host controller > Properties > Driver tab > Roll Back Driver using the same process above. If greyed out, go to the manufacturer site for your motherboard chipset and download the previous USB controller driver package manually. For Intel 12th and 13th gen platforms this is typically the Intel Chipset Device Software package, version 10.1.x rather than the 10.2.x that Windows Update may have pushed.

After rollback, block Windows from reinstalling the driver automatically. Open Settings > System > About > Advanced System Settings > Hardware tab > Device Installation Settings. Set it to "No (your device might not work as expected)" and confirm. This prevents the update loop.

Registry and HID Service Check

Some keyboard-not-working-after-Windows-update cases trace to the HID service being set to Manual or Disabled by an update script. Open Services (Win + R, type services.msc, Enter). Scroll to "Human Interface Device Service". Startup type must be set to Automatic. If it reads Manual or Disabled, double-click it, change Startup type to Automatic, click Start, then OK.

Also check this registry path: HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\kbdhid. The "Start" DWORD value must be 3 (demand start, which is correct for USB HID keyboards). If it reads 4, the device is disabled at the driver level. Set it to 3 and reboot.

For PS/2 keyboards (still common on desktop boards), check HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\i8042prt. The Start value must also be 3.

Comparison: Common Post-Update Failure Modes

SymptomMost Likely CauseFix Location
No keys register at allHID driver overwritten or HID service disabledDevice Manager rollback or services.msc
Keys register but wrong characters outputLanguage pack or layout swapSettings > Time & Language > Typing
Keys work but only after a long delayFilter Keys enabledSettings > Accessibility > Keyboard
Keyboard works in BIOS but not Windowskbdhid or i8042prt Start value set to 4Registry editor, services key
Keyboard dead on specific USB ports onlyUSB host controller driver version conflictDevice Manager, USB controllers section

Once your keyboard is responding again, run a full key matrix check with Keyboard Test to confirm every key is registering cleanly. If you also use a gaming mouse and want to verify nothing else was disrupted by the update, the Mouse Test tool covers button, movement, and scroll input in one session.

Frequently Asked Questions

Why does Windows Update keep breaking my keyboard driver?

Windows Update uses a driver ranking system that prioritizes digitally signed packages from Windows Update servers over locally installed vendor drivers. If Microsoft's catalog has a newer version number for a matching hardware ID, it will overwrite your working driver automatically unless you have disabled device driver updates in System Settings.

My Roll Back Driver button is greyed out. What do I do?

Windows only retains the previous driver package if it was installed within a certain window and the files were not cleaned up by Disk Cleanup or a storage sense pass. If it is greyed out, you need to source the correct INF file from your keyboard or motherboard manufacturer and install it manually via Device Manager > Update Driver > Browse my computer for drivers.

Will a USB-to-PS/2 adapter help while I troubleshoot?

Only if your motherboard has a PS/2 port and your keyboard supports the adapter electrically. Keyboards with USB-only controllers inside, which includes most modern mechanicals, will not function through a passive USB-to-PS/2 adapter. Active adapters with their own microcontroller do work but add another variable to the diagnosis.

Does this apply to wireless keyboards too?

Yes, with one addition. Wireless keyboards using a USB dongle (Logitech Unifying, LIGHTSPEED, or a proprietary 2.4 GHz receiver) go through the same HID driver stack. The dongle itself appears as a USB HID device. Run the same Device Manager rollback on the dongle's HID entry. Bluetooth keyboards additionally depend on the Bluetooth adapter driver, which is a separate rollback target under the Bluetooth section in Device Manager.

How do I stop Windows from reinstalling the bad driver after every reboot?

After completing your rollback, go to Settings > System > About > Advanced System Settings > Hardware > Device Installation Settings and select No. You can also use the Group Policy editor (gpedit.msc) at Computer Configuration > Administrative Templates > System > Device Installation > Device Installation Restrictions to block specific hardware IDs from being updated automatically.

The keyboard works in the Windows login screen but stops after I log in. What causes that?

That pattern points to a startup program or shell extension conflict rather than a driver issue. A common culprit is a keyboard macro or RGB management application (iCUE, G HUB, Synapse) that crashes on launch and takes the HID session with it. Boot into Safe Mode with Networking, confirm the keyboard works there, then disable startup items one by one via Task Manager > Startup Apps until you isolate the offender.

Launch Companion Diagnostic Tool

Test your hardware right now in your browser with zero install:

Open Keyboard Tester