| 0x4 | 在復原期間嘗試載入 MOF %2 時發生錯誤 %1。.MOF 檔案已標示為自動復原。 |
Error %1 encountered when trying to load MOF %2 while recovering .MOF file marked with autorecover. |
| 0xA | 無法在命名空間 \"%1\" 中使用查詢 \"%2\" 來重新啟用事件篩選，因為發生錯誤 %3。除非修正此問題，否則無法透過此篩選來傳遞事件。 |
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 已嘗試登錄查詢 \"%2\"，而其目標類別 \"%3\" 在 %4 命名空間中不存在。將略過該查詢。 |
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 | Windows Management Instrumentation ADAP 無法連線到命名空間 %1，錯誤為 %2 |
Windows Management Instrumentation ADAP failed to connect to namespace %1 with the following error %2 |
| 0x30 | Windows Management Instrumentation ADAP 無法在命名空間 %2 中儲存物件 %1，因為發生錯誤 %3 |
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 | 提供者 %1 已在 Windows Management Instrumentation 命名空間 %2 登錄以使用 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 Interop 命名空間類別 \"%1\" 已被覆寫。某些 Interop 案例可能無法正確運作。請從已提高權限的命令提示字元執行下列命令，以還原該行為: \"mofcomp %windir%\\system32\\wbem\\interop.mof\" 並以相同方式執行 mofcomp 已處理 %windir%\\system32\\wbem 與其子目錄下的所有 interop.mfl。 |
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 = %1; 操作 = %2; ProviderName = %3; ProviderGuid = %4; 路徑 = %5 的 ProviderInfo |
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 = %1; 操作 = %2; HostID = %3; ProviderName = %4; ProviderGuid = %5; 路徑 = %6 的 ProviderInfo |
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; 命名空間 = %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 | 識別碼 = %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; UserName = %3; ClientProcessID = %4，ClientMachine = %5; PossibleCause = %6 |
Namespace = %1; NotificationQuery = %2; UserName = %3; ClientProcessID = %4, ClientMachine = %5; PossibleCause = %6 |
| 0xB10016E5 | 命名空間 = %1; 事件篩選器 = %2 (意指其作用中事件識別碼: 5859); 取用者 = %3; 可能的原因 = %4 |
Namespace = %1; Eventfilter = %2 (refer to its activate eventid:5859); Consumer = %3; PossibleCause = %4 |
| 0xC00015FF | WMI Interop 命名空間類別 \"%1\" 已被覆寫。某些 Interop 案例可能無法正確運作。請從已提升權限的命令提示字元執行下列命令，以還原該行為: \"mofcomp %windir%\\system32\\wbem\\interop.mof\" 並以相同方式執行 mofcomp 已處理 %windir%\\system32\\wbem 與其子目錄下的所有 interop.mfl。 |
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. |