| Previous | Next |
| STATUS_TPM_NOCONTEXTSPACE | STATUS_TPM_INVALID_HANDLE |
STATUS_TPM_COMMAND_BLOCKED
Blocked command versus unsupported command
STATUS_TPM_COMMAND_BLOCKED tells the caller that the command was blocked. This does not mean the TPM failed to parse a request, and it does not automatically mean that the hardware lacks the capability. The diagnostic question is which component or configuration blocked the command.
Record the command path, TPM version, Windows feature and any broker or management software involved. Keep this separate from STATUS_TPM_EMBEDDED_COMMAND_UNSUPPORTED, which concerns a command carried in a legacy transport context and is explicitly an unsupported-command condition.
What to establish before changing state
- Identify the exact command and the calling software component.
- Check feature support and policy state before changing TPM ownership or firmware configuration.
- Preserve the original status and logs; a broad reset loses the evidence needed to locate the blocker.
References
- Microsoft: TPM error-code reference
- TCG TPM 1.2 command specification
- Microsoft: Get-TpmSupportedFeature cmdlet
Looking for a different code? Search another status or error code.