Fix TPM_E_INVALID_RESOURCE (0X80280035) in Windows

This error pops up when Windows can't save TPM context because the resource type doesn't match. Usually triggered by driver conflicts or corrupted TPM state. Fix takes 30 seconds to 15 minutes.

What is this TPM error?

You're seeing error 0X80280035, which means "TPM_E_INVALID_RESOURCE". Windows tried to save your TPM context—like a fingerprint for your security chip—but the resource type didn't match what it expected. This usually happens when you upgrade Windows (like from 10 to 11), after a major update, or if your TPM driver got replaced by a bad version.

I've seen this error mainly on Dell and Lenovo laptops from 2019-2022, but it can pop up on any machine with a discrete TPM chip (not the firmware TPM in AMD or Intel CPUs).

Fix 1: Restart the TPM service (30 seconds)

This is the quick fix. Sometimes the TPM just needs a kickstart. Here's how:

Press Windows Key + R, type services.msc, hit Enter.
Find TPM Base Services (or just "TPM Services" on older Windows builds).
Right-click it, choose Restart.
Close the window and reboot your PC.

If the error still shows up, move to Fix 2.

Fix 2: Update or roll back the TPM driver (5 minutes)

A bad driver version is the most common cause of this error. Windows Update sometimes pushes a generic driver that doesn't match your specific TPM chip. Here's what to do:

Right-click the Start button, choose Device Manager.
Expand Security devices. You'll see something like "Trusted Platform Module 2.0" or "Infineon TPM".
Right-click it, choose Update driver > Browse my computer for drivers > Let me pick from a list.
Select the driver version from your PC manufacturer (e.g., Dell, Lenovo, HP). Avoid the Microsoft generic one.
Click Next, then restart.

My opinion: Skip the automatic update search—it often pulls the wrong driver. Always get the driver from your PC maker's support site if the list doesn't show the right one.

If the error persists, try rolling back the driver instead: In Device Manager, right-click the TPM device, go to Properties > Driver > Roll Back Driver. This works if the error started after a recent driver update.

Fix 3: Clear the TPM (15+ minutes, advanced)

This is the nuclear option. Clearing the TPM wipes all keys, including BitLocker encryption keys and Windows Hello data. Make sure you have your BitLocker recovery key saved somewhere safe before doing this. This step can lock you out of your data.

Two ways to do it. First try the easy one:

Method A: Use the TPM Management Console

Press Windows Key + R, type tpm.msc, hit Enter.
If the TPM status says "Ready", look for a link that says Clear TPM on the right side. Click it.
Restart your PC. You'll be asked to confirm the TPM reset during boot—press a key when prompted.

Method B: Use Command Prompt (if the GUI doesn't work)

Open Command Prompt as Administrator. Search "cmd", right-click, choose "Run as administrator".
Type this command and hit Enter:

tpmtool clear

Reboot. Accept the TPM reset on the next boot (usually press F1, F12, or Y depending on your PC).

After the clear, Windows will reinitialize the TPM. The error 0X80280035 should be gone. You'll need to set up Windows Hello again if you used it.

When to call it quits and ask for help

If none of these fixes work, your TPM chip might be physically dying. Check the Windows Event Viewer under Applications and Services Logs > Microsoft > Windows > TPM for more clues. A failing TPM can cause random errors like this one. In that case, contact your PC manufacturer for a replacement—this is rare but happens on older hardware.

One last thing: if you're running Linux dual-boot, some distributions mess with TPM state. Disable TPM in BIOS before installing Linux, or use the Windows boot manager exclusively. That tripped me up the first time too.