| Previous | Next |
| TPM_20_E_HMAC | TPM_20_E_EXCLUSIVE |
TPM_20_E_DISABLED
The command exists but is not enabled
TPM_20_E_DISABLED represents TPM_RC_DISABLED. It does not mean that Windows failed to find the TPM. The command reached a TPM 2.0 device, but that device is configured not to accept the command. A command can be implemented in firmware yet disabled by platform policy, TPM state, vendor configuration, or a command-control mechanism.
This distinction matters when diagnosing a failed API call. Reinstalling a driver will not enable a command that firmware intentionally blocks. Conversely, clearing the TPM is excessive unless the vendor documentation explicitly identifies state corruption and recovery requires a clear.
Useful evidence
- Record the command code and query TPM capabilities to confirm whether it is implemented.
- Check UEFI security settings and enterprise policy for command restrictions or disabled TPM functionality.
- Compare behavior before and after a cold boot when the command depends on startup state.
- Consult the TPM or system firmware vendor before changing security controls; the generic response code does not identify which control disabled the command.
References
- TCG Part 2: TPM response-code definitions
- TCG Part 3: TPM command definitions
- Microsoft: Win32_Tpm command queries
Looking for a different code? Search another status or error code.