| Previous | Next |
| TPM_E_BAD_SCHEME | TPM_E_BAD_MODE |
TPM_E_BAD_DATASIZE
Which layer owns this HRESULT
TPM_E_BAD_DATASIZE (0x8028002B) 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 a TPM 1.2 data or blob length is inconsistent with the command, key, scheme or enclosing structure.
The first producer to identify for this HRESULT is the TPM 1.2 command decoder and state machine. TPM 1.2 is a command/response device with strict binary structures and stateful resources. Windows may present the device response as an HRESULT, but the diagnostic meaning still belongs to the command field, key, session, PCR, NV index or lifecycle check named by the TPM specification.
The result value 0x8028002B should remain attached to the symbolic name. Some this result logs store the value as a negative signed integer; others expose only a generic CNG, WMI, BitLocker or enrollment message. Neither substitution identifies the a TPM 1.2 data or blob length is inconsistent with the command, key, scheme or enclosing structure as precisely as it.
Diagnostic record
- Producer for this HRESULT: the TPM 1.2 command decoder and state machine.
- Rejected invariant: a TPM 1.2 data or blob length is inconsistent with the command, key, scheme or enclosing structure.
- Decisive capture: declared and actual lengths at every layer, paramSize, key modulus size, encrypted blob size, structure tags, and any base64 or network conversion.
- Safe comparison: compare a byte-for-byte command decode with the specification and test the nearest valid boundary size.
How to verify the distinction
Build the result minimal case around the original command contract. Use a disposable object when the request can write NV data, advance a counter, change authorization state or consume a lock transition. The comparison is valid only when the caller, TPM generation and security policy remain the same.
| Question | Evidence for this HRESULT |
|---|---|
| What exact state was rejected? | a TPM 1.2 data or blob length is inconsistent with the command, key, scheme or enclosing structure |
| Which layer owns the result? | The TPM 1.2 command decoder and state machine. |
| What must be correlated? | declared and actual lengths at every layer, paramSize, key modulus size, encrypted blob size, structure tags, and any base64 or network conversion |
| What is the controlled comparison? | compare a byte-for-byte command decode with the specification and test the nearest valid boundary size |
Common false equivalences
| Constant | Checkpoint represented by its standard message |
|---|---|
TPM_E_BAD_MODE | A mode parameter is bad, such as capArea or subCapArea for TPM_GetCapability, phsicalPresence parameter for TPM_PhysicalPresence, or migrationType for TPM_CreateMigrationBlob — a separate checkpoint when compared with this result. |
TPM_E_BAD_SCHEME | The signature or encryption scheme for this key is incorrect or not permitted in this situation — a separate checkpoint when compared with this result. |
TPM_E_BAD_PRESENCE | Either the physicalPresence or physicalPresenceLock bits have the wrong value — a separate checkpoint when compared with it. |
The codes above may appear in the same workflow, but they are not aliases. TPM_E_BADTAG rejects header type, while it reaches a length relationship in the body or referenced object.
What a real fix looks like
Fix serialization and preserve binary data exactly; increasing an output buffer cannot repair a malformed length inside the request. 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.
Proof for this HRESULT consists of a successful replay plus validation of the intended key, PCR, NV, context, event-log, provider or service result. A software fallback or a newly provisioned blank TPM answers a different question than it.
Source material
- 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.