| 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 (ID 为 %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.. |