Fix TPM_E_RESOURCES 0X80280015: TPM Runs Out of Memory
TPM can't handle your request because it ran out of internal memory. The fix is usually clearing TPM ownership or reducing TPM load. We'll cover both.
Annoying TPM Error — Let's Kill It
You're trying to use BitLocker, Windows Hello, or some TPM app and get that 0X80280015 error. Yeah, it's frustrating. The TPM has a tiny pool of memory, and it's full. Let's fix it.
The Quick Fix: Clear TPM Ownership
This is what works 90% of the time. Clearing TPM wipes all keys and resets the internal memory. Do this:
- Press Win + R, type
tpm.msc, hit Enter. - In the TPM Management window, click Clear TPM on the right panel.
- You'll see a warning. Click Restart.
- During reboot, your BIOS/UEFI will ask you to press a key (usually F1, F2, or Delete) to confirm. Do it.
- Windows boots. The TPM is clean.
After this, the error should be gone. You'll need to re-setup BitLocker or Windows Hello if you used them. That's the trade-off.
Pro tip: On Windows 11, you might need to go through Settings > Privacy & security > Windows Security > Device security > Security processor details > Security processor troubleshooting. Same result.
Still Stuck? Manually Clear via PowerShell
If the GUI won't cooperate—happens on some Dell or HP systems—use PowerShell. Open it as admin:
Run these commands:
Clear-Tpm -Force
That's it. The -Force skips the normal confirmation. You still need to reboot and press the key in BIOS. No way around that.
Why This Happens
TPM is a small, low-power chip. It's not like your system RAM. It has limited internal storage for keys, sessions, and credentials. Every time a program or Windows component asks TPM to hold a key or perform encryption, it uses a slot. When all slots are full, you hit 0X80280015.
Common triggers:
- Multiple BitLocker volumes on the same TPM
- Windows Hello biometrics store a lot of keys
- Virtual smart cards or certificate enrollment
- Third-party apps like VMware or encryption tools
Clearing TPM ownership frees all those slots.
Less Common Variations
1. TPM Firmware Bug
Some older TPM 2.0 chips (like on Intel 6th/7th gen CPUs) have resource leaks. They don't free memory properly after a key is released. The only fix is a firmware update from your PC manufacturer. Check your BIOS/UEFI updates. Lenovo and HP have released patches for this.
2. TPM Driver Issues
Go to Device Manager, find Security Devices > Trusted Platform Module 2.0. Right-click, pick Update driver > Browse my computer > Let me pick from a list. Choose the latest driver. If that fails, uninstall the device, reboot, let Windows reinstall.
3. Group Policy Override
Domain-joined machines sometimes get locked TPM configs. The admin might have set a max number of TPM keys. Run gpedit.msc (Pro/Enterprise only) and check Computer Configuration > Administrative Templates > System > Trusted Platform Module. Look for any policy limiting TPM resources. If you're not an admin, talk to IT.
4. Hardware TPM vs fTPM
On some motherboards (especially AMD), firmware TPM (fTPM) can be buggy. Go into BIOS and switch from fTPM to discrete TPM if you have one. Or update your BIOS to the latest version. MSI and ASUS boards had known fTPM stuttering issues that also caused resource errors.
Prevention for Next Time
You can't add more RAM to a TPM. But you can reduce how many keys it holds.
- Don't encrypt every drive with BitLocker using TPM-only. Use a password or USB key for secondary drives.
- Remove unused Windows Hello data. Go to Settings > Accounts > Sign-in options, remove face/ fingerprint data you don't need.
- Check for TPM firmware updates at least once a year. Manufacturers quietly fix leaks.
- Avoid turning TPM off and on repeatedly. That can corrupt its state.
If you're on a laptop that's 3+ years old, consider a TPM firmware upgrade before it becomes a problem. Most people never need to clear the TPM more than once a year. If you're doing it monthly, something else is eating slots. Could be a bad driver or a misbehaving app.
Was this solution helpful?