| Previous | Next |
| STATUS_TPM_DELEGATE_ADMIN | STATUS_TPM_OWNER_CONTROL |
STATUS_TPM_TRANSPORT_NOTEXCLUSIVE
A command escaped the expected exclusive transport session
STATUS_TPM_TRANSPORT_NOTEXCLUSIVE is tied to TPM 1.2 transport-session semantics. Transport sessions group one or more TPM commands so the platform can audit or protect the command sequence; some flows require exclusive use of that session.
The status means the TPM observed command execution that violated that exclusivity rule. In practical debugging this usually points to interleaving by another caller, an incorrectly reused TBS context, or command submission that did not remain inside the transport sequence that established the policy.
This is not the same as a bad authorization digest. The session may be valid, but the ordering and isolation requirements around the transport sequence were not preserved.
Diagnostic focus
- Log the TBS context, transport handle, and command ordinal sequence.
- Look for concurrent command submission through the same process or service path.
- Check whether a higher-level library opened a transport session but then sent a command through a different context.
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.