| Previous | Next |
| STATUS_TPM_COMMAND_CANCELED | STATUS_TPM_NOT_FOUND |
STATUS_TPM_TOO_MANY_CONTEXTS
Context exhaustion and handle lifecycle
STATUS_TPM_TOO_MANY_CONTEXTS means that a new TPM context could not be created because too many contexts are open. It is a resource-lifecycle problem: a workload can leak sessions or contexts even while every individual command is syntactically valid.
This is different from a persistent-key quota or a missing TPM. Track the processes and libraries holding TPM work, close or release resources through their documented APIs, and avoid solving the immediate failure by clearing the TPM. Clearing destroys protected material but does not identify the consumer that exhausted the context budget.
What to establish before changing state
- Identify processes with concurrent TPM activity and reproduce the failure under a controlled load.
- Audit session/context release paths in the caller and any broker or service it uses.
- Use bounded concurrency and retry only after the resource-owning operation has released state.
References
- TCG TPM 2.0 Library Specification
- TCG TPM 1.2 context return values
- Microsoft: TPM error-code reference
Looking for a different code? Search another status or error code.