| Previous | Next |
| STATUS_TPM_AREA_LOCKED | STATUS_TPM_READ_ONLY |
STATUS_TPM_BAD_LOCALITY
STATUS_TPM_BAD_LOCALITY is a Windows NTSTATUS value in the TPM facility. For STATUS_TPM_BAD_LOCALITY, it belongs to the TPM 1.2 error family and is normally surfaced through the Windows TPM stack, such as TPM Base Services, rather than by ordinary file, registry or network APIs.
Locality is a TPM mechanism for distinguishing command origins such as firmware, measured launch environments and the operating system. This status means the command reached the TPM with a locality that the target object or command does not permit.
It is especially relevant for PCR and NV operations whose attributes include locality rules. Ordinary application retries normally preserve the same locality and therefore repeat the failure.
Diagnostic focus
- Log the locality expected by the target object and the locality actually used by the command path.
- Review NV or PCR attributes before changing authorization data.
- Distinguish this from STATUS_TPM_NOTLOCAL, where locality information required for the reset path is absent.
References for STATUS_TPM_BAD_LOCALITY
- TCG: TPM 1.2 Main Specification
- Microsoft: TPM Base Services
- Microsoft: NTSTATUS values
- Linux kernel: TPM event log and PCR measurements
Looking for a different code? Search another status or error code.