Domain Time is Fast

Kyle Haviland 21 Reputation points
2021-05-18T14:05:13.857+00:00

My time runs fast by 4 minutes. I've tried changing to a government time server. It doesn't change. How do I fix it?

C:\Users\Administrator.WSCHD>w32tm /query /status
Leap Indicator: 0(no warning)
Stratum: 1 (primary reference - syncd by radio clock)
Precision: -6 (15.625ms per tick)
Root Delay: 0.0000000s
Root Dispersion: 10.0000000s
ReferenceId: 0x4C4F434C (source name: "LOCL")
Last Successful Sync Time: 5/18/2021 8:44:16 AM
Source: Local CMOS Clock
Poll Interval: 6 (64s)

C:\Users\Administrator.WSCHD>w32tm /query /configuration
[Configuration]

EventLogFlags: 2 (Local)
AnnounceFlags: 10 (Local)
TimeJumpAuditOffset: 28800 (Local)
MinPollInterval: 6 (Local)
MaxPollInterval: 10 (Local)
MaxNegPhaseCorrection: 172800 (Local)
MaxPosPhaseCorrection: 172800 (Local)
MaxAllowedPhaseOffset: 300 (Local)

FrequencyCorrectRate: 4 (Local)
PollAdjustFactor: 5 (Local)
LargePhaseOffset: 50000000 (Local)
SpikeWatchPeriod: 900 (Local)
LocalClockDispersion: 10 (Local)
HoldPeriod: 5 (Local)
PhaseCorrectRate: 7 (Local)
UpdateInterval: 100 (Local)

[TimeProviders]

NtpClient (Local)
DllName: C:\Windows\SYSTEM32\w32time.DLL (Local)
Enabled: 1 (Local)
InputProvider: 1 (Local)
CrossSiteSyncFlags: 2 (Local)
AllowNonstandardModeCombinations: 1 (Local)
ResolvePeerBackoffMinutes: 15 (Local)
ResolvePeerBackoffMaxTimes: 7 (Local)
CompatibilityFlags: 2147483648 (Local)
EventLogFlags: 1 (Local)
LargeSampleSkew: 3 (Local)
SpecialPollInterval: 3600 (Local)
Type: NT5DS (Local)

NtpServer (Local)
DllName: C:\Windows\SYSTEM32\w32time.DLL (Local)
Enabled: 1 (Local)
InputProvider: 0 (Local)
AllowNonstandardModeCombinations: 1 (Local)

VMICTimeProvider (Local)
DllName: C:\Windows\System32\vmictimeprovider.dll (Local)
Enabled: 1 (Local)
InputProvider: 1 (Local)

C:\Users\Administrator.WSCHD>w32tm /stripchart /computer:time.windows.com /dataonly
Tracking time.windows.com [40.119.6.228:123].
The current time is 5/18/2021 9:24:18 AM.
09:24:18, -262.7220698s
09:24:20, -262.7264162s
09:24:22, -262.7307705s
09:24:24, -262.7233308s

C:\Users\Administrator.WSCHD>w32tm /config /manualpeerlist:time.windows.com /syncfromflags:MANUAL
The command completed successfully.

C:\Users\Administrator.WSCHD>w32tm /config /update
The command completed successfully.

C:\Users\Administrator.WSCHD>w32tm /resync
Sending resync command to local computer
The command completed successfully.

C:\Users\Administrator.WSCHD>w32tm /stripchart /computer:time.windows.com /dataonly
Tracking time.windows.com [40.119.6.228:123].
The current time is 5/18/2021 9:25:39 AM.
09:25:39, -262.6665133s
09:25:41, -262.6558668s
09:25:43, -262.6557630s
09:25:45, -262.6414714s

Still 4 minutes off....

Windows for business | Windows Server | User experience | Other
0 comments No comments
{count} votes

Accepted answer
  1. Anonymous
    2021-05-18T19:03:02.61+00:00

    Ok, some new information. You can uncheck this one, then via PowerShell confirm. May want to reboot after making changes.

    97627-image.png

    --please don't forget to Accept as answer if the reply is helpful--

    0 comments No comments

17 additional answers

