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 No comments

113 answers

Sort by: Oldest
  1. Anonymous
    2016-02-22T13:46:52+00:00

    I had missed your post while writing the other posts.

    What do I do now?

    Was this answer helpful?

    0 comments No comments
  2. Anonymous
    2016-02-22T13:48:29+00:00

    leap indicator: 3 (last minute has 61 seconds)

    the status is 0 (unspecified)

    last successful sync time 2/22/2016  6:58:25 AM

    with the unspecified it is still malfunctioning?

    Status is 0 unspecified... or Stratum: 0 (unspecified)?

    John

    Was this answer helpful?

    0 comments No comments
  3. Anonymous
    2016-02-22T13:48:51+00:00

    I ran the microsoft fixit once again.

    It did not require a reboot.

    Was this answer helpful?

    0 comments No comments
  4. Anonymous
    2016-02-22T14:22:50+00:00

    ![](http://fud.community.services.support.microsoft.com/Fud/FileDownloadHandler.ashx?fid=a665c0b3-01f9-4776-9bea-625c3004ec6b)

    I think this is telling me that you have Group Policies in place on the time service, you should disable all the time service GPO's.

    Error message when you run the "w32tm /resync" command to synchronize Windows Server 2003 or Windows SBS to an external time source: "The computer did not resync because no time data was available"

    Written for Server 2003 but the time service is mostly unchanged in Windows 7 and this would also apply.

    After you disable the GPO's reset the time service again.  It would be a good idea to reboot or manually trigger a policy refresh with the gpupdate command at the command line after you disable the GPO's as some group policies do not refresh immediately.

    John

    Was this answer helpful?

    0 comments No comments
  5. Anonymous
    2016-02-22T15:03:48+00:00

    I've not yet worked with GPO's.  The default settings with the pre-installed windows 7 professional are likely in place.![](http://fud.community.services.support.microsoft.com/Fud/FileDownloadHandler.ashx?fid=8a612b07-15bb-44bb-9600-75e991b3cfa2)

    I have not yet rebooted but will reboot after this post.

    Was this answer helpful?

    0 comments No comments