| Previous | Next |
| TPM_E_AUDITFAIL_SUCCESSFUL | TPM_E_NOTLOCAL |
TPM_E_NOTRESETABLE
Interpret the boundary first
TPM_E_NOTRESETABLE (0x80280032) belongs to TPM 1.2 command processing. The base What Is page already shows the short Windows message; the additional diagnostic value is that this result marks the caller attempted to reset a PCR that lacks the resettable attribute in the TPM 1.2 profile.
Build the command transcript
| Question | Evidence for this HRESULT |
|---|---|
| What exact state was rejected? | the caller attempted to reset a PCR that lacks the resettable attribute in the TPM 1.2 profile |
| Which layer owns the result? | The TPM 1.2 command decoder and state machine. |
| What must be correlated? | PCR index, PCR attributes, locality, platform profile, command ordinal, and whether the caller confused reset with extend |
| What is the controlled comparison? | query PCR attributes and perform the experiment only on a PCR documented as resettable for the active locality |
Separate caller data from platform state. The result caller data includes the command, structures, lengths, handles and flags; platform state includes TPM generation, provisioning, locality, lockout, resource inventory, firmware and the TBS service lifecycle. This result is actionable only after the rejected side is identified.
Test one hypothesis
Use the following verification sequence:
- Capture the unmodified failing input and
0x80280032. - Query pcr attributes and perform the experiment only on a pcr documented as resettable for the active locality.
- Compare the first result divergent field or state transition.
- Repeat this result only after restoring the same baseline, with a bounded retry policy where the specification permits retry.
Do not merge these conditions
| Other code | Why a different remedy follows |
|---|---|
TPM_E_NOTLOCAL | Attempt to reset a PCR register that requires locality and locality modifier not part of command transport — a separate checkpoint when compared with this result. |
TPM_E_AUDITFAIL_SUCCESSFUL | TPM audit construction failed and the underlying command was returning success — a separate checkpoint when compared with it. |
TPM_E_BAD_TYPE | Make identity blob not properly typed — a separate checkpoint when compared with it. |
TPM_E_NOTLOCAL applies when a resettable PCR still requires a locality not present in the command. The result difference determines whether to change serialization, authorization, resource lifetime, firmware/PPI state, command policy or only retry timing.
A safe recovery path
Correct the original boundary by choosing this direction: use PCR_Extend for measurement accumulation or select a profile-defined resettable PCR; software cannot add the resettable attribute. Do not clear ownership, delete keys or reset PCR-related state merely to see whether the message disappears; those actions can destroy the evidence and protected material while leaving serialization or command-order defects unchanged.
A successful it outcome preserves the intended hardware trust boundary, passes the original request, and produces verifiable output. Masking it, swallowing this HRESULT or switching silently to a software provider is not remediation.
References used for this checkpoint
- TCG: TPM 1.2 Main Specification — source for the checkpoint.
- TCG: TPM 1.2 Part 2 — Structures — source for the checkpoint.
- TCG: TPM 1.2 Part 3 — Commands — source for the checkpoint.
- Microsoft: TPM Base Services portal — source for the checkpoint.
Looking for a different code? Search another status or error code.