Windows 10: how do i fix bitlocker lockout after windows update

Hello, I recently did a windows update and after the update I got a BitLocker screen asking for my recovery key. I entered the recovery key code and click continue then an Automatic Repair screen pops up "automatic repair couldn't repair your PC" with options to shut down or advanced options. and the same thing starts all over no matter what option I choose. Please help.

:)

 

TPM 1.2 Lockout

I entered a bitlocker key incorrectly and was told that there were too many attempts. This was about 36 hours ago

I used the recovery key to get onto my laptop but every time I restarted my machine the same error came up.

I have now done the following about 24-hours ago:

• Disabled Bitlocker including decrypting the drive
• Disabled the TPM
• Re-enabled the TPM
• Cleared the TPM

When I try and enable bitlocker again I get the message "The TPM is defending against dictionary attacks and is in a time-out period"

Questions

1) How do I overcome this block?

2) How does the time-out period work - do you have to keep the computer turned on for the whole period for it to reset?

3) Does every time I try and re-enable bitlocker reset the lockout period timer?

It is a Dell laptop so I think the lockout period is 24-hours.

 

BitLocker on Surface Pro 3 not working correctly

Hi JulianSchubert,

Thank you for posting your question in the Microsoft Community

TPM will lock itself out after a few incorrect authentication attempts. These could be due to incorrect PIN entry for BitLocker or incorrect PIN entry for TPM virtual smartcard PIN. For TPM version 1.2, the lockout behavior depends
on individual TPM manufacturer. For TPM 2.0, the specification states that the TPM will enter lockout after 32 incorrect attempts.

To terminate this BitLocker recovery loop, you need to suspend BitLocker within WinRE, I suggest you to follow the below steps.

Step 1:

1. Choose the “Skip this drive” link at the bottom of the page where you are asked to enter the recovery key. You should be presented with a menu that will let you get to a command prompt (The sequence is Advanced
   options -> Troubleshoot -> Advanced options -> Command prompt).
   
2. Once you have a command prompt,
   use the following command to check the BitLocker status of the C: drive:
   manage-bde -status c:
   
3. If the status is returned as locked, you’ll need to use the following command to unlock it using your recovery password:
   manage-bde -unlock c: -rp <your 48-digit recovery password>
   
4. Once the drive is unlocked you'll need to use the following command to suspend protection:
   manage-bde -protectors -disable c:
   
5. Then exit and reboot. The computer should now successfully boot Windows. Once there, use the BitLocker control panel to resume BitLocker protection.
   
6. You can reset TPM lockout using
   tpm.msc
   

Note: The recovery loop can occur for other reasons such as cases where TPM is disabled or malfunctions. You can still use the above steps to suspend BitLocker and boot Windows in such cases

Hope it helps.

 

Windows 10 BitLocker and TPM lockout

Hi,

I have hit an issue with BitLocker which uses TPM on a Windows 10 laptop.

In the past you were able to take ownership of the TPM and export the key/password. The current version of Win10 no longer allows this. This would all be fine if you no longer needed the key. Unfortunately on this laptop the TPM has now got itself in a locked
state after too many failed logins by the user. We were eventually able to login with the BitLocker recovery key after it rejected it initially. However because Windows retains ownership we do not have the TPM key and therefore we cannot do the reset.

I have trawled various TechNet articles and cannot see how we are supposed to resolve this. Does the TPM automatically clear the lockout itself after a period of time?

I have suspended BitLocker on that computer. It looks like I cannot resume it until the TPM lockout has ended.

Isn't this an oversight on how we are supposed to be able to resolve issues?

Thanks!

Stephen.