RE: High CPU usage by WMIPRVSE.EXE

"Steve S" wrote:

I'm running XP Pro w/sp2 My computer will lock up/ run real slow. it
will take over 2 hours to shut down after I request a restart ( has taken
over 1o hurs some times). it will run ok from 15 minutes to 3 hours then will
lock up again. Looking at the task manager the program wmiprvse.exe is
using about 100% of the cpu when the system locks up. i have applied the
hotfix to fix the memory leak problem, still have the real slow problem. Is
there a way to find out which program is running in wmiprvse that is causing
the system to run slow? or a way to remove WMI from my computer?


This can be a memory leak or a printer problem. Did you install any
hardware/software recently?.

Go through these cleaning steps:
1... Click start >> Control Panel >> Double Click Network and Internet
Connections >> Double click Internet Options, on the IE Properties window
you will see these Options:
General | Security | Privacy | Content | Connections | Programs
| Advanced .

Click on General Tab (1st Tab on the left) and you will see a Button called
[ Clear History ..] click on it to clear your History caches, then click on
[Delete Files..] to delete Internet Files created over the time, click on [
Delete Cookies...] to delete your cookies left by visiting websites.

= Then try to Disable the Add-Ons on your Browser somehow installed on your
browser, On how to disable the Add-ons follow this:
Click on Programs Tab and then click the Manage Add-Ons Button there Disable
the None/Not Verified Plug-ins/Add-ons ( you need to Renable them one-by-one
later and see which is the culprit .
How to manage Add-Ons:

Scan for malware from here:

Scan for viruses with an up2date Anti-virus software (full scan).

the legit files for WMi located here:

There a backup copy here
or here:

The Wmiprvse.exe process may experience a memory leak when WMI services and
RPC services are extensively used in Windows XP with Service Pack 2

WMI search:
MS:: <Quote>
Stopping and Starting the WMI Service

If you are experiencing problems with the WMI service you might need to
manually stop and restart the service. Before doing so you should enable
WMI’s verbose logging option. This provides additional information in the WMI
error logs that might be useful in diagnosing the problem. To enable verbose
logging using the WMI control, do the following:
1.Open the Computer Management MMC snap-in and expand Services and
2.Right-click WMI Control and click Properties.
3.In the WMI Control Properties dialog box, on the Logging tab, select
Verbose (includes extra information for Microsoft troubleshooting) and then
click OK.
Alternatively, you can modify the following registry values:
•Set HKEY_LOCAL_MACHINE\Software\Microsoft\WBEM\CIMOM\Logging to 2.
•Set HKEY_LOCAL_MACHINE\Software\Microsoft\WBEM\CIMOM\Logging File Max Size
to 4000000.
After enabling verbose logging try stopping the WMI service by typing the
Open a run command prompt:
net stop winmgmt

If the net stop command fails you can force the service to stop by typing
winmgmt /kill

Important. If you are running Windows XP or Windows Server 2003 the WMI
service runs inside a process named Svchost; this process contains other
services as well as WMI. Because of that, you should not try to stop
if you succeed, you’ll stop all the other services running in that process
well. Instead, use net stop winmgmt or winmgmt /kill in order to stop just
the WMI service.

You can then restart the service by typing the following command:
net start winmgmt

If the service does not restart try rebooting the computer to see if that
corrects the problem.
If it does not, then continue reading.
MS:: </Quote>

"WMI Diagnosis Utility"

Systems that have changed the default Access Control List permissions on the
%windir%\registration directory may experience various problems after you
install the Microsoft Security Bulletin MS05-051 for COM+ and MS DTC
Also you can download the DiagWMI from here and some good solutions on the

= Open a run command and try to re-register these DLLs:
regsvr32 hnetcfg.dll
regsvr32 netcfgx.dll
regsvr32 netman.dll
regsvr32 atl.dll
regsvr32 netshell.dll
Also try repair the WMI as descriped here:
What Firewall/Anti-Virus you have running on your machine?.
Let us know.