TBSIMP_E_LIST_NO_MORE_ITEMS (0X8029020D) Quick Fix

What is TBSIMP_E_LIST_NO_MORE_ITEMS (0X8029020D)?

This error shows up when Windows' TPM Base Services (TBS) tries to pull data from a list that's empty or already fully read. Think of it like a vending machine with no candy bars — you punch in the code, but nothing comes out. It's not a hardware failure. It's a software handshake gone wrong.

You'll see this error in Event Viewer under System logs, or in apps that talk directly to the TPM (like BitLocker, some security software, or Windows Hello). It's common after a Windows update (especially 22H2 or later) or after a driver change. It can also pop up if you've messed with TPM ownership or cleared the TPM.

The good news: you don't need to replace your motherboard. The bad news: there's no magic one-click fix. But I've got three steps that'll get you sorted.

Fix 1: The 30-Second Reboot + TPM Clear

This is the first thing I try on every help desk call. Nine times out of ten, it's all you need.

1. Restart your PC. Not shut down — actually restart. Windows 10 and 11 use Fast Startup, which doesn't fully reset the TPM driver. A restart does.
2. After the restart, open the TPM management console. Press Win + R, type tpm.msc, and hit Enter.
3. Look at the status. It should say "The TPM is ready for use." If it says anything else (like "Compatible TPM cannot be found"), skip to Fix 2.
4. If it's ready, close the window. That's it. Test your app or check Event Viewer again. The error should be gone.
5. If the error persists, go back to tpm.msc and click "Clear TPM" on the right-hand panel. You'll need to restart again. This wipes TPM keys, so if you use BitLocker, have your recovery key handy. After the restart, Windows re-initializes the TPM automatically.

Expected outcome after clear: Another restart, then open tpm.msc again. You should see "The TPM is ready for use." The error 0X8029020D should stop appearing. If not, move on.

Fix 2: The 5-Minute Driver Rollback (or Update)

This error often traces back to a bad TPM driver. Windows Update likes to push generic drivers that don't play nice with your specific TPM chip — especially on AMD systems with fTPM.

1. Press Win + X and select Device Manager.
2. Expand Security devices. You should see something like "Trusted Platform Module 2.0" — but it might be called "STMicroelectronics TPM" or "Infineon TPM" depending on your motherboard.
3. Right-click it and choose Properties.
4. Go to the Driver tab. Look at the Driver Date and Driver Version.
5. If the date is older than 6 months, click Update Driver → Browse my computer for drivers → Let me pick from a list of available drivers on my computer.
6. You'll see one or two options. Pick the one from the manufacturer (not Microsoft's generic one). If it's the only option, that's fine. Click Next.
7. If updating doesn't help, go back and click Roll Back Driver. This reverts to the previous driver that worked.

Expected outcome: After the driver change, restart your PC. Open Event Viewer (eventvwr.msc), go to Windows Logs → System, and look for any new TBS errors. They should be gone. If you still see 0X8029020D, try the next fix.

Fix 3: The 15-Minute Registry Permission Fix (Advanced)

This is the fix for when TBS can't access its own list. It's rare but happens after a security software update or a Windows feature update that locks down registry keys.

Warning: Editing the registry can break your system. Back it up first. File → Export from Registry Editor. Save the whole thing.

1. Press Win + R, type regedit, and hit Enter.
2. Navigate to HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\TBS. If that key doesn't exist, create it: right-click Microsoft → New → Key, name it TBS.
3. Right-click the TBS key and choose Permissions.
4. Click Advanced. In the new window, look at the Owner. It should be SYSTEM. If it's not, click Change, type SYSTEM, click Check Names, then OK.
5. Now check the permission entries. You need these four entries:

6. If any are missing, add them. Click Add → Select a principal → type the name → OK. Then set the permissions.
7. Once done, click OK on all dialogs. Close Registry Editor.
8. Restart your PC. The TBS service will start fresh with proper access.

Expected outcome: After restart, open tpm.msc. It should show the TPM ready. Check Event Viewer — no more 0X8029020D errors. This fix is permanent unless a future update overwrites the permissions.

One more thing: if none of these work, check your motherboard's firmware (BIOS/UEFI) for a TPM firmware update. Some manufacturers (like ASUS and Lenovo) have released patches for TPM bugs that cause this exact error. It's a pain but worth checking if you're stuck.