Windows Time Sync Offset

SteveCase · 02 Nov 2018

This a probably a different manifestation of the problem I reported in another thread ("Windows 10 Clock Running Slow"). I thought my PC Windows 10 clock was drifting behind, but during the last few days at least, that isn't the problem I'm experiencing. When I initiate a manual sync to an NTP server, (usually, but not always, successful), the resulting time is always about 1 second behind real time, and it stays like that. It doesn't matter how many times I repeat this, or which server I select, the resulting time offset is always the same. I also have a much slower Windows 10 laptop sharing the same internet connection which doesn't have this problem. Any ideas?

vgchat · 07 Nov 2018

So is it really that big of a deal if it's 1 second off? I mean sure, I can see it affecting you as a OCD thing but performance wise, what's the difference?

das10 · 08 Nov 2018

I have to agree that unless you are running crucially time sensitive/critical programs or network systems, you should ignore 1 second time differences.

( I presume you are running something like the following in a command box on both pc's, to see the difference ?

w32tm /stripchart /computer:time.windows.com /samples:5

-this may or may not give you an indication of why you might be getting the difference, but still not worth pursuing further for a few seconds difference. )

SteveCase · 08 Nov 2018

Thanks for your comments. I had come to the same conclusion - i.e. not worth losing sleep over. It is probably more of an OCD thing - irritating but not going to cause anything I normally do to grind to a halt. In any case I now have another problem which is more significant - msconfig freezes when I try to apply any changes, but I'll start a new thread for that one.