One of my Win10 machines has a large time offset, in the order to weeks (its a VM that gets unpaused on request).
In the age of short-lived SSL certificates, it is crucial for many (web-based) operations to have correct time set. For precision reasons (and because I don't want to be bothered to "manually" remember the actual time) I'd like to use NTP.
Unfortunately, because the time offset is so large, when synching to an NTP server the time is either adjusted very slowly or discarded altogether, (making the time practically unusable until the next reboot).
So I thought about doing something like:
- set the time manually to something approximately the wall-clock time
- enable automatic time synchronization (NTP), to do the final adjustments
Unfortunately, the system is playing tricks on me, as this is what's actually happening:
- I unpause the machine; it has a time of e.g.
- I login, right-click the clock, select "change time and date"
- I switch off the
automatic time synchronisation(as it was enabled in the paused machine)
- I click on
- I set the date to approx the current date, e.g.
- I close the window via the
Applybutton, and see how the (almost) correct is displayed in the task-bar
- I switch on the
automatic time synchronisationagain, to get the minutes and seconds right
- the spinning wheel is displayed for a few seconds and then...
- the time is restored to the old wrong value of
What is going on here?
After a couple of minutes the time will eventually synchronize to the NTP server (it's working fine).
But how can I sync to the NTP-server instantaneously? I really don't want to wait a couple of minutes to be able to use the machine, as the machine's sole purpose is to provide a clean environment to try out small things quickly.