| Previous | Next |
| TBSIMP_E_PPI_NOT_SUPPORTED | TBSIMP_E_NO_EVENT_LOG |
TBSIMP_E_TPM_INCOMPATIBLE
The decisive TPM checkpoint
TBSIMP_E_TPM_INCOMPATIBLE (0x8029021A) belongs to the public and internal TPM Base Services path. The base What Is page already shows the short Windows message; the additional diagnostic value is that this result marks the TPM generation or interface exposed by the platform is incompatible with the TBS implementation path being used.
The first producer to identify for it is the TBS client library, local RPC service and command scheduler before or around device execution. TBS centralizes TPM access through a local RPC service. A failure can therefore occur in the caller contract, RPC/service startup, scheduling, buffer handling or TPM submission, and each layer requires different evidence.
The result value 0x8029021A 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 TPM generation or interface exposed by the platform is incompatible with the TBS implementation path being used as precisely as it.
Before changing the platform
- Producer for it: the TBS client library, local RPC service and command scheduler before or around device execution.
- Rejected invariant: the TPM generation or interface exposed by the platform is incompatible with the TBS implementation path being used.
- Decisive capture: TPM version and interface type, context include flags, device information, firmware mode, OS build, and command encoding generation.
- Safe comparison: query device information and create a context requesting only the detected TPM generation.
Test the contract
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 it |
|---|---|
| What exact state was rejected? | the TPM generation or interface exposed by the platform is incompatible with the TBS implementation path being used |
| Which layer owns the result? | The TBS client library, local RPC service and command scheduler before or around device execution. |
| What must be correlated? | TPM version and interface type, context include flags, device information, firmware mode, OS build, and command encoding generation |
| What is the controlled comparison? | query device information and create a context requesting only the detected TPM generation |
Why another code is not equivalent
| Constant | Checkpoint represented by its standard message |
|---|---|
TBSIMP_E_UNKNOWN_ORDINAL | The TBS does not recognize the specified ordinal — a separate checkpoint when compared with this result. |
TBSIMP_E_COMMAND_FAILED | The TPM command failed — a separate checkpoint when compared with this result. |
TBSIMP_E_OUT_OF_MEMORY | There was not enough memory to fulfill the request — a separate checkpoint when compared with it. |
The codes above may appear in the same workflow, but they are not aliases. TBS_E_INVALID_CONTEXT_PARAM can result when the caller requests the wrong generation before reaching this internal compatibility check.
Evidence of success
Use matching tpm 1.2 or 2.0 structures and update platform firmware or windows when the exposed interface is inconsistent. Do not restart or disable TBS before capturing its service and event data. Most caller-contract errors are reproducible without touching TPM ownership, firmware state or stored keys.
Proof for it 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
- Microsoft: About TPM Base Services — source for the checkpoint.
- Microsoft: TBS return codes — source for the checkpoint.
- Microsoft: Tbsi_Context_Create — source for the checkpoint.
- Microsoft: Tbsip_Submit_Command — source for the checkpoint.
Looking for a different code? Search another status or error code.