This browser is no longer supported.
Upgrade to Microsoft Edge to take advantage of the latest features, security updates, and technical support.
![](data:image/svg+xml, %3Csvg xmlns='http://www.w3.org/2000/svg' height='64' class='font-weight-bold' style='font: 600 30.11764705882353px "SegoeUI", Arial' width='64'%3E%3Ccircle fill='hsl(297.6, 8%, 38%)' cx='32' cy='32' r='32' /%3E%3Ctext x='50%25' y='55%25' dominant-baseline='middle' text-anchor='middle' fill='%23FFF' %3EJH%3C/text%3E%3C/svg%3E)
This has been an issue now for a few years, but I cannot synchronize my Windows 10 computer with NTP at all, either via the GUI or using w32tm.exe.
Troubleshooting steps:
My computer is not on a domain, just a normal home computer.
I recently enabled logging for the NTP client, attached are the logs being generated.
Error message as seen from running w32tm \resync:
C:\WINDOWS\system32>w32tm /resync
Sending resync command to local computer
The computer did not resync because no time data was available.
Here's the pertinent parts (from what I can tell) when I attempt to run w32tm /resync:
154056 17:39:45.5071126s - RPC Call Attribute is local=1, kernel=0, session=0, authentication=6, protocol=2, OpNum=0
154056 17:39:45.5071485s - RPC Call - ForceResync
154056 17:39:45.5071642s - W32TmServiceMain: ********** Time Slip Notification **********
PCT: 999 154056 17:39:45.5071985s - ClockDispln TimeSlip: SetUnsync: LI:3 S:0 RDl:0 RDs:0 TSF:0x0
154056 17:39:45.5072289s - TimeProvCommand([NtpClient], TPC_TimeJumped) called.
154056 17:39:45.5072494s - UpdateTimerQueue1: TN:15555015310000::: LRT:15554859530000 LUT:15555015310000 LAFLTNS:0 TSLGT:0 LTNS:864000000000
154056 17:39:45.5072538s - PeerPollingThread: PeerListUpdated
154056 17:39:45.5072566s - W32TmServiceMain: waiting i16.000s (1024.000s)
154056 17:39:45.5072631s - PeerPollingThread: waiting forever
154056 17:40:01.5190923s - W32TmServiceMain: timeout
154056 17:40:01.5191404s - UpdateTimerQueue1: TN:15555175460000::: LRT:15554859530000 LUT:15555015310000 LAFLTNS:160118609 TSLGT:160118609 LTNS:864000000000
154056 17:40:01.5191513s - W32TmServiceMain: waiting 1024.000s
154056 17:40:01.5209445s - RPC Call - ForceResync
154056 17:40:01.5209717s - W32TmServiceMain: ********** Time Slip Notification **********
PCT: 1025 154056 17:40:01.5210038s - ClockDispln TimeSlip: SetUnsync: LI:3 S:0 RDl:0 RDs:0 TSF:0x0
Full log: 251202-w32time.log
Results are the same for using any NTP server I've been able to find online: Microsoft's, time.nist.gov, us.pool.ntp.org, etc. They all give the same error messages.
Other computers synchronize with NTP just fine on my network, so it is not an ISP issue.
I'm hoping someone here has some new suggestion that I haven't yet tried.
![](data:image/svg+xml, %3Csvg xmlns='http://www.w3.org/2000/svg' height='64' class='font-weight-bold' style='font: 600 30.11764705882353px "SegoeUI", Arial' width='64'%3E%3Ccircle fill='hsl(128, 8%, 22%)' cx='32' cy='32' r='32' /%3E%3Ctext x='50%25' y='55%25' dominant-baseline='middle' text-anchor='middle' fill='%23FFF' %3EA%3C/text%3E%3C/svg%3E)
Might try;
w32tm /unregister
net stop w32time
w32tm /register
net start w32time
w32tm /config /manualpeerlist:<ntp ip address> /syncfromflags:manual /reliable:yes /update
net stop w32time
net start w32time
then check
w32tm /query /source
w32tm /query /configuration
Many can be found here.
https://tf.nist.gov/tf-cgi/servers.cgi
--please don't forget to upvote and Accept as answer if the reply is helpful--
Thanks for the try, but I've tried all that multiple times. No change.
Please post the results above.
C:\WINDOWS\system32>w32tm /query /source
Free-running System Clock
C:\WINDOWS\system32>w32tm /query /configuration
[Configuration]
EventLogFlags: 2 (Local)
AnnounceFlags: 5 (Local)
TimeJumpAuditOffset: 28800 (Local)
MinPollInterval: 10 (Local)
MaxPollInterval: 15 (Local)
MaxNegPhaseCorrection: 54000 (Local)
MaxPosPhaseCorrection: 54000 (Local)
MaxAllowedPhaseOffset: 1 (Local)
FrequencyCorrectRate: 4 (Local)
PollAdjustFactor: 5 (Local)
LargePhaseOffset: 50000000 (Local)
SpikeWatchPeriod: 900 (Local)
LocalClockDispersion: 10 (Local)
HoldPeriod: 5 (Local)
PhaseCorrectRate: 1 (Local)
UpdateInterval: 360000 (Local)
[TimeProviders]
NtpClient (Local)
DllName: C:\WINDOWS\SYSTEM32\w32time.DLL (Local)
Enabled: 1 (Local)
InputProvider: 1 (Local)
AllowNonstandardModeCombinations: 1 (Local)
ResolvePeerBackoffMinutes: 15 (Local)
ResolvePeerBackoffMaxTimes: 7 (Local)
CompatibilityFlags: 2147483648 (Local)
EventLogFlags: 1 (Local)
LargeSampleSkew: 3 (Local)
SpecialPollInterval: 32768 (Local)
Type: NTP (Local)
NtpServer: time.nist.gov,0x1 (Local)
NtpServer (Local)
DllName: C:\WINDOWS\SYSTEM32\w32time.DLL (Local)
Enabled: 0 (Local)
InputProvider: 0 (Local)
Looks Ok. What do you see if you filter the system event log for TimeService like below?
then looking for the 35 and 37 events (the 158 are bogus because of hyper-v role)
Just checking if there's any progress or updates?
--please don't forget to upvote and Accept as answer if the reply is helpful--
I have attempted to compose a reply with an attached document and image but the site is not allowing me to post it. No error message or anything. when I click Submit the button becomes grayed out for a moment, then is active again. There are no errors in the browser console.
I am posting this message mostly as a test to see if posting without any attachments/images works still.
Thanks for the reply.
I have no 35 and 37 events, ignoring the 158s I only see 36 and 47 (with 36 being the most common).
This is the first part of my reply, I am writing it in piecemeal to see which part of it I am not allowed to post.
New forums user's profiles are more restricted. Try putting them up on OneDrive and share a link.
The first part of my reply is now pending moderator approval, here's the second part of my reply where I attempt to attach the log file:
I exported the event log (it's in CSV format, but had to add .log to the end since .csv files are not allowed here): 252081-time-service-event-logcsv.log
Text of 36 events:
The time service has not synchronized the system time for the last 86400 seconds because none of the time service providers provided a usable time stamp. The time service will not update the local system time until it is able to synchronize with a time source. If the local system is configured to act as a time server for clients, it will stop advertising as a time source to clients after 0 seconds. The time service will continue to retry and sync time with its time sources. Check system event log for other W32time events for more details. Run 'w32tm /resync' to force an instant time synchronization. You can control the frequency of the time source rediscovery using ClockHoldoverPeriod W32time config setting. Modify the EventLogFlags W32time config setting if you wish to disable this message.
Text of 47 events:
Time Provider NtpClient: No valid response has been received from manually configured peer [PEER ADDRESS HERE],0x1 after 8 attempts to contact it. This peer will be discarded as a time source and NtpClient will attempt to discover a new peer with this DNS name. The error was: The peer is unreachable.
Thanks again for the help.
No valid response has been received from manually configured peer [PEER ADDRESS HERE]
what was the configured peer? Is it still time.nist.gov? If so try using a different one using the method I posted above.
https://tf.nist.gov/tf-cgi/servers.cgi
--please don't forget to upvote and Accept as answer if the reply is helpful--
Just checking if there's any progress or updates?
--please don't forget to upvote and Accept as answer if the reply is helpful--