Windows 11 time keeps going wrong after you sync it

A Windows 11 laptop owner described a frustrating cycle in February 2025: Sync now corrected the clock, but the error returned. Both automatic settings were already enabled. The owner later reported a synchronization error while web browsing still worked. The thread does not establish a successful repair or prove that shutdown caused the fault. Microsoft Q&A discussion

It is tempting to press Sync now again and get back to work. First, open Date & time and record the clock and selected region while they are still wrong. Once corrected, the display no longer shows whether Windows had picked another region or whether the date itself had changed. That record gives you something to compare after the next restart. The steps below cover the Windows 11 system clock on a physical PC.

Capture the clock before correcting it

Record the date, time and selected time-zone name while they are wrong. Compare against a known-correct clock showing the same region. A phone's world-clock entry for another country is a poor reference for deciding whether your PC is keeping local time.

Observation	Next check	What it does not establish
The selected region is wrong	Choose the intended time zone and compare again	A battery fault
The region is correct, but the time is wrong	Read the synchronization result	Successful sync simply because websites load
The date resets after shutdown	Check the firmware date before Windows loads	Which component needs replacing

An offset of several hours makes the zone worth inspecting; the offset alone does not prove the cause. Likewise, a corrected clock does not demonstrate that its settings will survive the next startup.

Imagine two PCs that should display the same local time. On the first, selecting the intended region corrects the clock. Restart it and check that both the region and the time remain correct. On the second, the region was right from the start, but Sync now returns an error. Keep that message for support along with when it appeared. The next useful observation is different on each PC, even though both began with a wrong clock.

When Windows selects the wrong region

Open Settings → Time & language → Date & time. To choose a region yourself, turn off Set time zone automatically and select the appropriate entry. You can leave automatic clock setting enabled. For a region that observes daylight saving time, also check the daylight-saving setting. Microsoft's time settings instructions

A separate 2023 support question describes a more specific failure: manual selection produced the correct region, while switching automatic detection back on selected the wrong one again. Wrong time zone after restart

Windows uses location services for automatic time-zone selection. You can inspect them under Settings → Privacy & security → Location. Location estimates can use signals including nearby networks and IP addresses; an internet connection does not certify that the detected region is correct. Device-level controls also depend on administrator access. Microsoft's location service documentation

On a personal PC that stays in one place, selecting the correct zone manually gives you a specific change to test after restarting. Note whether that selection remains. If you later travel, revisit the region instead of assuming a manually chosen setting will follow you. There is no need to grant every app location access merely to investigate the system clock.

When Sync now fails or only helps temporarily

With the correct region selected, turn on Set time automatically and use Sync now. Read the outcome as well as the clock. Samsung's Windows 11/10 support procedure includes these checks. Record whether the attempt succeeds or an error appears. Samsung's date and time troubleshooting

If synchronization fails, keep the exact error text. Windows Time uses NTP over UDP port 123, so successful web browsing does not verify the time-service connection. This explains why the two results can differ; it does not identify a blocked port as the cause on your machine. Windows Time service reference

If you urgently need a correct clock on a personal PC, manual correction can be a temporary fallback: turn automatic time off and use the date-and-time Change control. Include the date, not just the hour. Keep a note that you made a manual correction. Otherwise, a support technician may see the now-correct display without knowing that automatic synchronization is still failing.

For a computer-clock or certificate warning in Firefox, correct the system time and retry the page. A bad date can affect certificate validation. If the clock is correct and the warning persists, the website's certificate may itself be invalid or expired. Moving the PC date until a site opens is not a repair for that certificate. Mozilla's time-related security error guidance

Once the immediate task is over, return to the failing behavior. Did automatic synchronization recover, or did you only enter a correct value? If the error appears again, keep both observations. They tell support more than a screenshot taken only after the clock has been fixed.

A work PC may follow a different time source

An Active Directory domain-joined computer normally follows the domain's time hierarchy. A company-issued PC is not necessarily configured that way, so ask IT which source it should use before replacing it with an internet server.

If IT requests diagnostic output and you have administrator access, open Command Prompt as administrator and run:

w32tm /query /source
w32tm /query /status

These queries display the current time source and Windows Time status without changing configuration. IBM also includes them in its Windows diagnostic procedure. Send the output, or the error if the query fails, along with when you ran it. If you lack permission, send the Date & time screen instead. A server name you do not recognize is not by itself evidence of a bad setting. IBM's synchronization diagnostics

Keep internal server details within your organization's support channel. A useful report might say that the region stayed correct but synchronization failed immediately after a restart. If colleagues independently report the same symptom, mention that too; there is no need to change their machines to manufacture a comparison.

A date that resets before Windows starts

A date that jumps into the past after power-off, especially alongside a startup request to set the clock, deserves a hardware investigation. Dell lists incorrect BIOS time and loss of settings after shutdown among desktop CMOS battery failure symptoms. Its replacement instructions are model-specific. Dell's desktop CMOS battery guidance

If you can enter BIOS or UEFI using the manufacturer's instructions, record the date before Windows starts. Do not change boot or security settings for this check. If you cannot access the screen, record the startup message and model number for support.

“The date was correct after signing in” is a different observation from “the firmware date was correct before Windows loaded.” Synchronization can correct the displayed date later, so a photograph taken after that correction may miss the original symptom. Report when you looked, not simply whether the time eventually became right.

Do not buy a generic coin-cell battery solely because a laptop loses time. Samsung describes models that retain time using the internal battery without a separate RTC battery. The machine's model determines what hardware exists and how it can be serviced. A wrong time-zone selection alone is not evidence that this hardware has failed.

Repeat the action that triggered the problem

After making a change, repeat the original trigger. If the clock changed after a restart, restart and compare. If it failed after being powered off overnight, check the next morning. A sleep-resume symptom should remain labeled as such rather than being reported as a shutdown failure.

Trigger: restart / power-on after shutdown / resume from sleep
PC date and time; reference date and time:
Selected time-zone name:
Automatic time and automatic time-zone settings:
Sync result and exact error:
Change made; immediate result; next recurrence:
Firmware date or startup message, if actually checked:

A stable manually selected region leaves you with a setting to retain. A persistent synchronization error leaves a message and source for support to investigate. A firmware date lost after power-off gives the manufacturer a different starting point. Leave unobserved fields blank or mark them unknown; a suspected battery or server fault should not be recorded as a confirmed result.