Fix Windows 11 Clock Showing the Wrong Time

A wrong Windows clock is not just cosmetic. It breaks HTTPS websites, throws certificate errors, and locks you out of apps that refuse to sign in, because a huge slice of internet security checks your system time. The good news: the cause is almost always one of four things, and the symptom tells you which.

This guide separates the two patterns: a clock that drifts while running, which is a software fix, and a clock that resets on every shutdown, which is usually hardware.

First, identify which problem you have

The exact behavior of the wrong clock points straight at the cause. Match yours:

Symptom	Likely cause	Where to go
Time is hours off but stable	Wrong time zone	Date and time settings
Time slowly drifts off	Sync not running or stale	Turn on auto time, Sync now
Sync button fails or does nothing	Windows Time service stopped	services.msc
Resets to an old date every boot	Dead CMOS battery	Replace the coin cell
Wrong only after dual-booting Linux	UTC vs local time clash	Set both OSes to agree

Sort which row you are in before you start changing settings, and you will not waste time on the wrong fix.

Key takeaways

• Turn on Set time automatically and Set time zone automatically, then sync.
• A wrong time zone makes the clock look wrong even when sync works.
• The Windows Time service must be running and set to automatic.
• A clock that resets to a past date on every boot points to a dead CMOS battery.
• Forcing a resync with w32tm /resync fixes a stuck time source.

Turn on automatic time and sync now

Most cases are just sync being off or stale.

1. Open Settings, then Time and language, then Date and time.
2. Turn on Set time automatically and Set time zone automatically.
3. Confirm the Time zone shown is correct.
4. Under Additional settings, click Sync now.

Why a wrong clock causes such big problems

It helps to understand why a few minutes of clock drift can lock you out of websites and apps, because it explains why fixing the time is worth the trouble. Modern internet security leans heavily on time. HTTPS certificates are only valid within a specific date range, and your browser checks every certificate against your system clock; if your clock is wrong, perfectly good certificates look expired or not-yet-valid, and the browser blocks the site as unsafe. Multi-factor codes and many authentication tokens are time-based, so a clock that is off by even a minute or two can make valid codes get rejected. Some software licenses and sign-in flows also refuse to proceed if the local time looks implausible. So a wrong clock is not a cosmetic glitch; it quietly breaks the trust checks that the secure web runs on. That is also why fixing the time often resolves a cluster of seemingly unrelated errors at once.

Make sure the Windows Time service is running

If sync fails, the underlying service may be stopped.

1. Press Windows + R, type services.msc, and press Enter.
2. Find Windows Time, right-click it, and choose Properties.
3. Set Startup type to Automatic and click Start.
4. Click OK and try Sync now again.

Force a resync and switch the time server

If the clock still drifts, force a fresh sync and consider a more reliable server.

1. Press Windows + X and choose Terminal (Admin).
2. Run w32tm /resync.
3. To change the server, open Control Panel, Date and Time, Internet Time, Change settings.
4. Set the server (for example to a public time server) and click Update now.

A stuck or unreachable time source is a common reason sync silently fails, and pointing Windows at a dependable server fixes the slow drift. Reliable public servers to try in the Internet Time settings include time.windows.com (the default), pool.ntp.org, and time.google.com. If one consistently fails to reach, switch to another.

A note for dual-boot users

If your clock is only wrong after booting into Windows from a Linux dual-boot, you are not seeing a sync failure at all. Windows assumes the hardware clock is set to local time, while Linux usually assumes it is UTC, so each one "corrects" the other and the time ends up off by your timezone offset. The clean fix is to make Windows use UTC too, or set Linux to local time. Our dual-boot Linux and Windows 11 guide covers exactly this clock mismatch and how to make the two agree.

Replace the CMOS battery if the clock resets on every boot

Here is the telltale hardware sign: if the clock jumps to a wrong, often old date every single time you fully power off and restart, the small coin-cell CMOS battery on the motherboard is dead. That battery (almost always a CR2032) keeps the real-time clock running while the PC is off, and after several years it gives out. On a desktop it is a cheap, swappable part costing a couple of dollars. On a laptop it is harder to reach and may warrant a service visit. After replacing it, go back into UEFI/BIOS, set the date and time, then re-enable automatic time and sync in Windows. A wrong clock can also break sign-in and certificate checks, the same way issues behind a Microsoft account you cannot sign in to sometimes manifest.

What to do right now

If your clock is wrong this minute, work down this list and stop when it is fixed:

• Open Settings, Time and language, Date and time and confirm the time zone is correct first.
• Turn on Set time automatically and Set time zone automatically, then click Sync now.
• If sync fails, open services.msc, set Windows Time to Automatic, and Start it.
• In an admin terminal, run w32tm /resync to force a fresh sync.
• If it still drifts, switch the time server under Control Panel, Date and Time, Internet Time.
• If the clock resets to an old date on every boot, replace the CMOS battery.

Frequently asked questions

Why does my clock reset every time I shut down?

That pattern points to a dead CMOS battery, the coin cell on your motherboard that powers the real-time clock while the PC is off. When it dies, the clock cannot keep time during shutdown and resets to a default past date on each boot. Replacing the battery fixes it permanently.

My time is several hours off but otherwise stable. Why?

A consistent multi-hour offset is almost always a wrong time zone rather than a sync failure. Open Date and time settings, set the correct time zone or turn on automatic time zone, and the clock corrects itself. Sync keeps it accurate to the second, but the time zone sets the hour.

Why does a wrong clock break websites?

Secure websites use certificates that are only valid within a date range, and your browser checks them against your system clock. If your clock is wrong, the browser thinks certificates are expired or not yet valid and blocks the site with a security warning. Fixing the time clears those errors.

How do I force Windows to sync the time immediately?

Open an elevated terminal and run w32tm /resync, or use the Sync now button under Settings, Time and language, Date and time, Additional settings. Both force Windows to contact the time server right away rather than waiting for its scheduled sync.