| Previous | Next |
| TBS_E_IOERROR | TBS_E_SERVICE_NOT_RUNNING |
TBS_E_INVALID_CONTEXT_PARAM
The state machine behind the code
TBS_E_INVALID_CONTEXT_PARAM means the TBS context-creation structure contains a version, flags or TPM-generation request that the API does not accept.
The first producer to identify 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.
Keep the result value 0x80284007 attached to the symbolic name. Some logs may store it as a negative signed integer or expose only a generic CNG, WMI, BitLocker or enrollment message. Preserve the original HRESULT because those representations can hide the TPM- or TBS-specific condition.
Evidence table
- Producer: the TBS client library, local RPC service and command scheduler before or around device execution.
- Rejected invariant: the TBS context-creation structure contains a version, flags or TPM-generation request that the API does not accept.
- What to capture: structure version, includeTpm12/includeTpm20 flags, reserved fields, structure size, OS version, and the exact context-create entry point.
- Safe comparison: zero-initialize the documented structure and request only the detected TPM generation.
Reproduction plan
| Question | Evidence |
|---|---|
| What exact state was rejected? | the TBS context-creation structure contains a version, flags or TPM-generation request that the API does not accept |
| Which layer owns the result? | The TBS client library, local RPC service and command scheduler before or around device execution. |
| What must be correlated? | structure version, includeTpm12/includeTpm20 flags, reserved fields, structure size, OS version, and the exact context-create entry point |
| Controlled comparison | zero-initialize the documented structure and request only the detected TPM generation |
Contrast with neighboring results
| Constant | Meaning |
|---|---|
TBS_E_SERVICE_START_PENDING | The TBS service has been started but is not yet running. |
TBS_E_INSUFFICIENT_BUFFER | A specified output buffer is too small. |
TBS_E_COMMAND_CANCELED | The command was canceled. |
The codes above may appear in the same workflow, but they are not aliases. TBS_E_BAD_PARAMETER covers parameters to TBS calls more generally.
Confirming remediation
Use the correct structure version and leave reserved fields zero; do not pass an application-private extension. 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 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 the original failure.
Source material
Looking for a different code? Search another status or error code.