| Previous | Next |
| CRYPT_E_NO_REVOCATION_DLL | CRYPT_E_REVOCATION_OFFLINE |
CRYPT_E_NO_REVOCATION_CHECK
A registered revocation function was available but could not perform a revocation check for the certificate context.
What to check for CRYPT_E_NO_REVOCATION_CHECK
- Distinguish this status from an actually revoked certificate and from a network-offline status.
- Inspect the certificate’s revocation information and the provider-specific events or logs.
- Verify chain-building and policy context as well as network reachability; revocation behavior depends on the certificate and the calling application policy.
Microsoft: CertVerifyRevocation
Microsoft: Certificate revocation list semantics
Microsoft: CertGetCertificateChain
Microsoft: CertVerifyCertificateChainPolicy
Diagnostic interpretation of CRYPT_E_NO_REVOCATION_CHECK
CRYPT_E_NO_REVOCATION_CHECK has the HRESULT value 0x80092012. AllStat records the condition as “The revocation function was unable to check revocation for the certificate.”. For CRYPT_E_NO_REVOCATION_CHECK, 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_CHECK
- Record the exact COM method or Windows API, its input object, the calling thread, and the full 0x80092012 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_CHECK or the crypt / revocation / check operation.
- For CRYPT_E_NO_REVOCATION_CHECK, compare the failing machine with a working one at the same configuration boundary: component version, policy, registration, identity, and target resource.
Retry and recovery for CRYPT_E_NO_REVOCATION_CHECK
Retry CRYPT_E_NO_REVOCATION_CHECK only when the owning API documents a transient state or after the condition described as “The revocation function was unable to check revocation for the certificate.” has changed. For CRYPT_E_NO_REVOCATION_CHECK, 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.