What does HRESULT 0x8028010B (TPM_20_E_PRIVATE) mean?

Status / error code:

Category:

Constant name:

Source:

Facility:

Operating System:

Description:

TPM2.0 TPM_RC_PRIVATE error.

Previous	Next
TPM_20_E_SEQUENCE	TPM_20_E_HMAC

TPM_20_E_PRIVATE

Where the failure is raised

TPM_20_E_PRIVATE (0x8028010B) 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 private or sensitive portion fails the consistency checks required for the object and its parent.

The first producer to identify for TPM_20_E_PRIVATE is the TPM 2.0 command parser and object-consistency checks. For TPM_20_E_PRIVATE, 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_20_E_PRIVATE, similar display properties do not make two blobs interchangeable.

Evidence that changes the diagnosis

Preserve these TPM_20_E_PRIVATE items before changing anything:

TPM_20_E_PRIVATE and 0x8028010B, the exact returning method or command, and the first nested status.
TPM2B_PRIVATE bytes, parent name and seed relationship, object public area, integrity and encrypted-sensitive fields, import/load command, and blob origin.
The TPM generation, manufacturer/firmware revision, Windows build, caller identity and TBS/provider state for TPM_20_E_PRIVATE.
The complete opaque TPM_20_E_PRIVATE request artifacts, redacting authorization secrets but not rewriting structure boundaries.

A controlled verification

Run this focused check: create and load one fresh object under the same parent without storage or transport conversion. Do not combine the TPM_20_E_PRIVATE test with firmware updates, TPM clearing, account changes, key recreation and policy edits in the same trial; such a result cannot isolate this boundary.

Checkpoint	Pass condition
the TPM 2.0 private or sensitive portion fails the consistency checks required for the object and its parent	The original `TPM_20_E_PRIVATE` command reaches the next defined state without returning this result.
Security behavior	The `TPM_20_E_PRIVATE` verification still uses the intended TPM, authorization, locality and policy.
Output integrity	The object, digest, event log or state transition produced after `TPM_20_E_PRIVATE` validates independently.

Related TPM and TBS results

Related result	Separate meaning
`TPM_E_ASYMMETRIC`	TPM2.0 Asymmetric algorithm not supported or not correct — a separate checkpoint when compared with `TPM_20_E_PRIVATE`.
`TPM_E_ERROR_MASK`	This is an error mask to convert TPM hardware errors to win errors — a separate checkpoint when compared with `TPM_20_E_PRIVATE`.
`TPM_E_FAIL`	The operation failed — a separate checkpoint when compared with `TPM_20_E_PRIVATE`.

The practical distinction is that TPM_E_ASYMMETRIC rejects an algorithm choice, whereas this response identifies the private object material.

Correction and proof

The supported direction is to restore the exact public/private pair and correct parent binding or import construction; private blobs are opaque and TPM-bound. For TPM_20_E_PRIVATE, do not pair a private blob with a public area or parent from another creation attempt. For TPM_20_E_PRIVATE, tPM 2.0 object material is cryptographically bound even when the algorithms and display names match.

If the same bytes still return TPM_20_E_PRIVATE after the documented preconditions are satisfied, retain this code-specific trace for the platform vendor or Windows component owner rather than erasing state.

Technical references

TCG: TPM 2.0 Library Specification — source for the TPM_20_E_PRIVATE checkpoint.
TCG: TPM 2.0 Part 2 — Structures and response codes — source for the TPM_20_E_PRIVATE checkpoint.
TCG: TPM 2.0 Part 3 — Commands — source for the TPM_20_E_PRIVATE checkpoint.
Microsoft: TPM recommendations — source for the TPM_20_E_PRIVATE checkpoint.

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