| 0x4 | 在恢复使用 autorecover 标记的 .MOF 文件时，在尝试加载 MOF %2 时遇到错误 %1。 |
Error %1 encountered when trying to load MOF %2 while recovering .MOF file marked with autorecover. |
| 0xA | 由于错误 %3，无法在命名空间“%1”中重新激活查询“%2”的事件筛选器。在解决该问题之前，无法通过此筛选器传送事件。 |
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. |
| 0x15 | 事件提供程序 %1 尝试注册语法无效的查询“%2”。将忽略该查询。可以使用 CIM studio 检查 WMI 存储库并更新列出的提供程序和查询的永久订阅以纠正该查询。如果永久订阅是使用已安装产品自带的 MOF 文件创建的，则必须联系应用程序供应商以纠正错误的注册。 |
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. |
| 0x16 | 事件提供程序 %1 尝试在 %3 命名空间中注册固有事件查询“%2”，但无法为该查询确定目标对象类集。将忽略该查询。 |
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. |
| 0x17 | 事件提供程序 %1 尝试在 %3 命名空间中注册查询“%2”，但该查询的范围太大。事件提供程序无法提供由系统提供的事件。将忽略该查询。请与应用程序供应商联系。 |
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. |
| 0x18 | 事件提供程序 %1 尝试在 %4 命名空间中注册查询“%2”，但该查询的目标类“%3”不存在。将忽略该查询。 |
Event provider %1 attempted to register query \"%2\" whose target class \"%3\" in %4 namespace does not exist. The query will be ignored. |
| 0x19 | 事件提供程序 %1 尝试注册查询“%2”，但该查询的目标类“%3”不是事件类。将忽略该查询。请与应用程序供应商联系。 |
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. |
| 0x1C | 无法初始化 WMI 核心或提供程序子系统或事件子系统，错误号为 %1。这可能是由于未正确安装的 WMI 版本、WMI 存储库升级故障、磁盘空间或内存不足造成的。 |
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. |
| 0x1D | 尝试初始化 Windows Management Instrumentation 服务时返回错误号 %1。这可能是由于未正确安装的 WMI 版本、WMI 存储库升级故障、磁盘空间或内存不足造成的。 |
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. |
| 0x2B | 由于以下错误 %2，Windows Management Instrumentation ADAP 无法连接到命名空间 %1 |
Windows Management Instrumentation ADAP failed to connect to namespace %1 with the following error %2 |
| 0x30 | 由于以下错误 %3，Windows Management Instrumentation ADAP 无法在命名空间 %2 中保存对象 %1 |
Windows Management Instrumentation ADAP was unable to save object %1 in namespace %2 because of the following error %3 |
| 0x3A | Windows Management Instrumentation ADAP 无法在 %1 中创建 Win32_Perf 基类: 结果=%2 |
Windows Management Instrumentation ADAP was unable to create the Win32_Perf base class in %1:Result=%2 |
| 0x3B | Windows Management Instrumentation ADAP 无法创建 Win32_PerfRawData 基类 %1 |
Windows Management Instrumentation ADAP was unable to create the Win32_PerfRawData base class %1 |
| 0x3F | 已在 Windows Management Instrumentation 命名空间 %2 中注册提供程序 %1 以使用 LocalSystem 帐户。此帐户是特权帐户；如果没有正确模拟用户请求，该提供程序可能会导致违反安全策略。 |
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. |
| 0x41 | 正在启动 Windows Management Instrumentation (WMI)服务以还原 WMI 存储库 |
Windows Management Instrumentation (WMI) Service is starting to restore the WMI repository |
| 0x42 | Windows Management Instrumentation 服务已从以下备份存储库中恢复: %1。 |
The Windows Management Instrumentation Service has recovered from the following backup repository: %1. |
| 0x43 | Windows Management Instrumentation (WMI)服务正在为 WMI 存储库启动备份操作，并将数据复制到以下文件: %1 |
The Windows Management Instrumentation (WMI) Service is starting the backup operation for the WMI repository and is copying data to the following file: %1 |
| 0x44 | Windows Management Instrumentation 存储库备份操作已完成将数据复制到 %1 的操作，但出现错误 %2。 |
The Windows Management Instrumentation repository backup operation completed copying data to %1 with error %2. |
| 0x15E0 | Windows Management Instrumentation (WMI)服务检测到与以下目录中的 WMI 存储库不一致: %windir%\\system32\\wbem\\repository。WMI 服务无法恢复该存储库。现在将删除该 WMI 存储库，然后根据自动恢复机制创建新的存储库。 |
The Windows Management Instrumentation (WMI) service detected an inconsistency with the WMI repository in the following directory: %windir%\\system32\\wbem\\repository. The WMI service was not able to recover the repository. The WMI repository will now be deleted and a new repository will be created based on the auto-recovery mechanism. |
| 0x15E1 | Windows Management Instrumentation 服务无法加载 %windir%\\system32\\wbem\\repository 目录中的存储库文件。这可能是由于存储库文件损坏、此目录的安全设置、磁盘空间不足或其他系统资源问题(如内存不足)造成的。如果每次重新启动计算机时都会发生此错误，则此计算机的管理员可能需要停止 WMI 服务，检查此文件夹及其文件的安全设置，然后运行 WMIDiag 以检查 Windows Management Instrumentation 的运行状况 |
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 like lack of memory. If this error happens every time the machine is rebooted then the administrator on this machine 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 |
| 0x15E2 | Windows Management Instrumentation 服务检测到以下备份文件存在不一致: %1。 |
The Windows Management Instrumentation service detected an inconsistency in the following backup file: %1. |
| 0x15E4 | Windows Management Instrumentation 服务遇到错误 %2，无法从以下备份存储库中恢复: %1。 |
The Windows Management Instrumentation service encountered the error %2 and was not able to restore from the following backup repository: %1. |
| 0x15E5 | %1 命名空间是使用 RequiresEncryption 标志标记的。如果脚本或应用程序没有相应的身份验证级别，则可能会拒绝访问此命名空间。请将身份验证级别更改为 Pkt_Privacy，然后再次运行脚本或应用程序。 |
The %1 namespace is marked with the RequiresEncryption flag. Access to this namespace might be denied if the script or application does not have the appropriate authentication level. Change the authentication level to Pkt_Privacy and run the script or application again. |
| 0x15E6 | Windows Management Instrumentation 服务无法为 %1 命名空间异步提供结果。该命名空间是使用 RequiresEncryption 标记的，但 WinMgmt 无法建立返回到客户端计算机的安全连接。请确保在客户端和服务器计算机之间建立信任关系，以使客户端能够识别服务器计算机帐户。 |
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. |
| 0x15EB | Windows Management Instrumentation 服务检测到不一致的系统关机。 |
The Windows Management Instrumentation service has detected an inconsistent system shutdown. |
| 0x15EC | Windows Management Instrumentation 已停止 WMIPRVSE.EXE，因为配额达到警告值。配额: %1，值: %2，最大值: %3，WMIPRVSE PID: %4，此进程中承载的提供程序: %5 |
Windows Management Instrumentation has stopped WMIPRVSE.EXE because a quota reached a warning value. Quota: %1 Value: %2 Maximum value: %3 WMIPRVSE PID: %4 Providers hosted in this process: %5 |
| 0x15EE | 在服务启动期间，Windows Management Instrumentation 服务找不到存储库文件。将根据自动恢复机制创建新的存储库。 |
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. |
| 0x15EF | 已成功启动 Windows Management Instrumentation 服务 |
Windows Management Instrumentation Service started sucessfully |
| 0x15F0 | 已通过自动恢复机制成功重新创建 Windows Management Instrumentation (WMI)存储库。 |
The Windows Management Instrumentation (WMI) repository was successfully re-created by the auto-recovery mechanism. |
| 0x15F1 | 已成功初始化 Windows Management Instrumentation 服务子系统 |
Windows Management Instrumentation Service subsystems initialized successfully |
| 0x15FF | 已覆盖 WMI 互操作命名空间类“%1”。某些互操作方案可能无法正常工作。请从提升的命令提示符中执行以下命令以恢复行为: \"mofcomp %windir%\\system32\\wbem\\interop.mof\" 或对 %windir%\\system32\\wbem 及其子目录中的所有 interop.mfl 执行类似的 mofcomp 命令。 |
WMI interop namespace class \"%1\" has been overwritten. Some of the Interop scenarios might not work properly. Please issue following commands from elevated command prompt to restore the behavior.\"mofcomp %windir%\\system32\\wbem\\interop.mof\" and similarly mofcomp all the interop.mfl under %windir%\\system32\\wbem and its subdirectories. |
| 0x10000038 | 经典 |
Classic |
| 0x50000002 | 错误 |
Error |
| 0x50000003 | 警告 |
Warning |
| 0x50000004 | 信息 |
Information |
| 0x90000001 | Microsoft-Windows-WMI |
Microsoft-Windows-WMI |
| 0x90000002 | Application |
Application |
| 0x91000001 | Microsoft-Windows-WMI-Activity |
Microsoft-Windows-WMI-Activity |
| 0xB1000001 | GroupOperationId = %1；OperationId = %2；操作 = %3；ClientMachine = %4；用户 = %5；ClientProcessId = %6；NamespaceName = %7 |
GroupOperationId = %1; OperationId = %2; Operation = %3; ClientMachine = %4; User = %5; ClientProcessId = %6; NamespaceName = %7 |
| 0xB1000002 | GroupOperationId 的 ProviderInfo = %1；操作 = %2；ProviderName = %3；ProviderGuid = %4；路径 = %5 |
ProviderInfo for GroupOperationId = %1; Operation = %2; ProviderName = %3; ProviderGuid = %4; Path = %5 |
| 0xB1000003 | 停止 OperationId = %1 |
Stop OperationId = %1 |
| 0xB100000B | CorrelationId = %1；GroupOperationId = %2；OperationId = %3；操作 = %4；ClientMachine = %5；用户 = %6；ClientProcessId = %7；NamespaceName = %8 |
CorrelationId = %1; GroupOperationId = %2; OperationId = %3; Operation = %4; ClientMachine = %5; User = %6; ClientProcessId = %7; NamespaceName = %8 |
| 0xB100000C | GroupOperationId 的 ProviderInfo = %1；操作 = %2；HostID = %3；ProviderName = %4；ProviderGuid = %5；路径 = %6 |
ProviderInfo for GroupOperationId = %1; Operation = %2; HostID = %3; ProviderName = %4; ProviderGuid = %5; Path = %6 |
| 0xB100000D | 停止 OperationId = %1；ResultCode = %2 |
Stop OperationId = %1; ResultCode = %2 |
| 0xB100000E | OperationId = %1；操作 = %2；通道 = %3；消息 = %4 |
OperationId = %1; Operation = %2; Channel = %3; Message = %4 |
| 0xB100000F | OperationId = %1；操作 = %2；ErrorID = %3；ErrorCategory = %4；消息 = %5；TargetName = %6 |
OperationId = %1; Operation = %2; ErrorID = %3; ErrorCategory = %4; Message = %5; TargetName = %6 |
| 0xB1000010 | OperationId = %1；操作 = %2；ErrorID = %3；消息 = %4 |
OperationId = %1; Operation = %2; ErrorID = %3; Message = %4 |
| 0xB1000011 | CorrelationId = %1；ProcessId = %2；协议 = %3；操作 = %4；用户 = %5；Namespace = %6 |
CorrelationId = %1; ProcessId = %2; Protocol = %3; Operation = %4; User = %5; Namespace = %6 |
| 0xB1000012 | WMI 事件已丢弃。ConsumerType = %1；Possiblecause = %2 |
WMI Events were dropped. ConsumerType = %1; Possiblecause = %2 |
| 0xB1000013 | 正在 WMI 存储库上执行删除操作。OperationID = %1；操作 = %2 |
Performing delete operation on the WMI repository. OperationID = %1; Operation = %2 |
| 0xB1000014 | 正在 WMI 存储库上执行更新操作。OperationID = %1；操作 = %2；标志 = %3 |
Performing Update operation on the WMI repository. OperationID = %1; Operation = %2; Flags = %3 |
| 0xB1000015 | WMI 事件已绑定。ConsumerType = %1；Possiblecause = %2 |
WMI Events were bound. ConsumerType = %1; Possiblecause = %2 |
| 0xB1000032 | 活动传输 |
Activity Transfer |
| 0xB1000064 | ComponentName = %1；MessageDetail = %2；FileName = %3 |
ComponentName = %1; MessageDetail = %2; FileName = %3 |
| 0xB1000065 | ComponentName = %1；ErrorId = %2；ErrorDetail = %3；FileName = %4 |
ComponentName = %1; ErrorId = %2; ErrorDetail = %3; FileName = %4 |
| 0xB10016E1 | %1 提供程序已启动，结果代码 %2。HostProcess = %3；ProcessID = %4；ProviderPath = %5 |
%1 provider started with result code %2. HostProcess = %3; ProcessID = %4; ProviderPath = %5 |
| 0xB10016E2 | Id = %1；ClientMachine = %2；用户 = %3；ClientProcessId = %4；组件 = %5；操作 = %6；ResultCode = %7；PossibleCause = %8 |
Id = %1; ClientMachine = %2; User = %3; ClientProcessId = %4; Component = %5; Operation = %6; ResultCode = %7; PossibleCause = %8 |
| 0xB10016E3 | 命名空间 = %1；NotificationQuery = %2；OwnerName = %3；HostProcessID = %4；提供程序 = %5，queryID = %6；PossibleCause = %7 |
Namespace = %1; NotificationQuery = %2; OwnerName = %3; HostProcessID = %4; Provider= %5, queryID = %6; PossibleCause = %7 |
| 0xB10016E4 | 命名空间 = %1；NotificationQuery = %2；用户名 = %3；ClientProcessID = %4，ClientMachine = %5；PossibleCause = %6 |
Namespace = %1; NotificationQuery = %2; UserName = %3; ClientProcessID = %4, ClientMachine = %5; PossibleCause = %6 |
| 0xB10016E5 | 命名空间 = %1；Eventfilter = %2 (请参考其激活 eventid:5859)；使用者 = %3；PossibleCause = %4 |
Namespace = %1; Eventfilter = %2 (refer to its activate eventid:5859); Consumer = %3; PossibleCause = %4 |