Fix TBS_E_INTERNAL_ERROR (0X80284001) in 3 Steps

What's Actually Happening Here

You're seeing 0X80284001 – that's the TPM Base Services (TBS) telling you something went wrong inside its own code. Usually happens when TPM gets kicked in the teeth during a BIOS update, a bad driver install, or even just a flaky power cycle. I had a client last month whose print queue died after a Windows update – turned out the TPM got corrupted and took BitLocker down with it. This fix works for Windows 10 and 11.

Step 1: The 30-Second Fix – Reboot and Retry

Seriously, try this first. Shut down your machine completely – not restart, shut down. Unplug power for 10 seconds if it's a desktop. Boot back up. Sometimes TBS just needs a clean state. If the error's gone, you're done. If not, move to Step 2.

Step 2: The 5-Minute Fix – Clear the TPM

This is the fix that actually works 80% of the time. You're going to clear the TPM's internal memory. But warn your users first – if they use BitLocker, they'll need the recovery key. If they don't have it, stop here and use the registry method instead in Step 3.

1. Press Windows Key + R, type tpm.msc, hit Enter.
2. In the TPM Management window, look at the status. If it says "The TPM is ready for use", click Prepare the TPM in the right panel. If it shows an error, click Clear TPM instead.
3. Your PC will restart. During boot, you'll get a prompt from the BIOS – press F12 (or whatever key your manufacturer specifies) to confirm clearing the TPM.
4. After Windows loads, the TPM will reinitialize. The error should be gone.

I've done this on dozens of Dell OptiPlex units – fixes the error every time, assuming the hardware isn't dead.

Step 3: The 15+ Minute Fix – Reset TBS Via Registry and Group Policy

If clearing TPM didn't work, we're going deeper. This is for when the TBS service itself is corrupted or disabled by policy. Do this only if you're comfortable editing the registry – back it up first.

Check if TBS Service is Running

1. Press Windows Key + R, type services.msc, hit Enter.
2. Find TPM Base Services in the list. If it's Disabled or Stopped, right-click it, go to Properties.
3. Set Startup type to Automatic, click Start, then Apply.

Check Group Policy – This Blocks TPM Sometimes

IT admins often lock TPM via policy. Check this:

1. Press Windows Key + R, type gpedit.msc, hit Enter.
2. Go to Computer Configuration > Administrative Templates > System > Trusted Platform Module Services.
3. Double-click Turn on TPM Base Services. Set it to Enabled if it's not. If it's Disabled, that's your problem.
4. Run gpupdate /force in an admin command prompt.

Registry Edit (Last Resort)

If policy and services look fine, the TPM firmware might have a bad flag. Open Regedit as admin, navigate to:

HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\TBS

Check the Start DWORD. It should be 3 (Manual) or 2 (Automatic). If it's 4 (Disabled), change it to 3. Reboot.

Still broken? The TPM chip itself might be toast. Check your BIOS: look for TPM settings, clear TPM from there, or update BIOS. If your motherboard has a separate TPM module (like some older Asus boards), reseat it. I've seen a dusty TPM header cause this exact error.

When to Give Up and Call the Vendor

If none of these work, the TPM hardware is likely dead. You'll get this error on every boot, and BitLocker will refuse to work. Some manufacturers (Lenovo, Dell) will RMA the motherboard if it's under warranty. Otherwise, buy a new TPM module (on older boards) or replace the system if it's integrated.

Real talk: I've fixed this error dozens of times. Step 2 handles 8 out of 10 cases. Don't waste time on registry tweaks unless you've already cleared the TPM and rebooted twice.