| Previous | Next |
| TBSIMP_E_SCHEDULER_NOT_RUNNING | TBSIMP_E_OUT_OF_MEMORY |
TBSIMP_E_COMMAND_CANCELED
Locate the first producer
TBSIMP_E_COMMAND_CANCELED (0x8029020B) 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 internal TBS queue marks the operation canceled before it can deliver a TPM response.
Data to retain
| Question | Evidence for this HRESULT |
|---|---|
| What exact state was rejected? | the internal TBS queue marks the operation canceled before it can deliver a TPM response |
| Which layer owns the result? | The TBS client library, local RPC service and command scheduler before or around device execution. |
| What must be correlated? | queue entry, context, cancel source, service or power event, command duration, and whether resource virtualization had begun |
| What is the controlled comparison? | repeat an idempotent command with cancellation disabled and no sleep transition |
Separate caller data from platform state. The result caller data includes the command, structures, lengths, handles and flags; platform state includes TPM generation, provisioning, locality, lockout, resource inventory, firmware and the TBS service lifecycle. This result is actionable only after the rejected side is identified.
Verification sequence
Use the following verification sequence:
- Capture the unmodified failing input and
0x8029020B. - Repeat an idempotent command with cancellation disabled and no sleep transition.
- Compare the first result divergent field or state transition.
- Repeat this result only after restoring the same baseline, with a bounded retry policy where the specification permits retry.
Codes that answer different questions
| Other code | Why a different remedy follows |
|---|---|
TBSIMP_E_OUT_OF_MEMORY | There was not enough memory to fulfill the request — a separate checkpoint when compared with this result. |
TBSIMP_E_SCHEDULER_NOT_RUNNING | The TBS scheduler is not running — a separate checkpoint when compared with it. |
TBSIMP_E_COMMAND_FAILED | The TPM command failed — a separate checkpoint when compared with it. |
TBS_E_COMMAND_CANCELED is the public result that callers should normally handle. The result difference determines whether to change serialization, authorization, resource lifetime, firmware/PPI state, command policy or only retry timing.
Exit condition for the incident
Correct the original boundary by choosing this direction: coordinate cancellation with context teardown and rebuild any volatile resources after the interrupted request. 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.
A successful it outcome preserves the intended hardware trust boundary, passes the original request, and produces verifiable output. Masking it, swallowing this HRESULT or switching silently to a software provider is not remediation.
References used for this checkpoint
- 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.