Windows 10: Event ID 134 Time Service Error

Microsoft Team,


I believe that after months of trial and error research, I have found the source of the "Event ID 134 Time Service error on my 2 PC's.

It appears to occur only when the computers awakens from "Sleep Mode". It never seems to occur if the computers are completely shut down.


Just wandering if Microsoft is aware of this problem, and are working on a fix for it !


Here is a transcript of the error:


*********************************************************************************************************************************************************

Log Name: System
Source: Microsoft-Windows-Time-Service
Date: 1/4/2020 5:06:10 AM
Event ID: 134

Task Category: None

Level: Warning

Keywords:

User: LOCAL SERVICE

Computer: DESKTOP-10xxxx

Description:

NtpClient was unable to set a manual peer to use as a time source because of DNS resolution error on 'time.windows.com,0x9'. NtpClient will try again in 15 minutes and double the reattempt interval thereafter. The error was: No such host is known. 0x80072AF9

Event Xml:

<Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event">

<System>

<Provider Name="Microsoft-Windows-Time-Service" Guid="{06edcfeb-0fd0-4e53-acca-a6f8bbf81bcb}" />

<EventID>134</EventID>

<Version>0</Version>

<Level>3</Level>

<Task>0</Task>

<Opcode>0</Opcode>

<Keywords>0x8000000000000000</Keywords>

<TimeCreated SystemTime="2020-01-04T10:06:10.415885400Z" />

<EventRecordID>10778</EventRecordID>

<Correlation />

<Execution ProcessID="13668" ThreadID="11484" />

<Channel>System</Channel>

<Computer>DESKTOP-10xxxx

<Security UserID="S-1-5-19" />

</System>

<EventData Name="TMP_EVENT_MANUAL_PEER_DNS_ERROR">

<Data Name="ErrorMessage">No such host is known. 0x80072AF9</Data>

<Data Name="RetryMinutes">15</Data>

<Data Name="DomainPeer">time.windows.com,0x9</Data>

</EventData>

</Event>


Thank you for looking

indyiceman

:)

 

Ongoing Time-Service Warning (Event 134)

Every day, my Event Viewer shows the same warnings twice: Event 134, Time-service. The message is: "NtpClient was unable to set a manual peer to use as a time source because of DNS resolution error on 'time.windows.com,0x9'." I have tried most of the 'solutions' found on the internet and none resolve the error.

I have tried both 'time.windows.com' and 'time.nist.gov' and both settings report the error. The 0x9 is not part of the option. The system time is not wrong. I don't have any DNS errors on the system. I would like to eliminate the warning from the event viewer.

Anyone know what causes the error or if there is really a fix?

Thanks.

Peter

 

Ongoing Time-Service Warning (Event 134)

I, too, get this shortly after a reboot or when my PC wakes from sleep. And the, usually within 30 seconds, I get

Event ID: 37
The time provider NtpClient is currently receiving valid time data from time.windows.com,0x9 (ntp.m|0x9|0.0.0.0:123->52.173.193.166:123).

I have no idea how long Windows waits for a DNS response, but I assume either the Windows TCP/PI stack or my router gets overwhelmed with network requests when Windows first comes up but everything eventually gets straightened out.

Do you get the EventID 37?

 

Ongoing Time-Service Warning (Event 134)

In this folder there is a file called hosts (no extension) that can be opened with notepad.

C:\Windows\System32\drivers\etc

Each line should start with the # sign which means the line is commented out. ( Informational ).

Could you see what is in your hosts file. Here is a copy of mine. All lines have a #





What AV(s) are you using?