support · reviewed answer

Windows keeps asking for the BitLocker recovery key

Enter only the key whose ID matches the screen, then identify the trigger—firmware/TPM change, boot-order change, dock/storage change or policy—before suspending protection. Repeated prompts are not fixed by guessing keys.

Direct answer

Enter only the key whose ID matches the screen, then identify the trigger—firmware/TPM change, boot-order change, dock/storage change or policy—before suspending protection. Repeated prompts are not fixed by guessing keys.

What this covers

  • A BitLocker-protected Windows device that can reach the recovery screen
  • The exact condition described in the direct answer
  • Customer-accessible observations and controls

What it does not cover

  • ×A different model, region or software interface that contradicts the cited source
  • ×A displayed code with a separate manufacturer meaning
  • ×Live electrical, gas, sealed-system or battery-cell repair
Try in this order0 of 4 completed
  1. Establish the exact starting state

    Reversible

    Photograph the recovery-key ID and locate the matching 48-digit key through the owner or administrator.

  2. Separate the fault or decision boundary

    Reversible

    After successful boot, review recent BIOS, TPM, boot, hardware and organization-policy changes.

  3. Apply the narrowest correction

    Reversible

    Reverse the unsupported change or suspend/resume BitLocker through the documented administrative process before planned firmware work.

  4. Verify before escalating

    Reversible

    Cold-start twice with normal hardware attached and confirm no prompt.

Evidence ledger

Sources behind this answer

Visible sources support the visible claims. Home Product Support records the publisher, the fact used and the review date; community reports can suggest an issue but do not become a published fact on their own.

Exact questions

Common follow-ups

What is the short answer to “Windows keeps asking for the BitLocker recovery key”?+

Enter only the key whose ID matches the screen, then identify the trigger—firmware/TPM change, boot-order change, dock/storage change or policy—before suspending protection. Repeated prompts are not fixed by guessing keys.

What should I check before changing anything?+

Photograph the recovery-key ID and locate the matching 48-digit key through the owner or administrator.

How do I know the action worked?+

Cold-start twice with normal hardware attached and confirm no prompt.

When should I stop?+

Clearing TPM, formatting or reinstalling can make encrypted data unrecoverable without the correct key.

Change recordAug. 17, 2026 — Added as a distinct support intent with its own scope, diagnostic boundary, verification and first-party source.
Report a correction
Wrong device or version?

Match the path before repeating the steps.

Match another device