| Previous | Next |
| TBS_E_INVALID_CONTEXT_PARAM | TBS_E_TOO_MANY_TBS_CONTEXTS |
TBS_E_SERVICE_NOT_RUNNING
TBS is the Windows broker for TPM access
TBS_E_SERVICE_NOT_RUNNING indicates that the TPM Base Services component is stopped and could not be started for the request. This is a Windows service-layer failure, not a response generated by TPM firmware. Until TBS is available, applications cannot create normal TBS contexts or submit commands through the broker.
The service may be disabled by configuration, fail during startup, or have a dependency or integrity problem. A present and healthy TPM device does not eliminate the need for the broker service.
Diagnostic steps
- Inspect the TBS service state, startup configuration, and Service Control Manager events.
- Distinguish this code from
TBS_E_SERVICE_DISABLED, which explicitly reports disabled configuration. - Check system-component integrity before attempting to replace TPM firmware.
- After TBS starts, create a fresh context; a context creation that previously failed should not be treated as valid.
References
- Microsoft: TPM Base Services overview and functions
- Microsoft: Tbsi_Context_Create
- Microsoft: TPM device information
Looking for a different code? Search another status or error code.