To set time and time zone in Windows, open Settings > Time & language > Date & time, turn on "Set time automatically" and "Set time zone automatically," or switch the time zone manually from the drop-down. If the clock is still wrong, a w32tm resync command forces a fresh sync from the Windows time server. The whole job takes about two minutes in Windows 11 and roughly three in Windows 10, where the path is Settings > Time & Language > Date & time.
That covers the default case. The interesting failures start when your PC syncs the hour but not the zone, when a dual-boot setup keeps flipping you to UTC, or when a Windows 11 machine with location services disabled refuses to set the zone at all. Below are the click paths for both versions, the exact values each setting writes into the registry, the command-line recovery route, and the mistakes that account for most "my clock is wrong" complaints.
What the Two Automatic Time Toggles Actually Change
The Date & time page has two independent switches, and understanding the split is what stops most confusion later. "Set time automatically" controls the clock value itself, handed to the Windows Time service. "Set time zone automatically" controls the zone offset, and it depends on a location fix.
Microsoft's documentation for the Windows Time service is the authority here. The service, running as w32time, syncs the local clock against an NTP server. Since Windows 10 version 1809, Microsoft's own time.windows.com has served as the default source, with time.nist.gov as the published fallback in older builds.
The zone toggle is a different mechanism entirely. It reads your location through the Windows location service and maps coordinates to a time zone using Microsoft's zone database. Disable location services and the zone toggle stays on but does nothing, which is why some laptops sit on the wrong zone while the hour itself is correct.
One more detail most guides skip: Microsoft reset the automatic time zone database in Windows 10 version 1903. Machines upgraded from earlier builds could keep stale zone mappings until the toggle was cycled off and on once. If a work PC has been imaged from an old template, that toggle has probably never been touched.
Numbered Steps to Set Date, Time, and Zone in Windows 11
Windows 11 uses the Settings app path, and the sequence below follows the actual screen order. Total time is about two minutes, plus up to 15 minutes of waiting if the automatic sync is slow.
1: Right-click the clock in the taskbar and choose "Adjust date and time," or press Win + I and open Time & language > Date & time. 2: Turn on "Set time automatically." Confirm the sync status line below it shows a recent sync time. 3: Turn on "Set time zone automatically" if you travel or move between zones. Leave it off if you want the zone fixed. 4: Set the zone by hand from the "Time zone" drop-down when the automatic toggle is off. The list shows UTC offsets and major cities, not just regions. 5: Click "Sync now" under "Additional settings" to force an immediate NTP check rather than waiting for the scheduled interval. 6: If the date itself is wrong, use "Set time manually" under "Additional settings" to fix it, then re-enable automatic sync. 7: Verify with the clock in the bottom-right corner and reopen the page — a value that snaps back means the service is failing, not the setting.
Failure handling: if "Sync now" returns an error, run Command Prompt as administrator and type w32tm /resync. If that reports "The computer did not resync because no time data was available," check that UDP port 123 is not blocked by a corporate firewall or VPN — NTP is the single most commonly filtered outbound protocol on enterprise networks, and it fails silently.
Windows 10's Slightly Different Route, Step by Step
Windows 10 keeps the same settings under a flatter menu tree, and the control names differ in a few places. Budget about three minutes, mostly for locating the "Additional date, time & regional settings" link.
1: Open Settings (Win + I) and pick Time & Language > Date & time. 2: Switch "Set time automatically" to On and confirm the "Last successful sync" line reads recently. 3: Switch "Set time zone automatically" to On, or leave it Off and pick a zone from the drop-down. 4: Click "Sync your clock" if the page offers it — Windows 10 exposes this button in some builds and hides it behind the additional settings link in others. 5: For manual changes, use "Change date and time" and "Change time zone" buttons rather than editing the clock in the taskbar. 6: Open Control Panel > Clock and Region > Date and Time if you need the legacy dialog, which still shows the "Internet Time" tab. 7: Restart the Windows Time service if the toggles grey out: run services.msc, find "Windows Time," and set Startup type to Automatic.
Failure handling: a greyed-out toggle usually means a domain policy is overriding it. On a work machine joined to an Active Directory domain, the domain controller is the time source and no local setting will stick. Ask IT before changing anything; resyncing a domain-joined PC to a public server can break Kerberos authentication, which tolerates a default skew of five minutes.
Why Your Clock Shows the Right Hour but the Wrong Zone
A clock that displays the correct local time while the zone name is wrong is a specific, common failure with a specific cause: the offset was set correctly once and the zone label never refreshed. The time looks fine because the offset does the work; the zone name is cosmetic until daylight saving changes arrive.
Automatic daylight saving adjustment is the setting that matters most. In Windows 11 it appears as "Adjust for daylight saving time automatically" under Additional settings. If it's off, the clock will not spring forward or fall back, and your machine will sit one hour off for the roughly eight months most of the Northern Hemisphere spends in DST.
DST rules themselves change. The United States has observed DST from the second Sunday in March to the first Sunday in November since the Energy Policy Act of 2005 took effect in 2007. Mexico abolished DST for most of the country in 2022, and the European Union has repeatedly debated ending the twice-yearly shift without enacting it. An out-of-date Windows build can carry a stale DST rule table, which is why Windows Update matters for a clock.
If the hour is wrong and the zone is right, the problem is almost always sync. Check the sync status line first, then run the command below rather than reinstalling anything.
The w32tm Commands That Fix a Clock That Won't Sync
The Windows Time service ships a diagnostic tool that most users never open. Run Command Prompt as administrator and these commands will tell you exactly where the sync is breaking.
| Command | What it tells you |
|---|---|
| w32tm /resync | Forces one immediate sync attempt; reports "no time data available" when NTP is blocked |
| w32tm /query /status | Shows the last sync time, the source server, and the remaining clock offset |
| w32tm /query /configuration | Lists whether the service is in domain or local mode and the configured NTP peers |
| w32tm /monitor | Reports the offset between your machine and the domain hierarchy's time servers |
| w32tm /stripchart /computer:time.windows.com | Live view of the offset against a chosen server, refreshed on demand |
| w32tm /tz | Prints the current time zone and its offset, useful for confirming a manual change stuck |
The useful number is at the end of w32tm /query /status: "Phase Offset," quoted in seconds with more decimals than you need. Anything beyond a couple of seconds means sync is failing, and a machine that drifts is not syncing at all.
Failure case worth knowing: after a laptop resumes from a long sleep or hibernation, the clock can be off by hours while the service reports a healthy status from before the sleep. A single w32tm /resync normally corrects it, and if it doesn't, restarting the Windows Time service with net stop w32time and net start w32time before the resync usually does.
Registry Values and Time Zone IDs Behind the Settings Page
Every toggle on the Date & time page writes to a registry value, and checking them directly is how you confirm a policy is fighting you. The hardware clock value at HKLM\SYSTEM\CurrentControlSet\Control\TimeZoneInformation\RealTimeIsUniversal is the one that matters for dual-boot.
Set that DWORD to 1 and Windows treats the hardware clock as UTC, which is also how Linux reads it. Leave it at 0 and Windows treats the hardware clock as local time, which is the default and the cause of the classic dual-boot symptom: Linux shows the right time, boot into Windows, reboot, and Linux is off by the offset. Setting the value to 1 and rebooting into Windows is the fix; some Windows builds overwrite it during shutdown, so verify it after a restart.
The other value is TimeZoneKeyName under the same key, which stores the Windows time zone name. Zone names are long identifiers like "Pacific Standard Time," and setting one manually to a European ID without changing the offset leaves you with a mismatched pair that looks correct one day and wrong the next. Changing zones through the Settings drop-down writes both values consistently, which is another argument for using the UI rather than editing the registry.
A Microsoft note worth repeating: don't set the clock back on a virtual machine that's managed by a hypervisor. Hyper-V and VMware both offer host time sync (Hyper-V through Integration Services' Time Synchronization checkbox), and conflicting sources make the guest clock oscillate.
Manual Zone Changes: When to Turn Automatic Off
Automatic zone detection suits a traveling laptop and fails a desktop that never moves. Turn the toggle off for the second case, and pick the zone by name once.
Manual is also the right choice when location services are disabled for privacy, when a corporate policy blocks location access, or when the machine sits in a border region and its location fix resolves to the wrong country. Windows has no "nearest city" heuristic you can tune; it either reads coordinates or it doesn't.
When changing zones manually, confirm the daylight saving switch afterward. Some zones have no DST at all, and Windows silently disables the toggle for those — Moscow, for example, has stayed on UTC+3 year-round since 2014, while most of Arizona stays on Mountain Standard Time year-round. Seeing the DST toggle greyed out after picking those zones is correct behavior, not a bug.
For a machine that crosses a border daily, automatic detection is still the cleaner answer. The alternative is remembering to switch, and people don't remember.
Fixing the Clock on a Domain-Joined or Managed Work PC
On a machine joined to Active Directory, the domain controller is the authoritative time source and the local Date & time page is mostly a display. The Windows Time service runs in domain mode and syncs to the domain hierarchy automatically. Editing the zone by hand may appear to work and then revert at the next policy refresh.
The setting to look for is the Group Policy entry that configures the Windows Time client and server. On a managed device, check with IT before touching anything — a resync against an external server can put the machine outside the Kerberos tolerance and lock out the user from network resources, which presents as a password problem rather than a clock problem.
Personal machines with a Microsoft account get a different nudge: cloud-synced settings can reapply old time settings after a fresh Windows install, so a brand-new laptop occasionally arrives on the previous machine's zone. Check the zone after signing in, not before.
When the toggles refuse to stay on, open services.msc and confirm Windows Time is running. A disabled service greys out every related control, and a third-party "clock fixer" utility disabling it is a more common cause than any Windows update.
Common Mistakes That Keep Windows Time Wrong
Four mistakes account for most of the complaints, and all four are avoidable.
Editing the clock in the taskbar without opening Settings doesn't persist — Windows resets it at the next sync, and the user concludes the clock is broken. Use the "Set time manually" control, which stops the automatic sync first and explains why.
Assuming the sync worked because no error appeared is the second mistake. The Settings page shows a sync time; check it. A machine that last synced three days ago is not syncing.
Leaving automatic zone detection on while traveling by car across a border with location services off is the third. The toggle is on, the setting appears healthy, and the zone is stale.
The fourth is ignoring the CMOS battery on older desktops. A coin-cell battery that's been in service five to ten years will let the hardware clock lose time when the machine is unplugged, and no software setting fixes that. Replacing the CR2032 costs a few dollars at any electronics retailer and is a five-minute job.
Quick Comparison of the Three Ways to Change the Zone
There are three routes, and they differ in what they overwrite.
| Method | Where | Persists across reboots | Risk |
|---|---|---|---|
| Settings drop-down | Settings > Time & language > Date & time | Yes | None, writes zone name and offset together |
| Control Panel legacy dialog | Control Panel > Date and Time > Change time zone | Yes | Same result, slower path |
| Command line tzutil /s "Pacific Standard Time" | Elevated Command Prompt | Yes | Typos in zone ID fail silently; tzutil /l lists valid IDs |
The third route is the one for scripted setup or fixing many machines. Run tzutil /l first to get the exact identifier; a misspelled ID returns an error rather than a corrupted setting, which is at least honest. The Date & time page in Settings remains the safest single change because it can't write a half-correct pair.
FAQ
Why does my Windows clock show the correct time but the wrong time zone?
The offset and zone name are separate values, and an old manual offset can outlive a zone label change. Open Settings > Time & language > Date & time and toggle "Set time zone automatically" off and back on to force a re-read. If the zone stays wrong with location on, the Windows location service is likely disabled in Privacy > Location. Fixing the zone is cosmetic until DST flips, at which point the hour goes wrong too.
Can I set Windows to use UTC and stop the dual-boot clock problem?
Yes. Set the RealTimeIsUniversal DWORD to 1 at HKLM\SYSTEM\CurrentControlSet\Control\TimeZoneInformation and reboot. Windows then reads the hardware clock as UTC, matching how Linux and macOS treat it. Verify the value after a restart on some builds, because older Windows versions have rewritten it during shutdown. Dual-boot users lose this fix entirely if Windows fast startup is enabled; turn that off in Power Options first.
What's the Windows command to change the time zone?
tzutil /s "Eastern Standard Time" changes it from an elevated Command Prompt, and tzutil /l lists every valid ID. The command writes the zone name and offset together and persists across reboots, unlike a bare registry edit. A typo returns "Invalid argument" rather than corrupting the setting. This is the route for imaging scripts, not a race with the Settings page.
How long does Windows take to sync the clock automatically?
The Windows Time service normally syncs once a week by default, so a fresh manual change can sit unconfirmed for days. "Sync now" in Settings forces one attempt immediately, and Success or an error appears within seconds. Machines that sleep often need a manual resync after wake because the scheduled check doesn't fire during sleep. A computer reporting a sync from several days ago is behaving as configured, not broken.
Does the time zone setting affect other software?
Yes, more than people expect. Calendar apps, scheduled tasks, Outlook meeting times, and anything that stores timestamps without an offset will shift when the zone changes. Some backup tools schedule by local time, so a zone change moves the run by the offset difference. Change the zone before scheduling anything recurring, not after.
Is it the clock or the battery when an old PC loses time?
The CMOS coin cell in a desktop lasts roughly five to ten years in typical use and less on a machine kept unplugged. Symptoms: the clock resets to a default date after every full power loss, while sync works fine once the machine is on. Replace the CR2032; a laptop with a swollen or degraded main battery can show a milder version of the same behavior.
Why won't my work laptop keep the time zone I chose?
A domain-joined machine defers to the domain hierarchy for time, and a Group Policy refresh can reapply the old settings within the policy interval. The local Settings page shows the change, then reverts. Ask IT whether a time zone policy applies before making changes; resyncing to an external NTP server on a domain machine can break Kerberos authentication, which allows five minutes of clock skew by default.