| Previous | Next |
| STATUS_TPM_BADCONTEXT | STATUS_TPM_MA_TICKET_SIGNATURE |
STATUS_TPM_TOOMANYCONTEXTS
The TPM context-management limit has been reached
STATUS_TPM_TOOMANYCONTEXTS means TPM 1.2 context-management capacity has been exhausted. The TPM or its access stack is tracking too many contexts for keys, sessions, or other TPM resources.
This differs from system RAM exhaustion. The limit is inside the TPM resource model, and it can be triggered by callers that save contexts without flushing them or by long-running services that leak TPM sessions.
On Windows, TBS cooperatively schedules TPM access, but it cannot make unlimited TPM contexts available. The diagnostic task is to find which caller path owns the handles or cached contexts.
Diagnostic focus
- Track loaded keys, authorization sessions, transport sessions, and saved contexts per process.
- Check for missing flush/context-close paths after errors.
- Reduce parallel TPM use or serialize high-volume operations through a single owner component.
References
- TCG: TPM 1.2 Main Specification
- TCG: TPM 1.2 Part 1 Design Principles
- TCG: TPM 1.2 Part 2 Structures of the TPM
- TCG: TPM 1.2 Part 3 Commands
- Microsoft: TPM Base Services
- Microsoft: MS-ERREF NTSTATUS values
Looking for a different code? Search another status or error code.