Windows 11 Clock Wrong? Check Time Zone and Synchronization Safely
If the Windows 11 clock is wrong, first check the date and your local time zone, enable automatic time, and try Sync now. A consistent difference of whole hours suggests a time-zone issue; a clock that gradually drifts or cannot synchronize needs a different investigation. Do not change registry values or replace a battery simply because one synchronization attempt fails.
Identify the pattern before changing settings
Compare the computer with a trusted clock, such as a phone configured to obtain its time automatically. Check the year, month and day as well as the minutes. Write down when the error appears: after travel, after restarting, after switching operating systems, or after the computer has been disconnected from power.
| Pattern | Check first |
|---|---|
| Consistent difference of one or more hours | Local time zone and daylight-saving settings |
| Clock drifts or Sync now fails | Network connection and time-service status |
| Date resets after loss of power | Whether the firmware clock also loses its date |
| Only a managed work computer is affected | Your organization’s IT guidance |
These are starting points, not diagnoses. A correct-looking clock does not prove that every time-related setting is correct, and a failed synchronization does not prove that the hardware is faulty.
1. Check the local time zone
Open Start → Settings → Time & language → Date & time. Choose the time zone that matches where you are using the computer. Do not select Seoul unless that is the appropriate zone for your location. Where daylight saving applies, check the relevant setting too.
Automatic time and automatic time-zone selection are separate controls. If automatic time-zone selection is unavailable, you can select the correct zone manually. A VPN’s exit location is not a reliable instruction for choosing your local zone. After changing the zone, check the clock again before trying more disruptive steps.
2. Request synchronization and read the result
Enable automatic time and use Sync now where it is available on the Date & time page. Look for a successful synchronization indication rather than pressing the button repeatedly. If the displayed time is corrected, restart normally and check whether it stays correct.
If synchronization fails, first make sure the connection is usable. A public Wi-Fi network may require a sign-in page before it provides normal access. Opening a website is a useful first check, although it does not prove that every network protocol is allowed. Do not disable the firewall as a blanket troubleshooting step.
For a personal computer, compare the behavior with and without your optional VPN connection if doing so is permitted. For a company or school computer, follow the network administrator’s instructions; do not replace the organization’s time source with an arbitrary public server.
Why browsing can work while time sync fails: Windows Time uses NTP over UDP port 123. A working web connection therefore does not establish that the time-service traffic can reach its source. If a managed network blocks that traffic, ask IT to check the permitted time source and network rules; do not turn off the firewall or replace the organization’s configuration.
3. Inspect the time service without resetting everything
Open the Services application and locate Windows Time. Note its state and any error when synchronization is requested. A startup-type label alone does not establish that the configuration is broken. If the service cannot start or a control is managed by your organization, preserve the error message and ask the responsible administrator.
Microsoft documents w32tm as a tool for examining and troubleshooting Windows Time. In an elevated Command Prompt, the following queries show the configured source and service status:
w32tm /query /source
w32tm /query /statusTo request a synchronization, use:
w32tm /resyncRead the returned message. An access error, a stopped service and an unavailable time source require different responses. Avoid copying a long reset script when you have not identified which condition applies.
| Observation | Why it helps |
|---|---|
| Exact error text | Distinguishes permissions, service and connectivity issues |
| Current time source | Shows whether Windows is using the expected source |
| Last successful synchronization | Helps establish when the failure began |
4. Separate Windows settings from other environments
If the problem appears only inside a virtual machine, investigate its host and guest time settings before assuming a physical clock fault. If it appears after alternating between operating systems, consult the relevant operating-system documentation rather than repeatedly changing the visible clock in each system.
Also consider whether another time-adjustment utility is installed. Change one setting at a time and keep a note of the original value. Otherwise a temporary improvement can make it difficult to tell which change mattered or how to undo an unsuccessful experiment.
5. Investigate a date that resets after power loss
If the date becomes incorrect after the computer has been disconnected from power, compare the firmware’s date with Windows before making hardware changes. A firmware clock that also repeatedly loses its date is a reason to consult the device manufacturer’s service guidance. It is not a reason to open every laptop or replace a battery without checking the model’s design.
Do not alter unrelated firmware options during this check. Managed machines, encrypted devices and laptops with difficult service access should be handled through the appropriate support channel. A single failed Sync now attempt, with the firmware clock otherwise stable, is not sufficient evidence for replacing hardware.
Manual time: a temporary or offline option
For a genuinely offline personal computer, manual time may be necessary. Record the previous settings, enter the full date carefully and recheck the local zone. When automatic synchronization becomes available again, restore your intended automatic setting. For a managed device, use the organization’s procedure instead.
If you only changed a setting for a comparison test, restore it when the test is complete. Do not leave a required VPN disconnected or forget a manually entered date after resolving the original problem.
How to confirm the problem is resolved
- The full date and time match a trusted reference.
- The selected zone matches your location.
- Synchronization succeeds when the network permits it.
- The clock remains correct after a normal restart.
- The original application or sign-in problem is tested again.
If an application still fails after the clock is correct, investigate that application separately. Incorrect time is one possible cause of an error, not an explanation for every connection or login failure.
Related guides
Read the Korean version of this guide, Wi-Fi connected without internet access (Korean), and why restarting can help (English).
Sources and scope
English adaptation of Waven’s Korean guide. Settings and command references rechecked on October 18, 2026: Microsoft Support: Date, time and time-zone settings; Microsoft Learn: Windows Time tools and settings. The tables and navigation aid are original explanatory text. No new English-interface screenshot or hands-on test is claimed.