Windows 10: WMI provider host two running at the same time and sometimes a third one.

I've already launched into safe mode and all WMI provider hosts are in the same file folder in safe mode and without safe mode, WMI provider host barely uses over 0.1 - 5.0 percent of the cpu and I just wanna know why there are two at the same time and sometimes a third pops up but then goes away. Here you can see three but a third one leaves soon enough and leaves two remaining. Any answers? All WMI provider hosts are located under this folder C:/Windows/System32/wbem

:)

 

WMI Provider Host - Windows 10

Hi,



Thank you for writing to Microsoft Community Forums.



We understand your concern as you the WMI provider host use high CPU of the PC. Usually, WMI Host Provider doesn’t use much usage of the CPU. It will use the CPU when any software or script that asks for some information via WMI. High usage of the
CPU is just the sign that another software is seeking for some information or requesting any data via WMI.



However, the high usage of the CPU for a long time for WMI is an indication that something is wrong because WMI Provider Host doesn’t occupy the resources of the CPU for a long time.



In this scenario, we would suggest you to perform these methods and check if the issue is fixed.



Method 1: Restart the WMI Provider Host Service

1. Press Windows key + R to launch the
   Run command, then type Services.msc and press the
   Ok.
   
2. Scroll down all the services and find
   Windows Management Instrumentation and then Right click on it and select
   Properties.
   
3. Set the startup type to Automatic and then restart the service.

Method 2: Restart other WMI provider Host related Services

1. Click on Start Menu and type CMD, right click on
   CMD icon and select Run as administrator.
   
2. In the Command Prompt Window type the following command and press
   Enter after each command.
   

• net stop iphlpsvc
  
• net stop wscsvc
  
• net stop Winmgmt
  
• net start Winmgmt
  
• net start wscsvc
  
• net start iphlpsvc
  

3. Restart your computer and check if the WMI provider Host having high CPU usage



Method 3: Uninstall the Components and Drivers that causes the Problem

1. Press Windows + XKey and select
   Event Viewer.
   
2. Click on the View Button that appears on the top of the Menu and then click on
   Show Analytic and Debug Logs.
   
3. On the left pane, navigate to this path Applications and Service Logs > Microsoft > Windows > WMI Activity > Operational log. Now Mark or Note down the Item that listed as an
   Error
   
4. Now press the Windows Logo Key +
   X simultaneously, then select Task Manager.
   
5. Now, click on the Service tab and Find the processes with the Matching IDs as seen in
   Event Viewer in the column of PID when You Locate or Find these Process then
   Uninstall or Disable those service.
   
6. Restart the PC and check

You may also refer this article and check if that helps to fix the issue:
High CPU usage by WMIPRVSE.EXE process at regular intervals in Windows



Note: Important this section, method, or task contains steps that tell you how to modify the registry. However, serious problems might occur if you modify
the registry incorrectly. Therefore, make sure that you follow these steps carefully. For added protection, back up the registry before you modify it. Then, you can restore the registry if a problem occurs.

Follow the steps to take
backup of registry.




Let us know how it goes.



Aditya Roy

Microsoft Community – Moderator

 

WMI Provider Host

"WMI Provider Host" will not stop; is running continuously.

 

WMI Provider Host

I have a desktop PC running Windows 10 that, several times a day, spikes up to 100% CPU usage. The culprit is WMI Provider Host, but I can't work out what's causing it to use so much.

It's been happening for weeks, and has had several reboots. Restarting services doesn't help. I tried to locate the source of the issue using the PID as detailed here - WMI Provider Host (WmiPrvSE.exe) High CPU Usage in Windows 10 - but it only pointed
to itself. It's causing major issues, rendering the PC practically unusable at random times.