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: Most helpful
Most helpful Newest Oldest
  1. Anonymous
    2016-02-25T13:45:22+00:00

    This notebook has HP sanitizer.......I had not learned to use it and will need to learn how to use it now.......you may have seen it in the earlier post of the HP client security.  The flash drive is 256 gb and the hard drive is 1 tb so I could move everything but would prefer not to move the operating system.

    If you are satisfied with the present state of the Windows installation you can make an image of the operating system drive and then restore the image back to the new laptop when you get it (or do a Bare Metal Restore using using a Windows backup) this is usually a piece of cake when the replacement computer is of the same make and model, even if the model is slightly different but of the same make this often works quite well, models from the same series are usually no problem.  In your case if the HP replacement laptop is the same model you should have no problems restoring an image.  There are caveats to this:

    1. If you have an Windows OEM version (which you most probably have) you cannot use the image on a different make of computer the Windows license will be invalid and you will not be able to activate it, for example you can't restore an HP image to a Dell computer.  If you have a retail version you would be able to activate the license on a different make of computer.
    2. If the new computer hardware is significantly different than the old one the image may not work well or may not boot at all, often times an in-place upgrade (repair install) and installing proper chipset and other hardware drivers will overcome this problem.
    3. You carry existing known or unknown problems along with you to the new hardware.

    Restoring from an image or with a Windows bare metal restore is often the preferred option for well maintained well tuned Windows installations, as we all know a lot of time can go into setting up a Windows installation to suit ones needs and preferences and starting again from scratch is often a dreaded endeavour.  On the other hand if the installation is problematic or has much detritus starting from a clean state may be a better option.

    John

    Was this answer helpful?

    0 comments
  2. Anonymous
    2016-02-25T11:49:00+00:00

    You will have to use the SSD manufacturer's  Secure Erase Tool for this, hard disk wiping tools are not suitable for use on SSD.  Being that you want to wipe the operating system drive you will need a tool that can be booted on a flash drive or CD, or maybe there is an HP tool can do this.

    John

    Was this answer helpful?

    0 comments
  3. Anonymous
    2016-02-25T11:33:25+00:00

    After fresh boot it displayed that the service has not been started

    net start w32time was successful in starting the service.

    It started though with unspecified and source the CMOS clock.

    Change date and time update was successful adnd the /query /status was switched to an IP address

    The time service is working properly, it wasn't started because by default it is set to start manually and it is set to sync every 7 days.  If you were to keep the computer you would have to change the sync frequency to keep the malfunctioning CMOS clock within acceptable error.  This could be done either by modifying the SpecialPollInterval value at HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\services\W32Time\TimeProviders\NtpClient or by using a scheduled task with the w32tm /resync command.

    John

    Was this answer helpful?

    0 comments