Keyboard Not Detected on Windows 11: USB Enumeration and Hidden Device Fixes
Launch Companion Diagnostic Tool
Test your hardware right now in your browser with zero install:
Open Keyboard TesterIf your keyboard is not detected on Windows 11, the most likely culprit is a USB enumeration failure caused by a corrupted HID descriptor cache, a dead VBUS rail on the port, or a ghost device entry blocking re-enumeration in Device Manager. Windows 11's stricter USB power management policies introduced in builds 22H2 and later will aggressively suspend ports that fail two consecutive enumeration handshakes, making the device invisible to both Device Manager and the HID stack. On the hardware side, the keyboard's onboard controller — typically an STM32F0 or similar ARM Cortex-M0 chip on mid-range boards — can lock up after a hot-plug event if the 5V VBUS line dropped below 4.75V during insertion, which is common on front-panel USB headers wired with thin 28AWG traces.
Verify the Port and Cable Before Touching Software
Plug the keyboard directly into a rear-panel USB-A port on the motherboard's PCH-connected header, not a front-panel port and not through a hub. Front-panel headers regularly measure 4.6–4.8V under load because of trace resistance; the USB 2.0 spec floor is 4.75V and some keyboard controllers will refuse to enumerate below it. Use a USB meter or a multimeter set to DC on the VBUS and GND pins (pins 1 and 4 on the Type-A connector) if you have one available.
Swap the cable if the keyboard uses a detachable one. Braided cables with thin internal conductors — common on cables marketed purely on aesthetics — add enough resistance to drop voltage further. Try a short, unbraided USB cable under 1.5 meters. If the keyboard uses a fixed captive cable, inspect the strain relief at both the board entry point and the connector for kinks. A partially broken inner conductor will pass 5V at idle but collapse under the 100mA enumeration burst.
Once you have the keyboard on a known-good rear port, run the Keyboard Test in your browser. If keypresses register there but Windows still shows no device in Device Manager, you have a driver or enumeration stack problem, not a hardware problem. If nothing registers in the tool either, the controller is not enumerating at all.
Clear Hidden and Ghost Devices from Device Manager
Windows 11 hides disconnected devices by default. A ghost entry from a previous driver install can hold a device ID that conflicts with the re-inserted keyboard, causing silent enumeration failure with no error in Event Viewer.
- Open an elevated command prompt and run:
set devmgr_show_nonpresent_devices=1then launch Device Manager from the same session withdevmgmt.msc. - In Device Manager, click View, then Show Hidden Devices.
- Expand Human Interface Devices and Keyboards. Greyed-out entries are ghost devices. Right-click each one and select Uninstall Device. Do not check the driver removal box unless you see a third-party filter driver listed.
- Expand Universal Serial Bus Controllers and uninstall any greyed-out USB Composite Device or USB Input Device entries as well.
- Unplug the keyboard, wait 10 seconds, replug. Windows should re-enumerate from scratch.
If Device Manager still shows nothing after replug, open Event Viewer at Windows Logs > System and filter for Source = usbhub3 or usbd. Event ID 24 indicates a descriptor read failure. Event ID 43 from the USB controller means the port itself is being reset-looped. Event ID 157 from the Kernel-Power source means the port lost power mid-enumeration, pointing back to a voltage problem.
USB Controller Driver and Power Management Settings
Windows 11 ships with the inbox usbhub3.sys and usbxhci.sys drivers. Motherboard vendors sometimes push a secondary Intel or AMD USB controller package through Windows Update that conflicts with the inbox driver on specific chipsets. Check Device Manager under Universal Serial Bus Controllers for any entry showing a vendor name other than Microsoft. If you see an Intel USB 3.x eXtensible Host Controller with a date older than 2022, update it through the motherboard vendor's support page directly — do not use the generic Intel Driver Support Assistant for this.
Selective Suspend is the second common software cause of a keyboard not showing up after sleep. Go to Control Panel > Power Options > Change Plan Settings > Change Advanced Power Settings > USB Settings > USB Selective Suspend Setting and set it to Disabled for both On Battery and Plugged In. This setting persists per power plan, so check every plan you use.
| Symptom | Most Likely Cause | Fix Layer |
|---|---|---|
| Not detected after sleep only | USB Selective Suspend re-suspending port | Power plan setting |
| Never detected, no Event Viewer entry | VBUS below 4.75V, controller not starting | Hardware — port or cable |
| Detected briefly then disappears | Ghost device ID conflict in HID stack | Device Manager cleanup |
| Detected in BIOS but not Windows | Filter driver or usbhub3.sys conflict | Driver reinstall |
| Detected on one port only | Dead port or PCH routing issue | Hardware — use working port |
BIOS Settings and Firmware-Level Checks
If the keyboard is not recognized in Windows 11 but does work in the BIOS, the problem is entirely in the OS stack and the hardware is fine. However, if the keyboard also fails to respond in BIOS, check these settings. Enter BIOS setup — typically Delete or F2 at POST — and confirm that USB Legacy Support or USB Keyboard Support is Enabled. On AMD X670 and B650 boards, there is a separate setting called XHCI Hand-Off that must be Enabled for the OS to take control of the USB controller from the BIOS firmware. If it is Disabled, the BIOS retains the controller and Windows never sees the device.
Some keyboards with onboard ARM controllers — particularly custom firmware boards running QMK or Via — can get stuck in bootloader mode after a failed firmware flash. In bootloader mode the keyboard enumerates as a DFU device, not an HID keyboard, so it will not appear under Keyboards in Device Manager. Look for an unknown device with VID 0x0483 (STMicroelectronics) or VID 0x03EB (Atmel/Microchip) in Device Manager. If you find one, you need to reflash the keyboard firmware using the appropriate tool for your board — QMK Toolbox for QMK-based boards, or the vendor's proprietary flasher.
After completing any of the above steps, recheck input response with the Keyboard Test. If you also use a mouse on the same system and want to confirm the USB stack is healthy for HID devices broadly, the Mouse Test will show whether pointer input is reaching the browser's HID layer correctly.
Frequently Asked Questions
Why does my keyboard work in BIOS but not in Windows 11?
BIOS uses its own USB stack independent of Windows. If the keyboard works there, the hardware is functional. The failure is in Windows's HID driver stack, a ghost device conflict, or a filter driver. Follow the Device Manager ghost device cleanup and USB Selective Suspend steps above.
My keyboard shows up in Device Manager but keys don't register. Is that a detection problem?
No. If the device node exists in Device Manager with no error code, enumeration succeeded. The input failure is in the HID report descriptor parsing or a software layer above the driver. Use the Keyboard Test to confirm whether the OS is receiving scancodes at all. If the tool shows keypresses but your applications do not, the issue is application-level input blocking, not a detection failure.
Can a USB hub cause a keyboard not to be detected on Windows 11?
Yes. Unpowered hubs drop VBUS voltage under load. A keyboard controller that draws close to the 100mA USB 2.0 enumeration limit — common on keyboards with per-key RGB — will fail to enumerate on a bus-powered hub that is already supplying two or three other devices. Use a powered hub with its own 5V adapter, or connect directly to the motherboard.
Does Windows 11 handle keyboard detection differently than Windows 10?
Yes, in two specific ways. Windows 11 22H2 and later apply more aggressive USB port suspend policies by default, and the HID arbitration layer is stricter about descriptor validation. A keyboard with a slightly malformed HID report descriptor that Windows 10 accepted may be silently rejected in Windows 11. In that case, a keyboard firmware update from the manufacturer is the only fix.
My wireless keyboard receiver is plugged in but the keyboard is not showing up. Same steps?
Start with the same USB enumeration checks — the receiver is a USB HID device and subject to the same ghost device and power issues. Also replace the keyboard batteries first, since a low-battery 2.4GHz transmitter will fail to complete the RF pairing handshake with the receiver even if the receiver itself enumerates correctly. If the receiver shows up in Device Manager but the keyboard does not pair, check the manufacturer's re-pairing procedure, which usually involves holding a button on the underside of the keyboard for five seconds.
How do I know if my USB port is physically damaged?
Plug a known-working device — a USB flash drive — into the suspect port. If it also fails to enumerate, the port is dead or the trace fuse on the motherboard (a small polyfuse labeled F1 or similar near the rear IO) has opened. These polyfuses reset after cooling down for 30 to 60 seconds with nothing plugged in. If the flash drive works but the keyboard does not, the port is fine and the problem is keyboard-specific.
Launch Companion Diagnostic Tool
Test your hardware right now in your browser with zero install:
Open Keyboard Tester