Chrome ERR_CERT_DATE_INVALID after system time update — fixed

Quick answer

Open Date & Time settings, turn off Set time automatically, restart Chrome, then turn it back on. If that doesn't work, force a sync with w32tm /resync in Command Prompt (Admin).

What's happening here

Chrome checks the system clock against the certificate's valid date range. When your system clock jumps — say you updated it manually after it drifted, or a dual-boot with Windows/Linux messed it up — the time falls outside the certificate's window. Chrome sees a mismatch and throws ERR_CERT_DATE_INVALID. I've seen this a hundred times on Windows 10 and 11 after Daylight Saving Time changes or after a BIOS battery swap.

Fix steps

1. Check the clock — click the time in the taskbar. If it's off by more than a minute, fix it. Right-click time > Adjust date/time.
2. Toggle automatic time sync — turn off Set time automatically, wait 5 seconds, turn it back on. Chrome often caches the bad time check. This forces Windows to re-sync.
3. Force a resync from Command Prompt — if step 2 doesn't help, open CMD as Admin and run:

   w32tm /resync

   You should see Successfully resynchronized with .... If you get an error, try:

   w32tm /unregister
   w32tm /register
   w32tm /resync

   This re-registers the Windows Time service. Works like a charm 9 times out of 10.
4. Clear Chrome's SSL cache — go to chrome://net-internals/#hsts, scroll down to Delete domain security policies, type google.com and hit Delete. Then clear browser cache: Settings > Privacy & security > Clear browsing data > Cached images and files. This isn't always needed, but I've seen this fix leftover bad state.
5. Restart Chrome — close all Chrome windows, reopen. Test the site that gave the error.

Alternative fixes if the main steps don't work

Check your BIOS time

If the OS time looks right but Chrome still complains, boot into BIOS/UEFI (usually F2 or Del during startup). Check the hardware clock. A dead CMOS battery causes the BIOS time to reset every cold boot. Replace the battery — it's a CR2032 coin cell. I've fixed half a dozen machines that way.

Reset Chrome flags

If you've messed with Chrome flags (like chrome://flags/#enable-quic or experimental TLS settings), reset them. Go to chrome://flags, click Reset all to default, then restart Chrome. Experimental flags sometimes break certificate validation.

Check for dual-boot time issues

Running Windows and Linux on the same machine? Linux uses UTC for hardware clock by default; Windows uses local time. This causes a consistent time offset. Fix: on Linux, run timedatectl set-local-rtc 1 --adjust-system-clock. That forces Linux to treat the hardware clock as local time. Reboot and both OSes will agree on the time.

Prevention tip

Keep the CMOS battery replaced every 3-5 years. On Windows, run w32tm /resync once a week via Task Scheduler if your machine tends to drift. For laptops that go between different time zones, keep Set time zone automatically on. And if you're using a proxy or VPN, check that your time sync traffic isn't being blocked — some corporate firewalls block NTP (port 123).

Bottom line: ERR_CERT_DATE_INVALID is almost always a clock issue. Fix the clock, fix Chrome. Don't start reinstalling Chrome or messing with certificates — that's wasted time.