W11 Pro NTP Client Failure

simsrw73 · Jan 30, 2023

I just upgraded my GPU from Nvidia to AMD which caused some random crashing, even after using gpu driver removal tool, so I did a clean install of W11 Pro which seems to have fixed it. However the Windows NTP Client is not working now. It did work before.

"An error occurred while Windows was synchronizing with...."

I'm attempting to sync to a local router that is verified working by other devices on my network, but the standard remote ntp servers also fail.

I found this python script that retrieves time from ntp server and it works correctly from the same desktop both to local and remote ntp servers:

Python:

import socket
import struct
import sys
import time

def RequestTimefromNtp(addr='192.168.99.1'):
    REF_TIME_1970 = 2208988800  # Reference time
    client = socket.socket(socket.AF_INET, socket.SOCK_DGRAM)
    data = b'\x1b' + 47 * b'\0'
    client.sendto(data, (addr, 123))
    data, address = client.recvfrom(1024)
    if data:
        t = struct.unpack('!12I', data)[10]
        t -= REF_TIME_1970
    return time.ctime(t), t

if __name__ == "__main__":
    print(RequestTimefromNtp())

The "Windows Time" service is running. I've restarted it as well as rebooting several times.

I've unregistered/rebooted/registered the time service with no change. ( w32tm /unregister)

Windows Firewall is open for udp on port 123. I've tried completely disabling the firewall as well with no change.

w32tm log file
154160 22:51:25.3743332s - ---------- Log File Opened -----------------154160 - Pastebin.com

w32tm secondary log file (?)
154160 22:52:45.8059015s - ---------- Log File Opened -----------------154160 - Pastebin.com

What else can I check? What is causing the failure? What is that secondary log file which has the same name as the log file but with a guid appended to the name?

OAT · Jan 30, 2023

So this error is interesting:

Logging Info: Time provider 'VMICTimeProvider' indicated that the current operating environment is unsupported and has stopped. This is expected for VMIC provider in non-Hyperv environments. This may be the expected behavior for the current provider in the current operating environment as well. error:-2147024846

Please from command line, one entry at a time:

w32tm /config /manualpeerlist:51.145.123.29,0x8 /syncfromflags:MANUAL
net stop w32time
net start w32time
w32tm /resync

See what you get.

simsrw73 · Jan 30, 2023

No joy. I don't understand where it's failing at. I can query my local ntp server (or any remote server) from this desktop using other tools, but I can't get w32tm to sync. This is a fresh install of Windows and fixed some problems that have been a huge thorn in my side for ages with wsl and wt, but now this one tiny thing is frustrating the heck out of me.

Code:

Sending resync command to local computer
The computer did not resync because no time data was available.

OAT · Jan 30, 2023

How bizarre.
I did find this for you.
Especially the reg value in
HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\W32Time\Parameters
and the error debugging part.