| 101 | 執行指令的診斷執行引擎 |
Scripted Diagnostics Execution Engine |
| 104 | 輸入引數 |
Input Arguments |
| 105 | 輸出引數 |
Output Arguments |
| 106 | 執行時間 |
Running Time |
| 107 | 狀態碼 |
Status Code |
| 110 | 名稱 |
Name |
| 111 | Windows 版本 |
Windows Version |
| 112 | SKU |
SKU |
| 113 | 架構 |
Architecture |
| 115 | 時間 |
Time |
| 116 | ID |
ID |
| 117 | 發行者 |
Publisher |
| 118 | 描述 |
Description |
| 119 | 封裝版本 |
Package Version |
| 120 | 檔案名稱 |
File Name |
| 121 | 偵錯報告 |
Debug Report |
| 122 | 內容 |
Contents |
| 123 | 指令碼 |
Script |
| 124 | 參數 |
Parameters |
| 127 | 以系統管理員身分執行 |
Running As Admin |
| 129 | 執行 |
Run |
| 132 | 初始化 |
Initialize |
| 133 | 診斷 |
Diagnose |
| 134 | 解析 |
Resolve |
| 135 | 驗證 |
Verify |
| 136 | 互動回應 |
Interaction Responses |
| 137 | 回呼指標 |
Callback Pointer |
| 138 | 文化特性 |
Culture |
| 139 | 封裝路徑 |
Path to Package |
| 140 | 解決方案 |
Resolution |
| 141 | 結果 |
Results |
| 142 | 結果報告 |
Results Report |
| 147 | 狀態 |
Status |
| 0x10000021 | 分析關鍵字 |
Analytic Keyword |
| 0x10000022 | 偵錯關鍵字 |
Debug Keyword |
| 0x10000023 | 管理關鍵字 |
Admin Keyword |
| 0x10000024 | 週期關鍵字 |
Lifecycle Keyword |
| 0x30000001 | 開始 |
Start |
| 0x30000002 | 停止 |
Stop |
| 0x50000002 | 錯誤 |
Error |
| 0x50000003 | 警告 |
Warning |
| 0x50000004 | 資訊 |
Information |
| 0x90000001 | Microsoft-Windows-Diagnosis-Scripted/Admin |
Microsoft-Windows-Diagnosis-Scripted/Admin |
| 0x90000002 | Microsoft-Windows-Diagnosis-Scripted/Operational |
Microsoft-Windows-Diagnosis-Scripted/Operational |
| 0x90000003 | Microsoft-Windows-Diagnosis-Scripted/Debug |
Microsoft-Windows-Diagnosis-Scripted/Debug |
| 0x90000004 | Microsoft-Windows-Diagnosis-Scripted/Analytic |
Microsoft-Windows-Diagnosis-Scripted/Analytic |
| 0xB0000001 | 執行指令的診斷引擎已執行位於 %1 且識別碼為 %2 的診斷套件。 |
The scripted diagnostic engine executed a diagnostic package located at %1 with ID %2. |
| 0xB0000065 | 執行指令的診斷引擎已開始初始化位於 %1 的診斷套件。 |
The scripted diagnostic engine started initializing a diagnostic package located at %1. |
| 0xB0000066 | 執行指令的診斷引擎已完成初始化位於 %1 的診斷套件。 |
The scripted diagnostic engine completed initializing a diagnostic package located at %1. |
| 0xB0000067 | 執行指令的診斷引擎已開始診斷名為 %1 的診斷套件。 |
The scripted diagnostic engine started diagnosing the diagnostic package %1. |
| 0xB0000068 | 執行指令的診斷引擎已完成診斷名為 %1 的診斷套件。 |
The scripted diagnostic engine completed diagnosing the diagnostic package %1. |
| 0xB0000069 | 執行指令的診斷引擎已開始執行診斷套件 %1 中的解決方案 %2。 |
The scripted diagnostic engine started running the resolution %2 in the diagnostic package %1. |
| 0xB000006A | 執行指令的診斷引擎已完成執行診斷套件 %1 中的解決方案 %2。 |
The scripted diagnostic engine completed running the resolution %2 in the diagnostic package %1. |
| 0xB000006B | 執行指令的診斷引擎已開始驗證診斷套件 %1。 |
The scripted diagnostic engine started verifying the diagnostic package %1. |
| 0xB000006C | 執行指令的診斷引擎已完成驗證診斷套件 %1。 |
The scripted diagnostic engine completed verifying the diagnostic package %1. |
| 0xB00000C9 | 執行指令的診斷引擎發生錯誤 %1。 |
The scripted diagnostic engine has encountered an error %1. |
| 0xB000012D | 執行指令的診斷引擎在函數 %1,行 %2 發生錯誤: %3。 |
The scripted diagnostic engine has encountered an error in function %1, line %2: %3. |
| 0xB0000191 | 封裝 %1 中偵測到根本原因 %2。 |
Rootcause %2 was detected in package %1. |
| 0xB0000192 | 封裝 %1 中已解決根本原因 %2。 |
Rootcause %2 was resolved in package %1. |
| 0xB00003E8 | 執行指令的診斷引擎已進入效能追蹤區段。 |
The scripted diagnostic engine has entered a performance tracing section. |
| 0xB00003EA | 執行指令的診斷引擎已結束效能追蹤區段。 |
The scripted diagnostic engine has exited a performance tracing section.. |