Windows is meant to re-sync the clock maybe weekly but it fails often so the time accuracy gets worse and today my laptop is 9.7 seconds fast. A deliberate clock re-sync (Sync Now) doesn't want to work as it can't reach the time server, so I'll have to stay 9.7 seconds or worse fast.
It works fine for me, my PC doesn't ever seem to get more than ~1 second ahead or behind. I've set the time server address to time.nist.gov instead of time.windows.com -- maybe that is what makes the difference. Btw, are you sure that your firewall doesn't block the time server, or the sync process?
In Windows 11, you can change the time server through Settings > Time & Language > Date & Time > Additional Clocks > Tab: Internet Time > Change Settings > (choose sync server).
Thanks for the info, but time.nist.gov fails as well.
From the panel I do see that the usual sync does work..... eventually..... where I was 9.7 sec fast, now only 3 sec fast(?) after one sync that happened yesterday...
Here in a remote suburb of Sydney Oz, my Internet seems to be on the end of a very long bit of wet string so is very unreliable at times.
I have never ever trusted PC clocks as my 1980's programming efforts (compiled Basic) were car club race timing using Commodore 64, they could be tuned to yield accurate timing due to their 1MHz clock. Meanwhile PC clocks seemed to tick over at 1/7 second intervals and were very unreliable so I never bothered to do the same suite of race timing programs with PCs.