Ongoing Time-Service Warning (Event 134)

Hi BoomerM3

Do you use a specific DNS?

Have you tried flushing the DNS? I might actually try these four commands, the first one for sure.

Use a Command Prompt(admin) or Powershell(admin)

Do not key in info in brackets, there for your information.

ipconfig /flushdns (Clear the dns cache)
nbtstat -RR (release and refresh NetBIOS names)
netsh int ip reset (reset ip settings)
netsh winsock reset (Reset Winsock Catalog)


Ken

I read error 134 is a DNS issue and I saw in your opening post that you are not having any DNS issues.

There is a tutorial on switching DNS which would totally rule out DNS in my opinion. Option 2 is easy and easy to undo.

Change IPv4 and IPv6 DNS Server Address in Windows

Is the base time on your machine correct, that is the time in your BIOS?

An in place repair / upgrade fixes a lot of issues. If you are using V1803 it is an inplace repair, older versions it is an upgrade. The process is non destructive but I always recommend members have a back up of their personal date.

Repair Install Windows 10 with an In-place Upgrade

Yes but I was just asking as older CMOS batteries can either lose time or outright reset themselves.

Will be interesting to see results.

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?

May sound crazy

Have you tried another user profile?

Found this article, you likely have already seen but just in case.

https://www.thewindowsclub.com/windo...on-fails-error

Any thoughts on doing inplace repair.

I should have asked in begining... when did this start? What changes were made or what outages occurred around this time?