Many thanks, matter is solved!
Many thanks, matter is solved!
Shawn, thank you for your advice about the Win 10 time fix. The Control Panel advice worked. The other suggestions like going to properties of Windows Time acomplished nothing but the CP did. I should have known. Control Panel, in my opinion is much better than Settings
I'm glad it could help jss3rd, and welcome to Ten Forums.
Hi folks, new member here. Useful post, many thanks. Just thought I'd leave some thoughts, some of which Brink, as a MVP might feel like passing on to MS.
I don't change machines very often, but two years ago I acquired a new machine running w8 which I immediately updated to 8.1. I upgraded to 10 in Feb. 2016. My old machine which I still have ran XP and never seemed to have any problems synchronising time. So with the new machine I didn't even think about it (and therefore had pure default config) until I'd had it about 4 months when I discovered it was a good minute fast. Surprised, I started to investigate and discovered a lot of debate about the problem. Settings seemed to be all right so I just did a manual sync through the Internet time tab in CP and forgot about it.
8 months later I again discovered the machine was over a minute fast, so had a closer look. Discovered the time service was not set to launch automatically (why not, Microsoft??), so did that. But even so, after much messing around with reg values, including specialpollinterval, the machine is still not doing the job properly.
What I find particularly annoying is that Windows' messages do not reflect the reality. If I open the CP Internet time dialogue it gaily says "The clock was synchronized on ..." date and time, whereas I know that it wasn't. From what I've seen in discussions, this message may just mean that it tried. Well that's a lot of use! Another example : This morning I used the command line to synchronise manually, and got the reply, "The computer did not resync because no time data was available", whereas in fact it did resync. The machine had again been over a minute fast and is now at the correct time.
So I'm going for the following option : use Task scheduler to launch a little cmd which will
- record current system time;
- do a resync and
- again record current system time,
all to a little log file where I can easily keep an eye on it.
One other remark : it seems to me silly to have all the Windows machines in the world going by default to time.windows.com. NTP is naturally susceptible to the quality of the connection. Since we know the user's country, why not use a time server in that country? [Edit : I know you get redirected to some other more local source but the redirection is haphazard and far more complicated than just going straight to a local time server.]
I use Dimension 4 and select a server near you. It is free software http://www.thinkman.com/dimension4/
It keeps the clock correct to millisecond accuracy. Why would I care? Because in some Ham Radio Digital modes it MUST be accurate and the builtin MS time service is NOT!!
Thanks MPSAN for the tip but I don't need anything sophisticated at the moment.
I scheduled a little cmd to run once a week. It ran this morning successfully. Here's the log result (system response is in French)
Current time: 30/07/2016 11:52:40,03
Envoi de la commande de resynchronisation … l'ordinateur local
La commande s'est terminée correctement.
Current time: 30/07/2016 11:52:26,35
So the machine had gained 14" since last week (about the same as my oven!!) but is now back on track.
OK, glad it was resolved for you.