0X80280045

TPM_E_BAD_COUNTER (0x80280045) Fix: Counter Handle Wrong

Windows Errors Intermediate 👁 0 views 📅 Jun 7, 2026

This TPM error means Windows got a bad counter handle. Usually after a driver update or TPM clear. Fix: reset the TPM or re-register the counter.

Quick Answer

Reset the TPM via tpm.msc or clear it in UEFI/BIOS. If that doesn't work, re-register your TPM counters with PowerShell command Clear-Tpm -AllowClear.

What This Error Actually Means

You’re looking at 0x80280045 – the TPM is telling you the counter handle it received is garbage. This usually happens after a firmware update, a driver reinstall, or if you manually cleared the TPM and then tried to use BitLocker or an app that relied on the old counter. The TPM keeps monotonically increasing counters for things like anti-replay or license enforcement. When the handle doesn’t match what the TPM expects, it throws this error. It’s annoying because Windows gives you zero guidance. I’ve seen this on Dell OptiPlex 7080s and Lenovo ThinkPads after BIOS updates – the TPM counters get orphaned.

Fix Steps

  1. Open the TPM Management Console: Press Win + R, type tpm.msc, hit Enter. Check the status. If it says “The TPM is ready for use,” you’re good on that front. If it says “Compatible TPM cannot be found,” you’ve got a bigger problem (check BIOS).
  2. Reset the TPM from the console: In tpm.msc, click “Prepare the TPM…” in the right-hand panel. Follow the prompts. This reinitializes the TPM and clears all counters. You’ll need to reboot. Note: this will invalidate any BitLocker keys stored in the TPM, so have your recovery key ready.
  3. If that fails, use PowerShell as admin: Run Clear-Tpm -AllowClear. This is more aggressive—it clears the TPM entirely. After reboot, Windows will reinitialize the TPM automatically. You’ll see a UEFI prompt asking you to press F12 or whatever to confirm the clear. Do it.
  4. Re-register the TPM counters: If the error persists after clearing, your TPM driver might be stale. Open Device Manager, expand “Security devices,” right-click “Trusted Platform Module 2.0,” choose “Update driver” > “Browse my computer for drivers” > “Let me pick from a list…” > select the default Microsoft driver (usually dated 2006) and install. Then reboot and run Initialize-Tpm in PowerShell as admin.

Alternative Fixes If the Main One Fails

  • Check UEFI/BIOS settings: Some systems have a TPM state that’s “Enabled” but not “Active.” On Dell systems, look for “TPM 2.0 Security” and set it to “Enabled” and “On.” On Lenovo, set “Security Chip” to “Active.” Reboot and try the fixes again.
  • Boot from a Windows installation media: Use the “Repair your computer” option, open Command Prompt, and run tpmtool unlock then tpmtool clear. This bypasses any OS-level lock.
  • Update your chipset drivers: Some TPM errors are actually caused by the Intel Management Engine or AMD PSP driver being outdated. Grab the latest from your PC manufacturer’s support site, not Windows Update. On a 2023 Lenovo Yoga, for example, updating the Intel ME fixed this within an hour.

Prevention Tip

Never clear the TPM while BitLocker is active unless you have the recovery key. And if you update your BIOS, always check the TPM status afterward – many updates reset the TPM to default, which kills your counter handles. If you’re using TPM-based apps (like Windows Hello for Business or certain VPNs), set a reminder to verify tpm.msc after every firmware update. Saves you a headache.

Was this solution helpful?

TPM_E_BAD_COUNTER 0x80280045 TPM error TPM counter handle Windows TPM error TPM driver error TPM reset Windows 11 TPM clear tpm.msc BitLocker TPM error Windows security error TPM 2.0 error counter handle incorrect 0x80280045 fix TPM initialization