How to Fix a Computer That Shows the Wrong Time
Published 2026-10-16 · Marion Remote Fix
Your computer clock is wrong. Maybe it is off by an hour, off by several hours, or showing a date from years ago. An incorrect system clock affects more than just knowing what time it is — it can cause website security certificate errors in your browser, break two-factor authentication codes, make emails appear out of sequence, disrupt file synchronization with cloud services, and cause scheduled tasks to run at the wrong time. Most causes of incorrect system time are straightforward to fix once you identify which one applies to your situation.
Quick fixes to try first
Force a time sync
- Windows: Right-click the clock in the taskbar and select Adjust Date and Time. Make sure Set Time Automatically is turned on. Click Sync Now. The computer contacts a time server and corrects the time immediately
- Mac: Open System Settings (or System Preferences), General, Date and Time. Ensure Set Date and Time Automatically is checked. Click the time server field and press Enter to force a sync
- If the sync succeeds and the time corrects, the problem was a missed automatic sync. If it fails or the time drifts back quickly, there is an underlying cause to address
Check the time zone
- If the time is wrong by exactly one, two, or more whole hours, the time zone setting is likely incorrect
- Windows: Settings, Time and Language, Date and Time. Check the Time Zone dropdown. Also check whether Set Time Zone Automatically is giving you the correct zone — if you are using a VPN, automatic zone detection may pick the VPN server location instead of your actual location
- Mac: System Settings, General, Date and Time, Time Zone. Verify the city or region matches your actual location
- If the time is exactly one hour off, daylight saving time adjustment may be incorrect. Ensure the Adjust for Daylight Saving Time Automatically option is enabled
Common causes of incorrect time
Automatic time sync is disabled
- If Set Time Automatically is turned off, the computer relies entirely on its internal hardware clock, which drifts naturally over time. Without periodic correction from a time server, the clock will gradually become inaccurate
- This setting can be turned off by software installations, system policy changes, or accidentally during settings changes. Turn it back on and sync immediately
CMOS battery is dying
- Desktop and laptop computers have a small coin-cell battery on the motherboard that powers the hardware clock when the computer is off. When this battery dies, the clock resets or drifts significantly each time the computer is shut down
- Symptoms: the time is correct while the computer is running (after syncing) but wrong each time you start up. The date may reset to a default like January 2000 or the year the motherboard was manufactured
- Additional symptoms: BIOS settings reset to defaults after each shutdown, or you see a CMOS battery error during startup
- Fix: replace the CMOS battery. On desktop computers, this is a simple CR2032 coin cell visible on the motherboard. On laptops, accessibility varies by model
Wrong time zone after OS update or reinstall
- Major Windows updates and clean installations sometimes reset the time zone to a default that does not match your location. If the time changed after an update, check the time zone setting first
- Windows may also detect your location incorrectly through IP geolocation, especially if you have moved recently or are using a VPN
Dual boot time conflict
- Computers that dual-boot Windows and Linux encounter a time conflict because the two operating systems handle the hardware clock differently by default
- Windows stores local time in the hardware clock. Linux stores UTC (Coordinated Universal Time). When you boot between them, each OS interprets the hardware clock differently, causing the displayed time to shift by your time zone offset
- Fix option 1: Tell Linux to use local time: run timedatectl set-local-rtc 1 in a Linux terminal
- Fix option 2: Tell Windows to use UTC: add a registry key named RealTimeIsUniversal (DWORD value 1) under HKEY_LOCAL_MACHINE, SYSTEM, CurrentControlSet, Control, TimeZoneInformation
Time service not running
- Windows uses the Windows Time Service (w32time) to synchronize the clock. If this service is stopped or disabled, automatic sync does not occur
- Open the Services application (type services.msc in the Start menu), find Windows Time, and verify it is running with the startup type set to Automatic
- If the service is stopped, start it manually. If it will not start, the service registration may be corrupted — open an elevated Command Prompt and run: net stop w32time then w32tm /unregister then w32tm /register then net start w32time then w32tm /resync
Firewall blocking time sync
- Time synchronization uses NTP (Network Time Protocol) over UDP port 123. Some firewalls, security software, or network configurations block this port
- If time sync consistently fails (clicking Sync Now produces an error), check whether your firewall or security software has a rule blocking NTP traffic
- On corporate networks, time sync may be managed by a domain controller rather than public time servers. If your work computer clock is wrong, contact your IT department rather than changing time settings yourself
VPN interference
- Some VPN connections interfere with automatic time zone detection. The computer may set the time zone based on the VPN server location rather than your physical location, making the clock appear wrong by several hours
- Fix: Set the time zone manually rather than automatically when using a VPN. The actual time sync (NTP) is usually unaffected — only the automatic zone detection gets confused
Setting the time manually
If automatic sync is not working and you need the correct time immediately:
- Windows: Settings, Time and Language, Date and Time. Turn off Set Time Automatically. Click Change under Set the Date and Time Manually. Set the correct date and time. Then turn Set Time Automatically back on so it syncs going forward
- Mac: System Settings, General, Date and Time. Uncheck the automatic option, set the time manually, then re-enable automatic
- Manual time setting is a temporary fix. If the underlying cause (dead CMOS battery, disabled time service, blocked NTP) is not addressed, the time will drift again
When incorrect time causes other problems
- Browser security warnings: HTTPS websites use time-sensitive security certificates. If your computer clock is significantly wrong (off by days, months, or years), your browser will flag every secure website with a certificate error because the certificates appear expired or not yet valid
- Two-factor authentication failures: Time-based one-time passwords (TOTP, used by apps like Google Authenticator and Microsoft Authenticator) are synchronized to the current time. If your computer clock is off by more than 30 to 60 seconds, the generated codes will not match what the server expects
- Email timestamp issues: Sent emails carry the timestamp from your computer. A wrong clock means your emails appear to arrive at incorrect times in the recipient inbox, potentially sorting out of order
- File sync conflicts: Cloud storage services (OneDrive, Dropbox, Google Drive) use file timestamps to detect changes. An incorrect clock can cause sync conflicts where the service thinks files have been modified when they have not, or misses actual changes
Need help fixing your clock?
If your computer clock keeps showing the wrong time despite trying these fixes, there may be a deeper software configuration issue, a failing CMOS battery that is hard to access, or a service conflict that needs professional diagnosis. Marion Remote Fix can remotely examine your time settings, sync configuration, and service status to identify and fix the root cause.