Use this when: At startup you see a blue screen asking for a BitLocker recovery key — a 48-digit number — before Windows loads.
Steps
|
Do this |
What should happen |
|
1. Understand what you are seeing. BitLocker encrypts the disk; this screen is asking to unlock it. It is not a virus and your files are not lost. |
It is triggered when the machine detects a change at startup — very often a Windows update, a firmware change, or a docked/undocked boot. |
|
2. Do not guess, and do not type your Windows password here. It will not work and repeated wrong entries waste time. |
The key is a specific 48-digit number that we hold. |
|
3. Note the Key ID shown on screen (the short code under the prompt) and the device name. |
This lets us find the exact key for your machine fast. |
|
4. Log a HIGH ticket or contact the IT Team . We look up your recovery key and read it to you, or unlock it with you on the line. |
We hold the recovery key for every company machine. This is usually a few minutes. |
|
5. Once you are back in, leave the machine on and connected so any pending update can finish. |
An update caught halfway is what triggered this on many machines recently. |
If that did not work
It asks for the key again on the next restart. Something is still changing at boot. Log it in the ticket — do not keep entering the key each time without telling us.
You were asked for a recovery key by someone over the phone or email. That is an attack — we contact you, you do not send it out. Report it as phishing (see the Cybersecurity guide).
You have the key from your own Microsoft account on a personal device. For a company machine, still call us — the account and encryption are managed on our side.
Important: Recent Windows updates have pushed some company machines — Dell business models included — into this screen on the first reboot after the update. It is a known pattern and not something you did wrong. We hold your key; call and we will get you back in.
Log a ticket
HIGH — Urgent — You are at the BitLocker recovery screen and cannot get past it. Call as well as logging it.