Restart the Windows Management Instrumentation service, then open Event Viewer → Applications and Services Logs → Microsoft → Windows → WMI-Activity → Operational, find the ClientProcessId in recent errors, and look that PID up in Task Manager. Update or remove that app.

What's going on

WMI (Windows Management Instrumentation) is a core service. Monitoring tools, RGB and fan utilities, antivirus, OEM support apps and management agents poll it constantly. When one polls too often, or a provider misbehaves, WmiPrvSE.exe uses lots of CPU.

Ending the process only helps briefly, because Windows starts it again when the next request arrives.

How it shows up

  • WMI Provider Host using 10–100% CPU in Task Manager.
  • Fans spin up and the PC lags.
  • Usage spikes at regular intervals.

Why it happens

  • A monitoring, RGB, OEM or antivirus app querying WMI heavily.
  • A buggy WMI provider from a driver package.
  • Corrupted WMI repository (rare).

How to fix it, step by step

  1. Restart the serviceIn an administrator PowerShell window run Restart-Service winmgmt -Force (it also restarts the services that depend on it).
  2. Find the client appIn Event Viewer open the WMI-Activity/Operational log, select recent errors and note ClientProcessId. In Task Manager → Details, add the PID column to find which program it is.
  3. Update or remove that appCommon culprits are hardware monitors, RGB/fan control, vendor 'support assistant' apps and old antivirus.
  4. Clean boot testRun msconfig → Services → hide Microsoft services → Disable all, restart, and re-enable in halves to find the cause.
  5. Check the repositoryRun winmgmt /verifyrepository as administrator. Only if it reports an inconsistency, run winmgmt /salvagerepository.

Command

winmgmt /verifyrepository

Elevated Command Prompt. This only checks the WMI repository and changes nothing.

Check it's fixed: WmiPrvSE.exe stays near 0% CPU at idle.

Keeping it from coming back

Run only one hardware-monitoring or RGB utility and keep vendor apps updated.