This started with a clean install of Win 10. Then it was OK for a week. Then EVERY day since then - end of June 2018.
Windows Time Service was set to Automatic (Trigger Start). I Changed it to JUST Automatic.
Not worth the risk of an in-place repair.
Your machine but have only seen one issue from an inplace repair and that machine was already in trouble.
Can you go into your windows update history and see what was install a week after clean. Particularly drivers at bottom of history.
Win 10 install on 6/8/2018.
First error on 6/15/2018
Next error on 6/22/2018
Next error on 7/1/2018
Then every day.
On 6/30/2018 installed KB43388853 - "This update makes stability improvements for the Windows 10, version 1803 servicing stack."
If you check your app list and sort it by install date anything coincide?
Have you run sfc /scannow (To a command prompt(admin)
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?
Yes, I get Event 37. Every day.
If your explanation is correct, why doesn't everyone get the warning message?
My explanation was pure guess. It may be way off base. But who knows? Everybody's configuration is different. A lot goes on during Windows initialization - a lot of high priority things that probably slow down other things with lower priority. I would not expect DNS name resolution for a time server to be high on the priority list.
The important thing is that within a few seconds Windows successfully connects with it's time service and gets the correct time. The fact that the first attempt fails is not a big deal.
BTW, I just rebooted before writing this response. I did not get the DNS timeout. Maybe it happens for me only on waking from sleep. Or maybe it's just random.
My error occurs ONLY on the morning startup. All later boots apparently do the time check.
The 'error' is not important, but it would be nice to cure it...
When you say start up in the morning is this a power on startup or an awake from sleep / hibernation?
If it is a power on failure then would you mine disabling Windows Fast Startup as a test. Windows Fast Startup is used when powering on.
Turn On or Off Fast Startup in Windows 10
I totally power off at night. Fast startup is turned off.
I would call it a cold start in the morning.
Quote