Windows 10: Extremely High CPU Usage - Service Host: DNS Client

My Windows Version: Version 1909 (OS Build 18363.535)

From time to time this process (in the title) will suddenly rise CPU usage, making everything extremely slow and even games from 1994 will play slowly, for example. Sometimes it subsides by itself, but sometimes I need to restart.

I'm at my wits end - I've search everywhere and all I can find are answers for previous OS or different processes that are hogging the CPU.





How do I fix this?

- - - Updated - - -

Bump

:)

 

Extremely High CPU Usage - Service Host: DNS Client

My Windows Version: Version 1909 (OS Build 18363.535)

From time to time this process (in the title) will suddenly rise CPU usage, making everything extremely slow and even games from 1994 will play slowly, for example. Sometimes it subsides by itself, but sometimes I need to restart.

I'm at my wits end - I've search everywhere and all I can find are answers for previous OS or different processes that are hogging the CPU.





How do I fix this?

- - - Updated - - -

Bump

 

Extremely High CPU Usage - Service Host: DNS Client

I have the same or similar issue apparently, and it's rendered my laptop completely unusable. It started happening randomly this week after trying to install a windows update. The only solution I got was to restore to before the update, just a temporary fix.

 

Extremely High CPU Usage - Service Host: DNS Client

You should try some anti-malware scans, since it could be caused by an infection, like being part of a botnet.

Norton Rescue Tools
Online Virus Scan from ESET

You could try http://nirsoft.net/utils/live_tcp_udp_watch.html to monitor DNS requests.
Close all internet related software and watch if there are too many requests via port 53.

Try this: Flush DNS Resolver Cache in Windows 10

You can also disable DNS Client, after you setup your DNS servers manually.

Change IPv4 and IPv6 DNS Server Address in Windows

Run CMD as admin and copy/paste to disable it, then restart.
Code:

To enable it back again: Run CMD as admin and copy/paste, then restart.
Code: