HRESULT 0x80284005 (TBS_E_INSUFFICIENT

Status / error code:

Category:

Constant name:

Source:

Facility:

Operating System:

Description:

A specified output buffer is too small.

Previous	Next
TBS_E_INVALID_CONTEXT	TBS_E_IOERROR

TBS_E_INSUFFICIENT_BUFFER

Where the failure is raised

TBS_E_INSUFFICIENT_BUFFER (0x80284005) 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 public TBS output buffer is valid but cannot hold the full returned result.

The first producer to identify for TBS_E_INSUFFICIENT_BUFFER is the TBS client library, local RPC service and command scheduler before or around device execution. For TBS_E_INSUFFICIENT_BUFFER, tBS centralizes TPM access through a local RPC service. For TBS_E_INSUFFICIENT_BUFFER, a failure can therefore occur in the caller contract, RPC/service startup, scheduling, buffer handling or TPM submission, and each layer requires different evidence.

Evidence that changes the diagnosis

Question	Evidence for `TBS_E_INSUFFICIENT_BUFFER`
What exact state was rejected?	the public TBS output buffer is valid but cannot hold the full returned result
Which layer owns the result?	For `TBS_E_INSUFFICIENT_BUFFER`, the TBS client library, local RPC service and command scheduler before or around device execution.
What must be correlated?	input capacity, required size returned through the length parameter, command maximum response, allocation arithmetic, and whether the same variable was reused incorrectly
What is the controlled comparison?	perform the documented sizing call or allocate the reported size and repeat without changing the command

A useful TBS_E_INSUFFICIENT_BUFFER trace links three code-specific timelines: the application call, the local TBS/provider or firmware event, and the raw command/response exchange. The TBS_E_INSUFFICIENT_BUFFER timestamps should describe one attempt; combining data from separate retries is particularly misleading for authorization sessions, context counters, DAA stages and lockout state.

A controlled verification

The one-variable check is to perform the documented sizing call or allocate the reported size and repeat without changing the command. Record the before/after state that the TBS_E_INSUFFICIENT_BUFFER command is allowed to change. If the TBS_E_INSUFFICIENT_BUFFER operation can have side effects, use a disposable key, session, counter or NV index rather than production material.

Capture TBS_E_INSUFFICIENT_BUFFER and 0x80284005 at the first code-specific return boundary.
Decode the TBS_E_INSUFFICIENT_BUFFER state: TBS function, context, pointer and buffer contract, service state, command size and nested status.
Run the TBS_E_INSUFFICIENT_BUFFER controlled comparison once and preserve both binary transcripts.
Verify the expected TBS_E_INSUFFICIENT_BUFFER output or state transition instead of relying on absence of a UI message.

Related TPM and TBS results

Comparison code	Built-in distinction
`TBS_E_INVALID_CONTEXT_PARAM`	One or more context parameters is invalid — a separate checkpoint when compared with `TBS_E_INSUFFICIENT_BUFFER`.
`TBS_E_INVALID_CONTEXT`	The specified context handle does not refer to a valid context — a separate checkpoint when compared with `TBS_E_INSUFFICIENT_BUFFER`.
`TBS_E_SERVICE_START_PENDING`	The TBS service has been started but is not yet running — a separate checkpoint when compared with `TBS_E_INSUFFICIENT_BUFFER`.

TBS_E_INSUFFICIENT_BUFFER specifically answers whether the public TBS output buffer is valid but cannot hold the full returned result. In contrast, TBS_E_BUFFER_TOO_LARGE rejects an excessive buffer rather than insufficient capacity.

Correction and proof

To remediate TBS_E_INSUFFICIENT_BUFFER, honor the returned required length and cap allocations against the documented TBS maximum. For TBS_E_INSUFFICIENT_BUFFER, do not restart or disable TBS before capturing its service and event data. For TBS_E_INSUFFICIENT_BUFFER, most caller-contract errors are reproducible without touching TPM ownership, firmware state or stored keys.

After correcting TBS_E_INSUFFICIENT_BUFFER, 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 TBS_E_INSUFFICIENT_BUFFER checkpoint.
Microsoft: TBS return codes — source for the TBS_E_INSUFFICIENT_BUFFER checkpoint.
Microsoft: Tbsi_Context_Create — source for the TBS_E_INSUFFICIENT_BUFFER checkpoint.
Microsoft: Tbsip_Submit_Command — source for the TBS_E_INSUFFICIENT_BUFFER checkpoint.

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