Windows Management Instrumentation (WMI) Problem

[Drew Cooper [MS]]

You might have better luck on the WMI newsgroup.

--
Drew Cooper [MS]
This posting is provided "AS IS" with no warranties, and confers no rights.

"Jerry R. George Jr." <talk2...@jerrygeorge.com> wrote in message
news:017001c2b041$695e0f50$d5f82ecf@TK2MSFTNGXA12...
> I'm having difficulty w/the Windows Management
> Instrumentation (WMI) service under WindowsXP. When I
> attempt to view the "Advanced" settings of my wireless
> network card, an error appears as follows:
> Windows cannot display the properties of this connection.
> Windows Management Instrumentation (WMI) might be
> corrupted.
>
> I followed the steps given at
> http://support.microsoft.com/default.aspx?scid=kb;en-
> us;319101 but have had no luck in solving the problem.
>
> Is there any way to reinstall WMI?

[Ivan Brugiolo [MSFT]]

/////////////////////////////////////////////////

This is an emergency manual re-install procedure that you can try,
and it's from a previous post on this newsgroup.
Use it at your own risk.
It has helped so far with non known failure cases.

/////////////////////////////////////////////

Try to remove, if they are there

HKLM\Software\Microsoft\OLE
"EnableRemoteConnect"="Y"
"LegacyAuthenticationLevel"=dword:00000001
"LegacyImpersonationLevel"=dword:00000001

Some legacy application from the Win9x era are known to create
those key that impair many DCOM functionality on the machine.

check the following registry key
HKLM\System\Software\Microsoft\WBEM\CIMOM\AutoRecover MOFs
it is supposed to have a list of *.MOF and *.MFL files, and it MUST begin
with cimwin32.mof
There are ISP connection kits and .NET Framework setups known to corrupt
this key.
Please delete it content if it appears to have few files or if it appears
corrupt.

check if in %windir%\system32\wbem there are about 40 MOF files.
There are certain applications known to delete them.
If you don't have them, please recover them from the CD of WinXP.
The complete list is found in %windir%\IFM\wbemoc.inf

Please check the following:
-1- that you system path has still %windir%\system32\wbem in it.
-2- that there are no wmiutils.dll and wbemcomn.dll in the system path that
comes before the one in system32\wbem.

c:\>for %i in ("wbemcomn.dll") do (echo %~$PATH:i)
c:\>for %i in ("wmiutils.dll") do (echo %~$PATH:i)

check if the wbemutils.dll registered as a COM component comes from the OS
or from Visual Studio and/or other development tools.
Make sure the OS Supplied one is used.

enable versbose logging
HKLM\Software\Microsoft\WBEM\CIMOM:Logging(REG_SZ) = "2"
HKLM\Software\Microsoft\WBEM\CIMOM:Logging File Max Size (REG_SZ) =
"4000000"

find the PID of the svchost.exe process running WinMgmt
HKLM\Software\Microsoft\WBEM\CIMOM:ProcessID (REG_DWORD) = XXX

crosss check the pid
c:\>tlist -s | findstr /i winmgmt
it must be the same as above, if not, trust tlist.exe more than the registry
for the steps below.

you can get "tlist .exe" and "kill.exe" (needed later)
from http://www.microsoft.com/ddk/debugging/installx86.asp

c:\>sc config winmgmt start= disabled
c:\>kill -f XXX <<<<<<<<<<<<<<<<<<<<<<<<<<<<<< pid obtained before
c:\>cd /D %windir%\system32\wbem
c:\WIN\system32\wbem>rmdir /s /q repository
c:\WIN\system32\wbem>rmdir /s /q Logs
c:\WIN\system32\wbem>mkdir Logs
c:\WIN\system32\wbem>for /R %i in (*.dll) do (regsvr32 /s %i)
c:\WIN\system32\wbem>regsvr32 /s fastprox.dll
c:\WIN\system32\wbem>for /R %i in (*.exe) do (%i -regserver) <<<<<<<<<<<<<
this will open wbemtest and/or wmic.exe. Just close it
c:\WIN\system32\wbem>sc config winmgmt start= auto
c:\WIN\system32\wbem>regsvr32 wbemupgd.dll <<<<<<<<<<<<<< this can take 30
seconds to 2 minutes
c:\WIN\system32\wbem>net start server && net start workstation && net start
AudioSrv && net start termservice

after this, please start %windir%\system32\wbem\wbemtest.exe,
and connect to the root\cimv2 namespace.

If something goes wrong, please read the logs under
%windir%\system32\wbem\Logs, just to see if there is something obviousely
wrong there.

--
This posting is provided "As Is" with no warranties, and confers no rights.
Use of included script samples are subject to the terms specified at
http://www.microsoft.com/info/cpyright.htm

"Drew Cooper [MS]" <dc...@online.microsoft.com> wrote in message
news:OlkMVQHsCHA.1668@TK2MSFTNGP09...