| Previous | Next |
| STATUS_TPM_BAD_DELEGATE | STATUS_TPM_TOOMANYCONTEXTS |
STATUS_TPM_BADCONTEXT
A saved TPM context blob cannot be restored or used
STATUS_TPM_BADCONTEXT indicates that a context blob presented to the TPM is invalid. TPM 1.2 context management lets software save and later reload certain resource contexts, but the blob must be intact, current, and valid for the TPM that created it.
This failure often follows stale cache use. A context blob can become unusable after TPM reset, owner changes, context-counter gaps, or corruption/truncation in caller storage.
Do not treat this as a file-format problem alone. The blob may be byte-for-byte intact but no longer acceptable to the TPM because its context generation or associated resource state has changed.
Diagnostic focus
- Record where the context blob was stored and whether it was modified or truncated.
- Check TPM reset, suspend/resume, clear, and ownership events between save and load.
- Flush cached contexts and recreate the TPM object when the generation no longer matches.
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.