Sort by: Most helpful
  1. Anonymous
    2021-05-18T14:21:06.653+00:00

    Assuming this is the PDC emulator you could;

    w32tm /unregister
    net stop w32time
    w32tm /register
    net start w32time
    w32tm /config /manualpeerlist:<ntp ip address> /syncfromflags:manual /reliable:yes /update
    net stop w32time
    net start w32time
    then check
    w32tm /query /source
    w32tm /query /configuration

    https://tf.nist.gov/tf-cgi/servers.cgi

    --please don't forget to Accept as answer if the reply is helpful--

    0 comments No comments

  2. Kyle Haviland 21 Reputation points
    2021-05-18T14:40:34.047+00:00

    Unfortunately, time is still off four minutes.

    C:\Users\Administrator.WSCHD>w32tm /unregister
    W32Time successfully unregistered.

    C:\Users\Administrator.WSCHD>net stop w32time
    The Windows Time service is stopping.The service name is invalid.

    More help is available by typing NET HELPMSG 2185.

    C:\Users\Administrator.WSCHD>w32tm /register
    W32Time successfully registered.

    C:\Users\Administrator.WSCHD>net start w32time
    The Windows Time service is starting.
    The Windows Time service was started successfully.

    C:\Users\Administrator.WSCHD>w32tm /config /manualpeerlist:time-d-g.nist.gov /syncfromflags:manual /reiable:yes /update
    The following arguments were unexpected:
    /reiable:yes

    C:\Users\Administrator.WSCHD>w32tm /config /manualpeerlist:"time-d-g.nist.gov" /syncfromflags:manual /reiable:yes /update
    The following arguments were unexpected:
    /reiable:yes

    C:\Users\Administrator.WSCHD>w32tm /config /manualpeerlist:"time-d-g.nist.gov" /syncfromflags:manual /reliable:yes /update
    The command completed successfully.

    C:\Users\Administrator.WSCHD>net stop w32time
    The Windows Time service is stopping.
    The Windows Time service was stopped successfully.

    C:\Users\Administrator.WSCHD>net start w32time
    The Windows Time service is starting.
    The Windows Time service was started successfully.

    C:\Users\Administrator.WSCHD>w32time /query /source
    'w32time' is not recognized as an internal or external command,
    operable program or batch file.

    C:\Users\Administrator.WSCHD>w32tm /query /source
    time-d-g.nist.gov

    C:\Users\Administrator.WSCHD>w32tm /query /configuration
    [Configuration]

    EventLogFlags: 2 (Local)
    AnnounceFlags: 5 (Local)
    TimeJumpAuditOffset: 28800 (Local)
    MinPollInterval: 6 (Local)
    MaxPollInterval: 10 (Local)
    MaxNegPhaseCorrection: 172800 (Local)
    MaxPosPhaseCorrection: 172800 (Local)
    MaxAllowedPhaseOffset: 300 (Local)

    FrequencyCorrectRate: 4 (Local)
    PollAdjustFactor: 5 (Local)
    LargePhaseOffset: 50000000 (Local)
    SpikeWatchPeriod: 900 (Local)
    LocalClockDispersion: 10 (Local)
    HoldPeriod: 5 (Local)
    PhaseCorrectRate: 7 (Local)
    UpdateInterval: 100 (Local)

    [TimeProviders]

    NtpClient (Local)
    DllName: C:\Windows\SYSTEM32\w32time.DLL (Local)
    Enabled: 1 (Local)
    InputProvider: 1 (Local)
    AllowNonstandardModeCombinations: 1 (Local)
    ResolvePeerBackoffMinutes: 15 (Local)
    ResolvePeerBackoffMaxTimes: 7 (Local)
    CompatibilityFlags: 2147483648 (Local)
    EventLogFlags: 1 (Local)
    LargeSampleSkew: 3 (Local)
    SpecialPollInterval: 3600 (Local)
    Type: NTP (Local)
    NtpServer: time-d-g.nist.gov (Local)

    NtpServer (Local)
    DllName: C:\Windows\SYSTEM32\w32time.DLL (Local)
    Enabled: 1 (Local)
    InputProvider: 0 (Local)
    AllowNonstandardModeCombinations: 1 (Local)

    VMICTimeProvider (Local)
    DllName: C:\Windows\System32\vmictimeprovider.dll (Local)
    Enabled: 1 (Local)
    InputProvider: 1 (Local)

    C:\Users\Administrator.WSCHD>w32tm /config /update
    The command completed successfully.

    C:\Users\Administrator.WSCHD>w32tm /resync
    Sending resync command to local computer
    The command completed successfully.

    0 comments No comments

  3. Anonymous
    2021-05-18T14:57:32.877+00:00

    May need to be patient. Read on here about possible correction algorithm.
    https://learn.microsoft.com/en-us/windows-server/networking/windows-time-service/windows-time-service-tools-and-settings#configure-computer-clock-reset

    --please don't forget to Accept as answer if the reply is helpful--

    0 comments No comments

  4. Kyle Haviland 21 Reputation points
    2021-05-18T14:59:43.397+00:00

    I did the above last Friday. The time still is not accurate. Is there anyway to force a negative offset?

    I'm currently doing all of the above on the domain controller. Have run gpudate and am still experiencing fast time.

    0 comments No comments

Your answer

Answers can be marked as Accepted Answers by the question author, which helps users to know the answer solved the author's problem.