| Previous | Next |
| STATUS_TPM_COMMAND_BLOCKED | STATUS_TPM_DUPLICATE_VHANDLE |
STATUS_TPM_INVALID_HANDLE
The requested TPM handle was not found
STATUS_TPM_INVALID_HANDLE indicates that a TPM-related handle supplied by the caller does not identify an existing object in the relevant handle namespace. Depending on the layer, that handle may be a TPM resource, a TBS context, or a provider object associated with TPM access.
This should be diagnosed as a lifetime problem before it is treated as a hardware problem. Handles can become invalid after context close, TPM reset, service restart, suspend/resume, or an earlier cleanup path that already flushed the object.
Compare this status with STATUS_TPM_BAD_HANDLE. Both involve handles, but the exact layer and handle type matter for deciding whether to recreate a Windows context or reload a TPM object.
Diagnostic focus
- Log the handle type and the API layer that returned the status.
- Check whether the TBS context or provider object was closed earlier.
- Recreate the context/object from a known-good root rather than reusing the stale handle.
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.