| Previous | Next |
| TPMAPI_E_INVALID_OWNER_AUTH | TPMAPI_E_EMPTY_TCG_LOG |
TPMAPI_E_FIPS_RNG_CHECK_FAILED
TPMAPI_E_FIPS_RNG_CHECK_FAILED is a Windows TPM API result. It indicates that generated random data failed the validation performed by the TPM API FIPS random-number check.
What to check for TPMAPI_E_FIPS_RNG_CHECK_FAILED
- Stop using the returned random data and preserve the error context for security diagnostics.
- Check TPM firmware, Windows updates, and any hardware-health events before retrying.
- Escalate repeated failures to the device or platform administrator because they can indicate a security-relevant fault.
Microsoft documentation for TPMAPI error codes
Diagnostic interpretation
This result has the HRESULT value 0x80290119. AllStat records the condition as “The random number generated did not pass FIPS RNG check.”.
Evidence to capture
- Capture any IErrorInfo text, activity identifier, event-log entry, and subsystem trace that mentions this result or the tpmapi / fips / rng / check operation.
- check the documented return contract of the specific API because the same HRESULT can require different recovery in different interfaces.
Retry and recovery
A retry is useful only after the cause behind TPMAPI_E_FIPS_RNG_CHECK_FAILED has been changed or removed. Reproduce the original call and confirm both the return value and the resulting resource state.
Looking for a different code? Search another status or error code.