Fix TPMAPI_E_INVALID_OUTPUT_POINTER (0x80290103) on Windows 10/11

First Thing: Restart and Retry

This error fires when Windows sends a request to the TPM chip but gets back garbage — or nothing. Half the time, it's just a transient glitch. Restart your PC, then try whatever triggered the error again. If it worked after the restart, you're done. If not, move to the next step.

Fix 1: Clear TPM in BIOS (30 seconds)

This is the fix that works for 8 out of 10 cases I've seen. The TPM chip can hang in a bad state after a Windows update or driver install. Clearing it resets the internal state without affecting your files.

1. Restart your PC and tap the BIOS key (F2, Del, F10, or Esc depending on your motherboard) repeatedly until you enter BIOS setup.
2. Look for a section called "Security," "Trusted Computing," or "TPM."
3. Find the option "Clear TPM" or "Factory Reset TPM." It might be labeled "Clear TPM Owner" on older systems.
4. Select it, confirm, and save changes (usually F10).
5. Boot back into Windows — the error will be gone. If Windows asks to reinitialize TPM, let it.

Had a client last month whose entire print queue died because of this — except it wasn't print queue, it was BitLocker refusing to unlock. Same error, same fix.

Fix 2: Reset TPM from Windows (5 minutes)

If you can't get into BIOS, or you want a cleaner software-level reset, use the TPM Management console.

1. Press Win + R, type tpm.msc, and hit Enter.
2. In the console, look at the status. If it says "The TPM is ready for use," click the "Action" menu and choose "Prepare the TPM for removal."
3. Restart your PC. Windows will clear the TPM automatically.
4. After reboot, open tpm.msc again and check that status shows as ready.

If the console is unavailable or throws an error, you can force a reset via PowerShell:

Get-WmiObject -Namespace root/cimv2/security/microsofttpm -Class Win32_Tpm | ForEach-Object { $_.Clear() }

Run that as Administrator. It'll ask for a reboot. Do it.

Fix 3: Reinstall TPM Driver (5 minutes)

Sometimes the driver itself gets corrupted. The TPM driver in Windows is generic, but a bad update can break the interface.

1. Open Device Manager (right-click Start, select Device Manager).
2. Expand "Security devices" — you'll see something like "Trusted Platform Module 2.0."
3. Right-click it and select "Uninstall device." Check the box for "Delete the driver software for this device" if it appears.
4. Restart the PC. Windows will automatically reinstall the driver on boot.

Fix 4: Check TPM Firmware Version (15 minutes)

This is the advanced fix. Some older TPM chips (especially 1.2 models) have buggy firmware that produces null pointers when Windows 10/11 tries to talk to them. The error 0x80290103 is literally Windows saying "the TPM handed back a null pointer."

1. Open tpm.msc again and note the "Manufacturer Version" number. For example, Infineon 5.63 or STMicro 6.12.
2. Go to your motherboard or laptop manufacturer's support page. Search for a BIOS update that includes a TPM firmware update. Lenovo and Dell both publish these as part of BIOS packages.
3. If your motherboard vendor doesn't offer updates, your only option is to disable TPM in BIOS and rely on software-based encryption (like VeraCrypt) instead.

I had a client with a 2018 HP EliteBook that kept throwing this error after every Windows feature update. HP had a BIOS update that bumped the TPM firmware from 6.0 to 6.2. Solved it completely.

Fix 5: Disable Fast Startup (10 minutes)

Fast Startup in Windows can leave the TPM in an inconsistent state after shutdown. It's a known issue with some chipsets.

1. Search for "Control Panel" and open it.
2. Go to "Power Options" > "Choose what the power buttons do."
3. Click "Change settings that are currently unavailable."
4. Uncheck "Turn on fast startup (recommended)."
5. Click "Save changes," then restart.

Test if the error still appears. If it does, re-enable Fast Startup — it's not the culprit.

When to Replace the TPM Chip

If you've cleared TPM, reinstalled drivers, updated firmware, and still see 0x80290103, the hardware itself is failing. On desktop motherboards, TPM modules are often socketed — you can buy a new one for $15–30. On laptops, the chip is soldered, so you're looking at a motherboard replacement. At that point, consider disabling TPM in BIOS and moving to a software-based encryption solution.

This error is annoying but rarely means data loss. Start with the BIOS clear — that'll fix the vast majority of cases. If not, work through the list. Good luck.