Keyboard is not working
Separate keyboard connection, accessibility, layout, driver, and hardware faults.
- Updated
- September 18, 2026
- Reading time
- 7 min read
- Windows support
- Windows 11 · Windows 10
Quick diagnosis
Separate keyboard connection, accessibility, layout, driver, and hardware faults.
Symptoms
- No keys respond
- Keys repeat or differ
Likely causes
- Battery or connection
- Filter Keys or layout
- Physical damage
Quick reversible checks
- Try another port or battery
- Use On-Screen Keyboard
Establish the scope
Separate all-key failure from a few repeating keys or characters that differ from their labels. Compare the On-Screen Keyboard and another ordinary application. An incorrect language layout changes characters without establishing a hardware fault; loss of all input calls for power and connection checks.
Apply the safer fix first
Reconnect the receiver or Bluetooth pairing. Review Filter Keys and the active language layout in Settings.
Investigate the cause
Compare a compatible wired keyboard in recovery or firmware only if that environment supports it; Bluetooth or unsupported ports may not work there. Failure with supported input outside Windows adds hardware evidence, but is not conclusive alone. Reinstall the device only when alternate input is available.
Protect the recovery path
Keep On-Screen Keyboard or another working keyboard available before device changes. Stop using liquid-damaged hardware and do not dismantle it while powered.
Verification
- Type a harmless sample in a local text editor and check the keys that originally failed.
- Confirm the intended layout, modifier keys, and sign-in input work after reconnecting without entering a password into a test document.
When to stop
Do not continue with broader resets when liquid damage occurred, keys fail outside Windows, or no alternate sign-in exists. Preserve the observations already collected and use the device maker, network administrator, Microsoft support, a qualified repair technician, or data-recovery help according to the evidence.
Review the safe troubleshooting workflow before any broader recovery step.