3.0 Beta 8 access violation
Malk
running it in XP compatability mode and as admin with the same result.
Heres what is in my log:
100325 08:25:28 : Started logging
100325 08:25:28 : What's Running version:3.0.0.969
100325 08:25:28 : Sourcename~SourceLUID: User32 ~0x8157AD02:0x8157AD02
100325 08:25:28 : ***********************
100325 08:25:28 : Token groups (count: 12)
100325 08:25:28 : ***********************
100325 08:25:28 : None, enabled
100325 08:25:28 : Everyone, enabled
100325 08:25:28 : Administrators, owner
100325 08:25:28 : Users, enabled
100325 08:25:28 : INTERACTIVE, enabled
100325 08:25:28 : CONSOLE LOGON, enabled
100325 08:25:28 : Authenticated Users, enabled
100325 08:25:28 : This Organization, enabled
100325 08:25:28 : S-1-5-5-0-121141, logon ID
100325 08:25:28 : LOCAL, enabled
100325 08:25:28 : NTLM Authentication, enabled
100325 08:25:28 : High Mandatory Level, integrity enabled
100325 08:25:28 : ***********************
100325 08:25:28 : Privileges :
100325 08:25:28 : ***********************
100325 08:25:28 :
SeChangeNotifyPrivilege,SeImpersonatePrivilege,SeCreateGlobalPrivilege
100325 08:25:28 : Before retrieving information objects
100325 08:25:28 : Create Exception:WMIEnum.Create adding enum failed
WBEM_E_INVALID_CLASS:Win32_PerfFormattedData_PerfProc_Process
100325 08:25:28 : Stack trace:
ChristerF
The core problem here is this line:
WBEM_E_INVALID_CLASS:Win32_PerfFormattedData_PerfProc_Process
This means basically that the WMI class can't get instantiated for
some reason.
If you would run Microsofts own diagnostic utility, it would find that
your installation has an issue with instantiating certain classes:
http://www.microsoft.com/downloads/details.aspx?FamilyID=d7ba3cd6-18d1-4d05-b11e-4c64192ae97d&displaylang=en
The previous What's Running version (2.2) didn't use WMI at all, and
that is why that version may work for people who have a malfunctioning
WMI subsystem.
Thanks for your patience!
/Christer