Re: WMIdiag, what have I learned

Tech Tip: Click here to run a free scan for Windows Errors and optimize PC performance



And the following Application errors
-------
Event Type: Error
Event Source: WinMgmt
Event Category: None
Event ID: 4
Description:
Failed to load MOF C:\WINDOWS\MICROSOFT.NET\FRAMEWORK\V1.1.4322\ASPNET.MOF while recovering repository file.
---------------
Event Type: Error
Event Source: WinMgmt
Event Category: None
Event ID: 4
Description:
Failed to load MOF C:\WINDOWS\MICROSOFT.NET\FRAMEWORK\V2.0.50727\ASPNET.MOF while recovering repository file.
--------------------
Event Type: Warning
Event Source: WinMgmt
Event Category: None
Event ID: 64
Description:
The named section Global\Wmi Provider Sub System Counters, was created with insufficient size, this could constitute a Denial of Service attack.
----------------
Event Type: Warning
Event Source: WinMgmt
Event Category: None
Event ID: 43
Description:
WMI ADAP failed to connect to namespace \\.\root\cimv2 with the following error: 0x80040154
--------------------
Event Type: Warning
Event Source: WinMgmt
Event Category: None
Event ID: 60
Description:
WMI ADAP was unable to process the performance libraries: 0x80041001
-------------------
Event Type: Error
Event Source: PerfDisk
Event Category: None
Event ID: 2001
Description:
Unable to read the disk performance information from the system. Disk performance counters must be enabled for at least one physical disk or logical volume in order for these counters to appear. Disk performance counters can be enabled by using the Hardware Device Manager property pages. Status code returned is data DWORD 0.
----------------------
Event Type: Warning
Event Source: WinMgmt
Event Category: None
Event ID: 64
Description:
The named section Global\Wmi Provider Sub System Counters, was created with insufficient size, this could constitute a Denial of Service attack.
---------------------
--------------------

Wesley Vogel wrote:
Repairing and re-registering the WMI
http://windowsxp.mvps.org/repairwmi.htm

Skip down to: Rebuilding the WMI Repository

.