w32tm /config /update: The command completed successfully
w32tm /query /source: Local CMOS clock
w32tm /query /status.....malfunctioning clock time work up and fix
![](data:image/svg+xml, %3Csvg xmlns='http://www.w3.org/2000/svg' height='64' class='font-weight-bold' style='font: 600 30.11764705882353px "SegoeUI", Arial' width='64'%3E%3Ccircle fill='hsl(128, 8%, 22%)' cx='32' cy='32' r='32' /%3E%3Ctext x='50%25' y='55%25' dominant-baseline='middle' text-anchor='middle' fill='%23FFF' %3EA%3C/text%3E%3C/svg%3E)
Anonymous
This mobile workstation was placed into use on 9/20/15 and has had persistent problems with incorrect time.
asdfasdfasdfasdfafd
Using windows 7 professional change date and time settings each of these settings were used to synchronize time: time.windows.com, time.nist.gov, time-nw.nist.gov, time-a.nist.gov and time-b.nist.gov.
All of these settings failed with progressive time delays using windows 7 professional.
Time synchronization was turned off and again the mobile workstation had progressive delayed time.
Often at approximately 1 minute and 15 to 20 seconds it would reset on its own to a few seconds delay with or without time synchronization.
The CMOS RTC battery was replaced and there was no change in the time delay problem.
A second operating system was used, Ubuntu.
Ubuntu was tested for 12 hours and it displayed time ahead on the time.is web site.
The computer manufacturer replaced the motherboard and the intel chip. The bios date and time were reset.
The first three days after the motherboard replacement the time delay was at its worst with over 5 minute delays.
On the third day there was a bios update.
After the bios update the mobile workstation malfunctioned as it did before the motherboard replacement. With windows 7 professional there was progressive delayed time up to approximately 1 minute and 15 to 20 seconds and then it would somehow reset itself. The mobile workstation was then rebooted to Ubunt to remoe windows 7 professional form the picture. This time Ubuntu was ran for approximately 36 hours. The time was always ahead. The rate of time ahead with Ubuntu seemed to be slower than the rate of time behind with windows 7 professional.
Using administrative command prompt I posted the results of the w32tm /query /status commands. The first one was with time synchronization off. The second one was after multiple configure internet time settings update now clicks. Multiple sfc /scannow were ran that indicated no integrity violations.
At this moment the time delay is 4 minutes and 39.1 seconds behind.
The latest w32tm /query /status displays: Leap Indicator: 3(last minute has 61 seconds).
What does this mean: last minute has 61 seconds?
What is Stratum and how come it changed to unspecified?
What is reference Id and how come it is now unspecified?
When the configure internet and time settings is viewed it displays next synchronization 2/25/2016 and it displays the clock was successfully synchronized with the time-nw.nist.gov on 2/19/2016 at 6:19 AM.
How come the date and time indicates a successful synchronized time on 2/19/2016 6:19 AM and the last few w32tm /query /status indicate the last successful sync time was on 2/18/2016 8:11:35 AM.
Windows for home | Previous Windows versions | Windows update
Locked Question. This question was migrated from the Microsoft Support Community. You can vote on whether it's helpful, but you can't add comments or replies or follow the question.
113 answers
Sort by: Newest
-
Anonymous
2016-02-22T22:17:43+00:00 -
Anonymous
2016-02-22T21:56:51+00:00 Look at the Windows Time service in the Services management console and make sure that it is set to Log On as shown here:
-
Anonymous
2016-02-22T21:44:37+00:00 how come it did not sync with the sync command?
Please issue the following commands, pressing <Enter> after each:
w32tm /config /update
w32tm /query /source
What does the /source command report?
Your clock is drifting by about 16 seconds or more per hour so in clean mode or safe mode you should find out in about an hour or so if the clock holds its time and if the problem is caused by software.
Forget about SFC /Scannow it will do nothing to fix your problem, it's a waste of time (no pun intended).
John
-
Anonymous
2016-02-22T20:50:55+00:00 how come it did not sync with the sync command?
It is now delayed to 27.9 seconds....that's about 10 to 15 seconds for the last hour
prior to the problems of the last few days with delays over 4 minutes it somehow would reset itself at about 1 min and 15 to 20 seconds.
For the hardware clock is there any way to test the hardware if problems are not detected with the onboard UEFI tests?
For windows is there any way to test if sfc /scannow finds no integrity violations?
The DISM commands with restore health don't work for windows 7 professional but the scanhealth command was ran.
It did not find any problems related to time in the CBS file.
What else can be done to work up this time problem on this new computer?
It has had time problems since its early use.
Figuring out how to save appropriate files then reinstalling windows would take me at least 8 to 12 hours. I was getting close to doing this just to report the findings to HP as they claim it is not a hardware problem. The HP support had thought it was the motherboard and replaced it. One upper level HP support stated that the problem with windows 7 and Ubuntu times indicates it is not the hardware. That did not make any sense to me.
So I am looking for something in the work up that can better define the problem.
In the clean boot would you look at the items checked and then uncheck half and then recheck and uncheck the other half? Then depending on that result decide if to divide again in half to narrow down? How long would you test the time delay for each step in the process?
-
Anonymous
2016-02-22T20:24:42+00:00 the time delay has progressed to 16.1 seconds behind:
The last sync was at 11.53AM, so in about 2 hours it drifted by 16.1 seconds, at that rate if it stays constant it will drift by about 193.2 seconds (3.22 minutes) per day. It doesn't appear to be a Windows problem, it seems that the hardware clock that can't keep proper time. Other than re-syncing at shorter intervals there is not much that the operating system can do.
Note that some applications (or malware) can cause the clock to gain or lose time, you can boot to safe mode or Clean Boot and see if the problem persists. If the problem is absent in Safe Mode or Clean Boot then there is something running in normal boot that psyches out the clock.
John