Fix TPM_E_DAA_TPM_SETTINGS (0X80280054) on Windows 10/11

What's actually happening here

You're seeing error code 0X80280054, which translates to TPM_E_DAA_TPM_SETTINGS. The TPM chip inside your PC holds a block of data called DAA (Direct Anonymous Attestation) — it's used for proving your system is trustworthy without revealing its identity. When Windows checks that data and finds it inconsistent, it throws this error.

This usually shows up during Windows Update, BitLocker setup, or when you run tpm.msc and the TPM status shows as "Not ready." I've seen it most on Dell and Lenovo laptops after a BIOS update went wrong.

Fix 1: Update or reinstall the TPM driver (most common cause)

The TPM driver is often the culprit. What's actually happening here is Windows Update pushes a generic TPM driver that doesn't play nice with your specific chip, especially on older firmware.

1. Press Win + X and pick Device Manager.
2. Expand Security devices. Look for Trusted Platform Module 2.0 or similar.
3. Right-click it and choose Update driver → Browse my computer for drivers → Let me pick from a list.
4. Pick the manufacturer-specific driver (e.g., Intel, STMicro, Infineon) instead of the generic Microsoft one. If there's only one driver, skip this.
5. If that doesn't fix it, right-click again → Uninstall device. Check Delete the driver software for this device. Reboot. Windows will reinstall the driver fresh.

The reason step 5 works is because it nukes the cached registry settings that probably got corrupted. A clean install often resolves the consistency check failure.

Fix 2: Clear the TPM (second most common)

If the driver fix didn't help, the TPM's internal DAA data is genuinely corrupted. You need to clear it. Warning: This disables BitLocker and any TPM-dependent features. Have your BitLocker recovery key handy.

1. Open Windows Security → Device security → Security processor details → Security processor troubleshooting.
2. Click Clear TPM. You'll need to restart.
3. During reboot, your BIOS might prompt you to press F1/F2 to accept TPM reset. Do it.
4. After Windows loads, run tpm.msc to verify the TPM is now "Ready."

What's actually happening here is the TPM chip itself holds the DAA data in non-volatile memory. Clearing it resets that entire block. The consistency check passes because there's nothing to check.

If you can't clear from Windows (error says TPM not ready), you can do it from BIOS. Reboot, mash F2/Del to enter BIOS, find the TPM/security section, and select Clear TPM or Reset TPM. It's sometimes labeled as "Factory reset TPM." Exact path varies by motherboard — check your manual.

Fix 3: Reset BIOS to defaults (rare but works when other fixes fail)

When neither driver nor TPM clear fixes it, the problem might be a BIOS setting that's confusing the TPM's internal state. I've seen this on HP ProBooks where a BIOS update changed the TPM firmware version from 1.2 to 2.0 without properly migrating the DAA data.

1. Reboot and enter BIOS (usually F2, F10, or Del).
2. Look for Reset to Default or Load Optimized Defaults. Apply it.
3. Save and exit. Let Windows boot.
4. Open tpm.msc and check status. It should say "Ready."

The reason this works is that resetting BIOS defaults also resets the TPM firmware interface settings. If something like "TPM Device Selection" was set to "Discrete" when it should be "Firmware" (or vice versa), this fixes it.

Quick-reference summary table

If none of these work, you might have a failing TPM chip. On desktops, you can replace the TPM module (if it's a discrete one). On laptops, you're looking at motherboard replacement. But try the fixes above first — 9 times out of 10, it's just a driver or a BIOS glitch.