What does HRESULT 0x80290106 (TPMAPI_E_BUFFER_TOO_SMALL) mean?

 
Previous Next
TPMAPI_E_OUT_OF_MEMORY TPMAPI_E_INTERNAL_ERROR

TPMAPI_E_BUFFER_TOO_SMALL

TPMAPI_E_BUFFER_TOO_SMALL is a Windows TPM API result. It indicates that the destination buffer cannot hold the returned TPM data or encoded result.

What to check for TPMAPI_E_BUFFER_TOO_SMALL

  • Read the returned required size when the API provides one, then allocate a larger buffer.
  • Verify that byte counts, not element counts, are supplied for buffers whose APIs use byte lengths.
  • Handle variable-size TPM blobs and logs without relying on a fixed legacy buffer size.

Microsoft documentation for TPMAPI error codes

Diagnostic interpretation

This result has the HRESULT value 0x80290106. AllStat records the condition as “The specified buffer was too small.”.

Evidence to capture

  • Capture any IErrorInfo text, activity identifier, event-log entry, and subsystem trace that mentions this result or the tpmapi / buffer / too / small operation.
  • compare the failing machine with a working one at the same configuration boundary: component version, policy, registration, identity, and target resource.

Retry and recovery

Before repeating the call, correct the state that produced TPMAPI_E_BUFFER_TOO_SMALL. Verify the repair with the same inputs and observation points rather than with a broader reset.


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