| Previous | Next |
| TBSIMP_E_HASH_TABLE_FULL | TBSIMP_E_TOO_MANY_RESOURCES |
TBSIMP_E_TOO_MANY_TBS_CONTEXTS
Locate the first producer
TBSIMP_E_TOO_MANY_TBS_CONTEXTS (0x80290217) 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 context table has no capacity for another client context.
The first producer to identify for it 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.
Data to retain
Preserve these this result items before changing anything:
- This result and
0x80290217, the exact returning method or command, and the first nested status. - open context count, process owners, create/close balance, crashed clients, service uptime, and configured platform limits.
- The TPM generation, manufacturer/firmware revision, Windows build, caller identity and TBS/provider state for it.
- The complete opaque request artifacts, redacting authorization secrets but not rewriting structure boundaries.
Verification sequence
Run this focused check: close one known context and create exactly one replacement. 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 internal TBS context table has no capacity for another client context | 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. |
Codes that answer different questions
| Related result | Separate meaning |
|---|---|
TBSIMP_E_TOO_MANY_RESOURCES | A new virtual resource could not be created because there are too many open virtual resources — a separate checkpoint when compared with it. |
TBSIMP_E_HASH_TABLE_FULL | No new entries can be added to the hash table — a separate checkpoint when compared with it. |
TBSIMP_E_NOTHING_TO_UNLOAD | No resources can be unloaded — a separate checkpoint when compared with it. |
The practical distinction is that TBS_E_TOO_MANY_TBS_CONTEXTS is the caller-facing version of this limit.
Exit condition for the incident
The supported direction is to ensure deterministic context closure and avoid creating one context per command. 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.