Fix TPMAPI_E_INVALID_DELEGATE_BLOB (0X80290114) Fast

1. Corrupted TPM State (Most Common Fix)

This is the one that gets you nine times out of ten. The delegate BLOB is basically a saved permission slip inside the TPM chip. When that slip gets corrupted — from a bad Windows update, a power failure during boot, or even messing with BitLocker settings — you hit this error. Had a client last month whose laptop rebooted mid-update. Came back up with this exact code. BitLocker wouldn't unlock, the whole drive was locked.

Here's the fix that works almost every time: clear the TPM. This resets the chip to factory default and wipes any corrupted delegate blobs.

1. Press Windows + R, type tpm.msc, hit Enter.
2. Look at the status. If it says "The TPM is ready for use," you're in good shape.
3. Click Clear TPM in the right panel. This will say "Prepare the TPM for removal" on some systems — same thing.
4. Restart your PC. It'll prompt you to press F12 (or whatever key your BIOS uses) to confirm. Do that.
5. Boot back into Windows. Open tpm.msc again. It should say "The TPM is ready for use."

Warning: Clearing the TPM breaks BitLocker encryption. If you use BitLocker, back up your recovery key first. Find it by going to your Microsoft account at account.microsoft.com/devices/recoverykey. Without that key, you're locked out of your data permanently.

If clearing the TPM didn't help, move on to the next cause.

2. Bad or Missing TPM Driver

Sometimes the TPM chip is fine, but Windows can't talk to it because the driver got borked. This is more common on custom-built desktops where the TPM header wasn't properly connected, or after a driver update that didn't take.

I saw this with a Dell Optiplex 7080 last week. The user updated the TPM driver through Windows Update, and it installed the wrong version. The error popped up whenever they tried to run any TPM command.

Here's the fix:

1. Press Windows + X, select Device Manager.
2. Expand Security devices. You should see Trusted Platform Module 2.0 (or 1.2 if you're on older hardware).
3. Right-click it and select Uninstall device. Check the box that says "Attempt to remove the driver for this device" if it appears.
4. Restart. Windows will automatically reinstall the correct driver.

If Windows doesn't pick up the driver automatically, download it from your motherboard or laptop manufacturer's support site. For example, on Dell systems, go to dell.com/support, enter your service tag, and download the TPM driver under "Chipset." Same for HP, Lenovo, or any OEM.

Sometimes the issue is that the TPM is disabled in the BIOS. Boot into your BIOS (usually F2 or Delete during startup), look for a section called Security or Trusted Computing, and make sure TPM is set to Enabled or Firmware TPM. If it was disabled, enable it, save, and reboot.

3. System File Corruption (Less Common but Worth Checking)

If neither of the above worked, the problem might be deeper — corrupt system files that affect the TPM management stack. This is rare but I've seen it twice in the last six months, both times after a failed Windows feature update.

Run these two commands in an administrative Command Prompt or PowerShell:

sfc /scannow
DISM /Online /Cleanup-Image /RestoreHealth

sfc checks and repairs protected system files. DISM fixes the Windows image itself, which is often the root cause. Run them in that order. Let DISM finish completely — it can take 15-20 minutes. After both complete, restart and check if the error persists.

If DISM reports that it couldn't find the source files, you may need to specify a repair source. Run this instead:

DISM /Online /Cleanup-Image /RestoreHealth /Source:C:\RepairSource\Windows /LimitAccess

Replace C:\RepairSource\Windows with the path to a Windows installation media or ISO. This is a pain, but it's the nuclear option that saved a client's machine last month when nothing else worked.

Quick-Reference Summary