| Previous | Next |
| TBS_E_INTERNAL_ERROR | TBS_E_INVALID_OUTPUT_POINTER |
TBS_E_BAD_PARAMETER
Classify the layer correctly
TBS_E_BAD_PARAMETER (0x80284002) 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 a public TBS API call rejected one or more input values before submitting a command to the TPM.
The first producer to identify for it 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.
Incident worksheet
| Question | Evidence for it |
|---|---|
| What exact state was rejected? | a public TBS API call rejected one or more input values before submitting a command to the TPM |
| Which layer owns the result? | The TBS client library, local RPC service and command scheduler before or around device execution. |
| What must be correlated? | function name, TBS context parameters, locality, priority, buffer pointers and lengths, flags, and process architecture |
| What is the controlled comparison? | invoke the same function with a minimal documented parameter set and a small known-good command buffer |
A useful this result trace links three code-specific timelines: the application call, the local TBS/provider or firmware event, and the raw command/response exchange. The result timestamps should describe one attempt; combining data from separate retries is particularly misleading for authorization sessions, context counters, DAA stages and lockout state.
A reproducible comparison
The one-variable check is to invoke the same function with a minimal documented parameter set and a small known-good command buffer. Record the before/after state that the result command is allowed to change. If the operation can have side effects, use a disposable key, session, counter or NV index rather than production material.
- Capture this result and
0x80284002at the first code-specific return boundary. - Decode the result state: TBS function, context, pointer and buffer contract, service state, command size and nested status.
- Run the result controlled comparison once and preserve both binary transcripts.
- Verify the expected this result output or state transition instead of relying on absence of a UI message.
Boundaries often confused with this one
| Comparison code | Built-in distinction |
|---|---|
TBS_E_INVALID_OUTPUT_POINTER | A specified output pointer is bad — a separate checkpoint when compared with it. |
TBS_E_INVALID_CONTEXT | The specified context handle does not refer to a valid context — a separate checkpoint when compared with it. |
TBS_E_INSUFFICIENT_BUFFER | A specified output buffer is too small — a separate checkpoint when compared with it. |
It specifically answers whether a public TBS API call rejected one or more input values before submitting a command to the TPM. In contrast, TBS_E_INVALID_CONTEXT_PARAM is specific to context-creation parameters.
Restore service safely
To remediate it, correct the API contract and structure sizes before investigating TPM firmware or key state. 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.
After correcting it, start with a fresh caller context where the protocol requires one, replay the original intended operation, and confirm that hardware-backed policy remains enforced.
Authoritative 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.