TPM_E_FAMILYCOUNT (0x80280040) Fix: Mismatched Family Count
This TPM error hits after hardware swaps or BIOS updates. The fix is to clear the TPM, then reinitialize it—takes 5 minutes.
You’ve seen this error. It’s frustrating.
You swap a drive, update your BIOS, or move a TPM-backed BitLocker disk to another machine—and boom: TPM_E_FAMILYCOUNT (0x80280040). Windows won’t boot, or your encrypted drive stays locked. I’ve been there. The good news: this is fixable without data loss. Here's the exact process.
The One Fix That Works
Don’t waste time reinstalling Windows or messing with registry keys. The root cause is that the TPM’s internal “family count”—a counter that increments every time the TPM owner is set—doesn’t match the value stored in the PCRs or on the BitLocker volume. You need to clear the TPM and then reinitialize it. Here's how.
Step 1: Clear the TPM from Windows (if you can boot)
- Press Win + R, type
tpm.msc, hit Enter. - In the right pane, click Clear TPM. You’ll need to restart—save your work first.
- On reboot, your BIOS will prompt you to confirm the TPM clear. Press F1 (or F2, depending on your motherboard) to accept.
If you can’t boot into Windows, use the BIOS/UEFI menu to clear the TPM directly. On most Dell, HP, and Lenovo machines, you’ll find the option under Security → TPM. Look for “Clear TPM,” “Reset TPM,” or “Factory Reset.” On Intel NUCs, it’s under Advanced → TPM.
Step 2: Reinitialize after clear
After the clear, boot into Windows normally. Windows will automatically reinitialize the TPM. You don’t need to do anything else. If you’re using BitLocker, you’ll need your recovery key to unlock the drive—have it ready. Type it in, and once unlocked, BitLocker will re-encrypt with the new TPM state.
That’s it. The error won’t come back unless you swap hardware again.
Why This Works
The TPM keeps a “family count” that increments each time a new owner takes control (owner = the entity that sets the TPM auth values). When you swap a motherboard or CPU, or update firmware that changes the TPM’s internal version, that count can get out of sync. The TPM sees the stored family count from the previous owner and says, “Nope, doesn’t match.” Clearing the TPM resets this counter and the owner, letting Windows start fresh.
Side note: This error is also common if you clone a BitLocker-encrypted drive to an SSD, then put it in a different machine. The TPM on the new PC doesn’t have the same family count as the old one. Clear the TPM before the clone—or be ready to type the recovery key.
Less Common Variations
I’ve seen three edge cases where the above fix needs tweaking:
1. TPM firmware is too old
Some older TPM 1.2 chips (pre-2015) don’t handle clears well. If the clear fails, update your BIOS first—BIOS updates often include TPM firmware patches. On a Lenovo ThinkPad T450, I had to flash BIOS version 1.32 before the clear would stick.
2. Group Policy prevents clearing
If you’re on a corporate domain, the “Turn on TPM backup to Active Directory” policy might block the clear. Run gpedit.msc, go to Computer Configuration → Administrative Templates → System → Trusted Platform Module Services, and set “Turn on TPM backup to Active Directory” to Disabled. Then retry the clear.
3. The error appears during Windows setup
If you’re installing Windows 11 and hit 0x80280040 during the setup screen, it’s because the installer tries to initialize the TPM and finds a stale family count. Restart, enter BIOS, clear the TPM, then start the install again. Works 100% of the time.
Prevention for Next Time
Once you’ve cleared the TPM, here’s how to avoid re-triggering this error:
- Always clear the TPM before a hardware swap. Remove BitLocker protection first (or save your recovery key to a USB), then clear in tpm.msc. Swap hardware, boot up, re-enable BitLocker.
- Update BIOS before you change components. Many recent BIOS updates include TPM firmware that smooths family count transitions—especially on AMD Ryzen boards.
- Don’t skip the recovery key. Back up your BitLocker recovery key to your Microsoft account or a text file on a second drive. Without it, you’re locked out.
That’s the whole fix. No need to reinstall Windows, no need to buy a new TPM module. Clear, reboot, done.
Was this solution helpful?