What does HRESULT 0x8029020A (TBSIMP_E_SCHEDULER_NOT_RUNNING) mean?

 
Previous Next
TBSIMP_E_RPC_INIT_FAILED TBSIMP_E_COMMAND_CANCELED

TBSIMP_E_SCHEDULER_NOT_RUNNING

Where the failure is raised

TBSIMP_E_SCHEDULER_NOT_RUNNING (0x8029020A) 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 command scheduler is not active when a request reaches it.

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.

The result value 0x8029020A 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 internal TBS command scheduler is not active when a request reaches it as precisely as it.

Evidence that changes the diagnosis

  • Producer for this HRESULT: the TBS client library, local RPC service and command scheduler before or around device execution.
  • Rejected invariant: the internal TBS command scheduler is not active when a request reaches it.
  • Decisive capture: TBS service state, scheduler startup events, pending commands, power transition, cancellation history, and OS servicing level.
  • Safe comparison: wait for normal service initialization and submit one capability command from a fresh context.

A controlled verification

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.

QuestionEvidence for this HRESULT
What exact state was rejected?the internal TBS command scheduler is not active when a request reaches it
Which layer owns the result?The TBS client library, local RPC service and command scheduler before or around device execution.
What must be correlated?TBS service state, scheduler startup events, pending commands, power transition, cancellation history, and OS servicing level
What is the controlled comparison?wait for normal service initialization and submit one capability command from a fresh context

Related TPM and TBS results

ConstantCheckpoint represented by its standard message
TBSIMP_E_COMMAND_CANCELEDThe command was canceled — a separate checkpoint when compared with this result.
TBSIMP_E_RPC_INIT_FAILEDThe RPC subsystem could not be initialized — a separate checkpoint when compared with this result.
TBSIMP_E_OUT_OF_MEMORYThere 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_SERVICE_START_PENDING is the public startup state, while this code names the internal scheduler.

Correction and proof

Restore service health or apply platform servicing; do not loop command submission while the scheduler remains stopped. 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 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


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