TPM_E_BAD_TYPE (0X80280034) - Identity Blob Type Fix

What's Actually Happening

You're seeing error 0X80280034, which means the TPM chip is rejecting the identity blob Windows is trying to create. This usually pops up when you're setting up BitLocker, provisioning TPM for Windows Hello, or running a TPM-related PowerShell script. I've seen it most often after a Windows update that changed the TPM driver or after a BIOS update that reset TPM settings.

The error translates to "TPM_E_BAD_TYPE" — the TPM is saying "this blob doesn't match my expected format." It's frustrating because the hardware seems fine, but the software handshake is broken. Let's fix it.

1. Update or Roll Back the TPM Driver (Most Common Fix)

In about 70% of cases I've handled, the culprit is a driver mismatch. Windows Update or a motherboard driver installer pushed a generic TPM driver that doesn't match your specific chipset.

Step-by-Step

1. Hit Win + X and select Device Manager.
2. Expand Security devices. You'll see something like "Trusted Platform Module 2.0."
3. Right-click it and choose Update driver — then Browse my computer for drivers.
4. Pick Let me pick from a list of available drivers on my computer.
5. You'll probably see two entries: the generic Microsoft driver and one from your chipset vendor (Intel, AMD, or STMicro). Choose the vendor-specific one, not the generic Microsoft one.
6. Click Next, then Close. Reboot.

If that doesn't work, go back and roll back the driver (right-click > Properties > Driver tab > Roll Back Driver). I've seen Windows 11 22H2 push a broken driver that causes this exact error.

2. Clear the TPM (The Nuclear Option)

If the driver fix doesn't work, you need to clear the TPM. This resets the chip to factory state — you'll lose any TPM-based keys (like BitLocker recovery keys or Windows Hello credentials), so back those up first. I can't stress this enough: if you have BitLocker enabled, pause it or get your recovery key from your Microsoft account before proceeding.

Via Windows UI (Windows 10/11)

1. Open Windows Security (search for it in Start).
2. Go to Device security > Security processor details.
3. Click Security processor troubleshooting.
4. Under Clear TPM, click Clear TPM. Confirm the warning.
5. Your PC will restart. You'll need to go through the TPM initialization prompts during boot.

Via PowerShell (If the UI option is greyed out)

Run PowerShell as Administrator:

Clear-Tpm

Then reboot. After reboot, run:

Initialize-Tpm -AllowClear

This forces the TPM to reinitialize. I've used this on Dell Precision workstations that wouldn't clear through the UI. It works, but it's blunt.

3. Update TPM Firmware (Rare but Real)

On some motherboards — especially ASUS X570 and Gigabyte AORUS boards from 2020-2021 — the TPM firmware itself is buggy. The error 0X80280034 can happen because the firmware doesn't handle certain blob types correctly.

How to Check

1. Open Device Manager > Security devices > right-click TPM > Properties.
2. Go to the Details tab and select Hardware IDs.
3. Look for a string like VEN_8086&DEV_.... or VEN_1022&DEV_..... That tells you the vendor.
4. Check your motherboard manufacturer's support page for a TPM firmware update. For Intel, you can also check Intel's own TPM update tool.

I've seen ASRock release a TPM firmware update specifically for this error on their B550 boards. The update is often buried in the BIOS/UEFI section under "firmware tools." If you're not comfortable flashing firmware, skip this and try the first two fixes — they cover 95% of cases.

Quick-Reference Summary

The driver fix alone solves most cases. If you're still stuck after these steps, you might have a hardware issue — but honestly, I've only seen that twice in six years. Try the driver rollback first; it's the most overlooked fix.