Fixing Windows 11 USB Keyboard and Mouse Issues: Quick Solutions

Unresponsive USB keyboards and mice can have several causes: the peripheral, connection, hub, driver, power management, or the computer itself. Establish where input stops working before changing system settings.

Start With the Connection and Device

Try another port directly on the PC, bypassing docks and hubs. A different port can help even on the same controller because the connector or hub path may differ. A USB 2.0 port is an alternative test, not a requirement for every keyboard or mouse.

Inspect the cable and connector for damage. For a wireless USB receiver, check batteries, pairing, and the receiver connection. Test the peripheral on another computer, and a known-working basic wired peripheral on this PC if available. See Microsoft’s mouse and keyboard checks.

Separate Firmware, Windows, and Sleep/Wake Symptoms

Record whether the keyboard works in firmware setup, at Windows sign-in, after sign-in, and after sleep. Failure only in one environment is a useful clue, but does not prove a specific driver is at fault. Firmware input support is model-dependent.

If Windows remains accessible through a built-in keyboard, touchpad, or touchscreen, save work and restart normally. Note any recent driver, Windows, docking-station, or firmware change. For wider failures, see USB device not recognized.

Check Drivers Without Removing All Input Support

Use Windows Update and the exact PC or motherboard manufacturer’s support page for applicable chipset, USB, dock, and input-device packages. Avoid generic driver-download sites. If the failure began after a driver change, check whether a supported rollback is available.

Device Manager can show errors and connected-device relationships. A controller’s Location Information is not guaranteed to provide a clear map to the physical sockets; use the manufacturer’s port documentation when needed. Do not uninstall every USB controller while relying on USB input to recover access.

Selective Suspend Is Not a Universal Fix

USB selective suspend allows an idle device to enter a low-power state while other devices remain active. It does not simply switch the entire hub off on every idle cycle. Microsoft recommends keeping it enabled.

For a repeatable sleep/wake failure, follow device-specific support guidance. If that guidance calls for a temporary power-setting test, record the original value, change one setting, reproduce the same sleep/wake sequence, and restore the setting if it does not help. Power Options and Device Manager controls vary by hardware and power model; their absence is not evidence of corruption. Do not use registry changes merely to expose missing options.

When Input Does Not Work in Normal Windows

Safe Mode can help narrow down a Windows software problem, but it cannot guarantee that USB input will work. If you can operate Windows, use Settings > System > Recovery > Advanced startup, or Shift + Restart. Keep your BitLocker recovery key available.

In Windows Recovery Environment, choose Troubleshoot > Advanced options > Startup Settings > Restart, then select Safe Mode. A password may be needed because PIN and biometric sign-in are unavailable there. If no usable input works in recovery, you cannot select this route without another supported input method; consult the device manufacturer.

Microsoft documents interrupting startup twice to reach recovery on the third start when normal access fails. Forced shutdown is a fallback, not the first test; never interrupt a firmware update. See Windows recovery environment and Startup Settings.

Firmware Settings Require Model-Specific Guidance

Some computers have USB initialization or firmware Fast Boot options that affect early input. Do not assume a Windows upgrade disabled Legacy USB support. Check the exact model’s manual, record any change, and test one option at a time.

Legacy USB input support is different from Legacy/CSM boot mode. Do not change storage mode, Secure Boot, or boot mode as a generic keyboard fix. Firmware Fast Boot and Windows Fast Startup are also different features.

Choose the Next Step From the Evidence

• Failure on multiple computers points toward the peripheral or receiver.
• Failure only through a dock points toward its connection, power, compatibility, or firmware.
• Failure only after sleep calls for a reproducible wake test and device-specific guidance.
• Failure after a particular software update calls for its documented rollback or recovery options.
• Failure in every environment with known-working devices warrants manufacturer hardware diagnostics.

If only one key is affected, use the more specific guide for the Windows key not working. Keep a record of changes and restore unsuccessful tests rather than applying unrelated fixes together.