B
Burt Harris (MSFT retired)
Time synchronization has been working well for years, but started failing almost a month ago. I think this is a problem with the server time.windows.com. Here's the error message in context:
Solutions proposed in earlier questions (dating back to 2014) don't solve the problem, the time service is running on my machine. It seems like connectivity to time.windows.com is down.
C:\WINDOWS\system32>tracert time.windows.com
Tracing route to time.microsoft.akadns.net [40.81.188.85]
over a maximum of 30 hops:
1 7 ms 5 ms 7 ms 10.0.0.1
2 * * * Request timed out.
3 * * * Request timed out.
4 * * * Request timed out.
5 * * * Request timed out.
6 * * * Request timed out.
7 * * * Request timed out.
8 * * * Request timed out.
9 * * * Request timed out.
10 * * * Request timed out.
11 ^C
Continue reading...
Solutions proposed in earlier questions (dating back to 2014) don't solve the problem, the time service is running on my machine. It seems like connectivity to time.windows.com is down.
C:\WINDOWS\system32>tracert time.windows.com
Tracing route to time.microsoft.akadns.net [40.81.188.85]
over a maximum of 30 hops:
1 7 ms 5 ms 7 ms 10.0.0.1
2 * * * Request timed out.
3 * * * Request timed out.
4 * * * Request timed out.
5 * * * Request timed out.
6 * * * Request timed out.
7 * * * Request timed out.
8 * * * Request timed out.
9 * * * Request timed out.
10 * * * Request timed out.
11 ^C
Continue reading...