WMI Problem

I am using Windows XP SP3. Each time the system boots several dialog boxes pop up, one after another as I click on them. Some say "WMI encountered a problem and needed to close." It comes up several times. Then I get those dialog boxes that ask whether or not I want to report it to Microsoft. They eventually go way after I've clicked them all away.

What does this mean and how do I fix it?

Thankls
pcwizz1Asked:
Who is Participating?
 
becraigConnect With a Mentor Commented:
Detailed steps:
Click Start -> Run and type CMD.EXE
Note: In Windows Vista, you need to open an elevated Command Prompt window. To do so, click Start, click All Programs, click Accessories, right-click Command Prompt, and then click Run as administrator.

Type this command and press Enter:

net stop winmgmt

Using Windows Explorer, rename the folder %windir%\System32\Wbem\Repository. (For example, %windir%\System32\Wbem\Repository_bad). %windir% represents the path to the Windows directory, which is typically C:\Windows.

Switch to Command Prompt window, and type the following and press ENTER after each line:
net start winmgmt
EXIT

For Windows XP Service Pack 2 and Service Pack 3

Click Start, Run and type the following command:
rundll32 wbemupgd, UpgradeRepository

This command is used to detect and repair a corrupted WMI Repository. The results are stored in the setup.log (%windir%\system32\wbem\logs\setup.log) file.



Re-registering the WMI components

The .DLL and .EXE files used by WMI are located in %windir%\system32\wbem. You might need to re-register all the .DLL and .EXE files in this directory. If you are running a 64-bit system you might also need to check for .DLLs and .EXE files in %windir%\sysWOW64\wbem.

To re-register the WMI components, run the following commands at the command prompt:

    CD %windir%\system32\wbem
    for /f %s in ('dir /b /s *.dll') do regsvr32 /s %s
    for /f %s in ('dir /b *.mof') do mofcomp %s

Registering WMI Service itself

Open the command console, type "net stop winmgmt". When you get the warning that other services need to be stopped type 'Y' and continue.

Open 'My Computer' and then go to the folder '%SystemRoot%\System32\WBEM\Repository' and delete that folder.

Reboot your system.

After you login, open the command console, and type the following commands in order:

    winmgmt /clearadap
    winmgmt /kill
    winmgmt /unregserver
    winmgmt /regserver
    winmgmt /resyncperf

reprinted from
http://www.madanmohan.com/2010/10/rebuilding-wmi-repository.html
0
 
becraigCommented:
You can follow the XP steps here to rebuild your wmi repository:

http://www.madanmohan.com/2010/10/rebuilding-wmi-repository.html

An actual screen shot of your errors would help but this walkthrough should clean up most if not all of your wmi issues.
0
 
pcwizz1Author Commented:
Thank you your answers. But before I do any of this can someone please tell me what WMI is and what it's used for?

Thanks
0
 
becraigCommented:
The purpose of WMI is to define a proprietary set of environment-independent specifications which allow management information to be shared between management applications. WMI prescribes enterprise management standards and related technologies for Windows that work with existing management standards, such as Desktop Management Interface (DMI) and SNMP. WMI complements these other standards by providing a uniform model. This model represents the managed environment through which management data from any source can be accessed in a common way.

Excerpt from:
http://en.wikipedia.org/wiki/Windows_Management_Instrumentation

This should give you all you need.
0
 
koit_tech1Commented:
Does this solution work for Windows 2003? Currently we experiencing high CPU 100% each time WMI error pops up.
0
Question has a verified solution.

Are you are experiencing a similar issue? Get a personalized answer when you ask a related question.

Have a better answer? Share it in a comment.

All Courses

From novice to tech pro — start learning today.