ThisCalculator

Everyday

Sync Time with Internet Server in Windows

Updated · Standard formula, shown below

Sync Time with Internet Server in Windows

To sync your Windows clock with an internet time server, open Settings > Time & Language > Date & time and click Sync now under the “Synchronize your clock” section. This forces an immediate connection to Microsoft’s default time server (time.windows.com) and corrects any drift in your system clock. For more control, you can change the server, adjust the sync frequency, or use the classic Control Panel interface—all covered below.

Why Windows Time Drifts and Why It Matters

Every computer clock drifts because it relies on a quartz crystal oscillator, which is accurate to only a few seconds per day under normal temperature changes. Over weeks, that drift adds up to minutes, which can break scheduled tasks, cause SSL certificate errors (“clock is wrong” warnings in browsers), and make file timestamps misleading. Network Time Protocol (NTP) solves this by comparing your clock to atomic clocks maintained by national laboratories and distributed through a hierarchy of public servers.

Windows has built-in NTP support, but it is configured conservatively: by default, it syncs once a week. If your PC is asleep or off at the scheduled time, the sync is skipped, and the clock keeps drifting. That is why many users find their clock is off by a few minutes even though “automatic time” is enabled.

How Windows Time Synchronization Works

Windows uses the Windows Time service (w32time) to query an NTP server on UDP port 123. The service sends a request with the current time, the server replies with its time and the network delay, and Windows applies a correction. The process is not instantaneous—it typically takes a few hundred milliseconds—and Windows adjusts the clock gradually rather than jumping it, to avoid breaking event sequencing.

There are two layers of settings:

  • Settings app (Windows 10/11): simple, but only lets you sync manually or change the server via the Control Panel.
  • Control Panel (Date and Time > Internet Time tab): lets you pick a server and sync immediately, but still uses the default weekly schedule.
  • Command line / Registry: for advanced users who want to change the sync interval or use a custom NTP server.

The default server, time.windows.com, is a pool of Microsoft-managed NTP servers. It is reliable and fast for most users, but some prefer public NTP pools like pool.ntp.org or regional servers for lower latency.

How to Sync Manually (Step-by-Step)

Here are the exact steps for the most common methods:

Method 1: Settings App (Windows 10/11)

  1. Press Windows + I to open Settings.
  2. Go to Time & Language > Date & time.
  3. Ensure Set time automatically is toggled on.
  4. Click Sync now under “Synchronize your clock.”
  5. Wait a few seconds; you should see “Your clock was successfully synced” with the server name and last sync time.

Method 2: Control Panel (All Windows versions)

  1. Open Control Panel (search for it in the Start menu).
  2. Go to Clock and Region > Date and Time.
  3. Switch to the Internet Time tab.
  4. Click Change settings…
  5. Check Synchronize with an internet time server.
  6. Choose a server from the drop-down (e.g., time.nist.gov) or type one manually.
  7. Click Update now and wait for the confirmation.

Method 3: Command Prompt (for scripting)

  1. Open Command Prompt as administrator.
  2. Run w32tm /resync to force a sync using the current configuration.
  3. To check the last sync status, run w32tm /query /status.

Choosing a Time Server: Which One Should You Use?

Microsoft’s default is fine for most people, but you might want to switch if you have specific needs:

  • time.windows.com – default, good for general use, but occasionally unreachable due to network issues.
  • time.nist.gov – US National Institute of Standards and Technology, highly accurate, but may be blocked in some regions.
  • pool.ntp.org – a global pool of volunteer servers; use 0.pool.ntp.org, 1.pool.ntp.org, etc. It’s decentralized and often faster.
  • time.google.com – Google’s public NTP service, uses leap smearing (see below).

If you are in a corporate network, your IT department may have an internal time server that you should use instead. For home users, any of the above will give accuracy within a few milliseconds.

Common Problems and Fixes

Sometimes syncing fails. Here are the most frequent causes and solutions:

  • Error: “An error occurred while Windows was synchronizing with…” – Usually a network issue. Check your internet connection, then try a different server. Also, make sure your firewall isn’t blocking UDP port 123.
  • Clock keeps drifting even after sync – The CMOS battery on your motherboard may be failing. Replace it (a common CR2032 coin cell).
  • Sync now is greyed out – This happens when “Set time automatically” is off. Turn it on first.
  • Time zone wrong – Ensure the correct time zone is selected, otherwise the clock will appear off by hours even if the UTC time is correct.
  • Windows Time service is disabled – Open Services (services.msc), find “Windows Time,” set Startup type to Automatic, and start it.

How to Change the Sync Frequency

By default, Windows syncs once every 7 days. To make it sync more often (e.g., daily), you can edit the registry:

  1. Open Registry Editor (regedit).
  2. Navigate to HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\W32Time\TimeProviders\NtpClient.
  3. Find the value SpecialPollInterval (in seconds). Default is 604800 (7 days).
  4. Change it to 86400 for daily, or 3600 for hourly.
  5. Restart the Windows Time service (or reboot).

Be cautious: too frequent syncing (every few minutes) is unnecessary and can strain public servers. Once a day is more than enough for a typical PC.

Leap Seconds and Leap Smearing

NTP servers transmit a flag when a leap second is about to occur (June 30 or December 31). Windows handles this by inserting the extra second at the end of the day. However, some services (like Google) use “leap smearing”—they stretch the length of a second over a 24-hour period, so their time is never exactly UTC but is always within a fraction of a second. If you need precise UTC, use a server that does NOT smear (most public NTP servers do not).

Frequently Asked Questions

Why is my Windows clock still wrong after syncing?

If the sync succeeds but the clock is still off, check your time zone and daylight saving settings. Also, if the CMOS battery is weak, the clock will drift again quickly. Finally, make sure you are not running a virtual machine that uses host time instead of NTP.

Can I use any NTP server?

Yes, you can type any valid NTP server address in the Control Panel. However, avoid obscure servers that may be unreliable or malicious. Stick to well-known public pools or your organization’s server.

Does syncing time require administrator rights?

Manual sync via the Settings app works for standard users, but changing the server or using the command line requires admin rights. The Windows Time service itself runs as SYSTEM.

Is it safe to sync time over the internet?

Yes, NTP is a plaintext protocol, but the risk is minimal because time data is not sensitive. However, an attacker could spoof a server and send wrong time, which could cause issues. That’s why using trusted servers and keeping your firewall rules tight is recommended.

What is the difference between automatic time and internet time?

“Automatic time” means Windows gets the time from the internet (or a network source) rather than relying solely on the internal clock. “Internet time” specifically refers to NTP. They are effectively the same in modern Windows.

Why does Windows sync so rarely by default?

Microsoft chose a 7-day interval to reduce load on their servers and because most users don’t need millisecond accuracy. If you need more frequent sync, you can change the registry as shown above.

Related

Method: the standard formula for this calculation, rounded as each result states. See how the calculators work or report an error.