| 0x50000002 | 錯誤 |
Error |
| 0x50000003 | 警告 |
Warning |
| 0x50000004 | 資訊 |
Information |
| 0x90000001 | Microsoft-Windows-VerifyHardwareSecurity |
Microsoft-Windows-VerifyHardwareSecurity |
| 0x90000002 | Microsoft-Windows-VerifyHardwareSecurity/Operational |
Microsoft-Windows-VerifyHardwareSecurity/Operational |
| 0x90000003 | Microsoft-Windows-VerifyHardwareSecurity/Admin |
Microsoft-Windows-VerifyHardwareSecurity/Admin |
| 0xB0000BB9 | 硬體安全性檢查: %1 |
Hardware Security Check: %1 |
| 0xB0000BBA | 目前已停用安全開機。請透過系統韌體啟用安全開機。 |
SecureBoot is currently disabled. Please enable SecureBoot through the system firmware. |
| 0xB0000BBB | 無法檢查安全開機是否已啟用。狀態: %1 |
Failed to check if secureboot is enabled. Status: %1 |
| 0xB0000BBC | 在 SecureBoot 資料庫中找到發行前/測試憑證。請重新佈建 SecureBoot，使其不在 EFI 資料庫的變數 %2 中包含 %1。憑證指紋 = %3 |
PreRelease/Test cert found in SecureBoot database. Please re-provision SecureBoot to not include %1 in variable %2 of EFI database. Certificate Thumbprint = %3 |
| 0xB0000BBD | 無法檢查是否有 SecureBoot DB 中的發行前/測試憑證。狀態: %1 |
Failed to check for PreRelease/Test certificates found in SecureBoot DB. Status: %1 |
| 0xB0000BBE | 偵測到未實際執行的 SecureBoot 原則。請透過系統韌體來移除偵錯/發行前原則。 |
A non-production SecureBoot Policy was detected. Remove Debug/PreRelease policy through the system firmware. |
| 0xB0000BBF | 無法檢查未實行的安全開機原則。狀態: %1 |
Failed to check for non-production SecureBoot Policy. Status: %1 |
| 0xB0000BC0 | 主機提供者 %1 正嘗試載入 %2 以叫用其 %3 API。%2 具有 %4 的 OriginalFilename 或 InternalName。 |
Host provider %1 is trying to load %2 to invoke its %3 API. %2 has an OriginalFilename or InternalName of %4. |
| 0xB0000BC1 | 主機提供者 %1 正嘗試載入 %2 以叫用其 %3 API。%2 具有 %4 的 OriginalFilename 或 InternalName。NtQuerySecurityPolicy 失敗，錯誤碼為 %5。 |
Host provider %1 is trying to load %2 to invoke its %3 API. %2 has an OriginalFilename or InternalName of %4. NtQuerySecurityPolicy failed with error code %5. |
| 0xB0000BC2 | 主機提供者 %1 正嘗試載入 %2 以叫用其 %3 API。%2 具有 %4 的 OriginalFilename 或 InternalName。它已由主機鎖定安全性原則封鎖。 |
Host provider %1 is trying to load %2 to invoke its %3 API. %2 has an OriginalFilename or InternalName of %4. It is blocked by host lockdown security policy. |
| 0xB0000BC3 | 主機提供者 %1 正嘗試載入 %2 以叫用其 %3 API。無法從資源找到 OriginalFilename 或 InternalName，錯誤碼為 %4。 |
Host provider %1 is trying to load %2 to invoke its %3 API. Failed to find the OriginalFilename or InternalName from resource with error code %4. |
| 0xB0000BC4 | 主機提供者 %1 正嘗試載入 %2 以叫用其 %3 API。%2 具有 %4 的 OriginalFilename 或 InternalName。因為 UMCI 或主機鎖定原則未啟用，系統已允許執行叫用。 |
Host provider %1 is trying to load %2 to invoke its %3 API. %2 has an OriginalFilename or InternalName of %4. The invoking is allowed because UMCI or host lockdown policy is not enabled. |
| 0xB0000BC5 | 主機提供者 %1 正嘗試載入 %2 以叫用其 %3 API。%2 具有 %4 的 OriginalFilename 或 InternalName。因為主機鎖定安全性原則的稽核模式，系統已允許執行叫用。 |
Host provider %1 is trying to load %2 to invoke its %3 API. %2 has an OriginalFilename or InternalName of %4. The invoking is allowed because of the audit mode of the host lockdown security policy. |
| 0xF0000001 | 檢查是否已啟用安全開機 |
Checking if secureboot is enabled |
| 0xF0000002 | 檢查 EFI 資料庫中是否存在任何已知的測試憑證/金鑰 |
Checking if any known test certificates/keys are present in EFI db |
| 0xF0000003 | 檢查是否未實行安全開機原則 |
Checking if secureboot policy is not production |