Fix TPM_E_DEACTIVATED (0X80280006) on Windows 11/10

You're staring at TPM_E_DEACTIVATED (0X80280006) and wondering why your PC suddenly won't boot Windows 11 or throws a BitLocker tantrum. This error usually shows up right after a BIOS update, a motherboard swap, or when you cleared the TPM through Windows settings and the thing didn't come back properly. I've seen it most often on Dell and Lenovo business machines, but it hits consumer boards too — especially ASUS and Gigabyte models after a firmware flash.

The root cause is simple: the TPM chip is physically there, but the system firmware has it disabled or put to sleep. The error code itself tells you — 'deactivated.' Windows can't talk to it because the BIOS or UEFI isn't letting the handshake happen. It's not a driver problem, not a hardware failure (usually), just a firmware toggle that got flipped off.

Before You Start

You'll need to get into your system's firmware setup — commonly called BIOS or UEFI. The key to press during boot is usually F2, Del, F10, or Esc. On some machines, you might need to hold Shift while clicking Restart in Windows to get into recovery, then go to Troubleshoot > Advanced Options > UEFI Firmware Settings. That's your path if Windows still boots but gives you the error in apps or settings.

Step-by-Step Fix

Step 1: Enter BIOS/UEFI Setup

Restart your computer. As soon as the screen lights up, start tapping the correct key. If you miss it, let Windows load and try again. Common keys by brand:

• Dell: F2
• HP: F10
• Lenovo: F1 or Enter then F1
• ASUS: F2 or Del
• MSI: Del
• Gigabyte: F2 or Del

After you get past the key press, you should see the BIOS main screen. If you see a black screen with white text, you're in. If Windows loads, you pressed the wrong key — restart and try again.

Step 2: Find the TPM Setting

The name varies by manufacturer. Look for these terms under Security or Advanced tabs:

• "TPM"
• "Trusted Platform Module"
• "PTT" (Intel Platform Trust Technology — Intel machines)
• "fTPM" (AMD firmware TPM)
• "Security Chip" (some Dells)

If you can't find it, check the manual for your motherboard or laptop model. On newer boards, it's often under Advanced > Trusted Computing. On older Dells, it's under Security > TPM 1.2/2.0 Security.

Step 3: Enable and Activate the TPM

Once you find the setting, you'll see options like:

• Disabled / Enabled
• Deactivated / Activated (sometimes a sub-option)
• Clear TPM (use this only if you're sure — it resets the TPM and can cause BitLocker to require a recovery key)

Set it to Enabled and Activated. If there's a separate "Activate" option, pick that too. On some boards, you need to set the TPM state to "Enabled" and then also set the "Activation Policy" to "Allow" or "Turn on."

Here's a real example: On a Dell OptiPlex 7080, you go to Security > TPM 2.0 Security > TPM State and change it from Deactivated to Activated. Hit Apply or F10 to save.

Step 4: Save and Exit

Press F10 (or select Save & Exit) to confirm. The machine will restart. You should see the usual Windows boot. After the restart, the error should be gone.

Step 5: Check TPM Status in Windows

Open PowerShell as administrator (right-click Start, select Windows PowerShell (Admin)). Run this command:

Get-Tpm

Look for TpmReady: True and Enabled: True. If you see TpmReady: False, the TPM still isn't fully usable. You might need a firmware update or a CMOS clear.

Alternatively, you can type tpm.msc into the Run dialog (Win + R) and hit Enter. The TPM Management console should show "The TPM is ready for use" near the bottom. If it says "Compatible TPM cannot be found" or shows an error, something's still off.

If It Still Fails

Three things to check:

1. BIOS update. Manufacturers often fix TPM detection bugs in newer BIOS versions. Go to your motherboard or laptop support page, download the latest BIOS, and flash it. This alone fixes the issue on many ASUS boards after a Windows update changed TPM requirements.
2. Clear CMOS. Power off, unplug the power cord, remove the motherboard battery for 30 seconds, then put it back. This resets all BIOS settings to default, which sometimes wakes up a stuck TPM. On laptops, you might need to hold the power button for 30 seconds with the battery out to drain residual charge.
3. Fresh TPM initialization. If you can get into Windows but the error pops up in apps (like BitLocker), try clearing the TPM from within Windows: go to Settings > Update & Security > Windows Security > Device Security > Security Processor Details > Security Processor Troubleshooting, then click Clear TPM. Restart after that. Watch out — this will invalidate any BitLocker keys stored in the TPM, so have your recovery key handy.

If none of that works, you might be dealing with a dead TPM chip. On some older systems, especially those with discrete TPM modules (not firmware-based), the chip physically fails. You'd see the same error in BIOS even with it set to Enabled. In that case, replacing the TPM module (if it's socketed) or using a firmware-based TPM (like Intel PTT) is the fix. Check your motherboard manual to see if it supports switching to firmware TPM — many boards let you toggle between discrete and firmware TPM in the BIOS.

One last thing: if you're running a custom-built PC with a newer AMD or Intel CPU, make sure the TPM is set to firmware mode (fTPM for AMD, PTT for Intel). Discrete TPM modules are becoming rare on consumer boards, and if you have one plugged in but the motherboard defaults to firmware, you'll get this error. Switch it in BIOS under Trusted Computing > TPM Device Selection and try again.