[belZaah]

I used to manage NT-based infra back in the day, have been on a mac for 15 years now because of stuff like this. A few years ago I bought a Windows box for my daughter. Out of the box the clock was wrong and it would just hang on auto-update. No message, no logs anywhere, just hangs. A few years later the son comes of age and gets his own box. And it’s the same story, no automatic adjustment of the clock. I’m running a bog standard unifi network leading to fiber, nothing complicated, everything else works including all the windows laptops of my wife. But a basic standards-based library-supported Windows function.

[oxygen_crisis]

Windows NTP client uses UDP port 123 as both the destination and source port, rather than letting the OS assign an ephemeral source port.

Many ISPs (e.g. AT&T Fiber) block UDP traffic with source port 123 to mitigate NTP amplification attacks.

Most people won't notice that problem since low-end consumer routers tend to mangle the source port when they perform outbound NAT. The ISP-provided router will generally do this itself until you enable "DMZ+" or "IP Passthrough" or some similarly-named mode, as home networking experts will typically do so they can manage NAT and firewalling on their own devices.

If a Windows laptop can sync and the wired Windows desktops can't, your wi-fi AP might be doing the necessary source port mangling.

If you add a NAT rule to your router to change the source port for NTP traffic, you should get time sync working.

[7bit]

Windows uses NTP by default with sane settings -- and it logs by default. So whatever issue you're experiencing is not a Microsoft problem, but a *you problem*. And the fact you state that there are no logs, which is false, kinda proves it.

[fragmede]

that's such a cop out. Whatever store GP is buying computers from is messing things up, but how come Microsoft lets things get so bugged up in the first place? If I get an iPhone, it'll just work.

[D13Fd]

Agreed. I have several windows gaming PCs for my kids. One of them occasionally decides it’s in California and has to be corrected. Why? I have no idea.

Every single Mac, iPad, and iPhone gets this right with zero configuration.

[keeda]

My theory, having seen what happens due to incorrect date/time settings on Windows (e.g. rebooting a laptop after the battery has been drained for extended durations):

1. The time, and critically date, is wrong (not syncing with the NTP servers, potentially due to ISP filtering, as the sibling comment implies)...

2. Which is causing SSL errors because the wrong date causes the expiry date on the SSL certificates to appear nonsensical...

3. Which causes connection failures to pretty much any HTTPS endpoint...

3. Which is preventing updates because no sane OS would download updates over an insecure connection.