Last week a KB-article was released with “Suggested hotfixes for WMI related issue on Windows platforms”. It really recommend that you read it because WMI is critical to Configuration Manager, Group polices, Operations Manager and so on. As you all know without working WMI we cannot manage the systems out there.
I will deploy the following WMI stability hotfix in all my Windows 7 projects, note that is is updated for Windows 2008 R2 SP1 and Windows 7 SP1.
KB2465990 – 0x80041002 (WBEM_E_NOT_FOUND)” error occurs when you try to open a WMI namespace on a computer that is running Windows 7 or Windows Server 2008 R2″ I recommend that you have a look at it.
From the KB article:
Hotfix list for Windows Vista and Windows Server 2008
2464876 The WMI repository is corrupted on a computer that is running Windows Server 2008 or Windows Vista
http://support.microsoft.com/default.aspx?scid=kb;en-US;2464876 (http://support.microsoft.com/default.aspx?scid=kb;en-US;2464876)
973243 The default gateway is missing on a computer that is running Windows Server 2008 or Windows Vista after the computer restarts if the default gateway is set by using the Netsh command
http://support.microsoft.com/default.aspx?scid=kb;EN-US;973243 (http://support.microsoft.com/default.aspx?scid=kb;EN-US;973243)
Hotfix list for Windows 7 and Windows Server 2008 R2
2465990 “0x80041002 (WBEM_E_NOT_FOUND)” error occurs when you try to open a WMI namespace on a computer that is running Windows 7 or Windows Server 2008 R2
http://support.microsoft.com/default.aspx?scid=kb;en-US;2465990 (http://support.microsoft.com/default.aspx?scid=kb;en-US;2465990)
2492536 Msinfo32.exe takes a long time to display or export system information on a computer that has many MSI-X-supported devices and that is running Windows 7 or Windows Server 2008 R2
http://support.microsoft.com/default.aspx?scid=kb;en-US;2492536 (http://support.microsoft.com/default.aspx?scid=kb;en-US;2492536)
982293 The Svchost.exe process that has the WMI service crashes in Windows Server 2008 R2 or in Windows 7
http://support.microsoft.com/default.aspx?scid=kb;EN-US;982293 (http://support.microsoft.com/default.aspx?scid=kb;EN-US;982293)
974930 An application or service that queries information about a failover cluster by using the WMI provider may experience low performance or a time-out exception
http://support.microsoft.com/default.aspx?scid=kb;EN-US;974930 (http://support.microsoft.com/default.aspx?scid=kb;EN-US;974930)
Hotfix list for Windows Server 2003 SP2
2257980 “0x80041002 (WBEM_E_NOT_FOUND)” error code occurs when you try to open a WMI namespace on a computer that is running Windows Server 2003 SP2
http://support.microsoft.com/default.aspx?scid=kb;en-US;2257980 (http://support.microsoft.com/default.aspx?scid=kb;en-US;2257980) For all supported x86-based versions of Windows Server 2003
Hotfix list for Windows XP
933062 A hotfix is available that improves the stability of the Windows Management Instrumentation repository in Windows XP
http://support.microsoft.com/default.aspx?scid=kb;EN-US;933062 (http://support.microsoft.com/default.aspx?scid=kb;EN-US;933062)
The whole KB can be found here: http://support.microsoft.com/kb/2591403
I totally agree. WMI is critical to GP, SCCM and SCOM. I’ve seen many times where WMI corruption will cause SCCM clients to fail even in a Windows 7 environment using OSD.
Does this information still apply for today’s version of System Center 2012 and System Center 2012 SP1?
Hi,
As ConfigMgr 2012 uses WMI as well so if you are running on Windows 2008 r2, then they are still valid.
/Jörgen
We are getting lot of WMI erros on windows 2003 Systems after we upgrade to the sccm client sp1… Did any one have any idea