Windows XP WMI has encountered a problem and needs to close.
I repeatedly get an error box stating "WMI has encountered a problem and needs to close". Is there a fix for this? I am running XP Media Edition 2004 with service pack 3 installed.1 person needs an answerI do too
July 23rd, 2010 7:44pm

I repeatedly get an error box stating "WMI has encountered a problem and needs to close". Is there a fix for this? I am running XP Media Edition 2004 with service pack 3 installed.Try scanning first to eliminate a viral infection then proceed with the rest of the steps:Scan for malware from here:SuperAntispyware - Freehttp://www.superantispyware.com/superantispywarefreevspro.htmlMalwarebytes© Corporation - Anti-Malwarehttp://www.malwarebytes.org/mbam/program/mbam-setup.exeThis can happen if you are running a third party software which may be damaged/corrupted and they are running on Start up, so try to run the system in a clean state to see if it is a running Application on start up causing this!How to perform a clean boot procedure to prevent background programs from..:http://support.microsoft.com/kb/331796If you are experiencing problems with the WMI service you might need tomanually stop and restart the service. Before doing so you should enableWMI’s verbose logging option. This provides additional information in the WMIerror logs that might be useful in diagnosing the problem. To enable verboselogging using the WMI control, do the following:1. Open the Computer Management MMC snap-in and expand Services andApplications.2 .Right-click WMI Control and click Properties.3 .In the WMI Control Properties dialogue box, on the Logging tab, selectVerbose (includes extra information for Microsoft troubleshooting) and thenclick 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 Sizeto 4000000. After enabling verbose logging try stopping the WMI service by typing thefollowingOpen a run command prompt:net stop winmgmt If the net stop command fails you can force the service to stop by typingthis:winmgmt /kill Important. If you are running Windows XP or Windows Server 2003 the WMIservice runs inside a process named Svchost; this process contains otherservices as well as WMI. Because of that, you should not try to stopSvchost;if you succeed, you’ll stop all the other services running in that processaswell. Instead, use net stop winmgmt or winmgmt /kill in order to stop justthe WMI service.You can then restart the service by typing the following command:net start winmgmtIf the service does not restart try rebooting the computer to see if thatcorrects the problem.If it does not, then continue reading. The WMI Diagnosis Utility -- Version 2.0http://www.microsoft.com/downloads/details.aspx?familyid=d7ba3cd6-18d1-4d05-b11e-4c64192ae97d&displaylang=enAlso you can download the DiagWMI from here and some good solutions on thepage:http://windowsxp.mvps.org/repairwmi.htm.= Open a run command and try to re-register these DLLs:regsvr32 hnetcfg.dllregsvr32 netcfgx.dllregsvr32 netman.dllregsvr32 atl.dllregsvr32 netshell.dll Also try repair the WMI as described here:http://groups.google.com/group/microsoft.public.win32.programmer.wmi/msg/1da6ab3690bc75a0What Firewall/Anti-Virus you have running on your machine?Let us know your progress.nass -- http://www.nasstec.co.uk
Free Windows Admin Tool Kit Click here and download it now
July 24th, 2010 3:44pm

This topic is archived. No further replies will be accepted.

Other recent topics Other recent topics