Windows 10: Why is *LOCALSERVICENONETWORKFIREWALL....* & *SERVICE HOST: DIAGNOSTIC POLICY....* taking...

Why is *LOCALSERVICENONETWORKFIREWALL....* & *SERVICE HOST: DIAGNOSTIC POLICY....* taking so much CPU and MEMORY and DISK ?I tried restarting windows defend service but it didn't got fixed... and I want to ask one more question what if I disable these services and delete them? are they really important ?will my pc be affected in a bad way from that? Here are 2 screen shots of my problem...

:)

 

Diagnostic Policy Service

Check
[FIX] Service Host: Diagnostic Policy Service High CPU Usage In Windows 10

MP

 

Diagnostic Policy Service is Taking up CPU

Hi,

My name is Mohammed Shuaib, an Independent Advisor and I'm here to assist you with the issue of Diagnostic Policy consuming high CPU. Please follow the steps in the below article to fix the issue.

https://www.kapilarya.com/fix-service-host-diag...

Let me know the status after performing the above.

Regards

Shuaib

Independent Advisor

Standard Disclaimer: There are links to non-Microsoft websites. The pages appear to be providing accurate, safe information. Watch out for ads on the sites that may advertise products frequently classified as a PUP (Potentially Unwanted Products). Thoroughly
research any product advertised on the sites before you decide to download and install it.

 

The Diagnostic Policy Service is not running

Hi,

To resolve this issue, launch the command prompt as Admin and enter
these:

• Type " net localgroup Administrators /add networkservice " then press Enter.
• Type " net localgroup Administrators /add localservice " then press Enter.

Also, we need to make sure that the following services are started.

1. Press Windows key
+ R.

2. On the dialog box, type services.msc

3. Under Services (Local)
list, find the services: Diagnostic policy, Diagnostic Service, Diagnostic system host.

4. Check the status of the services is started or not.

5. If the services are not started, you can
Right Click a status and Start a service.

6. Restart your computer.

Please post back with the result for further assistance.