BitLocker recovery key: where to find it, how to back it up, and how to avoid the blue screen
The BitLocker recovery screen asks for a 48-digit key. Where to find it (Microsoft account, Entra ID, Intune, AD), back it up in one command, avoid the screen.
Updated 14 November 2026 · 4 min read
One Monday morning, a colleague calls: their laptop shows a blue "BitLocker recovery" screen and asks for a 48-digit key. Without this key, the disk stays encrypted and unreadable. With it, the device restarts in two minutes. So everything happens before the incident: knowing where the keys are, and checking that they exist for every device.
The short answer
The BitLocker recovery key is in the user's Microsoft account (aka.ms/myrecoverykey) for a personal PC, and in Microsoft Entra ID, Intune or Active Directory for a company PC. On a device that still boots, the command manage-bde -protectors -get C: displays it. To avoid the recovery screen, suspend BitLocker before any BIOS or UEFI update. And to know which devices in your fleet are encrypted, LongLife shows the BitLocker status of every device, always up to date.
Where to look for the key, depending on the device
| Device situation | Where the key is |
|---|---|
| Personal PC, Microsoft account | aka.ms/myrecoverykey, with the user's Microsoft account |
| Company PC joined to Microsoft Entra ID | Entra admin centre: Devices, then the device record, BitLocker keys section |
| PC managed by Intune | Intune admin centre: Devices, the device record, then "Recovery keys" |
| PC joined to an Active Directory domain | "Active Directory Users and Computers" console, "BitLocker Recovery" tab of the computer object, if backup to AD is configured |
| Encryption turned on manually | Paper printout or text file saved when it was turned on |
To find the right key among several, look at the recovery screen: it shows a key ID (a string of characters). It must match the ID of the saved key.
Display the key of a device that boots
On a working device, you can read and write down its key in advance. Open an elevated Command Prompt (Start menu, type "cmd", then "Run as administrator") and run:
manage-bde -status C:The "Protection Status" line shows whether encryption is on. Then, to display the protectors:
manage-bde -protectors -get C:The output lists the disk's protectors. Find the "Numerical Password" block: it contains the ID (in braces) and the 48-digit password, in eight groups of six. This is what you will need to type on the recovery screen.
The same result in PowerShell (run as administrator):
(Get-BitLockerVolume -MountPoint "C:").KeyProtector | Where-Object KeyProtectorType -eq "RecoveryPassword" | Select-Object KeyProtectorId, RecoveryPasswordBack up the key to Entra ID or Active Directory
If a device was encrypted before it was joined to the directory, its key may not be there. To send it to Microsoft Entra ID, in an elevated PowerShell:
$cle = (Get-BitLockerVolume -MountPoint "C:").KeyProtector | Where-Object KeyProtectorType -eq "RecoveryPassword"
BackupToAAD-BitLockerKeyProtector -MountPoint "C:" -KeyProtectorId $cle.KeyProtectorIdFor an Active Directory domain, the equivalent uses manage-bde, replacing the placeholder with the ID displayed above (braces included):
manage-bde -protectors -adbackup C: -id {VOTRE-IDENTIFIANT}Then check in the console that the key appears on the device's record.
At the recovery screen
- Write down the key ID shown on the screen.
- Find the matching key in the Microsoft account, Entra ID, Intune or Active Directory (see the table above).
- Type the 48 digits. The hyphens between groups are added automatically.
- Once Windows has started, find the cause (see below) so the screen does not come back at the next startup.
If the key cannot be found, there is no workaround: neither Microsoft nor the manufacturer can regenerate it. You then have to reset the device and erase the disk.
Why the screen appears, and how to avoid it
BitLocker relies on the TPM chip, which checks that the boot chain has not changed. At the slightest change, it asks for the key as a precaution. The most common causes:
| Cause | How to avoid it |
|---|---|
| BIOS or UEFI update | Suspend BitLocker just before |
| Enabling, disabling or clearing the TPM | Suspend BitLocker before touching it |
| Change to Secure Boot | Suspend BitLocker before |
| Change of boot order, booting from a USB stick | Avoid, or suspend BitLocker before |
| Motherboard replacement | Retrieve the key before the work |
To suspend BitLocker for a single restart, in an elevated PowerShell:
Suspend-BitLocker -MountPoint "C:" -RebootCount 1Or in an elevated Command Prompt:
manage-bde -protectors -disable C: -RebootCount 1The disk stays encrypted: only the startup check is paused, and it resumes by itself after the restart. Check with manage-bde -status C: that protection is back "On".
LongLife: encryption across the whole fleet, at a glance
On one device, manage-bde -status is enough. Across a whole fleet, you need to know at all times which devices are protected. That is what LongLife does:
- the BitLocker status of every device, always up to date: you immediately see unencrypted disks;
- the full security posture alongside: antivirus, firewall, updates;
- incidents detected continuously, with the recommended action;
- action: a signed remote script or an on-site work order to fix a device.
Recovery keys stay where they belong, in your Microsoft account, Entra ID, Intune or Active Directory: LongLife does not store them.
The free plan covers up to 15 devices. Book a meeting to see your fleet in LongLife, or estimate the savings with the simulator. To go further, read our guide to IT fleet management.
Sources
- Microsoft, BitLocker recovery key: support.microsoft.com
- Microsoft, manage-bde protectors command: learn.microsoft.com
- Microsoft, BackupToAAD-BitLockerKeyProtector cmdlet: learn.microsoft.com
- Microsoft, Suspend-BitLocker cmdlet: learn.microsoft.com
- Microsoft, BitLocker recovery overview: learn.microsoft.com
Frequently asked questions
Where can I find my BitLocker recovery key?
On a personal PC, in your Microsoft account, at aka.ms/myrecoverykey. On a company PC, in Microsoft Entra ID or Intune (the device record), or in Active Directory if the company backs up keys there. Otherwise, on a printout or in a file saved when encryption was turned on.
How do I display the BitLocker recovery key of a device that still boots?
In a Command Prompt run as administrator, the command manage-bde -protectors -get C: lists the disk's protectors, including the 48-digit recovery password and its ID.
Why does BitLocker ask for the recovery key at startup?
Because it has detected a change in the boot chain. The most frequent causes are a BIOS or UEFI update, a change to or clearing of the TPM, a change to Secure Boot or to the boot order.
What if the BitLocker recovery key cannot be found?
Without the key, the data on the disk is unreadable: neither Microsoft nor support can regenerate it. The only option left is to reset the device and erase the disk. That is why the key of every device must be backed up before you need it.
How much longer can your fleet last?
The simulator estimates in one minute the budget and CO₂ saved by extending your renewal cycle.