w32tm /query /status.....malfunctioning clock time work up and fix

Anonymous
2016-02-19T17:23:14+00:00

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.

0 comments

113 answers

Sort by: Oldest
Most helpful Newest Oldest
  1. Anonymous
    2016-02-23T01:46:01+00:00

    I entered regedit

    ![](http://fud.community.services.support.microsoft.com/Fud/FileDownloadHandler.ashx?fid=f341431b-191b-45ae-9264-7d1f853b3c22)

    how do you find what you had posted earlier with the regedit command?

    Was this answer helpful?

    0 comments
  2. Anonymous
    2016-02-23T02:23:52+00:00

    You're not at the right key, the key is:

    HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\services\W32Time\Config

    The key is divided into segments, separated by backslashes:

    HKEY_LOCAL_MACHINE\

    SYSTEM\

    CurrentControlSet\

    services\

    W32Time\

    Config

    ![](http://fud.community.services.support.microsoft.com/Fud/FileDownloadHandler.ashx?fid=a9879764-e524-4873-9a0f-3e5fba4cdf75)

    Navigate down to the \Services\W32Time key:

    ![](http://fud.community.services.support.microsoft.com/Fud/FileDownloadHandler.ashx?fid=c1487f13-e11a-4f9f-8e73-3b1351163d2b)

    You can also search the registry (you can copy and paste):

    ![](http://fud.community.services.support.microsoft.com/Fud/FileDownloadHandler.ashx?fid=cbce9bf6-3128-46cf-aeaa-537b1ca566fe)

    Just be careful when you edit the registry, you have certainly read warnings before, improper edits could cause serious damage that could prevent your machine from booting or require you to reinstall the operating system.  As long as you are careful and know what the key/values are for you can edit with confidence, in this case, providing that you are at the right key, all you can do is screw up the time sync service...but it's already screwed up and you know how to reset it with the W32tm /unregister /register commands.

    John

    Was this answer helpful?

    0 comments
  3. Anonymous
    2016-02-23T02:43:05+00:00

    all of the boxes are checked

    whats screwed up :) :) :)

    what have you found so far with these checks?

    ![](http://fud.community.services.support.microsoft.com/Fud/FileDownloadHandler.ashx?fid=53dd89bb-dfa3-436c-819c-30bc59dbf8f5)

    Was this answer helpful?

    0 comments
  4. Anonymous
    2016-02-23T03:13:10+00:00

    all of the boxes are checked

    whats screwed up :) :) :)

    what have you found so far with these checks?

    That nothing much has changed since Windows 2000 and that I have just about if not exhausted all the check points I can think of.  Try clean boot and see if things work better.  Keep looking in the Event Log for clues, look for warnings and errors from the Time-Service, this may point you in the right direction.  If the clock problem persists in clean boot or in safe mode then I really don't think this is a Windows (or Linux) problem.  If you have available time you could always boot the computer and access the BIOS and leave it idle there for a sufficiently long period of time (a day or so) and see if the BIOS loses/gains time while the computer is booted.

    John

    Was this answer helpful?

    0 comments
  5. Anonymous
    2016-02-23T03:26:26+00:00

    did all of the checks pass?

    it's unclear as to the cause of the time drift?

    under msconfig there are 24 boxes, 12 on each view

    ![](http://fud.community.services.support.microsoft.com/Fud/FileDownloadHandler.ashx?fid=c360fd29-0522-4a77-ae22-d041e7cb216e)

    ![](http://fud.community.services.support.microsoft.com/Fud/FileDownloadHandler.ashx?fid=ba56ddce-128c-401b-9d13-d126b73f1964)

    would you start by updating the time first, then unchecking 12, then rebooting, then checking for one hour to see the amount of drift?

    then update the time again then recheck the 12 and then uncheck the other 12 and reboot, then check for one hour to see the amount of drift?

    If the drift is the same for each then nothing further to do?

    Only if the drift is significantly reduced or eliminated is there something left to do by splitting the 12 into 6 each and then see what happens?

    Does the time need to be reset at all?  Would it be the same to just leave it as is and record the numbers?

    or start with unchecking all for the hour and see what happens with the drift?

    Was this answer helpful?

    0 comments