Computer Clock Wrong or Not Syncing: Windows Time Sync and CMOS Battery Fixes

The clock in the taskbar running hours behind or minutes ahead, or resetting to some date years ago every time you power on, is more than an annoyance. A wrong clock sets off a chain of odd symptoms, including certificate warnings that block websites, browser sessions that will not stay signed in, file timestamps that make no sense, and software activation that refuses to run. Fixing the time often clears several of those at once.

1. Check whether the time zone or format is simply wrong

This is the most common layer and the easiest to fix.

  1. Right-click the clock in the taskbar > Adjust date and time.
  2. Confirm the time zone is the one shown as "(UTC+08:00) Beijing, Chongqing, Hong Kong, Urumqi". Picking the wrong country during setup puts you out by whole hours.
  3. You can turn off "Set time zone automatically" and choose it yourself, or leave it on and let Windows decide.
  4. Set the regional format to Chinese (Simplified, China) so that dates display in the order you expect.

2. Turn on time sync and force it

Windows is meant to check in with Microsoft's time server on its own, and that occasionally breaks.

  1. Go to Control Panel > Date and Time > the Internet Time tab > Change settings.
  2. Tick "Synchronize with an Internet time server" and enter time.windows.com. Servers that work better inside China include ntp.aliyun.com and cn.pool.ntp.org.
  3. Choose Update now. On success it reports that the clock was synchronized successfully.
  4. A failure usually means no network, or a firewall blocking UDP port 123. Try another server or check the network and repeat.

To force a sync from the command line, run this in an admin terminal.

w32tm /resync

If it reports that the service is not running, start the Windows Time service with net start w32time first, then run the command above.

3. The Windows Time service has been disabled

Some tuning utilities and trimmed-down Windows builds switch the time service off.

  1. Press Win+R, type services.msc and press Enter.
  2. Find Windows Time (w32time), set its startup type to Automatic (Delayed Start), and choose Start.
  3. Confirm, then go back to section 2 and sync again.

4. The clock resets on every boot, which means a flat CMOS battery

If the date falls back to something like 1 January 2009 after you power off, and your correction does not stick, the motherboard CMOS battery is almost certainly flat. It is a coin cell, usually a CR2032.

  • Typical signs. The clock loses time each day or resets outright, BIOS settings go missing as well, and some machines print "CMOS checksum error" and ask you to press F1.
  • How to fix it. Shut down, unplug the power lead, open the case or the back panel, find the coin cell on the motherboard and fit a new CR2032 of the same type. It costs very little. A desktop is a straightforward DIY job, while a laptop is worth checking against a guide for your model or taking to a shop.
  • One detail that misleads people. While you are online, Windows quietly corrects the clock from the network, which hides the battery problem. So a machine that is fine while plugged in but wrong after a night powered off is showing the classic battery symptom.

Discharging the motherboard to reset BIOS is a different procedure, described in Windows Won't Boot, Blue Screen, or Black Screen.

5. Dual boot with Linux or macOS fighting over the clock

On a dual-boot machine the pattern is familiar. Windows shows the right time, you boot into Linux, and back in Windows it is 8 hours out. The two systems read the hardware clock, the RTC, differently, one treating it as local time and the other as UTC.

The usual fix is to tell Windows to use UTC as well. Run this in an admin terminal and restart, after which both sides agree, with no change needed on the Linux or macOS side.

reg add "HKLM\System\CurrentControlSet\Control\TimeZoneInformation" /v RealTimeIsUniversal /t REG_DWORD /d 1

6. What a wrong clock breaks

This is why the time is worth fixing before anything else.

  • Certificate errors. With the clock far enough out, HTTPS validity checks fail and the browser refuses the page with "Your connection is not private". Syncing the time often fixes it immediately.
  • Activation failures. Licence checks that depend on the clock fail with errors like 0x80072F8F. Activation is covered in more depth in Windows Activation Error 0xC004F211.
  • Sessions and verification codes. Many sites validate tokens against a time window, so a wrong clock signs you out constantly and invalidates codes.
  • File and backup timestamps. File History and the de-duplication logic in sync clients both rely on them.

7. Order to work through

Check the time zone, sync once by hand, confirm the time service is set to automatic, replace the CMOS battery if a night powered off still throws it out, and set UTC for a dual boot.

Common questions

The clock loses a few minutes on every boot but never resets to zero. Is that the battery?

Not necessarily. Do a manual sync and check that Windows Time is set to Automatic first. Only a fallback to a factory date after power loss, together with BIOS settings disappearing, points at the CMOS battery.

Sync fails with an error about synchronizing with the time server. Why?

Usually the network or the port. Check that the firewall allows UDP 123, try ntp.aliyun.com, and bear in mind that a corporate network may block it by policy.

Does the UTC registry change affect Windows Update?

No. The value only changes how Windows interprets the hardware clock, and it does not affect updates or activation.

I replaced the battery and the time is still wrong. Then what?

Check that the battery is seated properly in its holder and that it is not in backwards. In rare cases the clock circuit on the motherboard itself has failed, which needs repair.