Fix: WMI Provider Host (WmiPrvSE.exe) High CPU Usage On Windows 10

WMI Provider Host WmiPrvSE is a Windows Host Management Process that is used by the Developers for Monitoring Purposes.

WMI Provider High CPU Usage
WMI Provider High CPU Usage

This behavior is usually seen on Production Environment After upgrading Windows 7 to 10 many of the users have noticed spike in CPU usage which makes the system lag, hot and slow. My personal guess is that the issue is caused by an unusual behavior of this service not following the patterns it is supposed to.

To fix this issue we will run some basic command on the command prompt and restart the Windows Management Instrumentation Service.

Restarting the Windows Management Instrumentation Service

Hold the Windows key on your keyboard and Press R. In the run dialog; type services.msc

servicesrun

From the services console; locate the Windows  Management Instrumentation Service, What i usually do is click on any of the service and then press the key to get to the services starting with the Word W. Then do a quick scan to locate the one i want.

WmiPrvSE

Now choose Restart to restart the service. You can also stop the service from here if you want but it is not recommended. So let it run and we’ll fix the High CPU Usage issue with this process.

Restart Other Associated Services

Once this is done, hover over your mouse to the bottom left corner onto the Start Button and do a (Right-Click) on it. A Contextual menu will open; choose Command Prompt (Admin) from here.

WmiPrvSE1

In the command prompt window that opens up; type the following commands one by one; after each command press the Enter key.

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

2015-10-26_040001

Once done; Reboot your PC and check. This should allow the process to drop significantly and the CPU will be back to its normal use. If not, proceed to the next method below.

Perform a Clean Boot to Identify a Faulty Application

It is possible that a certain application might be causing the high CPU usage by WMI Provide Host. Therefore, in this step, we will be performing a Clean boot and isolating the application that is causing the excessive usage. In a clean boot, only the services which are vital in the Boot process are loaded and extra services and applications are disabled. In order to perform a Clean Boot:

  1. Log in to the computer with an Administrator account.
  2. Press “Windows” + “R” to open up the “RUN” prompt.
    Opening Run Prompt
  3. Type in “msconfig” and press “Enter“.
    Running MSCONFIG
  4. Click on the “Services” option and uncheck the “Hide all Microsoft Services” button.
    Clicking on the “Services” tab and Un-checking the “hide all Microsoft Services” option
  5. Click on the “Disable All” option and then on “OK“.
    Clicking on the “Disable All” option
  6. Click on the “Startup” tab and click on the “Open Task Manager” option.
    Clicking on the “Open Task Manager” option
  7. Click on the “Startup” button in the task manager.
  8. Click on any application in the list that has “Enabled” written next to it and select the “Disable” option.
    Clicking on the “Startup” tab and selecting an application listed there
  9. Repeat this process for all applications in the list and restart your computer.
  10. Now your computer has been booted in the “Clean Boot” state.
  11. Check to see if the issue goes away.
  12. If the high CPU usage is no longer encountered it means that a third party application or service was causing it.
  13. Start by enabling one service at a time in the same manner and stop when the high CPU usage comes back.
  14. Reinstall the service/application by enabling which the high usage comes back or keep it disabled.

Locate the Process Using Event Viewer and Uninstall It

Open the Event Viewer. If you are using Windows 7 or earlier, search for Event Viewer in the Start Menu and then open it. If you are using Windows 8/8.1 or 10, simply press Windows Logo key + X to open the WinX Menu and then click on Event Viewer in the WinX Menu.

wmi provider host - 1

Click on View in the toolbar at the top of the Event Viewer window and enable the Show Analytic and Debug Logs option.

wmi provider host - 2

In the left pane of the window, navigate to Applications and Services Logs > Microsoft > Windows > WMI-Activity.

wmi provider host - 3

Double-click on WMI-Activity to expand its contents, and click on Operational in the list of its contents to open the WMI Provider Host’s operational logs.

Look for any errors, and when you find one, click on it to display its specifications at the bottom of the window.

Under the General tab of the specifications of the error you clicked on, look for the term ClientProcessId, and when you find it, note down or remember the number(s) – 1079, for example – that follow it.

wmi provider host - 4

Close the Event Viewer and open the Task Manager. Hold the Windows Key and Press R. In the Run Dialog, type taskmgr and click OK. Navigate to the Services tab and look for the service that has the same Process ID (PID) as the number(s) that followed the ClientProcessID term.

2015-12-11_120924

The service that has the corresponding Process ID is the culprit, so once you find it, immediately disable it and then go to Control Panel > Programs & Features and uninstall the program that the culprit service was for. Once the program has been uninstalled, WMI Provider Host should go back to using an extremely minimal amount of CPU.

Setting the WMI service to Demand

If your WMI service is constantly on a high CPU usage it’s possible that some of your program such as Discord is using the process. Follow this step to stop this from happening:-

  1. Search for Command Prompt and click “Run as administrator”.
  2. Once the Command Prompt is opened you will have to type the following commands one by one:-
    sc config Wmi start= demand
  3. Now restart your computer and check to see if the issue persists.

If none of the methods above worked for you at all it’s possible that there is a program conflicting with your WMI Process in that case you will have to clean boot your computer.

ABOUT THE AUTHOR

Kamil Anwar


Kamil is a certified MCITP, CCNA (W), CCNA (S) and a former British Computer Society Member with over 9 years of experience Configuring, Deploying and Managing Switches, Firewalls and Domain Controllers also an old-school still active on FreeNode.