| Previous | Next |
| TPM_E_NOCONTEXTSPACE | TPM_20_E_ATTRIBUTES |
TPM_E_ASYMMETRIC
Meaning beyond the built-in message
TPM_E_ASYMMETRIC (0x80280081) belongs to TPM 2.0 object processing. The base What Is page already shows the short Windows message; the additional diagnostic value is that this result marks the TPM 2.0 command selected an asymmetric algorithm or key relationship that is unsupported or incompatible.
The first producer to identify for it is the TPM 2.0 command parser and object-consistency checks. TPM 2.0 separates an object public area from protected private material and validates their algorithms, parent binding and integrity when commands load or use the object. Similar display properties do not make two blobs interchangeable.
Read this result as its own boundary in a sequence, not as a verdict that every TPM feature is broken. The sequence reaches the TPM 2.0 command selected an asymmetric algorithm or key relationship that is unsupported or incompatible, and the component returns 0x80280081 before the application can safely assume that later key, attestation, boot or licensing work occurred.
Decode the relevant state
- Request identity: exact function or command, input lengths, flags, caller context and this result.
- State identity: command code, object public area, type, nameAlg, scheme, key bits or curve, parent attributes, and TPM capability results.
- Platform identity for it: TPM generation, manufacturer/firmware revision, Windows build and relevant service events.
- Binary identity: preserve opaque structures byte-for-byte and log
0x80280081in hexadecimal.
One-variable test
Create a disposable object using one asymmetric profile advertised by the same tpm and repeat the operation. Keep every other this result test condition unchanged. If the comparison reaches a later checkpoint, then the original the condition has been isolated even when a second defect remains.
| Observed outcome | Interpretation |
|---|---|
| The exact request succeeds | The changed condition belongs to the rejected the TPM 2.0 command selected an asymmetric algorithm or key relationship that is unsupported or incompatible. |
| A more specific earlier code appears | Preserve the earlier result in the result trace; the previous trace probably lost the first producer. |
| The same code returns with identical bytes | Escalate the persistent it with firmware, service and command evidence rather than broad configuration changes. |
| The code disappears only after destructive reset | The result experiment is not diagnostic because original protected state and evidence were removed. |
Differential diagnosis
| Nearby constant | Why it is different |
|---|---|
TPM_20_E_PRIVATE | TPM2.0 TPM_RC_PRIVATE error — a separate checkpoint when compared with it. |
TPM_E_ERROR_MASK | This is an error mask to convert TPM hardware errors to win errors — a separate checkpoint when compared with it. |
TPM_E_FAIL | The operation failed — a separate checkpoint when compared with it. |
For this page, the useful contrast is: TPM_20_E_PRIVATE concerns validation of the sensitive/private portion rather than asymmetric algorithm selection.
Supported corrective direction
Apply the narrow remedy: select a supported algorithm/scheme combination and regenerate dependent objects; do not reinterpret a TPM 1.2 key template as TPM 2.0. Do not pair a private blob with a public area or parent from another creation attempt. TPM 2.0 object material is cryptographically bound even when the algorithms and display names match.
Close the incident only when the same API or TPM command passes with the intended hardware-backed behavior and the expected output can be independently validated.
References
- TCG: TPM 2.0 Library Specification — source for the checkpoint.
- TCG: TPM 2.0 Part 2 — Structures and response codes — source for the checkpoint.
- TCG: TPM 2.0 Part 3 — Commands — source for the checkpoint.
- Microsoft: TPM recommendations — source for the checkpoint.
Looking for a different code? Search another status or error code.