| Previous | Next |
| TBSIMP_E_INVALID_PARAMETER | TBSIMP_E_SCHEDULER_NOT_RUNNING |
TBSIMP_E_RPC_INIT_FAILED
Locate the first producer
TBSIMP_E_RPC_INIT_FAILED (0x80290209) 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 TBS implementation could not initialize the local RPC path used between the client library and service.
The first producer to identify for this HRESULT 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.
Data to retain
Preserve these this result items before changing anything:
- This result and
0x80290209, the exact returning method or command, and the first nested status. - service state, RPC subsystem events, endpoint registration, process token, boot timing, servicing state, and the first failure.
- The TPM generation, manufacturer/firmware revision, Windows build, caller identity and TBS/provider state for this HRESULT.
- The complete opaque request artifacts, redacting authorization secrets but not rewriting structure boundaries.
Verification sequence
Run this focused check: create a context from a minimal local process after the TBS service and RPC services are running. Do not combine the result 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 TBS implementation could not initialize the local RPC path used between the client library and service | The original this result command reaches the next defined state without returning it. |
| Security behavior | The result verification still uses the intended TPM, authorization, locality and policy. |
| Output integrity | The object, digest, event log or state transition produced after it validates independently. |
Codes that answer different questions
| Related result | Separate meaning |
|---|---|
TBSIMP_E_SCHEDULER_NOT_RUNNING | The TBS scheduler is not running — a separate checkpoint when compared with it. |
TBSIMP_E_INVALID_PARAMETER | One or more parameters is invalid — a separate checkpoint when compared with it. |
TBSIMP_E_COMMAND_CANCELED | The command was canceled — a separate checkpoint when compared with it. |
The practical distinction is that TBSIMP_E_SCHEDULER_NOT_RUNNING occurs after RPC may be available but command scheduling is not active.
Exit condition for the incident
The supported direction is to repair Windows service or RPC initialization and preserve system events; TPM ownership changes are unrelated. 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.
If the same bytes still return it 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
- 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.