Fix CRYPT_E_REVOKED (0x80092010) Certificate Error

The 30-Second Fix: Check Your Date & Time

Nine times out of ten, this error happens because your PC's clock is wrong. Certificates have an expiration date. If your system thinks it's 2019 or 2028, Windows will say the cert is revoked.

Right-click the time in your taskbar (bottom-right corner).
Select Adjust date/time.
Turn on Set time automatically and Set time zone automatically.
If they're already on, turn them off, wait 10 seconds, then turn them back on.
Click Sync now under Additional settings.
After clicking Sync now you should see a success message: "Your clock was successfully synchronized."

Now try whatever gave you the error again. If it works, you're done. If not, move to the next step.

The 5-Minute Fix: Update Root Certificates

Windows stores a list of trusted root certificates. Sometimes that list gets stale. An outdated root cert can make a valid certificate look revoked. Here's how to fix it.

Press the Windows key and type cmd.
Right-click Command Prompt and select Run as administrator.
Type this command and press Enter:
```
certutil -urlcache * delete
```
This clears the cached certificate revocation lists (CRLs).
Then type:
```
certutil -generateSSTFromWU root.sst
```
This downloads the latest root certificates from Microsoft Update. It takes about 30 seconds. You won't see any output until it finishes.
After it finishes, type:
```
certutil -addstore root root.sst
```
This installs the updated root certs into your system store.
Close the command prompt.

Try your application again. If the error still shows up, restart your computer and try again. Sometimes Windows needs a fresh start to pick up the new certificates.

The 15-Plus-Minute Fix: Dig Deeper

If the first two fixes didn't work, something more specific is wrong. Here are the real culprits I've seen in my years as a help desk manager.

Antivirus or Firewall Blocking Certificate Checks

Some antivirus programs (especially Norton, McAfee, and Bitdefender) intercept HTTPS traffic. They replace certificates with their own. If their cert is revoked or broken, you get error 0x80092010.

Temporarily disable your antivirus. Not just "pause" — actually turn off real-time protection.
Try the action that gave the error.
If it works now, you have two choices:

Switch to Windows Defender (built-in, free, and doesn't break certificate checks).
Or dig into your antivirus settings and turn off "SSL scanning" or "HTTPS scanning." That option is usually buried in advanced settings.

Corrupted Certificate Store

Sometimes the certificate store itself gets damaged. This happens after failed Windows updates or malware cleanup.

Open an elevated Command Prompt (same as before).
Type:
```
certutil -store my
```
Look for any certificates that say "REVOKED" or have a red X. Write down their serial numbers.
To remove a bad certificate, use:
```
certutil -delstore my "serial number here"
```
Replace "serial number here" with the actual serial number (no spaces in the hex string).
Then rebuild the store:
```
certutil -repairstore my ""
```
This tries to fix any issues in the personal certificate store.

Check the Specific Certificate with PowerShell

If you know which application or website is throwing the error, you can check its certificate manually.

Open PowerShell as administrator.

For a website, type:

[Net.ServicePointManager]::SecurityProtocol = [Net.SecurityProtocolType]::Tls12
$webRequest = [Net.WebRequest]::Create('https://the-broken-site.com')
$webRequest.GetResponse()
$cert = $webRequest.ServicePoint.Certificate
$cert.Subject

Replace the-broken-site.com with the actual URL.

Check the output. If it says "The certificate is revoked" in the error, the remote server's cert is truly revoked. That's not your fault — you need to contact the website owner.

Reset Windows Update Components

A broken Windows Update can prevent certificate updates. This is rare but worth trying if nothing else worked.

Open Command Prompt as administrator.
Stop the services by typing these commands one at a time:
```
net stop wuauserv
net stop cryptSvc
net stop bits
net stop msiserver
```
Each should say "The service was stopped successfully."

Rename the software distribution folder:

ren C:\Windows\SoftwareDistribution SoftwareDistribution.old

Restart the services:

net start wuauserv
net start cryptSvc
net start bits
net start msiserver

Restart your PC and try again.

One last thing: if you're using a corporate laptop with a VPN, disconnect from the VPN first. Some VPNs redirect certificate checks through their own servers, and those servers can block or replace certs. I've seen this on Cisco AnyConnect and Palo Alto GlobalProtect more times than I can count.

That's the complete fix for CRYPT_E_REVOKED (0x80092010). Start with the date/time, then the root cert update, then work through the advanced steps. Stop as soon as the error goes away. You don't need to do all of them.