How To Fix WMI Provider Host High CPU In Windows 11 (2026)
WMI Provider Host is the Windows process WmiPrvSE.exe, and it can show high CPU use for two different reasons.
Either one of the small add-on modules it loads is busy, or another program keeps sending it heavy requests.
This guide follows Microsoft’s own troubleshooting method to find which one it is, so you fix the cause instead of just ending the process.
Quick answer: what to check first
| What you see | What it usually means | What to do |
|---|---|---|
| WmiPrvSE.exe stays high on the Details tab | A provider inside it is busy, or a program keeps asking it questions | Follow steps 1 to 6 to find the program making the requests |
| CPU use comes in regular spikes | Something runs on a schedule, such as a monitoring tool or script | Match the spike times to the WMI-Activity log (step 6) |
| svchost.exe running Winmgmt is the busy one, not WmiPrvSE.exe | The WMI service itself is the one using CPU | Use step 4 to confirm, then step 8 if it shares a host |
| High use only while one program is open | That program is probably the one sending the queries | Close it or turn off its service to test (step 7) |
Important: Microsoft’s guide says there is no single fix, because the cause differs from one PC to the next.
What WMI Provider Host is
WMI stands for Windows Management Instrumentation, the part of Windows that lets programs and scripts ask the system about itself.
Microsoft identifies WMI Provider Host as the WmiPrvSE.exe process, which loads WMI providers, the small DLL files that answer those requests.
Microsoft’s article is written for Windows Server, but it states that the method applies to any Windows operating system, so the same steps work on Windows 11.
In most cases the CPU is used by WmiPrvSE.exe, and in a few cases by an svchost.exe process that hosts the WMI service, named Winmgmt.
Step 1: Find the busy WmiPrvSE.exe in Task Manager
- Press Ctrl, Shift and Esc together to open Task Manager.
- Select the Details tab.
- If there is no PID column, right-click any column heading, choose Select columns, and tick PID.
- Sort by Name and find the WmiPrvSE.exe row that is using the CPU.
- Write down its PID number.
There can be more than one WmiPrvSE.exe row, so the PID is how you tell them apart later.
To check the service host instead, open the Services tab, find Winmgmt, note its PID, right-click it, and choose Go to details.
Step 2: Note when the CPU use happens
Microsoft asks you to describe the pattern before changing anything.
- Is the use constant, intermittent, random or spiky?
- Does it happen at a set time, or at sign-in and sign-out?
- What else is running at that moment, such as scripts, monitoring tools or services?
Step 3: Graph the process in Performance Monitor
- Open an elevated Command Prompt and run
perfmon. - Select Performance Monitor, then select the plus button to open Add Counters.
- Expand Process, select ID Process, select all the WmiPrvse# instances, then choose Add and OK.
- Add % Processor Time for the WmiPrvse# instance whose ID Process value matches your PID.
- Delete the other instances so only the busy one stays on the graph.
The graph shows whether the use is steady or comes in bursts, which is the detail Microsoft says to record.
Step 4: Check whether svchost.exe is hosting WMI
Run this in an elevated Command Prompt to see which svchost.exe process hosts Winmgmt.
tasklist /svc /fi "Services eq Winmgmt"
If the PID in the result matches the busy process, the WMI service itself is the one using the CPU.
Step 5: See which provider is loaded
A single WmiPrvSE.exe can load several providers, and any one of them could be using the CPU.
Microsoft offers two ways to list them.
- Run its script that lists all running WMI providers.
- Run Process Explorer as administrator, open the properties of the WmiPrvSE.exe PID, and select the WMI Providers tab.
Microsoft’s example shows the provider MS_NT_EVENTLOG_PROVIDER in the root\CIMV2 namespace, loaded from ntevt.dll in the system32\wbem folder.
If the PID keeps changing because the process restarts, tasklist /m ntevt.dll finds the current PID by DLL name.
Step 6: Find the program sending the queries
Open Event Viewer and go to Applications and Services Logs, then Microsoft, then Windows, then WMI-Activity.
Event ID 5857 in the Operational log shows which WmiPrvSE.exe PID hosts a provider at that moment.
For the requests themselves, turn on the Trace log.
- In Event Viewer, select View, then Show Analytic and Debug Logs.
- Right-click Trace and choose Enable Log.
- Let the problem happen, then right-click Trace and choose Save All Events As.
Microsoft warns that this adds logging for nearly every event source, so turn it off when you finish.
Look for ExecQuery, ExecMethod, ExecQueryAsync and CreateInstanceEnum entries, which show the WMI class, the user and the ClientProcessId that sent the request.
Match that ClientProcessId to a program in Task Manager, Process Explorer or Process Monitor.
Which tool answers which question
| Question | Tool | Where |
|---|---|---|
| Which WmiPrvSE.exe is busy? | Task Manager | Details tab, PID column |
| Is the use steady or spiky? | Performance Monitor | Run perfmon, Process counters |
| Which provider is inside it? | Process Explorer | Properties, WMI Providers tab |
| Which program asks for the data? | Event Viewer | WMI-Activity, Trace log |
| Which calls happen most often? | WMIMon | Microsoft’s suggested capture tool |
Step 7: Test by turning off the suspect
Once you have a suspect, turn off its service or uninstall the program for a short test and watch whether the CPU use stops.
Microsoft’s examples include monitoring applications and services, System Center Configuration Manager processes such as policyhost.exe and Monitoringhost.exe, PowerShell scripts that run WMI queries, and any third-party application.
If the use drops, update, reconfigure or remove that program, and contact its maker about the query it sends.
Optional: move Winmgmt to its own svchost.exe
Use this only if the svchost.exe that hosts Winmgmt also hosts other services, because it separates them so you can see which one uses the CPU.
Run sc config Winmgmt type= own, restart the WMI service, and verify with tasklist /svc.
When you are done, run sc config Winmgmt type= share and restart the service again to go back to the normal setup.
Error codes you may see in the WMI log
Microsoft lists these codes for WMI problems, so search the event text for them.
| Code | Name |
|---|---|
| 0x80041003 | WBEM_E_ACCESS_DENIED |
| 0x80041004 | WBEM_E_PROVIDER_FAILURE |
| 0x80041011 | WBEM_E_PROVIDER_NOT_FOUND |
| 0x80041013 | WBEM_E_PROVIDER_LOAD_FAILURE |
What not to do
- Do not rebuild the WMI repository on your own, because Microsoft warns that WMI loses the data it has gathered unless Microsoft Support does it.
- Do not leave the Trace log turned on after you finish.
- Do not assume the process is a virus, since WMI Provider Host is a normal Windows component.
When to contact Microsoft support
If you cannot find the cause, Microsoft lists a data collection method for support cases using its TSS tool from aka.ms/getTSS.
You run it from an elevated PowerShell window while the problem is happening, keep it running for more than two minutes, and upload the zip file it creates after you open a case.
Sources: Microsoft: WMI high CPU usage troubleshooting, Microsoft: WMI connectivity and access scenario guide.
Related guides: find the app using your CPU in Task Manager, a slow Windows 11 PC, NVDisplay.Container.exe writing to the SSD.