What to Do When Your Computer’s Date and Time Keep Changing
I’ll help you distinguish a wrong time zone from a synchronization failure or a dying motherboard battery, so you can fix the underlying problem instead of repeatedly correcting the clock by hand.
A computer that keeps changing its date or time can make email look out of order, break websites, confuse file timestamps, and interfere with software updates. The tempting fix is to correct the clock manually, but that often treats the symptom for only a few hours or until the next restart.
The useful first question is when the change happens. If the clock is consistently off by one or more hours, the time zone or daylight-saving setting is the likely cause. If it becomes wrong after every shutdown, a weak motherboard battery is more suspicious. If it drifts gradually while the computer is running, automatic time synchronization may be disabled or unable to reach its time server.
Start by identifying the pattern
Write down the correct time, shut down or restart the computer, and check the clock again. Notice whether the date changes as well as the time, and whether the error is a neat number of hours or an irregular amount.
A consistent offset usually points to a time-zone setting. For example, a computer set to a neighboring time zone may be exactly one, two, or several hours wrong. A clock that loses minutes over a day suggests synchronization or hardware timing trouble. A clock that resets to an old date after the computer has been unplugged is a strong clue that the real-time clock battery is no longer holding its setting.
Also check whether the problem affects only the clock display or whether the operating system itself reports a different date and time. Some computers show a correct local time while a firmware menu or another operating system displays a different one. That can happen when two systems interpret the motherboard clock differently, rather than because the clock is physically failing.
Check the time zone before changing anything else
Open your computer’s date and time settings and confirm the selected time zone matches your actual location. If you travel regularly, avoid assuming that the setting will always change automatically. Some computers can detect location, but that feature may depend on permissions, network access, or a setting that has been turned off.
Check whether the operating system is set to adjust the clock for daylight-saving changes where applicable. Time-zone rules differ by region and can change over time, so a location that looks close on a map isn't necessarily the correct setting. Choose the named city or region that belongs to your local time zone rather than manually adding or subtracting hours.
Manual adjustment is appropriate as a temporary workaround, but it is usually the wrong permanent solution. If the time zone is incorrect, changing the clock by hand leaves the computer with the wrong underlying location. It may correct the visible time today and then be changed again by automatic synchronization tomorrow.
Turn on automatic date, time, and synchronization
Once the time zone is correct, enable the operating system’s automatic date and time option. The exact wording differs between Windows, macOS, and Linux, but the relevant settings are normally grouped under Date & Time or System Settings.
Automatic synchronization lets the computer compare its clock with a network time server. This is generally the easiest choice for a home computer because it corrects small amounts of drift without requiring you to monitor the clock. If the computer has been offline, it may not update until it reconnects to the internet.
After enabling the setting, use the available Sync now, Set automatically, or equivalent control if one is provided. Give the computer a moment to contact the time server, then confirm that the displayed time and date are correct. If synchronization fails, look for an error message rather than repeatedly pressing the button. The message may indicate that the network is unavailable, the service is disabled, or another setting is preventing the update.
A school, business, or managed computer may use its organization’s time server instead of a public one. In that situation, changing advanced synchronization settings can create a different problem. If the computer is managed by someone else, the sensible approach is to reconnect to the organization’s network or ask its support team which time source the computer should use.
Check the network and time service
Time synchronization needs more than an internet connection icon. A captive portal at a hotel, airport, or café may require you to sign in before the computer can reach external services. A firewall, VPN, security program, router setting, or organization policy can also block the time service while ordinary web browsing continues to work.
Try disconnecting and reconnecting to the network, completing any sign-in page, and temporarily testing without a VPN if your network policy allows it. If the clock corrects itself on one network but not another, the network configuration is more likely to be responsible than the computer’s hardware.
On Windows, the Windows Time service must be running for normal automatic synchronization. On Linux, a time-synchronization service such as systemd-timesyncd, Chrony, or another distribution-selected service performs this job. macOS manages the relevant service through its Date & Time settings. You generally don't need to change service settings manually unless the ordinary control can't restore synchronization.
Don't run several competing time-synchronization tools at once. A manually installed utility, a virtualization program, and the operating system can disagree about which one controls the clock. If you recently installed a system-management tool or changed advanced settings, remove the duplicate source or return to the operating system’s standard time service.
Consider the motherboard’s real-time clock battery
If the time becomes wrong mainly after the computer has been powered off, especially when it has been unplugged, the small battery on the motherboard may be weak. This battery powers the real-time clock when the computer has no normal power. It is separate from the battery that powers a laptop while you are using it.
A failing battery can cause more than an incorrect clock. The computer may forget firmware settings, show a message about changed configuration, or reset certain startup options. The date may jump back to an old year, which can then cause websites, encrypted connections, and software installers to report certificate or expiration errors.
Replacing the battery is often a reasonable repair for a desktop computer, but the practical difficulty varies. A desktop may use a readily accessible coin-cell battery, while a laptop can have a less accessible battery, a connector, or a battery wrapped in an insulating cover. Opening a device can also affect warranty coverage or introduce a risk of static or physical damage.
If the computer is still under warranty, check the manufacturer’s repair options first. For a desktop, a repair shop can usually diagnose and replace the battery quickly. For a laptop, compare the repair cost with the machine’s age and value before buying parts. Replacing a battery may be worthwhile if the computer is otherwise reliable; it may not make sense if several other repairs are already needed.
A new battery won't solve a time-zone error or a network synchronization problem. It is most useful when the clock loses its settings during power loss or the firmware reports that its configuration has been reset.
Check firmware settings and dual-boot conflicts
Enter the computer’s firmware or BIOS/UEFI setup only if the normal operating-system checks don't explain the behavior. The firmware clock should show a sensible date and time. If it is already wrong before the operating system loads, the issue is likely related to the motherboard battery or firmware configuration rather than an operating-system display setting.
Be careful when changing firmware options. You usually need to adjust only the date and time, not unrelated startup, security, or storage settings. If you are unsure which screen controls the clock, leave the other options alone.
A computer with Windows and Linux installed can show a different time when you switch between systems even though the hardware clock is working. The systems may interpret the motherboard’s stored time as either local time or Coordinated Universal Time (UTC). The result is often an offset of a whole number of hours, with each operating system correcting the clock for its own interpretation.
This is a configuration mismatch, not necessarily a dead battery. Set both systems to use the same convention, preferably the one recommended by your Linux distribution and dual-boot setup. If you aren't comfortable changing the configuration, search the documentation for your specific operating systems or ask a technician; random changes can make the clock alternate between two incorrect values.
When manual correction is the better choice
Automatic network synchronization is usually best for an everyday computer, but it isn't always appropriate. An offline computer, a specialized workstation, or a device on a restricted network may need manual timekeeping. In that case, you should check the clock periodically and understand that it will drift over time.
Manual correction can also be useful for diagnosing the problem. If you set the correct time and it remains accurate while the computer is running but becomes wrong after shutdown, suspect the real-time clock battery. If it changes soon after you connect to a particular network, investigate synchronization or network policy. Treat each manual correction as a test result, not as the complete repair.
Don't set the clock far into the past or future merely to make a program work. Large date changes can affect file timestamps, browser security checks, scheduled tasks, backups, and software licensing. Once the underlying problem is fixed, restore the correct date and time and restart affected programs.
A sensible order for fixing the problem
Begin with the time zone, because it is easy to check and can create a perfectly consistent error. Then enable automatic time and attempt one synchronization while connected to a reliable network. If the clock still drifts, look for VPN, firewall, service, or organization-related causes.
If the clock resets after shutdown, inspect the firmware clock and consider the motherboard battery. If two operating systems disagree, investigate their UTC-versus-local-time configuration. These possibilities can overlap, so change one relevant setting at a time and observe what happens after a restart.
Once the clock stays correct through a restart, a period of normal use, and a short loss of power, the problem is probably resolved. Keep automatic synchronization enabled unless your computer has a specific reason to remain offline, and avoid relying on repeated manual corrections when the pattern points to a battery, network, or configuration fault.