WMI Event Messages

The following list lists events supported by WMI logs in Windows Vista and later operating systems.

WBEM_MC_REPOSITORY_INCONSISTENT

1073747424 (0x400015E0)

The Windows Management Instrumentation Service detected an inconsistency with the WMI repository in the directory %windir%\system32\wbem\repository and was not able to recover it. The WMI repository will now be deleted, A new repository will be created based on the auto-recovery mechanism.

WBEM_MC_PROVIDER_SUBSYSTEM_LOCALSYSTEM_PROVIDER_LOAD

2147483711 (0x8000003F)

A provider, %1, has been registered in the Windows Management Instrumentation namespace %2 to use the LocalSystem account. This account is privileged and the provider may cause a security violation if it does not correctly impersonate user requests.

WBEM_MC_MOF_NOT_LOADED_AT_RECOVERY

3221225476 (0xC0000004)

Error %1 encountered when trying to load MOF %2 while recovering .MOF file marked with autorecover.

WBEM_MC_CANNOT_ACTIVATE_FILTER

3221225482 (0xC000000A)

Event filter with query "%2" could not be reactivated in namespace "%1" because of error %3. Events cannot be delivered through this filter until the problem is corrected.

WBEM_MC_INVALID_EVENT_PROVIDER_QUERY

3221225493 (0xC0000015)

Event provider %1 attempted to register a syntactically invalid query "%2". The query will be ignored. The query can be corrected by examining the WMI repository with CIM studio and updating the permanent subscriptions for the listed provider and query. If the permanent subscription is created with MOF file coming with an installed product, the application vendor must be contacted to correct the faulty registration.

WBEM_MC_INVALID_EVENT_PROVIDER_INTRINSIC_QUERY

3221225494 (0xC0000016)

Event provider %1 attempted to register an intrinsic event query "%2" in %3 namespace for which the set of target object classes could not be determined. The query will be ignored.

WBEM_MC_EVENT_PROVIDER_QUERY_TOO_BROAD

3221225495 (0xC0000017)

Event provider %1 attempted to register query "%2" in %3 namespace which is too broad. Event providers cannot provide events that are provided by the system. The query will be ignored. Contact the application vendor.

WBEM_MC_EVENT_PROVIDER_QUERY_NOT_FOUND

3221225496 (0xC0000018)

Event provider %1 attempted to register query "%2" whose target class "%3" in %4 namespace does not exist. The query will be ignored.

WBEM_MC_EVENT_PROVIDER_QUERY_NOT_EVENT

3221225497 (0xC0000019)

Event provider %1 attempted to register query "%2" whose target class "%3" is not an event class. The query will be ignored. Contact the application vendor.

WBEM_MC_WBEM_CORE_FAILURE

3221225500 (0xC000001C)

Failed to Initialize WMI Core or Provider SubSystem or Event SubSystem with error number %1. This could be due to a badly installed version of WMI, WMI repository upgrade failure, insufficient disk space or insufficient memory.

WBEM_MC_ADAP_CONNECTION_FAILURE

3221225515 (0xC000002B)

Windows Management Instrumentation ADAP failed to connect to namespace %1 with the following error %2.

WBEM_MC_ADAP_PERFLIB_PUTCLASS_FAILURE

3221225520 (0xC0000030)

Windows Management Instrumentation ADAP was unable to save object %1 in namespace %2 because of the following error %3.

WBEM_MC_ADAP_UNABLE_TO_ADD_WIN32PERF

3221225530 (0xC000003A)

Windows Management Instrumentation ADAP was unable to create the Win32_Perf base class in %1:Result=%2.

WBEM_MC_ADAP_UNABLE_TO_ADD_WIN32PERFRAWDATA

3221225531 (0xC000003B)

Windows Management Instrumentation ADAP was unable to create the Win32_PerfRawData base class %1.

WBEM_MC_REPOSITORY_FAILED_TO_START

3221231073 (0xC00015E1)

The Windows Management Instrumentation Service failed to load the repository files under the directory %windir%\system32\wbem\repository. This can be caused by a corruption in the repository files, security settings on this directory, lack of disk space, or other system resource issues such as lack of memory. If this error occurs each time the computer is restarted then the administrator on this computer may need to stop WMI Service, review the security setting on this folder and files under this folder, and run WMIDiag to validate the health of Windows Management Instrumentation.

WBEM_MC_WBEM_REQUIRES_ENCRYPTION_DENIED

3221231077 (0xC00015E5)

Access to the %1 namespace was denied because the namespace is marked with RequiresEncryption but the script or application attempted to connect to this namespace with an authentication level below Pkt_Privacy. Change the authentication level to Pkt_Privacy and run the script or application again.

WBEM_MC_WBEM_REQUIRES_ENCRYPTION_ASYNC_DENIED

3221231078 (0xC00015E6)

Windows Management Instrumentation Service could not deliver results asynchronously for %1 namespace. The namespace is marked with RequiresEncryption but WinMgmt could not establish a secure connection back to the client computer. Ensure there is a trust relationship between the client and server computers so that the client recognizes the server computer account.

WBEM_MC_WBEM_HOST_KILLED

3221231084 (0xC00015EC)

Windows Management Instrumentation has stopped WMIPRVSE.EXE because a quota reached a warning value. Quota: %1 Value: %2 Maximum value: %3 WMIPRVSE PID: %4.

WBEM_MC_WBEM_REPFILESNOTFOUND

3221231086 (0xC00015EE)

During the service startup, the Windows Management Instrumentation service was unable to locate the repository files. A new repository will be created based on the auto-recovery mechanism.

WBEM_MC_WBEM_STARTED_SUCESSFULLY

3221231087 (0xC00015EF)

Windows Management Instrumentation Service started successfully.

WBEM_MC_WBEM_CORE_PSS_ESS_INITIALIZED

3221231089 (0xC00015F1)

Windows Management Instrumentation Service subsystems initialized successfully.

WBEM_MC_WBEM_SERVICE_INIT_FAILURE

3221225501 (0xC000001D)

Error number %1 was returned in trying to initialize Windows Management Instrumentation Service. This could be due to a badly installed version of WMI, WMI repository upgrade failure, insufficient disk space or insufficient memory.

WBEM_MC_WBEM_REPOSITORY_RECREATED

3221231088 (0xC00015F0)

Windows Management Instrumentation Repository successfully recreated using Autorecovery mechanism.

Requirements

See also

WMI Events

WMI Troubleshooting