If the Surface Pro 3 does boot into Windows after entering the recovery key, the supported first step is to suspend BitLocker once, restart, and then resume protection:
- Open Control Panel > BitLocker Drive Encryption.
- Next to the system drive, select Suspend protection.
- Restart the Surface normally.
- Go back to BitLocker Drive Encryption and select Resume protection.
If the problem started after a Surface firmware, UEFI, or TPM update, this repeated recovery prompt can happen when BitLocker is using PCR values other than the default PCR 7 and PCR 11, such as when Secure Boot is off or PCR values were changed by policy.
If the device does not start normally even after entering the correct recovery key, use Windows Recovery Environment and repair the boot records:
- Force two failed boot attempts so the device enters Windows Recovery Environment (WinRE).
- Go to Troubleshoot > Advanced options > Command Prompt.
- Enter the BitLocker recovery key if prompted.
- Run:
bootrec /scanos
bootrec /rebuildbcd
bootrec /fixmbr
bootrec /fixboot
If the issue is specifically tied to a Surface TPM or UEFI update and Windows still will not start, the documented recovery path is:
- Get the BitLocker recovery password.
- Create a Surface recovery image USB on another computer.
- Boot the Surface from that USB.
- Open Troubleshoot > Advanced Options > Command Prompt.
- Unlock the OS drive and disable TPM protectors:
manage-bde.exe -unlock -recoverypassword <Password> <DriveLetter>:
manage-bde.exe -protectors -disable <DriveLetter>:
- Restart and enter the recovery password again if prompted.
Important: disabling protectors reduces BitLocker protection until it is turned back on. After Windows starts, re-enable protection from Manage BitLocker.
To help prevent the issue from returning after firmware-related changes:
- Verify Secure Boot is set to Microsoft Only in Surface UEFI.
- Restore default PCR usage if Group Policy changed it.
- On Surface devices, the default BitLocker binding is PCR 7 and PCR 11 when Secure Boot is correctly configured.
References: