Fix Chrome ERR_SSL_PROTOCOL_ERROR (Windows 10/11)

Chrome refuses to load sites with ERR_SSL_PROTOCOL_ERROR. Usually caused by bad cached SSL state, antivirus interference, or expired certificates. Here's how to fix it.

Quick Fix (30 seconds)

Check your system clock. Seriously, do this first. If your Windows date or time is off by more than a few minutes, HTTPS handshakes fail instantly with ERR_SSL_PROTOCOL_ERROR. It's the #1 cause and nobody checks it until they've wasted 20 minutes.

Right-click the clock in the taskbar → Adjust date/time.
Toggle Set time automatically to On (if it's already on, turn it off, wait 5 seconds, then turn it back on).
Also toggle Set time zone automatically on.

If the time resets every boot, you've got a dead CMOS battery. That's a hardware fix, but for now, you can still use Windows Time Sync to keep it accurate each session.

Moderate Fix (5 minutes)

Still getting the error? Let's clear Chrome's cached SSL state and flush the system DNS cache. This handles most cases where a site used to work and suddenly stopped.

Flush Chrome's SSL Cache

Close Chrome completely (check the system tray for background Chrome processes).
Open File Explorer and paste this into the address bar:
```
chrome://net-internals/#ssl
```
Wait, that's a Chrome URL. You need to do this while Chrome is closed. Instead, go to %LOCALAPPDATA%\Google\Chrome\User Data and delete the Default\Network folder. That's where the SSL cache lives. Don't worry, it rebuilds automatically.
Alternatively, you can open Chrome, go to chrome://net-internals/#ssl, click Clear session cache, then go to chrome://net-internals/#sockets and click Flush socket pools.

Flush DNS in Windows

Open a command prompt as Administrator and run:

ipconfig /flushdns

Check for Chrome Flags Gone Wrong

Chrome flags like --ignore-certificate-errors or experimental QUIC can actually cause this. Go to chrome://flags, search for QUIC, and set it to Disabled. Also click Reset all at the top right to clear any other flags you might have messed with.

Advanced Fix (15+ minutes)

If the issue persists, we're dealing with something deeper. The usual suspects: antivirus TLS interception, corporate policy, or corrupted Chrome profile.

Bypass Antivirus/Proxy SSL Scanning

ESET, Kaspersky, Bitdefender — they all inject their own SSL certificates to decrypt your traffic. Sometimes that breaks Chrome. Temporarily disable the web protection or SSL scanning module and see if the site loads. If it does, whitelist that site or disable the SSL scanning for Chrome.

Check the Certificate Chain

Some sites fail because they're missing intermediate certificates. Even if the site owner messed up, you can still fix it on your end. Open the site in IE or Edge (they use a different certificate store) and see if it loads. If it does, export the intermediate certificate from Edge and import it into Windows' Trusted Root store:

In Edge, click the padlock → Certificate.
Go to the Certification Path tab, select the intermediate certificate, and click View Certificate.
Go to Details → Copy to File and export as .cer.
Open the exported file, click Install Certificate, and place it in Local Machine → Trusted Root Certification Authorities.

Reset Chrome via a New Profile

If none of that works, your Chrome profile might be corrupted. Create a new test profile — it's faster than a full reset:

Close Chrome.
Rename %LOCALAPPDATA%\Google\Chrome\User Data\Default to Default.old.
Restart Chrome. It'll create a fresh profile. Test the site again.
If it works, you can migrate your bookmarks and passwords from the old profile via chrome://settings/importData.

If the fresh profile still fails, it's not Chrome — it's your network. Check your router's DNS settings (try 8.8.8.8 and 8.8.4.4), or check if a VPN is intercepting traffic.

Last Resort: Disable Chrome's QUIC Protocol

QUIC is UDP-based HTTP/3, and some enterprise firewalls choke on it. If you've already reset flags and that didn't help, force Chrome to use TCP only:

Right-click the Chrome shortcut → Properties.
In the Target field, append --disable-quic (with a space before the dashes).
Click OK and restart Chrome.

That's a permanent workaround. A bit hacky, but I've seen it solve stubborn ERR_SSL_PROTOCOL_ERROR cases on corporate networks.

If you're still stuck after all this, run netsh winsock reset and reboot. That resets the entire network stack, and it's the nuclear option. But honestly, 90% of the time it's the clock or the SSL cache clear.