Windows 10/117 min readReviewed 2026-07-29

Keyboard works in Windows but not in BIOS or BitLocker

Use a direct wired keyboard and firmware USB support when vendor or wireless drivers are unavailable preboot.

Quick diagnosis

A keyboard that begins working only after Windows loads depends on a stack the firmware environment does not provide.

Common symptoms

The keyboard cannot enter BIOS or a BitLocker PIN but works after Windows starts.
The behavior is repeatable with the same keyboard state.
Changing an unrelated Windows preference does not reliably fix it.

Likely causes

Preboot firmware may lack support for a wireless receiver, hub, vendor protocol, or disabled legacy USB path.
A connection, driver, or configuration boundary affecting the keyboard.
Hardware failure only if the symptom follows the same keyboard across controlled comparisons.

Before changing anything

Record the current keyboard settings and connection path.
Change one variable at a time.
Keep a known-good comparison device, port, mode, or application available.

Diagnose it in this order

1
Create a repeatable baseline
Reproduce the symptom in a simple Windows surface and record exactly when it occurs: The keyboard cannot enter BIOS or a BitLocker PIN but works after Windows starts.
2
Run the discriminating test
Connect a simple wired keyboard directly to a rear motherboard USB port and retest preboot.
3
Apply the narrow fix
Enable the firmware’s documented USB keyboard support and use a direct wired keyboard for recovery or BitLocker entry.
4
Repeat the original comparison
Keep every unrelated setting fixed and repeat the baseline for longer than the normal failure interval.

Solutions

Keyboard works in Windows but not in BIOS or BitLocker

Enable the firmware’s documented USB keyboard support and use a direct wired keyboard for recovery or BitLocker entry.

Record firmware settings and keep BitLocker recovery information before changing boot or USB options.

Verify the fix

Enter firmware setup and type the BitLocker recovery/PIN interface across two cold boots.
Restart or reconnect once and repeat the same controlled test.
Confirm the change did not create a new failure in the comparison state.

Roll back safely

• Restore the recorded keyboard settings, connection, driver, or mode if the result is not repeatable.

When to stop and escalate

• If the symptom follows the keyboard across another PC or source after the documented checks, use manufacturer support or warranty service.

Related tests and guides

testKeyboard tester

Frequently asked questions

Why test before changing several settings?

A one-variable comparison shows whether the proposed mechanism actually controls the symptom and preserves a safe rollback.

Sources

USB keyboard and mouse may not work before the operating system
Dell Support. Preboot firmware may lack support for a wireless receiver, hub, vendor protocol, or disabled legacy USB path.
Mouse and keyboard problems in Windows
Microsoft Support. Direct-port, battery, cable, hub-bypass, driver, and cross-PC diagnostic order.

Diagnose it in this order

Create a repeatable baseline

Reproduce the symptom in a simple Windows surface and record exactly when it occurs: The keyboard cannot enter BIOS or a BitLocker PIN but works after Windows starts.

Run the discriminating test

Connect a simple wired keyboard directly to a rear motherboard USB port and retest preboot.

Apply the narrow fix

Enable the firmware’s documented USB keyboard support and use a direct wired keyboard for recovery or BitLocker entry.

Repeat the original comparison

Keep every unrelated setting fixed and repeat the baseline for longer than the normal failure interval.

Sources

USB keyboard and mouse may not work before the operating system

Dell Support. Preboot firmware may lack support for a wireless receiver, hub, vendor protocol, or disabled legacy USB path.

Mouse and keyboard problems in Windows

Microsoft Support. Direct-port, battery, cable, hub-bypass, driver, and cross-PC diagnostic order.