The system time becomes completely wrong whenever the PC wakes up from sleep

Weber Felix 0 Reputation points
2026-11-11T09:32:35.28+00:00

Hi all,

The system time becomes completely wrong whenever my PC wakes up from sleep, happens to all client machines. Is this usually a sign of a failing CMOS battery, an issue with Windows Time (w32time) failing to resync after wake-up, or a buggy motherboard ACPI/chipset driver? Thanks!

Windows for business | Windows Client for IT Pros | User experience | Other
0 comments No comments

2 answers

Sort by: Newest
  1. Ronald Sabiiti 1,670 Reputation points Independent Advisor
    2026-11-11T10:27:43.83+00:00

    Hi Felix,

    Since the incorrect system time occurs across multiple client machines after waking from sleep, I recommend checking Windows Time synchronization and any shared domain time-source configuration before suspecting CMOS battery failure.

    Please try the following;

    1. Run w32tm /query /status and w32tm /query /source to check the current time source and synchronization status.
    2. Run w32tm /resync /rediscover to trigger synchronization.
    3. Check Event Viewer → System for Windows Time Service errors around the time the machines resume.
    4. If the issue persists, check BIOS/UEFI time and update the chipset, power-management, and BIOS firmware where applicable.

    Microsoft references:

    Hope this helps!

    Ronald.

    Was this answer helpful?

    0 comments No comments

  2. AI answer

    2026-11-11T09:32:51.6166667+00:00

    A failing CMOS battery is a likely cause when the clock is wrong after sleep or shutdown, especially if this happens across affected machines and the time appears to drift back to hardware clock values. One documented symptom is that Windows time can revert to the CMOS clock setting, and Microsoft Q&A guidance also notes that if a computer loses time after shutdown, that indicates a faulty CMOS battery.

    A Windows Time resync problem is also plausible. One accepted troubleshooting path is to verify that the SynchronizeTime scheduled task is enabled in Task Scheduler under Task Scheduler Library > Microsoft > Windows > Time Synchronization, and that the Windows Time service is running in services.msc. If needed, change the Internet time server and test synchronization again.

    There is also evidence that sleep and hibernation transitions can interact with system time. Microsoft documents cases where, after resume, the system time changes and is synchronized with the hardware clock. That means an incorrect hardware clock can surface immediately after wake.

    Based on the available information, the most supported interpretation is:

    1. Check the hardware clock / CMOS battery first if the time is grossly wrong after wake or after power-off.
    2. Verify Windows time sync components next:
      • Task Scheduler > Microsoft > Windows > Time Synchronization > ensure SynchronizeTime is enabled.
      • Services > ensure Windows Time is started or restarted.
      • In Control Panel > Date and Time > Internet Time, confirm the correct time zone and test another time server.
    3. If the issue persists across multiple client machines, that points less to a single bad battery and more to a common platform, firmware, or configuration factor. The provided context does not confirm ACPI/chipset driver faults as the cause, but it does show that wake behavior depends on firmware, RTC, and power-state handling.

    AI-generated content may be incorrect. Read our transparency notes for more information.

    Was this answer helpful?

Your answer

Answers can be marked as 'Accepted' by the question author and 'Recommended' by moderators, which helps users know the answer solved the author's problem.