HRESULT 0x80280081 (TPM_E_ASYMMETRIC): meaning and diagnosis

Status / error code:

Category:

Constant name:

Source:

Facility:

Operating System:

Description:

TPM2.0 Asymmetric algorithm not supported or not correct.

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 TPM_E_ASYMMETRIC is the TPM 2.0 command parser and object-consistency checks. For TPM_E_ASYMMETRIC, 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. For TPM_E_ASYMMETRIC, similar display properties do not make two blobs interchangeable.

Read TPM_E_ASYMMETRIC 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 TPM_E_ASYMMETRIC.
State identity: command code, object public area, type, nameAlg, scheme, key bits or curve, parent attributes, and TPM capability results.
Platform identity for TPM_E_ASYMMETRIC: TPM generation, manufacturer/firmware revision, Windows build and relevant service events.
Binary identity: preserve opaque structures byte-for-byte and log 0x80280081 in hexadecimal.

One-variable test

Create a disposable object using one asymmetric profile advertised by the same tpm and repeat the operation. Keep every other TPM_E_ASYMMETRIC test condition unchanged. If the comparison reaches a later checkpoint, then the original TPM_E_ASYMMETRIC condition has been isolated even when a second defect remains.

Observed outcome	Interpretation for `TPM_E_ASYMMETRIC`
The exact request succeeds	For `TPM_E_ASYMMETRIC`, 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 `TPM_E_ASYMMETRIC` trace; the previous trace probably lost the first producer.
The same code returns with identical bytes	Escalate the persistent `TPM_E_ASYMMETRIC` result with firmware, service and command evidence rather than broad configuration changes.
The code disappears only after destructive reset	The `TPM_E_ASYMMETRIC` 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 `TPM_E_ASYMMETRIC`.
`TPM_E_ERROR_MASK`	This is an error mask to convert TPM hardware errors to win errors — a separate checkpoint when compared with `TPM_E_ASYMMETRIC`.
`TPM_E_FAIL`	The operation failed — a separate checkpoint when compared with `TPM_E_ASYMMETRIC`.

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. For TPM_E_ASYMMETRIC, do not pair a private blob with a public area or parent from another creation attempt. For TPM_E_ASYMMETRIC, tPM 2.0 object material is cryptographically bound even when the algorithms and display names match.

Close the TPM_E_ASYMMETRIC 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 TPM_E_ASYMMETRIC checkpoint.
TCG: TPM 2.0 Part 2 — Structures and response codes — source for the TPM_E_ASYMMETRIC checkpoint.
TCG: TPM 2.0 Part 3 — Commands — source for the TPM_E_ASYMMETRIC checkpoint.
Microsoft: TPM recommendations — source for the TPM_E_ASYMMETRIC checkpoint.

Looking for a different code? Search another status or error code.