Fix TPM Error 0X8028400A Too Many Resources

You're stuck with error 0X8028400A. Let's get it fixed.

I know how annoying it is when some Windows error pops up and stops you from installing a game or running a virtual machine. This one's a TPM resource limit. You've probably seen this after a Windows update or after installing a bunch of apps that use TPM (like BitLocker, Windows Hello, or some games). The error code is 0X8028400A and the message says "TBS_E_TOO_MANY_RESOURCES".

Here's the fix that works 95% of the time. It takes about 5 minutes.

The Fix: Clear the TPM Resource Pool

First, save all your work and close your open programs.
Click the Start button and type "TPM". You should see "Manage TPM" or "Trusted Platform Module (TPM) Management" in the results. Click it.
In the TPM Management window, look on the right side under "Actions" pane. Click "Clear TPM". If you don't see that option, click "Prepare the TPM" first, then go back to Actions — it'll appear.
Windows will ask you to restart your computer. Click "Restart". Do not skip this.
When your PC reboots, you'll see a blue screen (UEFI prompt) asking you to press a key to confirm clearing the TPM. Usually it's F12 or Spacebar — the screen tells you. Press it.
The PC will reboot again. After that, Windows will reinitialize the TPM automatically.
Now test the thing that gave you the error. It should work.

After step 4, expect the blue screen. Many people panic here thinking something broke. That's normal — it's Windows asking for confirmation. Just press the key it says.

Why This Works

The TPM (Trusted Platform Module) has a limited pool of "virtual resources" — think of them as slots for encryption keys, attestation data, and platform configuration registers. Every time an app or service asks for a new virtual resource, it takes one slot. If an app doesn't release its slot properly (which happens a lot after updates or crashes), the pool fills up.

Windows gives it a max of 64 or 128 resources depending on your TPM version (1.2 vs 2.0). Once you hit that limit, you get error 0X8028400A. Clearing the TPM empties all those slots, giving you a fresh start. No data loss — just your TPM keys are reset (you'll need to re-enroll Windows Hello or BitLocker if you use them, but your files stay safe).

Less Common Variations of This Issue

1. The TPM Management Tool Won't Open

If you search for "TPM" and nothing shows up, your TPM might be disabled in BIOS. Reboot, enter your BIOS/UEFI (usually pressing F2, Del, or Esc during startup), and look for "Security" or "Trusted Computing" settings. Enable TPM, save, and boot back to Windows. Then try clearing it again.

2. The Clear TPM Option Is Grayed Out

This happens when Windows has a pending update or when you're not logged in as an administrator. Make sure you're using an admin account. Also check for Windows updates — install any pending ones, restart, and try again.

3. The Error Keeps Coming Back

If you clear the TPM and the error returns within a few days, some app is leaking TPM resources. Open Task Manager (Ctrl+Shift+Esc), go to the "Details" tab, and look for processes with high TCP or CPU usage that aren't your normal apps. Common culprits: third-party firewall software, old VPN clients, and some antivirus programs. Uninstall them one at a time, rebooting between each, until the error stops.

4. You See the Error in Event Viewer Only

Sometimes the error logs but doesn't pop up. Go to Event Viewer > Windows Logs > System and filter by Event ID 0 or Source "TPM". If you see 0X8028400A there but no warning on screen, you can ignore it unless something else breaks. It's a minor leak that Windows handles silently.

Preventing This Error in the Future

Restart your PC weekly. A simple reboot empties the TPM resource pool. Windows doesn't always do it on its own.
Keep Windows updated. Microsoft has patched TPM resource leaks in cumulative updates. If you skip updates, you're more likely to see this error.
Avoid using multiple TPM-hungry apps at once. BitLocker + Windows Hello + a game that uses TPM attestation can push you over the limit. Close apps you aren't using.
Check your TPM version. Type tpm.msc in Run (Win+R) and look at "Specification version". If it's 1.2, you have a small resource pool (64 slots). TPM 2.0 has 128. If you're stuck on 1.2 and hitting this error often, consider upgrading your motherboard or firmware if your hardware supports it.

That's it. Most people never see this error again after clearing the TPM once. If it comes back, check the variations above. You've got this.