| 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 (0x8029020E) belongs to TBS resource virtualization. The base What Is page already shows the short Windows message; the additional diagnostic value is that this result marks the internal TBS list does not contain the requested context, resource or scheduling entry.
The first producer to identify for this HRESULT 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 for this HRESULT |
|---|---|
| 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 |
| What is the controlled comparison? | create a fresh entry and access it before any close, flush or power transition |
Record the original command or API call before this result retry logic 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 result 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 this result inputs and the first response, not only the final application dialog.
- Stop after the first changed the checkpoint; a later error means this boundary was passed even if the whole workflow still fails.
Adjacent failure boundaries
| Result | Different diagnostic question |
|---|---|
TBSIMP_E_NOT_ENOUGH_SPACE | The TPM does not have enough space to load the requested resource — a separate checkpoint when compared with this result. |
TBSIMP_E_LIST_NO_MORE_ITEMS | The specified list is empty, or the iteration has reached the end of the list — a separate checkpoint when compared with it. |
TBSIMP_E_NOT_ENOUGH_TPM_CONTEXTS | There are too many TPM contexts in use — a separate checkpoint when compared with it. |
The decisive distinction for this HRESULT is that TBSIMP_E_HASH_BAD_KEY reports the analogous failure in a hash-table lookup. The short platform wording — “The specified item was not found in the list.” — does not supply that differential diagnosis by itself.
Repair without destroying evidence
The corrective direction is to 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.
A verified it repair reproduces the original request with the same intended security policy and passes this checkpoint. Replacing it with a broader wrapper status, silently falling back to software keys, or suppressing verification is not proof of success.
Technical references
- Microsoft: Resource Virtualization in TBS — source for the checkpoint.
- Microsoft: Command Scheduling in TBS — source for the checkpoint.
- Microsoft: About TPM Base Services — source for the checkpoint.
- Microsoft: Power Management in TBS — source for the checkpoint.
Looking for a different code? Search another status or error code.