Solved Event ID 134 Time-Service

Windows 11 Pro 23H2 OS Build 22631.4890

I built a new PC two weeks ago. Every morning on startup Event Viewer logs Event ID 134 Time-Service:

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)

This only logs on startup, it never logs again all day so after the first error the NtpClient was able to connect. As stated it happens every morning at startup. It also happens if I change to "time.nist.gov" so that tells me the issue is not with Microsoft or NIST.

This error provide a guild {06edcfeb-0fd0-4e53-acca-a6f8bbf81bcb}.

I have went into the registry and disabled this guild from logging an error in:
HKEY_LOCAL_MACHINE\System\ControlSet001\Control\WMI\AutoLogger\EventLog-Application
HKEY_LOCAL_MACHINE\System\ControlSet001\Control\WMI\AutoLogger\EventLog-System
HKEY_LOCAL_MACHINE\System\CurrentControlSet\Control\WMI\AutoLogger\EventLog-Application
HKEY_LOCAL_MACHINE\System\CurrentControlSet\Control\WMI\AutoLogger\EventLog-Sysjtem

but it still logs every morning at startup.

I have searched the registry for this guild and with my limited knowledge have not found any other instances of this guild that would have anything to do with logging an error in Event Viewer.

Also this error logs at this same time I see the welcome screen. I press the start button and this error logs 19 seconds later, it takes 19 to 20 seconds to even see the welcome screen.
Does anyone know how I can get this to stop logging every morning?

I also looked in task scheduler and services.msc to see if I can set it to delay until after the PC boots all the way into Windows, but did not see any way to do it.

Also I have been using guilds and changing the registry in WMI\AutoLogger for the past 13 years with no issues and I keep accurate records of what I change in case I need to enable some guild I have disabled.

I have Windows Home. There seems to be no problem in any combination.







Description of the Windows Time Service

For anyone who searches for this issue.

In services.msc I changed "Windows Time" from "Manual" start to "Automatic Delayed" start. This changed also transferred the "Trigger" requirement included with "Manual" over to "Automatic Delayed".

This changed got rid of Event ID 134 Time-Service logging every timed the PC started.