top of page

How to Keep Your PC Clock Accurate for FT8 and Other Digital Modes

Why Precise Time Matters
 

Digital modes such as FT8, JS8Call, and WSPR rely on tightly synchronized time slots. If your PC’s clock drifts by more than a couple of seconds, you may miss decodes, transmit outside the expected window, or introduce logging errors. Maintaining accurate UTC alignment is essential for reliable weak‑signal digital operation.

Windows includes a built‑in time synchronization service (Windows Time / W32Time) that uses Network Time Protocol (NTP) servers to keep the system clock aligned. However, on a typical standalone PC, its default behaviour synchronizes time only infrequently (often on the order of days), which is insufficient for time‑critical digital modes.

 

This guide shows how to configure Windows to synchronize time much more regularly using standard, reliable NTP servers—without installing third‑party software—ensuring your station remains accurately synchronized for digital mode operation.

Step-by-Step: Configure Hourly NTP Sync on Windows

Step 1: Enable Internet Time Sync

This guide applies to both Windows 10 and Windows 11. The layout may vary slightly between versions, but the settings and PowerShell commands are the same.

  1. Open Settings > Time & Language > Date & Time

  2. Ensure the following options are enabled:
    - Set time automatically

    - Set time zone automatically

  3. Scroll down to Synchronize your clock and click Sync now
     

This confirms that Windows is actively synchronizing system time and that the Windows Time service (W32Time) is functioning correctly.

By default, standalone Windows systems synchronize time using Microsoft’s public NTP service, time.windows.com. In the next step, we’ll configure additional NTP servers to improve reliability and prepare Windows for more frequent synchronization.

Step 2: Set Regular Sync Interval via PowerShell

By default, standalone Windows systems synchronize time only infrequently (typically once every few days). For digital modes such as FT8, this is not precise enough—PC clocks can drift several seconds over that period, leading to missed decodes or mistimed transmissions.

To improve accuracy, we’ll configure Windows to synchronize time much more regularly using its built‑in Windows Time service (W32Time). This provides regular, predictable corrections without installing any third‑party software.

Don’t worry if you’re not familiar with PowerShell—this step is simple and only requires copying and pasting a command.

Open PowerShell as Administrator

  1. Press Windows + X

  2. Select Windows PowerShell (Admin) or Terminal (Admin)
    (The name varies slightly depending on Windows version.)

  3. When prompted, click Yes to accept the User Account Control (UAC) prompt


A blue PowerShell window similar to the one below will open.

Powershell.JPG

Next, we’ll copy and paste six PowerShell commands into the PowerShell window. Each command performs a specific task; they are safe to run and can be entered one at a time.

1. Set how often Windows checks the time.

This command sets a shorter minimum update interval of around 64 seconds.
Windows will usually start by checking the time more frequently (around once per minute), then automatically increase the interval as the clock stabilises to reduce network traffic and improve efficiency.

Copy the entire command below, paste it into the PowerShell window, and press Enter:
 

Set-ItemProperty -Path "HKLM:\SYSTEM\CurrentControlSet\Services\W32Time\TimeProviders\NtpClient" -Name "SpecialPollInterval" -Value 64

2. Configure which internet time servers Windows uses

This command sets the time servers your computer will use and enables a more accurate way of keeping time.
Windows will start by checking the time more frequently, then automatically adjust how often it synchronises as the clock becomes stable. This helps improve accuracy while reducing unnecessary network traffic. Multiple servers are included so your computer can stay synchronised if one is temporarily unavailable.


Copy the entire text in red below and paste it into the Powershell Window and hit "ENTER"

w32tm /config /manualpeerlist:"pool.ntp.org,0x8 time.cloudflare.com,0x8 time.google.com,0x8 time.windows.com,0x8" /syncfromflags:MANUAL /update

 

3. Restarts the Windows Time service.
This forces Windows to reload and apply the new configuration immediately.


Copy the entire text in red below and paste it into the Powershell Window and hit "ENTER"


Restart-Service w32time

4. Force an immediate time resynchronisation

This command tells Windows to rediscover its configured NTP servers and synchronise the clock right now, rather than waiting for the next scheduled check.

Copy the entire text in red below and paste it into the Powershell Window and hit "ENTER"

w32tm /resync /rediscover

5. Display the current time synchronisation status
This shows whether Windows is synchronised, which server is being used, and the current clock offset.

Copy the entire text in red below and paste it into the Powershell Window and hit "ENTER"

w32tm /query /status

6. Check real‑time clock accuracy

This performs a short live comparison between your PC clock and an external NTP server, showing the time offset in milliseconds.


Copy the entire text in red below and paste it into the Powershell Window and hit "ENTER"

w32tm /stripchart /computer:time.cloudflare.com /samples:5 /dataonly

In Powershell, you should now see something like this:

PS_NTP.JPG

Windows Time Synchronisation - w32tm /query /status explanation
 

Using the above PowerShell commands, the Windows Time service has been successfully reconfigured and is operating normally. The output from w32tm /query /status confirms correct behaviour. The following explains the key values and how they should be interpreted:

Leap Indicator

Indicates whether any leap‑second adjustments are pending.
A value of “no warning” confirms the time source is valid and operating normally.

Stratum

Shows the level of the time source in the NTP hierarchy.
Lower values (such as 2–3) indicate synchronisation with a reliable server that is close to an authoritative time source.

Precision

Represents the resolution of the system clock hardware.
This is a fixed characteristic of the system and does not indicate accuracy or any fault.

Root Delay

Measures the network round‑trip time between your PC and the time server.
Lower values indicate better network conditions and typically improve time accuracy.

Root Dispersion

Root dispersion is a Windows Time confidence value.
It represents the maximum estimated uncertainty in the time source, not the actual clock error.

After configuration changes or a restart, this value may initially appear high (even several seconds). This is normal.
As Windows continues to synchronise successfully, it increases its confidence and this value will gradually decrease over time.

Reference ID

An internal identifier for the current time source.
This confirms that the system is using an external NTP server.

Last Successful Sync Time

Shows when the system last synchronised successfully.
A recent timestamp confirms the service is working correctly.

Source

Displays the current time server being used.
This confirms that your configured servers are in use.

Poll Interval

Indicates how often Windows checks the time server.
In normal operation, this value adjusts automatically based on how stable your system clock is. Longer intervals usually mean the clock is already stable.

Real‑time comparison (understanding stripchart)

The w32tm /stripchart command provides a live comparison between your PC clock and an internet time server.

However, the values shown include network delay and do not represent the true clock accuracy.

It is normal to see values in the range of tens to hundreds of milliseconds, especially when comparing to servers that are further away. What matters most is that the values remain stable and consistent across samples.

Your system’s actual clock accuracy is typically much better than these numbers suggest, often within tens of milliseconds.

Important takeaway

  • w32tm /query /status → confirms correct synchronisation ✅

  • Root Delay → shows network quality ✅

  • Root Dispersion → shows confidence (not error) ✅

  • stripchart → shows a live comparison affected by network delay ❗

Taken together, these confirm that your system clock is synchronised and operating correctly.

bottom of page