| Previous | Next |
| E_SKYDRIVE_ROOT_TARGET_VOLUME_ROOT_NOT_SUPPORTED | TPM_E_AUTHFAIL |
TPM_E_ERROR_MASK
Read the result in context
TPM_E_ERROR_MASK means the HRESULT bit pattern used to recognize Windows mappings of TPM hardware responses, not a command outcome by itself.
The first producer to identify is Windows error classification rather than TPM command execution. Windows defines masks alongside concrete HRESULT values so software can classify facilities and embedded device responses. The mask has no independent command checkpoint, retry rule or remediation.
Fields worth decoding
| Question | Evidence |
|---|---|
| What exact state was rejected? | the HRESULT bit pattern used to recognize Windows mappings of TPM hardware responses, not a command outcome by itself |
| Which layer owns the result? | Windows error classification rather than TPM command execution. |
| What must be correlated? | the original 32-bit value before a wrapper converts it to signed decimal, plus the low TPM response-code bits and the API that surfaced it |
| Controlled comparison | apply the mask to a captured HRESULT and separately decode the embedded TPM return code; do not issue a TPM command merely to reproduce the mask constant |
Record the original command or API call before retry logic for this result mutates its nonces, handles, buffers or state. Also retain the full HRESULT as 0x80280000; signed decimal logging can obscure the TPM/TBS facility and make searches less precise.
Controlled comparison
- Establish the baseline with the same device, Windows build, account and TPM generation.
- Perform one narrow experiment: apply the mask to a captured HRESULT and separately decode the embedded TPM return code; do not issue a TPM command merely to reproduce the mask constant.
- Compare raw inputs and the first response, not only the final application dialog.
- Stop after the first changed result; if a later error replaces this HRESULT, this condition was passed even if the whole workflow still fails.
Adjacent failures
| Result | Different diagnostic question |
|---|---|
TPM_E_FAIL | The operation failed. |
TPM_E_SHA_THREAD | There is no existing SHA-1 thread. |
TPM_E_SHA_ERROR | The calculation is unable to proceed because the existing SHA-1 thread has already encountered an error. |
The key distinction is that a concrete TPM_E_* value describes a failed checkpoint; this mask only classifies a family of values.
Repair without destroying evidence
To correct this, change the decoder or telemetry schema so it preserves the full hexadecimal value and then diagnose the actual embedded TPM code. Do not report the mask constant as if the TPM returned it. A mask is useful for classification only after the complete HRESULT has been retained.
Technical references
Looking for a different code? Search another status or error code.