What does HRESULT 0x80092011 (CRYPT_E_NO_REVOCATION_DLL) mean?

 
Previous Next
CRYPT_E_REVOKED CRYPT_E_NO_REVOCATION_CHECK

CRYPT_E_NO_REVOCATION_DLL

No installed or registered revocation function was available to check the certificate. This is a local revocation-provider capability issue, not a conclusion that the certificate is revoked.

What to check for CRYPT_E_NO_REVOCATION_DLL

  • Identify which certificate type and revocation provider the application expected to use.
  • Check the application and system configuration that registers or enables the relevant provider.
  • Do not disable revocation checking as a permanent workaround; restore the supported validation path.

Microsoft: CertVerifyRevocation

Microsoft: Certificate revocation list semantics

Diagnostic interpretation of CRYPT_E_NO_REVOCATION_DLL

CRYPT_E_NO_REVOCATION_DLL has the HRESULT value 0x80092011. AllStat records the condition as “No Dll or exported function was found to verify revocation.”. For CRYPT_E_NO_REVOCATION_DLL, in practice, interpret that wording at the boundary owned by cryptography, certificate, trust, or key-provider processing, rather than treating the value as a generic Windows message.

Evidence to capture for CRYPT_E_NO_REVOCATION_DLL

  • Record the exact COM method or Windows API, its input object, the calling thread, and the full 0x80092011 value before a wrapper converts it to an exception or Boolean result.
  • Capture any IErrorInfo text, activity identifier, event-log entry, and subsystem trace that mentions CRYPT_E_NO_REVOCATION_DLL or the crypt / revocation / dll operation.
  • Preserve the first failure in the call chain; a later HRESULT can describe cleanup rather than the original crypt / revocation / dll condition.

Retry and recovery for CRYPT_E_NO_REVOCATION_DLL

Retry CRYPT_E_NO_REVOCATION_DLL only when the owning API documents a transient state or after the condition described as “No Dll or exported function was found to verify revocation.” has changed. For CRYPT_E_NO_REVOCATION_DLL, configuration, policy, format, and authorization failures normally require correction first; an immediate loop can hide the original call site and add secondary errors.


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