| Previous | Next |
| STATUS_TPM_FAIL | STATUS_TPM_INSTALL_DISABLED |
STATUS_TPM_BAD_ORDINAL
The TPM does not accept the command ordinal
STATUS_TPM_BAD_ORDINAL is a Windows NTSTATUS value mapped from the TPM facility. In this package the code belongs to TPM 1.2 style command processing, where Windows software, TBS, the TPM driver, and the hardware device all may be visible in the same failure path.
The relevant area is TPM command ordinal dispatch. TPM commands are selected by ordinal values. This status means the ordinal is not implemented, not recognized for the TPM family/version, or is inconsistent with the current device mode.
Do not confuse this with a malformed command parameter. If the ordinal itself is wrong, the TPM has not reached command-specific parameter semantics. This often points to a version mismatch, using TPM 2.0 command assumptions against a TPM 1.2 path, or sending a vendor/optional command to hardware that does not implement it.
Diagnostic focus
- Log the numeric ordinal and the TPM family/version reported by capability queries.
- Check whether Windows command blocking or an application compatibility layer rewrote the command path.
- Verify that the command is allowed before the TPM has completed startup/self-test if the failing path is early boot.
References
- TCG: TPM 1.2 Part 1 Design Principles
- TCG: TPM 1.2 Part 3 Commands
- Microsoft: TPM Base Services
- Microsoft: Using TPM Base Services
- Microsoft: MS-ERREF NTSTATUS values
Looking for a different code? Search another status or error code.