BITLOCKER repeat

Carolyn Brennan 20 Reputation points
2026-07-05T18:52:23.8666667+00:00

microsoft surface pro 3 using windows 10 keeps asking for the recovery key which i have entered numerous times. how do i get this to stop?

Windows for home | Windows 10 | Security and privacy
0 comments No comments

Answer accepted by question author

Sin-D 11,190 Reputation points Microsoft External Staff Moderator
2026-07-05T23:22:46.8466667+00:00

Hi Carolyn Brennan,

I understand how frustrating this can be when you have to enter the BitLocker recovery key every time you start your Surface Pro 3.

To help narrow this down further, could you let me know:

  • Does the device eventually boot into Windows after you enter the recovery key?
  • Did the issue start after a Windows update, Surface firmware update, BIOS/UEFI change, or hardware change?
  • Is BitLocker asking for the key on every startup, or only occasionally?

Based on your description, BitLocker may be detecting a change in the device's boot, TPM, or security configuration and is repeatedly entering recovery mode.

If you can successfully reach the Windows desktop after entering the recovery key, please try:

  1. Open “Control Panel” > “BitLocker Drive Encryption.”
  2. Next to your system drive, select “Suspend protection.”
  3. Restart the device once normally.
  4. Return to “BitLocker Drive Encryption” and select “Resume protection.”

You can also review Microsoft's guidance on BitLocker recovery here: Find your BitLocker recovery key

If the answer is helpful, please click "Accept Answer" and kindly upvote it. If you have extra questions about this answer, please click "Comment".    

Note: Please follow the steps in our documentation to enable e-mail notifications if you want to receive the related email notification for this thread.

Was this answer helpful?

2 people found this answer helpful.

0 additional answers

Sort by: Most helpful

Your answer

Answers can be marked as 'Accepted' by the question author and 'Recommended' by moderators, which helps users know the answer solved the author's problem.