| Previous | Next |
| TBSIMP_E_LIST_NO_MORE_ITEMS | TBSIMP_E_NOT_ENOUGH_SPACE |
TBSIMP_E_LIST_NOT_FOUND
Read the result in context
TBSIMP_E_LIST_NOT_FOUND means the internal TBS list does not contain the requested context, resource or scheduling entry.
The first producer to identify is the TBS context and virtual-resource manager that maps finite TPM slots for multiple clients. TBS resource virtualization maps client-visible virtual handles to finite physical TPM key, authorization and transport slots. Cleanup, eviction and context ownership determine whether a mapping can be restored.
Fields worth decoding
| Question | Evidence |
|---|---|
| What exact state was rejected? | the internal TBS list does not contain the requested context, resource or scheduling entry |
| Which layer owns the result? | The TBS context and virtual-resource manager that maps finite TPM slots for multiple clients. |
| What must be correlated? | requested identifier, list type, insertion and removal events, context, virtual handle, and concurrent cancellation or cleanup |
| Controlled comparison | create a fresh entry and access it before any close, flush or power transition |
Record the original command or API call before retry logic for this result mutates its nonces, handles, buffers or state. Also retain the full HRESULT as 0x8029020E; signed decimal logging can hide the result TPM/TBS facility and make searches less precise.
Controlled comparison
- Establish the baseline with the same device, Windows build, account and TPM generation.
- Perform one narrow experiment: create a fresh entry and access it before any close, flush or power transition.
- Compare raw inputs and the first response, not only the final application dialog.
- Stop after the first changed result; if a later error replaces this HRESULT, this condition was passed even if the whole workflow still fails.
Adjacent failures
| Result | Different diagnostic question |
|---|---|
TBSIMP_E_NOT_ENOUGH_SPACE | The TPM does not have enough space to load the requested resource. |
TBSIMP_E_LIST_NO_MORE_ITEMS | The specified list is empty, or the iteration has reached the end of the list. |
TBSIMP_E_NOT_ENOUGH_TPM_CONTEXTS | There are too many TPM contexts in use. |
The key distinction is that TBSIMP_E_HASH_BAD_KEY reports the analogous failure in a hash-table lookup.
Repair without destroying evidence
To correct this, stop using removed entries and preserve diagnostics if the service loses a live entry unexpectedly. Do not confuse a TBS virtual handle with a physical TPM handle or copy it to another process. Resource virtualization intentionally scopes mappings to a client context.
Technical references
Looking for a different code? Search another status or error code.