| Previous | Next |
| TPM_20_E_NV_DEFINED | TPM_20_E_CPHASH |
TPM_20_E_BAD_CONTEXT
TPM_20_E_BAD_CONTEXT maps to TPM_RC_BAD_CONTEXT. The context presented to TPM2_ContextLoad is not valid. This is different from TPM_20_E_INTEGRITY: integrity reports a failed protected-data check, while this status means the context is not a valid loadable context for the TPM.
What to retain with a context
- Associate saved contexts with the TPM instance, boot/reset epoch, handle type, and client session that created them.
- Do not restore contexts after the conditions that invalidate them, such as a reboot or relevant TPM startup transition.
- Flush stale state and create a fresh session or object context when the application can safely do so.
TCG TPM 2.0 Part 2: TPM_RC_BAD_CONTEXT · TCG TPM 2.0 Part 3: TPM2_ContextLoad
Looking for a different code? Search another status or error code.
