When This Error Hits
You're either trying to sign into Windows with a PIN or fingerprint, and Windows Hello throws this error. Or maybe BitLocker just refused to unlock and gave you 0x80290117. The trigger? Almost always a BIOS update, a motherboard swap, or a TPM firmware update that changed the Platform Configuration Registers (PCRs). PCRs are basically a hash of your system's boot state. If they don't match what Windows expects, you get this error.
Had a client last month who updated his Lenovo ThinkPad's BIOS and couldn't log in with his fingerprint for three days. This error was the culprit.
Root Cause (Plain English)
The TPM stores a snapshot of your system's boot process — that's the PCR data. When you set up Windows Hello or BitLocker, Windows tells the TPM, "Only release the key if the PCR values match this specific snapshot." After a BIOS update, the boot sequence changes (different firmware version, different UEFI settings), so the PCR values don't match. The TPM says, "Nope, PCR data is invalid," and throws 0x80290117.
You can't fix it by just rebooting. You need to reset the TPM or update the drivers.
Fix: Clear TPM (If No BitLocker)
If you don't use BitLocker or other TPM-dependent encryption, the quickest fix is to clear the TPM. This wipes the stored PCR snapshots and resets everything.
- Back up anything important. Clearing TPM can invalidate saved keys for apps like Outlook or browsers. Just in case.
- Restart your PC and enter UEFI/BIOS. Usually by pressing
F2,Del, orF10during boot. - Find the TPM settings. Look under "Security" or "Advanced" — sometimes labeled "Trusted Computing" or "TPM 2.0".
- Clear/Reset the TPM. There should be an option like "Clear TPM" or "Reset to factory defaults". Select it.
- Save changes and exit. Let the PC reboot.
- Reconfigure Windows Hello. Go to
Settings > Accounts > Sign-in optionsand set up your PIN or fingerprint again. The error should be gone.
Pro tip: If you can't find the option in BIOS, you can clear TPM from Windows itself. Press Win + R, type tpm.msc, and hit Enter. In the TPM Management console, click "Clear TPM" in the right-hand pane. You'll need to restart.
Fix: Update TPM Driver (If BitLocker Enabled)
If BitLocker is active, do not clear the TPM — you'll lose your BitLocker keys unless you have the recovery key. Instead, update the TPM driver.
- Open Device Manager. Right-click the Start button and select Device Manager.
- Expand "Security devices". You'll see "Trusted Platform Module 2.0" or similar.
- Right-click it and select "Update driver".
- Choose "Browse my computer for drivers". Then "Let me pick from a list of available drivers on my computer".
- If there's a newer driver listed, select it. If not, uncheck "Show compatible hardware" and try the standard Microsoft TPM driver (usually dated 2006). This often overwrites the corrupted driver.
- Restart and test. The PCR mismatch should clear after a reboot.
This worked for a client with a Dell Precision workstation that had a TPM firmware glitch after a Windows update.
Still Failing? Check These
- BitLocker recovery key. If you cleared TPM with BitLocker active, you'll need that 48-digit recovery key to unlock the drive. Have it ready. Store it in your Microsoft account or print it.
- BIOS settings. Some motherboards have a "TPM Device Select" option that switches between discrete and firmware TPM. Make sure it's set to the correct one (usually firmware TPM for modern CPUs).
- TPM firmware update. Check your motherboard manufacturer's support page for a TPM firmware update. I've seen this fix persistent PCR errors on HP EliteDesk machines.
- Windows update. A cumulative update can sometimes resolve TPM driver issues. Run Windows Update and install any pending patches.
- Last resort — re-enroll Windows Hello. Even after clearing TPM, some users need to go to
Settings > Accounts > Sign-in optionsand remove then re-add their PIN or biometric sign-in. This forces a fresh PCR binding.
If none of this works, you might have a failing TPM chip. That's hardware-level — time for a motherboard swap or a TPM module replacement if your board supports it.