| Previous | Next |
| STATUS_TPM_BAD_DATASIZE | STATUS_TPM_BAD_PRESENCE |
STATUS_TPM_BAD_MODE
The TPM rejected a command mode value
STATUS_TPM_BAD_MODE is a Windows NTSTATUS value mapped from the TPM facility. For STATUS_TPM_BAD_MODE, 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 modes and capability selectors. Some TPM commands include mode-like parameters such as capability areas, locality/physical-presence controls, or migration mode selectors. This status means such a mode value is not valid in the current command context.
Do not reduce this to a generic bad parameter. The failing value usually selects a sub-operation or policy branch. Log the specific field name and current TPM state, because a mode can be valid generally but invalid while the TPM is disabled, deactivated, locality-constrained, or using a different command family.
Diagnostic focus
- Identify the exact mode field: capability area, sub-capability, locality, physical-presence, or migration selector.
- Check current TPM state and locality before retrying the same mode.
- Use capability queries to avoid sending selectors that this TPM version does not implement.
References for STATUS_TPM_BAD_MODE
- 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: Using TPM Base Services
- Microsoft: MS-ERREF NTSTATUS values
Looking for a different code? Search another status or error code.