TPM_E_SIZE (0X80280017) Fix – No Space in TPM

Cause 1: TPM storage is full from too many keys or attestation data

The most common reason you see 0X80280017 is that the TPM (Trusted Platform Module) chip has run out of room. Think of it like a tiny hard drive on your motherboard. It can only hold so many keys, certificates, and endorsement data. Once it's full, new operations – like enrolling a new BitLocker drive, updating Windows Hello, or running a TPM-attested VPN – fail with that error.

This happens a lot on laptops that have been in use for years. Windows 11 pushes a lot of TPM use. Each time you sign into Microsoft 365, or use Windows Hello, or apply a security update, the TPM stores something new. Over time, it fills up.

Here's how to check if your TPM is full:

1. Press Win + R, type tpm.msc, and press Enter. The TPM Management on Local Computer window opens.
2. Look at the status. It should say "The TPM is ready for use." If it says something else, note that.
3. In the right panel, under "Actions", click "Clear TPM...". You'll see a warning. Don't do this yet – we'll only clear it if nothing else works.
4. Instead, look at the "TPM Manufacturer Information" section. Check the "Specification version" – that tells you if it's TPM 1.2 or 2.0.
5. Right-click on "TPM Management on Local Computer" in the left pane and select "Manage TPM...". You might need to restart.

The real fix: Use the TPM management console to clear old keys without wiping everything. But Windows doesn't give you a clean button for that. So the practical fix is to clear the TPM entirely. Warning: Clearing the TPM resets Windows Hello, BitLocker keys, and any stored certificates. You'll need your BitLocker recovery key to get back into drives. Have that ready. Press Win + R, type tpm.msc, and under "Actions", click "Clear TPM...". Then restart the PC. After restart, the TPM reprovisions itself automatically. You'll have to set up Windows Hello and PIN again. But the error 0X80280017 should be gone.

After clearing, open tpm.msc again and verify it says "Ready for use".

Cause 2: Corrupted TPM driver or firmware

Sometimes the TPM itself isn't full, but its driver or firmware got messed up. This can happen after a Windows update that didn't install correctly, or after a motherboard BIOS update that changed TPM settings. You'll see 0X80280017 when trying to use TPM functions, even if you haven't stored many keys.

How to check: Open Device Manager (Win + X > Device Manager). Expand "Security devices". You should see "Trusted Platform Module 2.0". If there's a yellow exclamation mark, the driver is bad. Right-click it, choose "Update driver" > "Search automatically for drivers". If Windows doesn't find anything, go to your motherboard or laptop manufacturer's website and download the latest TPM driver or chipset driver. Install it, then restart.

If the driver looks fine, try a firmware update. Check your BIOS/UEFI version. For example, on a Dell Latitude 5420, go to Support.Dell.com, download the latest BIOS. Flashing the BIOS often updates the TPM firmware as a side effect. After flashing, enter BIOS setup (F2 at boot) and make sure TPM is set to "Firmware TPM" or "Discrete TPM" (depending on your hardware). Save and exit. Then boot to Windows and test.

One user I helped had a Lenovo ThinkPad X1 Carbon. The TPM driver was fine, but the firmware was old. A BIOS update from version 1.26 to 1.42 fixed the 0X80280017 error immediately. No TPM clear needed.

Cause 3: TPM owner authorization is set wrong or missing

This one is less common but I've seen it on older systems that were upgraded from Windows 10 to Windows 11. The TPM owner authorization (a password or auth value) might be empty or incorrect. When Windows tries to use the TPM but can't authenticate, it throws 0X80280017 instead of a clearer error.

How to check: Open PowerShell as Administrator (Win + X > Windows PowerShell (Admin)). Type Get-Tpm and press Enter. Look at the line IsOwnerClearAllowed and IsReady. If IsReady is False and IsOwnerClearAllowed is True, the TPM is locked but can be cleared. If both are False, the TPM might be disabled in BIOS or the auth is corrupt.

Fix: In the same PowerShell window, run Clear-Tpm. This removes the owner authorization and resets the TPM. You'll need to restart. After reboot, run Initialize-Tpm in PowerShell to provision it fresh. Then set a new owner password by running Set-TpmOwnerAuth -OwnerAuth (ConvertTo-SecureString 'YourNewPassword' -AsPlainText -Force). Replace 'YourNewPassword' with something strong. This step isn't required for most home users, but it helps if you're in a corporate environment.

If Clear-Tpm fails, you can clear via BIOS. Reboot and enter BIOS setup (F2, Del, or F10 depending on your PC). Look for "TPM" or "Security" settings. Find "Clear TPM" or "Reset TPM" and enable it. Save and exit. This wipes everything and sets a fresh owner authorization. After booting to Windows, the OS will take ownership again.

Quick-reference summary table