Skip to main content
Print

What to Do When Windows Asks for a BitLocker Recovery Key

You turn on a Windows laptop and instead of the sign-in screen you get a blue page that says BitLocker recovery, with the text Enter the recovery key for this drive and a long Recovery key ID. Windows has not loaded yet, so your normal password is useless. The drive is encrypted and the computer is refusing to unlock it automatically.

This is not a sign the machine is broken or hacked. Something about the hardware or startup configuration changed, so the security chip declined to release the encryption key without proof from a human, and the 48-digit recovery key is that proof. It most often hits staff after a BIOS update, a motherboard repair, or a Windows feature update, and it is routine in organizations that enforce encryption through Intune, including most healthcare and government contractor firms.

Why This Happens

BitLocker normally unlocks the drive silently using the Trusted Platform Module (TPM), a security chip on the motherboard. At boot, the TPM measures the firmware, boot loader, Secure Boot state, and other components, and releases the disk key only if those measurements match the ones recorded when BitLocker was turned on. If anything differs, the TPM withholds the key and Windows asks for the recovery key.

Firmware, BIOS, or hardware changes

A BIOS update changes the measured firmware, and vendor firmware updates delivered through Windows Update are the most common trigger on business laptops. Replacing the motherboard replaces the TPM entirely. Toggling Secure Boot, changing the boot order, or plugging in a dock or USB drive when the firmware boots from USB or network first can also alter the measurements.

Windows updates and boot configuration changes

Feature updates such as Windows 11 24H2 or 25H2 rewrite parts of the boot environment. Microsoft suspends BitLocker for one reboot during the upgrade, but an interrupted update or a repair utility that modifies the boot configuration data (BCD) can invalidate the protectors.

Automatic device encryption with no escrowed key

Windows 11 turns on device encryption automatically on most modern hardware. If a PC was set up with a personal Microsoft account and later joined to the company, the key sits in that personal account rather than in your Entra ID (formerly Azure AD) tenant, and IT cannot find it when the prompt appears.

How to Fix It

Method 1: Retrieve the key from your organization

  1. Write down the first eight characters of the Recovery key ID on the blue screen. It identifies which key to look up; it is not the key itself.
  2. Give the key ID to your IT team. In an Entra ID joined environment, an admin opens the Microsoft Entra admin center, Devices, All devices, selects the device, and opens BitLocker keys, or searches by key ID under Devices, BitLocker keys. In Intune, it is under the device’s Recovery keys.
  3. In on-premises Active Directory, open the computer object in Active Directory Users and Computers and view the BitLocker Recovery tab (requires the BitLocker Recovery Password Viewer feature).
  4. Type the 48 digits on the recovery screen. Windows will boot normally.

Method 2: Retrieve the key from a Microsoft account or self-service

  1. On another device, sign in at https://account.microsoft.com/devices/recoverykey with the Microsoft account used when the PC was set up, match the key ID, and copy the key. If that account belongs to a former employee, they must sign in to retrieve it.
  2. For work accounts, if allowed, the user can open https://myaccount.microsoft.com/device-list on a phone, select the device, and choose View BitLocker Keys. Admins control this under Devices, Device settings in the Entra admin center.

Method 3: Undo the firmware change first

  1. Enter firmware setup (usually F2, F12, or Del at power-on). Confirm Secure Boot is On, the TPM is enabled, and the internal drive is first in the boot order. Unplug docks and USB drives.
  2. Reboot. If the TPM state was the only problem, Windows unlocks normally. If not, use Method 1 or 2.

After the key is entered: reseal BitLocker

After a firmware or hardware change, the prompt returns on the next boot unless the protectors are refreshed. Once signed in, run in an elevated PowerShell prompt:

Suspend-BitLocker -MountPoint "C:" -RebootCount 1
Restart-Computer

BitLocker resumes after one reboot and seals the key to the new measurements. Then confirm the key is escrowed to your tenant, using the numerical password protector ID from the first command:

manage-bde -protectors -get C:
BackupToAAD-BitLockerKeyProtector -MountPoint "C:" -KeyProtectorId "{ID}"

For on-premises AD, use manage-bde -protectors -adbackup C: -id {ID} instead.

How to Verify the Fix Worked

  • Windows boots twice in a row without the recovery screen, once with the dock attached.
  • manage-bde -status C: shows Protection On and Fully Encrypted.
  • The device in Entra or Intune shows a recovery key with a recent backup date.
  • Get-Tpm in PowerShell returns TpmReady: True.

If It Still Isn’t Working

Check Event Viewer for the reason BitLocker entered recovery. Under Applications and Services Logs, Microsoft, Windows, BitLocker-API, Management, event ID 24620 or 24621 states which platform configuration register (PCR) changed: firmware (PCR 0), Secure Boot policy (PCR 7), or boot manager (PCR 4 or 11).

If the key is rejected, confirm you matched the full key ID and the correct drive; data and OS drives have separate keys.

If the prompt returns every boot despite resealing, the TPM may be failing. Check tpm.msc for errors, update firmware, then suspend and resume once more.

Stop and escalate if no copy of the key exists in Entra ID, Intune, Active Directory, or any Microsoft account. At that point the data is unrecoverable and the machine must be wiped. Tools that claim to crack BitLocker do not work against a TPM protector.

How Capital Techies Handles This for Managed Clients

For managed clients, we push BitLocker through Intune with a policy that escrows the recovery key to Entra ID before encryption begins, so a key that is not in the tenant does not exist. Our RMM checks encryption status and key backup daily, and firmware updates are staged and tested rather than left to vendor auto-updaters, which removes the most common trigger. When a user hits the recovery screen, our help desk retrieves the key in minutes. Under HIPAA and CMMC, documented encryption with escrowed keys is what turns a lost laptop from a reportable breach into a non-event.

If your team is chasing recovery keys, talk to Capital Techies about managed IT support before a laptop goes missing.

Frequently Asked Questions

Where is my BitLocker recovery key stored?

On a work computer, the key is almost always escrowed to your organization’s Entra ID or Active Directory, where an IT admin retrieves it by the Key ID shown on the blue screen. On a personal device, it is at account.microsoft.com/devices/recoverykey. If the drive was encrypted manually, the key may have been printed or saved to a USB drive.

Can I bypass the BitLocker recovery screen without the key?

No. Without the 48-digit recovery key or the normal TPM unlock, the data on the drive cannot be read. If no copy of the key exists anywhere, the only path forward is to reinstall Windows, which erases the drive. This is why managed environments enforce key escrow before encryption starts.

Why does the computer ask for the key every single time it boots?

Repeated prompts mean the TPM measurements keep changing at each boot. Common triggers are a pending BIOS update, Secure Boot toggled off, a dock or external drive in the boot order, or a failing TPM. Suspending and resuming BitLocker after the fix reseals the key to the current configuration.

Related Articles

Table of Contents