TPM DAA Resources Error 0x80280050 Fix

You're working away, maybe setting up Windows Hello for the first time, or running a BitLocker recovery, and boom — the screen throws up TPM_E_DAA_RESOURCES (0x80280050) with that cryptic message about lacking resources. I've seen this on Dell Latitude 5420s and Lenovo ThinkPad T14s running Windows 11 22H2, right after a firmware update or a failed TPM attestation. It's especially brutal when it kills your fingerprint login.

The error means the TPM's DAA (Direct Anonymous Attestation) command buffer is full. Think of DAA as the TPM's way of proving it's a real TPM without revealing its identity. Each DAA command needs a temporary slot. When those slots are all taken — usually by a failed or interrupted attestation process — new commands can't run. The TPM won't clear them on its own. Microsoft's official docs are thin here, so the fix is manual.

Root Cause: Stale DAA Sessions

The TPM tracks open DAA sessions in volatile memory (NVIndex 0x01D00000 on TPM 2.0). A crash, a power loss, or a competing app like an old VPN client that tried to use the TPM can leave these sessions hanging. They don't auto-expire. Once you exceed the TPM's internal limit — usually 5–8 concurrent sessions — you hit this error.

On Intel PTT (Platform Trust Technology) and AMD fTPM, this is common after a BIOS update that doesn't properly reset the TPM state. On discrete TPM chips (Infineon, STMicro), it's rarer but can happen after a forced shutdown.

How to Fix It

Skip the registry hacks — they don't touch the TPM resource pool. The real fix is to clear the TPM's volatile state. You've got two paths. Try the safe one first.

Fix 1: Clear TPM via Windows (Safe Reboot)

1. Press Win + R, type tpm.msc, and hit Enter.
2. In the TPM Management console, look under TPM Manufacturer Information. If it says Specification Version 2.0, you're good. If it's 1.2, skip to Fix 2 (the OS tool only works on 2.0).
3. Click Actions menu, then Clear TPM. You'll need to restart the computer. During restart, you must press a key (usually F12 or F10) to confirm the clear. Yes, you'll lose any TPM-bound keys — but that's the point. BitLocker will ask for your recovery key on next boot, so have it ready.
4. After the restart, go back to tpm.msc and check the status is Ready.
5. Test the feature that was failing — fingerprint setup, BitLocker, whatever. The error should be gone.

Fix 2: Clear TPM from BIOS (More Reliable)

This one works on any TPM, including 1.2 chips and systems where the OS clear fails.

1. Restart and enter BIOS/UEFI setup. On Dells, tap F2 repeatedly. On Lenovo, F1 or Enter then F1. On HPs, F10.
2. Find the TPM settings. They're usually under Security -> TPM or Security Chip.
3. Look for an option like Clear TPM, Reset TPM, or Erase TPM. On some BIOS versions (e.g., Dell 2.30.0), it's called TPM Clear and requires you to check a box and accept a warning.
4. Save and exit. The system will reboot and the TPM will reinitialize. Again, have your BitLocker recovery key handy.
5. Re-enable TPM in BIOS if it got disabled. Then boot to Windows and verify TPM is ready in tpm.msc.

Fix 3: Reset via PowerShell (No Reboot Needed)

If you can't reboot immediately, this clears the volatile DAA resources without a full TPM reset. It's a workaround, not a permanent fix — but it works.

Get-WmiObject -Namespace root/cimv2/security/microsofttpm -Class Win32_Tpm | Invoke-WmiMethod -Name Clear

Run that in an elevated PowerShell. It sends a clear command to the TPM driver. You'll still need to restart eventually to re-provision the TPM, but it buys you time. I've used this on a Surface Pro 9 mid-meeting.

What If It Still Fails?

If the error returns after a few days, there's a deeper issue. Check these in order:

• BIOS version. Go to the manufacturer's site and update your BIOS. A buggy TPM firmware is the #1 cause of repeated DAA exhaustion. For example, Dell's 1.17.0 BIOS for the Latitude 5430 had this exact problem — fixed in 1.19.0.
• Third-party security software. Uninstall any TPM-aware tools like McAfee Endpoint Encryption or Symantec TPM utils. They sometimes hold DAA sessions open.
• Group Policy. If this is a company machine, check if a policy forces TPM attestation on every login. That can exhaust resources if the attestation fails silently. Run gpresult /h gp.html and search for TPM.

In rare cases, the TPM chip itself is dying. If nothing works and you're still seeing the error, contact your OEM support and ask for a TPM replacement. On Intel PTT or AMD fTPM, that means a motherboard swap. Painful, but I've had to do it twice on HP EliteBooks.