How to Fix a Computer Clock That Shows the Wrong Time

Published 2026-10-16 · LuxuriousComputers Repair

A computer clock that shows the wrong time is more than a minor annoyance. Incorrect system time causes SSL certificate errors in your browser (making websites appear unsafe), breaks email timestamps, prevents software activation and license checks from working, causes files to save with wrong dates, and can prevent Windows Update from downloading. Two-factor authentication codes that are time-based (TOTP) will also fail if your clock is off by more than about 30 seconds.

Check your timezone setting first

The most common reason for a clock showing the wrong time is simply a wrong timezone setting. This happens after Windows updates, when traveling with a laptop, or when Windows misdetects your location.

  1. Right-click the clock in the taskbar and select Adjust date and time
  2. Check the Time zone dropdown. Make sure it matches your actual location. If you are in Eastern Time, it should say (UTC-05:00) Eastern Time (US and Canada)
  3. If Set time zone automatically is turned on and it is choosing the wrong zone, turn it off and set the correct zone manually. Automatic timezone detection relies on your IP address geolocation, which is not always accurate — especially on VPNs or corporate networks

If the timezone was wrong and you fix it, the time should immediately jump to the correct value. If the time is still wrong after setting the correct timezone, the problem is deeper.

Force a time sync with the internet

Windows synchronizes its clock with an internet time server periodically, but this sync can fail silently for weeks without you noticing. Forcing a manual sync usually fixes a clock that has drifted.

  1. Open Settings, Time and Language, Date and Time
  2. Make sure Set time automatically is turned on
  3. Click Sync now under Additional settings. Windows contacts the time server and adjusts the clock
  4. If the sync fails, try again — the default Microsoft time server (time.windows.com) is sometimes slow to respond. If it keeps failing, you can change the time server

Change the time server

If time.windows.com is not responding reliably, switching to a different NTP server can help.

  1. Open Control Panel, Clock and Region, Date and Time
  2. Click the Internet Time tab, then Change settings
  3. In the Server field, replace the current server with one of these alternatives: pool.ntp.org (a pool of thousands of volunteer time servers worldwide), time.google.com (Google's public NTP), or time.cloudflare.com (Cloudflare's NTP)
  4. Click Update Now, then OK

Fix the Windows Time service

The Windows Time service (W32Time) handles automatic time synchronization. If this service is stopped or misconfigured, your clock will drift and never correct itself.

  1. Open Command Prompt as administrator
  2. Check the service status: w32tm /query /status. If you get an error saying the service has not been started, that is your problem
  3. Start and configure the service with these commands run one at a time:
  • net stop w32time (stop the service if it is running in a bad state)
  • w32tm /unregister (remove the current configuration)
  • w32tm /register (re-register with default settings)
  • net start w32time (start the service)
  • w32tm /resync /force (force an immediate sync)

After running these commands, check the clock. It should now show the correct time. If the service keeps stopping on its own, check the Windows Event Viewer (Event Viewer, Windows Logs, System) for W32Time errors that indicate what is preventing it from running.

CMOS battery — the clock resets every time you shut down

If your computer shows the correct time while it is running but resets to a wrong time (often January 1 of some past year, or exactly midnight) every time you shut down and restart, the CMOS battery is dead. The CMOS battery is a small coin-cell battery (usually CR2032) on the motherboard that keeps the system clock running when the computer is off. It also maintains BIOS settings like boot order and hardware configuration.

Signs of a dead CMOS battery

  • The clock resets to a default date and time after every shutdown or power loss
  • BIOS settings reset to defaults after shutdown (you may see messages like "CMOS checksum error" or "Press F1 to enter setup" during boot)
  • The computer takes longer to boot because it has to re-detect hardware each time
  • The time drifts significantly faster than normal — losing minutes per hour rather than seconds per day

Replacing the CMOS battery (desktop)

  1. Shut down the computer and unplug it from power
  2. Open the side panel
  3. Locate the CMOS battery on the motherboard — it is a silver coin-cell battery about the size of a nickel, usually in a small clip holder. On most motherboards it is near the bottom half of the board, clearly visible
  4. Note which side faces up (the positive side with text and markings). Gently push the retaining clip to the side and the battery pops out
  5. Insert a new CR2032 battery (available at any pharmacy, grocery store, or electronics store for a few dollars) with the positive side facing the same direction as the old one
  6. Close the case, plug in, and power on. Enter BIOS setup (usually Del or F2 during boot) and set the correct date and time. Also re-apply any BIOS settings that were reset to defaults (boot order, XMP memory profiles, fan curves)

A CR2032 battery lasts 3 to 5 years in most systems. If your computer is that age or older and you have never replaced it, this is likely your issue.

Laptop CMOS battery

Laptop CMOS batteries are smaller, often soldered or connected via a small wire harness, and located underneath the keyboard or behind a service panel. Replacing one requires partial disassembly of the laptop. Search your laptop model number plus "CMOS battery replacement" for a specific guide — the process varies significantly between models.

Dual-boot systems — Linux and Windows time conflict

If you dual-boot Windows and Linux, the clock may jump by several hours every time you switch between the two operating systems. This happens because Windows and Linux interpret the hardware clock differently by default. Windows treats the hardware clock as local time (your timezone). Linux treats it as UTC (Coordinated Universal Time). When Linux sets the hardware clock to UTC and Windows reads it as local time, the displayed time is off by whatever your UTC offset is.

The fix is to make both systems agree. The easiest method is to tell Linux to use local time for the hardware clock, matching Windows:

  • In Linux, run: timedatectl set-local-rtc 1

Alternatively, you can tell Windows to use UTC, but this is less commonly done and can cause issues with some Windows applications.

Clock drift — the time slowly gets more wrong

If your clock gradually drifts — gaining or losing a few seconds per day, eventually adding up to minutes or hours over weeks — the problem is that automatic time sync is not running. Check:

  • Set time automatically is turned on in Settings, Time and Language, Date and Time
  • The Windows Time service is running (open Services, find Windows Time, ensure Status is Running and Startup type is Automatic)
  • Your firewall is not blocking NTP traffic. NTP uses UDP port 123. Some corporate firewalls or overly aggressive security software blocks this. If you are on a company network, the network admin may have a local NTP server you should use instead of an internet server
  • Your internet connection is working when the sync attempts happen. If the computer is offline at the scheduled sync time, the sync fails and the clock drifts until the next successful sync

Clock problems after a Windows update

Windows updates sometimes reset the timezone to Pacific Time (Microsoft's default) or disable the time sync service. If your clock went wrong immediately after an update:

  1. Check and correct the timezone (step 1 above)
  2. Force a time sync (step 2 above)
  3. Verify the Windows Time service is still running and set to Automatic startup

This is a known recurring issue. It does not indicate a hardware problem — it is a configuration reset caused by the update process.

Clock repair help in Marion

If your computer clock keeps resetting or showing the wrong time and the steps above have not fixed it, LuxuriousComputers Repair in Marion can diagnose whether the issue is a dead CMOS battery, a software configuration problem, or a motherboard issue, and fix it on-site.

← Back to Blog