| Previous | Next |
| TBSIMP_E_LIST_NOT_FOUND | TBSIMP_E_NOT_ENOUGH_TPM_CONTEXTS |
TBSIMP_E_NOT_ENOUGH_SPACE
The state machine behind the code
TBSIMP_E_NOT_ENOUGH_SPACE (0x8029020F) 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 TPM does not have room to load the resource selected by TBS virtualization at this moment.
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.
Evidence table
Preserve these this result items before changing anything:
- This result and
0x8029020F, the exact returning method or command, and the first nested status. - resource type, physical TPM slots, virtual resource count, load and eviction commands, pinned or non-evictable objects, and context ownership.
- The TPM generation, manufacturer/firmware revision, Windows build, caller identity and TBS/provider state for this HRESULT.
- The complete opaque request artifacts, redacting authorization secrets but not rewriting structure boundaries.
Reproduction plan
Run this focused check: flush one disposable resource and retry loading a fresh object of the same type. Do not combine the result test with firmware updates, TPM clearing, account changes, key recreation and policy edits in the same trial; such a result cannot isolate this boundary.
| Checkpoint | Pass condition |
|---|---|
| the TPM does not have room to load the resource selected by TBS virtualization at this moment | The original this result command reaches the next defined state without returning it. |
| Security behavior | The result verification still uses the intended TPM, authorization, locality and policy. |
| Output integrity | The object, digest, event log or state transition produced after it validates independently. |
Contrast with neighboring results
| Related result | Separate meaning |
|---|---|
TBSIMP_E_NOT_ENOUGH_TPM_CONTEXTS | There are too many TPM contexts in use — a separate checkpoint when compared with it. |
TBSIMP_E_LIST_NOT_FOUND | The specified item was not found in the list — a separate checkpoint when compared with it. |
TBSIMP_E_RESOURCE_EXPIRED | The requested resource is no longer available — a separate checkpoint when compared with it. |
The practical distinction is that TBSIMP_E_OUT_OF_MEMORY is host memory exhaustion; it is TPM resource space.
Confirming remediation
The supported direction is to release resources, avoid pinning unnecessary objects, and let TBS virtualize supported resource classes. 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.
If the same bytes still return it after the documented preconditions are satisfied, retain this code-specific trace for the platform vendor or Windows component owner rather than erasing state.
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.