Many Windows users notice the system clock shifting by minutes or hours without any manual change. This behavior can interrupt meetings, backups, logs, and scheduled tasks, making it feel like the computer time is unreliable.
When the windows clock keeps changing, it is usually due to time sync settings, conflicting services, or hardware issues. Understanding the common triggers helps you fix the problem quickly and keep accurate time on your device.
| Symptom | Possible Cause | Quick Check | Recommended Action |
|---|---|---|---|
| Clock jumps forward or backward by hours | Time server mismatch or time zone change | Check current time zone and last sync result | Verify time zone and force resync with reliable server |
| Minutes drift slowly each day | Hardware clock battery or BIOS clock issue | Check if offset grows steadily in Event Viewer | Replace CMOS battery or update BIOS/ firmware |
| Time resets after restart | Windows Time service disabled or startup delay | Review service status and boot logs | Enable Windows Time service and set automatic delayed start |
| Time changes after resume from sleep | Sleep interrupt affecting clock source | Compare time before sleep and after wake | Update drivers and disable aggressive power saving |
Sync Configuration and Time Server Settings
Windows uses built-in time synchronization to match the system clock with an internet time server. Incorrect settings here are a common reason the windows clock keeps changing unexpectedly.
By default, your PC contacts time.windows.com, but network policies or manual changes can switch to a different server. If the chosen server responds slowly or is temporarily offline, Windows may apply a large correction that makes the clock jump.
Checking Your Current Time Server
Open a command prompt as administrator and run w32tm /query /status to see which time server is in use and how recent the last sync was. Note the Offset field, as large offsets often precede visible clock changes.
You can switch to a more stable local or regional server in Settings, or use the same command with /setsntp to define preferred servers. After changing the server list, run w32tm /resync to force an immediate update and confirm the new source is working.
Time Service and Scheduled Task Behavior
The Windows Time service controls manual and automatic adjustments. If it is stopped, delayed, or misconfigured, the clock may drift or suddenly jump when another process attempts a correction.
Certain scheduled tasks or Group Policy objects can trigger a time reset on specific events. When these tasks run with higher privileges, they may overwrite your current settings and cause noticeable changes in the displayed time.
Managing the Windows Time Service
Open services.msc, locate Windows Time, and confirm its startup type is set to Automatic. If the service is stopped, right-click it and choose Start, then monitor the status to ensure it remains running after reboots.
Check Task Scheduler for tasks referencing time sync or daylight saving adjustments. Disable or edit any nonstandard tasks that seem to modify system time, and review logs to identify which process initiated the last correction. Event Viewer under System and Application logs with the Time-Service source is helpful here.
Hardware and BIOS Considerations
The hardware clock, maintained by a small battery on the motherboard, preserves time when the PC is off. A weak CMOS battery is a frequent reason the windows clock keeps changing after shutdowns or power interruptions.
In some cases, the BIOS clock is used as the primary reference during early boot. If the BIOS time is incorrect or not set to UTC, Windows may apply an offset that leads to inconsistent time once the operating system loads.
Inspecting Clock Behavior Across Boot
Compare the time shown in BIOS setup on startup with the Windows clock after login. A significant difference points to hardware issues, while alignment at boot and drift only later suggests software sync problems.
Replace the CMOS battery if the clock loses time even when the PC is normally powered. After replacing the battery, enter the BIOS, verify the date and time, save settings, and then let Windows handle synchronization for consistency across sessions.
Network, Domain, and Virtual Machine Factors
In corporate or school environments, domain controllers and Group Policy can override local time settings. Joining a domain often forces the windows clock keeps changing to follow the network’s authoritative time source.
Virtual machines may experience clock drift because their virtual hardware does not always reflect real time accurately. Hypervisor time synchronization features can cause abrupt adjustments when the VM resumes from pause or migration.
Handling Domain and Virtual Machine Scenarios
On a domain PC, consult your IT administrator before changing time settings, as policies will likely reapply. For virtual machines, configure time sync integration tools appropriately and avoid aggressive periodic corrections that lead to visible jumps.
Stable Time Setup and Maintenance
Consistent time on your PC supports accurate logging, secure authentication, and reliable scheduled operations across applications and services.
- Confirm the correct time zone and a reliable time server in Date & Time settings
- Ensure the Windows Time service is enabled and set to start automatically
- Check Event Viewer and Task Scheduler for processes that modify time unexpectedly
- Replace the CMOS battery if the hardware clock loses time when powered off
- Document and test time-related behavior after domain join, BIOS updates, or migration to virtual machines
FAQ
Reader questions
Why does my clock jump by several hours after waking from sleep?
This usually happens when the system wakes with a different network time offset, especially if hibernation file time data conflicts with the real-time clock. Disable hibernation or configure Windows Time for gradual corrections to reduce sudden jumps.
Can antivirus or third-party apps interfere with time sync?
Yes, some security software or tuning utilities may hook time functions, block sync attempts, or adjust the clock for forensic reasons. Temporarily disable such apps and observe whether the windows clock keeps changing to confirm or rule out interference.
What should I do if the time drifts slowly even with sync enabled?
Slow drift often points to a failing CMOS battery or inconsistent time source selection. Replace the battery, check BIOS settings, ensure only one reliable server is configured, and monitor drift after a clean resync.
Will changing time zones affect scheduled tasks and logs?
Switching time zones shifts displayed times in logs and task triggers based on whether the system uses UTC or local time. Verify how scheduled tasks store time values and adjust triggers or logging formats to avoid confusion after a zone change.