microsoft-windows-system-events.dll.mui Microsoft-Windows-System-Events 資源 482ba15cc759a04af40855ad3770bc43

  1. File Info
  2. MUI

File info

File name: microsoft-windows-system-events.dll.mui
Size: 68608 byte
MD5: 482ba15cc759a04af40855ad3770bc43
SHA1: 9ebdf8d55816bd740d8e1b953a49c7ee97813169
SHA256: ed963d2f778b64c4870b5dc901f64d0a55bd298f034df2a09958e22d93b856ba
Operating systems: Windows 10
Extension: MUI

Translations messages and strings

If an error occurred or the following message in Chinese (Traditional) language and you cannot find a solution, than check answer in English. Table below helps to know how correctly this phrase sounds in English.

id Chinese (Traditional) English
0x1可能偵測到 CVE: %1%n其他資訊: %2%n%n偵測到對已知弱點 (%1) 的探測嘗試時，會產生此事件。%n此事件是由使用者模式處理程序所引發。%n Possible detection of CVE: %1%nAdditional Information: %2%n%nThis Event is generated when an attempt to exploit a known vulnerability (%1) is detected.%nThis Event is raised by a User mode process.%n
0x2可能偵測到 CVE: %1%n其他資訊: %2%n%n偵測到對已知弱點 (%1) 的探測嘗試時，會產生此事件。%n此事件是由核心模式驅動程式所引發。%n Possible detection of CVE: %1%nAdditional Information: %2%n%nThis Event is generated when an attempt to exploit a known vulnerability (%1) is detected.%nThis Event is raised by a kernel mode driver.%n
0x12CMicrosoft-Windows-Kernel-AppCompat Microsoft-Windows-Kernel-AppCompat
0x12DMicrosoft-Windows-AIT Microsoft-Windows-AIT
0x12EMicrosoft-Windows-Kernel-ApphelpCache Microsoft-Windows-Kernel-ApphelpCache
0x12FMicrosoft-Windows-AeSwitchBack Microsoft-Windows-AeSwitchBack
0x130Microsoft-Windows-AeLookupServiceTrigger Microsoft-Windows-AeLookupServiceTrigger
0x133%1 %1
0x136可執行檔 %2 在嘗試修改登錄機碼 %4 時接收到拒絕存取錯誤。 The executable %2 received an access denied error when trying to modify the registry key %4.
0x1F4Microsoft-Windows-Kernel-Network Microsoft-Windows-Kernel-Network
0x1F5已傳送資料。 Data sent.
0x1F6已接收資料。 Data received.
0x1F7已嘗試連線。 Connection attempted.
0x1F8已發出中斷連線要求。 Disconnect issued.
0x1F9已重新傳輸資料。 Data retransmitted.
0x1FA已接受連線。 Connection accepted.
0x1FB已嘗試重新連線。 Reconnect attempted.
0x1FCTCP 連線嘗試失敗。 TCP connection attempt failed.
0x1FD通訊協定已代表使用者複製資料。 Protocol copied data on behalf of user.
0x1FE已透過 UDP 通訊協定傳送資料。 Data sent over UDP protocol.
0x1FF已透過 UDP 通訊協定接收資料。 Data received over UDP protocol.
0x200UDP 連線嘗試失敗。 UDP connection attempt failed.
0x201TCPv4: 從 %4:%6 到 %3:%5 已傳輸 %2 個位元組。 TCPv4: %2 bytes transmitted from %4:%6 to %3:%5.
0x202TCPv4: 從 %4:%6 到 %3:%5 已收到 %2 個位元組。 TCPv4: %2 bytes received from %4:%6 to %3:%5.
0x203TCPv4: 已嘗試在 %4:%6 與 %3:%5 之間建立連線。 TCPv4: Connection attempted between %4:%6 and %3:%5.
0x204TCPv4: %4:%6 與 %3:%5 之間的連線已結束。 TCPv4: Connection closed between %4:%6 and %3:%5.
0x206TCPv4: 已在 %4:%6 與 %3:%5 之間建立連線。 TCPv4: Connection established between %4:%6 and %3:%5.
0x207TCPv4: %4:%6 與 %3:%5 之間的重新連線嘗試。 TCPv4: Reconnect attempt between %4:%6 and %3:%5.
0x208TCPv4: 連線嘗試失敗，錯誤碼為 %2。 TCPv4: Connection attempt failed with error code %2.
0x209TCPv4: 已代表使用者在 %4:%6 與 %3:%5 之間的連線通訊協定中複製 %2 個位元組。 TCPv4: %2 bytes copied in protocol on behalf of user for connection between %4:%6 and %3:%5.
0x20AUDPv4: 從 %4:%6 到 %3:%5 已傳輸 %2 個位元組。 UDPv4: %2 bytes transmitted from %4:%6 to %3:%5.
0x20BUDPv4: 從 %4:%6 到 %3:%5 已收到 %2 個位元組。 UDPv4: %2 bytes received from %4:%6 to %3:%5.
0x20CUDPv4: 連線嘗試失敗，錯誤碼為 %2。 UDPv4: Connection attempt failed with error code %2.
0x20DTCPv6: 從 %4:%6 到 %3:%5 已重新傳輸 %2 個位元組。 TCPv6: %2 bytes transmitted from %4:%6 to %3:%5.
0x20ETCPv6: 從 %4:%6 到 %3:%5 已收到 %2 個位元組。 TCPv6: %2 bytes received from %4:%6 to %3:%5.
0x20FTCPv6: 已嘗試在 %4:%6 與 %3:%5 之間建立連線。 TCPv6: Connection attempted between %4:%6 and %3:%5.
0x210TCPv6: %4:%6 與 %3:%5 之間的連線已結束。 TCPv6: Connection closed between %4:%6 and %3:%5.
0x212TCPv6: 已在 %4:%6 與 %3:%5 之間建立連線。 TCPv6: Connection established between %4:%6 and %3:%5.
0x213TCPv6: %4:%6 與 %3:%5 之間的重新連線嘗試。 TCPv6: Reconnect attempt between %4:%6 and %3:%5.
0x214TCPv6: 已代表使用者在 %4:%6 與 %3:%5 之間的連線通訊協定中複製 %2 個位元組。 TCPv6: %2 bytes copied in protocol on behalf of user for connection between %4:%6 and %3:%5.
0x215UDPv6: 從 %4:%6 到 %3:%5 已傳輸 %2 個位元組。 UDPv6: %2 bytes transmitted from %4:%6 to %3:%5.
0x216UDPv6: 從 %4:%6 到 %3:%5 已收到 %2 個位元組。 UDPv6: %2 bytes received from %4:%6 to %3:%5.
0x258Microsoft-Windows-Kernel-Disk Microsoft-Windows-Kernel-Disk
0x259已從 %5 的磁碟 %1 讀取 %3 個位元組。 %3 bytes read from disk %1 at %5.
0x25A%3 個位元組已寫入 %5 的磁碟 %1。 %3 bytes written to disk %1 at %5.
0x25B緩衝區已排清至磁碟 %1。 Buffers flushed to disk %1.
0x2BCMicrosoft-Windows-Kernel-Boot Microsoft-Windows-Kernel-Boot
0x2BD系統是以 %1x%2@%3bpp 開機。 System was booted in %1x%2@%3bpp.
0x2BEBootUX 畫面是以 %1x%2@%3bpp 顯示。 BootUX screen was displayed in %1x%2@%3bpp.
0x2BF視訊位元傳送速率為每毫秒 %1 個位元組。 Video bit transfer rate is %1 bytes per ms.
0x2C0開機程式庫已存取裝置 %1 上的檔案 %2。已讀取 %3 個位元組並寫入 %4 個位元組。 Boot library accessed file %2 on Device %1. Read %3 bytes and wrote %4 bytes.
0x2C1開機應用程式 %1 的檔案 IO: 已讀取的位元組總數 = %2，已寫入的位元組總數 = %3。 File IO for boot application %1: Total Bytes Read = %2, Total Bytes Written = %3.
0x2C2映像 %1 無法通過 IntegrityCheck 的原因是 %3。映像旗標是 %2。由於偵錯工具 %4，已忽略錯誤。 Image %1 failed IntegrityCheck reason is %3. Image flags are %2. Error ignored due to debugger %4.
0x2C3Bootmgr 期間是 %1 毫秒。 Bootmgr duration is %1 milliseconds.
0x2C4映像 %1 並非自我簽署。 Image %1 is not self-signed.
0x2C5開機環境無法存取 BIOS 列舉的裝置 (%1)。 A device (%1) that was enumerated by the BIOS was inaccessible to the boot environment.
0x2C6變數 %1 需要 %2 個位元組，而且狀態已設定為 %3。 Variable %1 requires %2 bytes and was set with status %3.
0x2C7應用程式 %1 的元素 %2 不在原則中。 Element %2 of application %1 was not in policy.
0x2C8安全開機原則更新導致狀態 %1。 A Secure Boot Policy update resulted in status %1.
0x2C9安全開機撤銷清單更新導致狀態 %1。 A Secure Boot Revocation List update resulted in status %1.
0x2CA抓取驅動程式清單使用了 %1 毫秒。 Retrieving the driver list took %1 milliseconds.
0x2CB載入驅動程式使用了 %1 毫秒。 Loading the drivers took %1 milliseconds.
0x2CC載入登錄區 %1 使用了 %2 毫秒。 Loading hive %1 took %2 milliseconds.
0x2CD載入 %1 的經過時間是 %2 毫秒。 The time elapsed loading %1 was %2 ms.
0x2CE執行 %1 的經過時間是 %2 毫秒。 The time elapsed executing %1 was %2 ms.
0x2CF為 WIM 壓縮檔 %2 建置區塊表格失敗，狀態為: %1 Building chunk table for WIM compressed file %2 failed with status: %1
0x2D0「軟開機」無法準備目標作業系統。操作狀態: %1 失敗點: %2 Soft Restart failed to prepare target Operating System. Operation status: %1 failure point: %2
0x2D1開機應用程式無法處理持續資料，狀態為: %1 Boot application failed to process persistent data with status: %1
0x320Microsoft-Windows-Kernel-File Microsoft-Windows-Kernel-File
0x352設定提供者 %1 上的特徵時發生錯誤。錯誤: %2 Error setting traits on Provider %1. Error: %2
0x353提供者 %1 的註冊已加入提供者群組 %2 A registration for Provider %1 has joined Provider Group %2
0x354啟用資訊 Enable Info
0x355設定提供者特徵 Set Provider Traits
0x356加入提供者群組 Join Provider Group
0x385Microsoft-Windows-Kernel-EventTracing Microsoft-Windows-Kernel-EventTracing
0x386工作階段 \"%1\" 無法寫入記錄檔 \"%2\"，發生下列錯誤: %3 Session \"%1\" failed to write to log file \"%2\" with the following error: %3
0x387即時工作階段 \"%1\" 的備援檔案已經達到大小上限。因此，在取得可用空間之前，新事件將不會記錄到這個工作階段。這種錯誤一般是在即時模式下啟動追蹤工作階段，但沒有任何即時使用者所造成。 The backing-file for the real-time session \"%1\" has reached its maximum size. As a result, new events will not be logged to this session until space becomes available. This error is often caused by starting a trace session in real-time mode without having any real-time consumers.
0x388工作階段 \"%1\" 無法啟動，錯誤如下: %3 Session \"%1\" failed to start with the following error: %3
0x389因為以下錯誤，工作階段 \"%1\" 已停止: %3 Session \"%1\" stopped due to the following error: %3
0x38A已經達到工作階段 \"%1\" 的檔案大小上限。因此，事件可能會遺失 (未記錄) 到檔案 %2。檔案大小上限目前設定成 %5 個位元組。 The maximum file size for session \"%1\" has been reached. As a result, events might be lost (not logged) to file \"%2\". The maximum files size is currently set to %5 bytes.
0x38B追蹤工作階段 \"%2\" 切換至 \"%1\" 事件記錄檔時發生錯誤。錯誤: %3 An error was encountered while tracing session \"%2\" was switching to the \"%1\" event log file. Error: %3
0x38E提供者 %1 已向「Windows 事件追蹤」登錄。 Provider %1 was registered with Event Tracing for Windows.
0x38F提供者 %1 已從「Windows 事件追蹤」取消登錄。 Provider %1 was unregistered from Event Tracing for Windows.
0x390工作階段 \"%3\" 已開始。 Session \"%3\" was started.
0x391工作階段 \"%3\" 已停止。 Session \"%3\" was stopped.
0x392工作階段 \"%3\" 的設定已修改。 The configuration of session \"%3\" has been modified.
0x393工作階段 \"%3\" 的事件已排清。 The events from session \"%3\" have been flushed.
0x394工作階段 \"%2\" 已啟用提供者 %1。 Provider %1 has been enabled to session \"%2\".
0x395工作階段 \"%2\" 不再啟用提供者 %1。 Provider %1 is no longer enabled to session \"%2\".
0x396提供者 %1 的安全性設定已從 %2 修改成 %3。 The security settings of provider %1 have been modified from %2 to %3.
0x397工作階段 \"%3\" 的安全性描述元已更新。 The security descriptor for session \"%3\" has been updated.
0x398提供者 Provider
0x399工作階段 Session
0x39B記錄 Logging
0x39D停止 Stop
0x39E開始 Start
0x39F停用 Disable
0x3A0啟用 Enable
0x3A1解除登錄 Unregister
0x3A2登錄 Register
0x3A3排清 Flush
0x3A4設定 Configure
0x3A7寫入緩衝區 Write Buffer
0x3A8檔案切換 File Switch
0x3AC堆疊相互關聯事件。此事件包含一個呼叫堆疊，而且此呼叫堆疊與先前的事件 (透過 MatchId 相互關聯) 相關聯。 Stack correlation event. This event contains a call stack which is associated with a prior event which is correlated by the MatchId.
0x3AD堆疊追蹤 Stack Trace
0x3AE使用者模式堆疊追蹤 User Mode Stack Trace
0x3AFMicrosoft-Windows-Kernel-EventTracing/Analytic Microsoft-Windows-Kernel-EventTracing/Analytic
0x3B0Microsoft-Windows-Kernel-EventTracing/Admin Microsoft-Windows-Kernel-EventTracing/Admin
0x3B1已遺失事件 Lost Event
0x3B3「記錄器」模式與「附加」模式不相容 Logger mode incompatible with Append mode
0x3B4作業系統版本不符 OS version mismatch
0x3B5指標大小不符 Pointer size mismatch
0x3B6不支援的 BufferSize Unsupported BufferSize
0x3B7BufferSize 不符 BufferSize mismatch
0x3B8「預先配置」模式與「附加」模式不相容 Preallocate mode is incompatible with Append mode
0x3B9檔案大小查詢失敗 File size query failed
0x3BA已達檔案大小上限 Maximum file size reached
0x3BB已寫入的緩衝區數目是零 Number of buffers written is zero
0x3BC處理器數目不符 Numberf of processors mismatch
0x3BD儲存軟開機保存記錄 \"%1\" 時發生錯誤。錯誤: %5 Error saving soft restart persisted log \"%1\" Error: %5
0x3BEGUID 項目 GUID Entry
0x3BF提供者群組項目 Provider Group Entry
0x3C0Microsoft-Windows-Kernel-StoreMgr Microsoft-Windows-Kernel-StoreMgr
0x3C1Microsoft-Windows-Kernel-StoreMgr/Operational Microsoft-Windows-Kernel-StoreMgr/Operational
0x3C2%5%n%n虛擬位址: %2%n實體位址: %3%n損毀視窗大小: %4 %5%n%nVirtual Address: %2%nPhysical Address: %3%nCorruption Window Size: %4
0x3C3已偵測並處理記憶體損毀。請在此電腦上執行記憶體診斷，若有需要，應更換記憶體晶片。 A memory corruption was detected and handled. Memory diagnostics should be run on this machine and, if necessary, memory chips should be replaced.
0x3C4已偵測並處理 ReadyBoost 快取中的資料損毀。此損毀很可能是因為硬體故障所造成。雖然 ReadyBoost 一律會偵測及處理此類錯誤，如果出現太多此類錯誤，可能表示 ReadyBoost 裝置已過度耗損，因而造成效能降低。您應該考慮更換 ReadyBoost 快取裝置。 A data corruption was detected and handled in a ReadyBoost cache. This corruption was most likely caused by faulty hardware. While ReadyBoost will always detect and handle these errors, seeing a lot of these may mean that the ReadyBoost device has worn out which reduces its performance. You should consider replacing the ReadyBoost cache device.
0x3C5ReadyBoost 快取無法持續於開機之間。若快取裝置在其他電腦上被修改，或是此電腦開機至其他作業系統，可能就會發生此問題。 A ReadyBoost cache failed to persist across boot. This may happen if the cache device was modified on another computer or if this computer was booted into another operating system.
0x3C6%1%n%n裝置名稱: %4%n快取路徑: %6 %1%n%nDevice name: %4%nCache path: %6
0x3C7ReadyBoost 快取已刪除，因為已在關聯的裝置偵測到重複的資料損毀例項，並已處理。雖然 ReadyBoost 一律會偵測並處理這些錯誤，但重複的損毀例項可能表示 ReadyBoost 裝置已過度耗損，因而造成效能降低。您應該考慮更換 ReadyBoost 裝置。 A ReadyBoost cache was deleted due to repeated data corruption instances on the associated device that have been detected and handled. While ReadyBoost will always detect and handle these errors, repeated corruption instances may mean that the ReadyBoost device has worn out which reduces its performance. You should consider replacing the ReadyBoost device.
0x3C8ReadyBoost 快取已刪除，因為關聯的裝置發生重複的 I/O 失敗。通常會在移除裝置 (例如，SD 記憶卡) 時發生此問題，但這也可能表示硬體故障。 A ReadyBoost cache was deleted due to repeated I/O failures on the associated device. This typically happens when the device (e.g. an SD card) is removed, but it may also indicate faulty hardware.
0x3E8Microsoft-Windows-LicensingStartServiceTrigger Microsoft-Windows-LicensingStartServiceTrigger
0x3F2Microsoft-Windows-WSServiceStartServiceTrigger Microsoft-Windows-WSServiceStartServiceTrigger
0x44CMicrosoft-Windows-Kernel-LiveDump Microsoft-Windows-Kernel-LiveDump
0x44DMicrosoft-Windows-Kernel-LiveDump/Analytic Microsoft-Windows-Kernel-LiveDump/Analytic
0x44E即時傾印擷取傾印資料 API Live Dump Capture Dump Data API
0x44F調整大小工作流程 Sizing Workflow
0x450擷取分頁工作流程 Capture Pages Workflow
0x451即時傾印寫入延遲傾印資料 API Live Dump Write Deferred Dump Data API
0x452即時傾印捨棄延遲傾印資料 API Live Dump Discard Deferred Dump Data API
0x453調整大小工作流程: 鏡像已開始。 Sizing Workflow: Mirroring started.
0x454調整大小工作流程: 鏡像階段 0 已結束。 Sizing Workflow: Mirroring Phase 0 ended.
0x455調整大小工作流程: 鏡像階段 1 已結束。 Sizing Workflow: Mirroring Phase 1 ended.
0x456調整大小工作流程: 系統靜止已開始。 Sizing Workflow: System Quiesce started.
0x457調整大小工作流程: 系統靜止已結束。 Sizing Workflow: System Quiesce ended.
0x458擷取分頁工作流程: 鏡像已開始。 Capture Pages Workflow: Mirroring started.
0x459擷取分頁工作流程: 鏡像階段 0 已結束。 Capture Pages Workflow: Mirroring Phase 0 ended.
0x45A擷取分頁工作流程: 鏡像階段 1 已結束。 Capture Pages Workflow: Mirroring Phase 1 ended.
0x45B擷取分頁工作流程: 系統靜止已開始。 Capture Pages Workflow: System Quiesce started.
0x45C擷取分頁工作流程: 系統靜止已結束。 Capture Pages Workflow: System Quiesce ended.
0x45D擷取分頁工作流程: 複製記憶體分頁已開始。 Capture Pages Workflow: Copy memory pages started.
0x45E擷取分頁工作流程: 複製記憶體分頁已結束。 Capture Pages Workflow: Copy memory pages ended.
0x45F即時傾印擷取傾印資料 API 已開始。 Live Dump Capture Dump Data API started.
0x460即時傾印擷取傾印資料 API 已結束。NT 狀態: %1。 Live Dump Capture Dump Data API ended. NT Status: %1.
0x461寫入傾印檔案已開始。 Writing dump file started.
0x462寫入傾印檔案已結束。NT 狀態: %1。總計 %2 個位元組 (標頭|主要|次要: %3|%4|%5 個位元組)。 Writing dump file ended. NT Status: %1. Total %2 bytes (Header|Primary|Secondary: %3|%4|%5 bytes).
0x463API 開始 API Start
0x464API 結束 API End
0x465傾印檔案寫入開始 Dump File Write Start
0x466傾印檔案寫入結束 Dump File Write End
0x467鏡像開始 Mirroring Start
0x468鏡像階段 0 結束 Mirroring Phase 0 End
0x469鏡像階段 1 結束 Mirroring Phase 1 End
0x46A系統靜止開始 System Quiesce Start
0x46B系統靜止結束 System Quiesce End
0x46C複製記憶體分頁開始 Copying Memory Pages Start
0x46D複製記憶體分頁結束 Copying Memory Pages End
0x46E即時傾印寫入延遲傾印資料 API 已啟動。 Live Dump Write Deferred Dump Data API started.
0x46F即時傾印寫入延遲傾印資料 API 已結束。NT 狀態: %1， Live Dump Write Deferred Dump Data API ended. NT Status: %1.
0x470寫入延遲傾印資料至檔案已開始。 Write deferred dump data to file started.
0x471寫入延遲傾印資料到檔案已結束。NT 狀態: %1。總計 %2 個位元組 (標頭|主要|次要: %3|%4|%5 個位元組)。 Write deferred dump data to file ended. NT Status: %1. Total %2 bytes (Header|Primary|Secondary: %3|%4|%5 bytes).
0x472即時傾印捨棄延遲傾印資料 API 已啟動。 Live Dump Discard Deferred Dump Data API started.
0x473即時傾印捨棄延遲傾印資料 API 已結束。NT 狀態: %1。 Live Dump Discard Deferred Dump Data API ended. NT Status: %1.
0x474調整大小工作流程: 預估。NT: %2 個位元組 (最小 %1 個位元組)。Hypervisor: 主要 %3 個位元組。次要 %4 個位元組。 Sizing Workflow: Estimation. NT: %2 bytes (Minimum %1 bytes). Hypervisor: Primary %3 bytes. Secondary %4 bytes.
0x475調整大小工作流程: 配置。NT: %1 個位元組。Hypervisor: 主要 %2 個位元組。次要 %3 個位元組。 Sizing Workflow: Allocation. NT: %1 bytes. Hypervisor: Primary %2 bytes. Secondary %3 bytes.
0x476緩衝區預估資料 Buffer Estimation Data
0x477緩衝區配置資料 Buffer Allocation Data
0x478調整大小工作流程: RemovePages 回呼已開始。 Sizing Workflow: RemovePages Callbacks started.
0x479調整大小工作流程: RemovePages 回呼已結束。 Sizing Workflow: RemovePages Callbacks ended.
0x47A調整大小工作流程: RemovePages 回呼 %1 已開始。 Sizing Workflow: RemovePages Callback %1 started.
0x47B調整大小工作流程: RemovePages 回呼 %1 已結束。 Sizing Workflow: RemovePages Callback %1 ended.
0x47C調整大小工作流程: RemovePages 回呼 %1 失敗。NT 狀態: %2。 Sizing Workflow: RemovePages Callback %1 failed. NT Status: %2.
0x47D移除頁面回呼 Remove Pages Callbacks
0x47E由於系統上的記憶體壓力，即時傾印要求已中止 Live Dump request aborted due to memory pressure on system
0x4B0Windows 已開始處理磁碟區掛接要求。%n%n 磁碟區 GUID: %1%n 磁碟區名稱: %3%n Windows has started processing the volume mount request.%n%n Volume GUID: %1%n Volume Name: %3%n
0x4B1已成功地掛接磁碟區。%n%n 磁碟區 GUID: %1%n 磁碟區名稱: %3%n The volume has been successfully mounted.%n%n Volume GUID: %1%n Volume Name: %3%n
0x4B2Windows 無法掛接磁碟區。%n%n 狀態: %4%n 磁碟區 GUID: %1%n 磁碟區名稱: %3%n Windows failed to mount the volume.%n%n Status: %4%n Volume GUID: %1%n Volume Name: %3%n
0x4B3Microsoft-Windows-Kernel-IO Microsoft-Windows-Kernel-IO
0x4B4Microsoft-Windows-Kernel-IO/Operational Microsoft-Windows-Kernel-IO/Operational
0x4B5Windows 已設定為封鎖舊版檔案系統篩選器。%n%n 篩選器名稱: %2%n Windows is configured to block legacy file system filters.%n%n Filter name: %2%n
0x4B6舊版檔案系統篩選器無法附加到位元組可定址磁碟區。%n%n 篩選器名稱: %2%n 磁碟區名稱: %4%n Legacy file system filters cannot attach to byte addressable volumes.%n%n Filter name: %2%n Volume name: %4%n
0x4B7機器上已停用傾印，因為啟用傾印加密時發生錯誤: %1。 %n如需有關傾印加密的詳細資訊，請參閱 http://go.microsoft.com/fwlink/?LinkId=824149
 Dumps are disabled on the machine since there was an error enabling dump encryption: %1. %nSee http://go.microsoft.com/fwlink/?LinkId=824149 for more information on dump encryption
0x4B8發生內部錯誤 An internal error occurred
0x4B9缺少公開金鑰或指紋登錄 Public Key or Thumbprint registry missing
0x4BA無效的公開金鑰 Invalid Public Key
0x4BB不支援的公開金鑰大小 Unsupported Public Key Size
0x514Microsoft-Windows-Kernel-Audit-API-Calls Microsoft-Windows-Kernel-Audit-API-Calls
0x578Microsoft-Windows-Audit-CVE Microsoft-Windows-Audit-CVE
0x5DCMicrosoft-Windows-User-Diagnostic Microsoft-Windows-User-Diagnostic
0x640Microsoft-Windows-Heap-Snapshot Microsoft-Windows-Heap-Snapshot
0x6A4Microsoft-Windows-Threat-Intelligence Microsoft-Windows-Threat-Intelligence
0x708Microsoft-Windows-Security-LessPrivilegedAppContainer/Operational Microsoft-Windows-Security-LessPrivilegedAppContainer/Operational
0x709Microsoft-Windows-Security-LessPrivilegedAppContainer Microsoft-Windows-Security-LessPrivilegedAppContainer
0x70A已拒絕位於 %1 的較少特殊權限之應用程式容器對資源的存取 (StackHash: %2)。 Access to the a resource has been denied for a less privileged app container at %1 (StackHash: %2).
0x01000001系統時間已從 %2 變更為 %1。%n%n變更原因: %3。 The system time has changed to %1 from %2.%n%nChange Reason: %3.
0x01000002偵測到授權原則快取損毀。 License policy-cache corruption detected.
0x01000003已修復授權原則快取損毀。 License policy-cache corruption has been fixed.
0x01000004授權原則快取已到期，因為它沒有在預期的期間內更新。 License policy-cache has expired because it was not updated within expected duration.
0x01000005{登錄區已修復} 登錄區 (檔案): '%3' 原已損毀，現已修復。某些資料可能已遺失。 {Registry Hive Recovered} Registry hive (file): '%3' was corrupted and it has been recovered. Some data might have been lost.
0x01000006由登錄所起始的 I/O 操作無法還原。登錄無法排清登錄區 (檔案): '%3'。 An I/O operation initiated by the Registry failed unrecoverably.The Registry could not flush hive (file): '%3'.
0x0100000B登錄區 %2 (TM: %3，RM: %4) 的 TxR 初始化階段已完成，結果=%5 (內部碼=%6)。 TxR init phase for hive %2 (TM: %3, RM: %4) finished with result=%5 (Internal code=%6).
0x0100000C作業系統已經在系統時間 %7 啟動。 The operating system started at system time %7.
0x0100000D作業系統已經在系統時間 %1 關閉。 The operating system is shutting down at system time %1.
0x0100000F登錄區 %2 已重新組織為開始大小為 %3 個位元組且結束大小為 %4 個位元組。 Hive %2 was reorganized with a starting size of %3 bytes and an ending size of %4 bytes.
0x01000010已清除登錄區 %2 中的存取歷程記錄，更新了 %3 個機碼並建立了 %4 個修改的頁面。 The access history in hive %2 was cleared updating %3 keys and creating %4 modified pages.
0x01000012作業系統正於軟開機後啟動。 The operating system is starting after soft restart.
0x0600000AError status code %1 returned when %3 attempted to load dependency %2. Error status code %1 returned when %3 attempted to load dependency %2.
0x0600000B不允許從目前的目錄載入相依性 %2 (若此動作是由 %1 嘗試)。發現另一個 DLL: %3。如需詳細資訊，請參閱 http://go.microsoft.com/fwlink/?LinkId=718136。 Loading dependency %2 from the current directory was not allowed when attempted by %1. Another DLL was found: %3. For more information, see http://go.microsoft.com/fwlink/?LinkId=718136.
0x0600000C不允許從目前的目錄載入相依性 %2 (若此動作是由 %1 嘗試)。找不到任何其他 DLL，且相依性解析失敗。如需詳細資訊，請參閱 http://go.microsoft.com/fwlink/?LinkId=718136。 Loading dependency %2 from the current directory was not allowed when attempted by %1. No other DLL was found and the dependency resolution failed. For more information, see http://go.microsoft.com/fwlink/?LinkId=718136.
0x0A000032對 %1 的存取是由原則規則 %2 監視。 Access to %1 is monitored by policy rule %2.
0x0A000361系統管理員依照預設的軟體限制原則層級，已經限制了對 %1 的存取。 Access to %1 has been restricted by your Administrator by the default software restriction policy level.
0x0A000362系統管理員依照放置於路徑 %3 的原則規則 %2 的位置，已經限制了對 %1 的存取。 Access to %1 has been restricted by your Administrator by location with policy rule %2 placed on path %3.
0x0A000363系統管理員依照軟體發行者原則，已經限制了對 %1 的存取。 Access to %1 has been restricted by your Administrator by software publisher policy.
0x0A000364系統管理員依照原則規則 %2，已經限制了對 %1 的存取。 Access to %1 has been restricted by your Administrator by policy rule %2.
0x0C00000A系統韌體已配置先前被判定為不可靠的記憶體區域。這樣可能會造成系統不穩定和/或資料損毀。 The system firmware has allocated a memory region previously determined to be unreliable. This has the potential to cause system instability and/or data corruption.
0x0C000010Windows 無法從休眠恢復，錯誤狀態為 %1。 Windows failed to resume from hibernate with error status %1.
0x0C000011已顯示開機管理程式多重 OS 選擇畫面。 The boot manager multi OS selection screen was displayed.
0x0C000012此系統上有 %1 個開機選項。 There are %1 boot options on this system.
0x0C000013此系統上有 %1 個開機工具選項。 There are %1 boot tool options on this system.
0x0C000014上次關機的成功狀態為 %1。上次開機的成功狀態為 %2。 The last shutdown's success status was %1. The last boot's success status was %2.
0x0C000015已顯示 OS 載入器進階選項功能表，而且使用者已選取選項 %1。 The OS loader advanced options menu was displayed and the user selected option %1.
0x0C000016已顯示 OS 載入器編輯選項功能表。 The OS loader edit options menu was displayed.
0x0C000017開機期間按下了 Windows 鍵。 The Windows key was pressed during boot.
0x0C000018開機期間按下了 F8 鍵。 The F8 key was pressed during boot.
0x0C000019開機功能表原則為 %1。 The boot menu policy was %1.
0x0C00001A此開機期間使用了一次性開機順序。 A one-time boot sequence was used during this boot.
0x0C00001B開機類型為 %1。 The boot type was %1.
0x0C00001DWindows 無法執行快速啟動，錯誤狀態為 %1。 Windows failed fast startup with error status %1.
0x0C00001E韌體已回報開機衡量標準。 The firmware reported boot metrics.
0x0C000020bootmgr 花了 %1 毫秒的時間等候使用者輸入。 The bootmgr spent %1 ms waiting for user input.
0x0C00007C虛擬化基礎的安全性啟用原則檢查，於階段 %1 失敗，狀態為: %2 The virtualization-based security enablement policy check at phase %1 failed with status: %2
0x0C000099虛擬化型安全性 (原則: %3) 是 %2。 Virtualization-based security (policies: %3) is %2.
0x0C00009C虛擬化型安全性 (原則: %3) 是 %2，狀態為: %1 Virtualization-based security (policies: %3) is %2 with status: %1
0x0F000009應用程式 %1 已終止，錯誤為 %2，原因是 Windows 二進位檔案 %3 發生問題。這可能是因為該二進位檔案未經簽署、包含不受信任的簽章、已損毀或已遭竄改。請重新整理您的電腦以修正此問題。 App %1 was terminated with error %2 because of an issue with Windows binary %3. This could be because the binary is unsigned, contains an untrusted signature, or has been corrupted or tampered with. Refresh your PC to fix this issue.
0x10000001結構化狀態 Structured State
0x10000002未結構化重設 Unstructured Reset
0x10000003記憶體不足 Out Of Memory
0x10000004Apiset 錯誤 Apiset Error
0x10000005WinRT WinRT
0x10000006低階資料存放區錯誤 Low-level Data Store Error
0x1000000A無法載入套件 %1 的應用程式設定。錯誤碼: %2 Failure to load the application settings for package %1. Error Code: %2
0x1000000B無法讀取套件 %1 的應用程式設定。錯誤碼: %2 Failure to read an application setting for package %1. Error Code: %2
0x1000000C無法寫入套件 %1 的應用程式設定。錯誤碼: %2 Failure to write an application setting for package %1. Error Code: %2
0x1000000D無法針對套件 %2 將儲存資料夾 %1 具現化，錯誤碼: %3 Failure to instantiate storage folder %1 for package %2 with Error Code: %3
0x10000014已觸發修復，因為套件 %2 的作業 %1 發生錯誤 %3。 Triggered repair because operation %1 against package %2 hit error %3.
0x10000015為套件 %2 的作業 %1 執行修復時發生錯誤 %3，傳回錯誤碼: %4 Repair for operation %1 against package %2 with error %3 returned Error Code: %4
0x10000016資料夾路徑 %1 無法通過存取檢查: 錯誤碼: %2 Folder path %1 failed access check: Error Code: %2
0x10000021詳細資訊內容事件 Verbose context events
0x10000022狀況觸發事件 Scenario trigger events
0x10000034SQM SQM
0x11000005時間 Time
0x16000005已過時的 DLL Deprecated dlls
0x16000006嚴重的使用者回呼例外狀況 Fatal user callback exception
0x16000007Dll 載入失敗。 A dll failed to load.
0x16000008啟動 16 位元應用程式 Launch 16bit application
0x16000009Windows 元件隨選安裝。 Windows component on demand.
0x1600000A載入器發生嚴重錯誤。 The Loader encountered a fatal error.
0x17000031回應時間 Response Time
0x19000005已過時的 COM 介面 Deprecated COM interfaces
0x1F000001處理程序 Process
0x1F000002AppContainer AppContainer
0x1F000003DesktopAppXProcess DesktopAppXProcess
0x1F000004DesktopAppXContainer DesktopAppXContainer
0x3000000A狀況開始會啟用 WDI 內容記錄器的內容提供者。 Scenario start enables context providers to the WDI context logger.
0x3000000B狀況結束會停用 WDI 內容記錄器的內容提供者。 Scenario end disables context providers to the WDI context logger.
0x3000000C當狀況仍然在執行中且超過最大的時間間隔時，SEM 會自動終止它。 When a scenario has remained in-flight beyond the maximum time window it is automatically terminated by the SEM.
0x3000000DSEM 中的狀況開始嘗試失敗。 A scenario start attempt failed in the SEM.
0x3000000ESEM 中的狀況結束嘗試失敗。 A scenario end attempt failed in the SEM.
0x3000000FSEM 收到開始新狀況的要求，但是執行中狀況的數目已達上限。 The SEM received a request to start a new scenario, but the maximum number of scenarios were already in-flight.
0x30000010SEM 登錄命名空間中的設定參數無效。 There is an invalid configuration parameter in the SEM registry namespace.
0x30000011SEM 所設定的狀況超過允許的計數上限。 The SEM is configured with more scenarios than the maximum allowed count.
0x30000012SEM 所設定的狀況有太多內容提供者。 The SEM is configured with a scenario with too many context providers.
0x30000013SEM 所設定的狀況有太多結束事件。 The SEM is configured with a scenario that has too many end events.
0x30000014在所有狀況間指定的提供者數目超過允許數目上限。 The number of providers specified across all scenarios is above the maximum allowed amount.
0x31000000資訊 Info
0x3500001ENLS 資料表作業 NLS data table operations
0x3500001FNLS 初始化 NLS initialization
0x35000020NLS 設定變更 NLS configuration changes
0x35000021NLS 作業 NLS operations
0x35000022NLS 清理作業 NLS clean-up operations
0x3B00001F叫用回呼函式 Invoke callback function
0x3B000020停用即時快取 Disable live cache
0x3B000021更新資源快取資訊清單 Update resource cache manifest
0x3B000022建置資源快取 Build resource cache
0x3B000024結束 End
0x50000002錯誤 Error
0x50000003警告 Warning
0x55000001重大 Critical
0x55000005詳細資訊 Verbose
0x70000009SEM 狀況週期 SEM Scenario Lifecycle
0x7000000ASEM 初始化 SEM Initialization
0x73000001此事件群組會追蹤來自現有檔案之掛接登錄區的效能。 This group of events tracks the performance of mounting hives from existing files.
0x73000002此事件群組會追蹤解除載入登錄區的效能。 This group of events tracks the performance of unloading hives.
0x73000003此事件群組會追蹤排清登錄區的效能。 This group of events tracks the performance of flushing hives.
0x73000004此事件群組會追蹤登錄關閉的效能。 This group of events tracks the performance of registry shutdown.
0x73000005此事件群組會追蹤載入登錄區的效能。 This group of events tracks the performance of loading hives.
0x73000006此事件群組會追蹤還原登錄區的效能。 This group of events tracks the performance of restoring hives.
0x73000007此事件群組會追蹤匯出登錄區的效能。 This group of events tracks the performance of exporting hives.
0x7500001ENLS 字碼頁函式 NLS code page functions
0x75000020NLS 日期/時間函式 NLS date/time functions
0x75000021NLS 自動的地區及語言選項 NLS Unattended Regional and Language Options
0x75000022NLS 群組原則 NLS group policy
0x75000023NLS 地區設定函式 NLS locale functions
0x7B00001EMUI NotifyUILanguageChange 工作 MUI NotifyUILanguageChange task
0x7B00001FMUI 資源快取建立器 MUI resource cache builder
0x90000001Microsoft-Windows-Kernel-WDI Microsoft-Windows-Kernel-WDI
0x90000002Microsoft-Windows-Kernel-WDI/Analytic Microsoft-Windows-Kernel-WDI/Analytic
0x90000003Microsoft-Windows-Kernel-WDI/Debug Microsoft-Windows-Kernel-WDI/Debug
0x90000004Microsoft-Windows-Kernel-WDI/Operational Microsoft-Windows-Kernel-WDI/Operational
0x90000005Microsoft-Windows-AppModel-State Microsoft-Windows-AppModel-State
0x90000006Microsoft-Windows-AppModel-State/Debug Microsoft-Windows-AppModel-State/Debug
0x90000007Microsoft-Windows-AppModel-State/Diagnostic Microsoft-Windows-AppModel-State/Diagnostic
0x91000001Microsoft-Windows-Kernel-General Microsoft-Windows-Kernel-General
0x91000002系統 System
0x92000001Microsoft-Windows-Kernel-Process Microsoft-Windows-Kernel-Process
0x93000001Microsoft-Windows-Kernel-Registry Microsoft-Windows-Kernel-Registry
0x94000001Microsoft-Windows-Kernel-Acpi Microsoft-Windows-Kernel-Acpi
0x95000001Microsoft-Windows-International Microsoft-Windows-International
0x95000002Microsoft-Windows-International/Operational Microsoft-Windows-International/Operational
0x96000001Microsoft-Windows-User-Loader Microsoft-Windows-User-Loader
0x96000002應用程式 Application
0x97000001Microsoft-Windows-Kernel-BootDiagnostics Microsoft-Windows-Kernel-BootDiagnostics
0x98000001Microsoft-Windows-UAC Microsoft-Windows-UAC
0x98000002Microsoft-Windows-UAC/Operational Microsoft-Windows-UAC/Operational
0x99000001Microsoft-Windows-COM Microsoft-Windows-COM
0x9A000001Microsoft-Windows-SoftwareRestrictionPolicies Microsoft-Windows-SoftwareRestrictionPolicies
0x9B000001Microsoft-Windows-MUI Microsoft-Windows-MUI
0x9B000002Microsoft-Windows-MUI/Operational Microsoft-Windows-MUI/Operational
0x9B000003Microsoft-Windows-MUI/Admin Microsoft-Windows-MUI/Admin
0x9B000004Microsoft-Windows-MUI/Analytic Microsoft-Windows-MUI/Analytic
0x9B000005Microsoft-Windows-MUI/Debug Microsoft-Windows-MUI/Debug
0x9D000001Microsoft-Windows-PCI Microsoft-Windows-PCI
0x9E000001Microsoft-Windows-Kernel-ShimEngine Microsoft-Windows-Kernel-ShimEngine
0x9E000002Microsoft-Windows-Kernel-ShimEngine/Operational Microsoft-Windows-Kernel-ShimEngine/Operational
0x9F000001Microsoft-Windows-AppModel-Runtime Microsoft-Windows-AppModel-Runtime
0x9F000002Microsoft-Windows-AppModel-Runtime/Analytic Microsoft-Windows-AppModel-Runtime/Analytic
0xB0000001刪除下列檔案時發生錯誤: %1。錯誤碼: %2 Error while deleting file: %1. Error Code: %2
0xB0000002刪除下列目錄時發生錯誤: %1。錯誤碼: %2 Error while deleting directory: %1. Error Code: %2
0xB0000003配置記憶體時發生錯誤 Error while allocating memory
0xB0000004ApiSet 函式: %1 已傳回執行結果，錯誤碼: %2 ApiSet Function: %1 returned with Error Code: %2
0xB0000005低階資料存放區存取錯誤。函式: %1 已傳回執行結果，錯誤碼: %2 Low-level data store access error. Function: %1 returned with Error Code: %2
0xB0000006已略過清除暫存狀態的作業，因為磁碟使用率不高。 Cleanup of temporary state has been skipped due to low disk usage.
0xB0000007已完成清除暫存狀態的作業。 Cleanup of temporary state has completed.
0xB0000008暫存狀態的清除無法列舉使用者設定檔。物件: %1，錯誤碼: %2。 Cleanup of temporary state was unable to enumerate the user profiles. Object: %1, Error Code: %2.
0xB0000009暫存狀態的清除意外中止。 Cleanup of temporary state has aborted unexpectedly.
0xB000000E需要為使用者 %2 更新套件 %1的狀態位置，因為找不到結構描述。錯誤碼: %3 Need to update state locations of package %1 for user %2 because the schema is not found. Error Code: %3
0xB000000F需要為使用者 %2 更新套件 %1的狀態位置，因為找不到套件。錯誤碼: %3 Need to update state locations of package %1 for user %2 because the package is not found. Error Code: %3
0xB0000010需要為使用者 %2 更新套件 %1的狀態位置，因為套件完整名稱已變更。錯誤碼: %3 Need to update state locations of package %1 for user %2 because the package full name has changed. Error Code: %3
0xB0000011需要為使用者 %2 更新套件 %1的狀態位置，因為結構描述版本已變更。錯誤碼: %3 Need to update state locations of package %1 for user %2 because the schema version has changed. Error Code: %3
0xB0000012已成功修正套件 %1 的狀態位置。 Succeeded to fix state locations for package %1.
0xB0000013無法修正套件 %1 的狀態位置。錯誤碼: %2 Failure to fix state locations for package %1. Error Code: %2
0xB0000020狀況事件對應程式已為具有 %4 內容提供者的提供者 %1 (事件識別碼 %2) 啟動狀況。內容記錄器捨棄的事件計數為 %3。 The Scenario Event Mapper started a scenario for provider %1 (event ID %2) with %4 context providers. The context logger dropped event count was %3.
0xB0000021狀況事件對應程式已為具有 %4 內容提供者的提供者 %1 (事件識別碼 %2) 停止狀況。內容記錄器捨棄的事件計數為 %3。 The Scenario Event Mapper stopped a scenario for provider %1 (event ID %2) with %4 context providers. The context logger dropped event count was %3.
0xB0000022提供者 %1 (事件識別碼 %2) 的執行中狀況逾時，而且已由狀況事件對應程式自動停止。 An in-flight scenario from provider %1 (event ID %2) timed out and was stopped automatically by the Scenario Event Mapper.
0xB0000023狀況事件對應程式無法為提供者 %1 (事件識別碼 %2) 啟動新的狀況，因為執行的狀況數目已達上限。 The Scenario Event Mapper was unable to start a new scenario for provider %1 (event ID %2) because the maximum number of scenarios are already in flight.
0xB0000024狀況事件對應程式無法為提供者 %1 (事件識別碼 %2) 啟動狀況。錯誤碼是 %3。 The Scenario Event Mapper was unable to start a scenario for provider %1 (event ID %2). The error code was %3.
0xB0000025狀況事件對應程式無法為提供者 %1 (事件識別碼 %2) 停止狀況。錯誤碼是 %3。 The Scenario Event Mapper was unable to stop a scenario for provider %1 (event ID %2). The error code was %3.
0xB0000026狀況事件對應程式所設定的狀況數目超過上限。將忽略提供者 %1 (事件識別碼 %2) 的狀況。 The Scenario Event Mapper is configured with more than the maximum number of scenarios. The scenario for provider %1 (event ID %2) will be ignored.
0xB0000027狀況事件對應程式為具有提供者 %1 (事件識別碼 %2) 的狀況所設定的內容提供者數目超過上限。將忽略該狀況。 The Scenario Event Mapper is configured with more than the maximum number of context providers for the scenario with provider %1 (event ID %2). The scenario will be ignored.
0xB0000028狀況事件對應程式為具有提供者 %1 (事件識別碼 %2) 的狀況所設定的結束事件數目超過上限。將忽略該狀況。 The Scenario Event Mapper is configured with more than the maximum number of end events for the scenario with provider %1 (event ID %2). The scenario will be ignored.
0xB0000029狀況事件對應程式所設定的提供者數目超過上限。將忽略提供者 %1。 The Scenario Event Mapper is configured with more than the maximum number of providers. The provider %1 will be ignored.
0xB000002A狀況事件對應程式所設定的狀況不受支援。提供者 %1 (事件識別碼 %2) 的狀況發生錯誤碼 %3，將被忽略。 The Scenario Event Mapper is configured with an unsupported scenario. The scenario for provider %1 (event ID %2) encountered error code %3 and will be ignored.
0xB1000001系統時間已從 %2 變更為 %1。 The system time has changed to %1 from %2.
0xB2000001由父系 %3 在 %2 時啟動的處理程序 %1 在名稱為 %5 的工作階段 %4 執行。 Process %1 started at time %2 by parent %3 running in session %4 with name %5.
0xB2000002處理程序 %1 (在 %2 時啟動) 在 %3 時停止，結束代碼為 %4。 Process %1 (which started at time %2) stopped at time %3 with exit code %4.
0xB2000003執行緒 %2 (在處理程序 %1) 已啟動。 Thread %2 (in Process %1) started.
0xB2000004執行緒 %2 (在處理程序 %1) 已停止。 Thread %2 (in Process %1) stopped.
0xB2000005處理程序 %3 已載入名稱為 %7 的映像。 Process %3 had an image loaded with name %7.
0xB2000006處理程序 %3 已解除載入名稱為 %7 的映像。 Process %3 had an image unloaded with name %7.
0xB2000007處理程序 %1 中執行緒 %2 的基礎 CPU 優先順序已從 %3 變更為 %4。 Base CPU priority of thread %2 in process %1 was changed from %3 to %4.
0xB2000008處理程序 %1 中執行緒 %2 的 CPU 優先順序已從 %3 變更為 %4。 CPU priority of thread %2 in process %1 was changed from %3 to %4.
0xB2000009處理程序 %1 中執行緒 %2 的分頁優先順序已從 %3 變更為 %4。 Page priority of thread %2 in process %1 was changed from %3 to %4.
0xB200000A處理程序 %1 中執行緒 %2 的 I/O 優先順序已從 %3 變更為 %4。 I/O priority of thread %2 in process %1 was changed from %3 to %4.
0xB200000B已暫停執行處理程序 %1。 Execution of the process %1 has been suspended.
0xB200000C已繼續執行處理程序 %1。 Execution of the process %1 has been resumed.
0xB200000D工作 %1 已啟動，狀態碼為 %2。 Job %1 started with status code %2.
0xB200000E工作 %1 已終止，狀態碼為 %2。 Job %1 terminated with status code %2.
0xB200000F已列舉的處理程序 %1 已在時間 %2 啟動 (由在名為 %6 之工作階段 %4 中執行的父系 %3 啟動)。 Enumerated process %1 had started at time %2 by parent %3 running in session %4 with name %6.
0xB2010001由父系 %3 在 %2 時啟動的處理程序 %1 在名稱為 %6 的工作階段 %4 執行。 Process %1 started at time %2 by parent %3 running in session %4 with name %6.
0xB4000001記憶體範圍描述元已標示為保留。 A memory range descriptor has been marked as reserved.
0xB4000002應停用的 GPE 位元上觸發意外的 GPE 事件。 Unexpected GPE event was fired on GPE bits that should be disabled.
0xB4000003已經收到 ACPI 熱溫區 %2 的溫度變更通知 (通知(thermal_zone, 0x80))。 %n_TMP = %3K %n_PSV = %4K %n_AC0 = %5K %n_AC1 = %6K %n_AC2 = %7K %n_AC3 = %8K %n_AC4 = %9K %n_AC5 = %10K %n_AC6 = %11K %n_AC7 = %12K %n_AC8 = %13K %n_AC9 = %14K %n_HOT = %15K %n_CRT = %16K A temperature change notification (Notify(thermal_zone, 0x80)) for ACPI thermal zone %2 has been received. %n_TMP = %3K %n_PSV = %4K %n_AC0 = %5K %n_AC1 = %6K %n_AC2 = %7K %n_AC3 = %8K %n_AC4 = %9K %n_AC5 = %10K %n_AC6 = %11K %n_AC7 = %12K %n_AC8 = %13K %n_AC9 = %14K %n_HOT = %15K %n_CRT = %16K
0xB4000004已經收到 ACPI 熱溫區 %2 的跳變點變更通知 (通知(thermal_zone, 0x81))。 %n_TMP = %3K %n_PSV = %4K %n_AC0 = %5K %n_AC1 = %6K %n_AC2 = %7K %n_AC3 = %8K %n_AC4 = %9K %n_AC5 = %10K %n_AC6 = %11K %n_AC7 = %12K %n_AC8 = %13K %n_AC9 = %14K %n_HOT = %15K %n_CRT = %16K A trip point change notification (Notify(thermal_zone, 0x81)) for ACPI thermal zone %2 has been received. %n_TMP = %3K %n_PSV = %4K %n_AC0 = %5K %n_AC1 = %6K %n_AC2 = %7K %n_AC3 = %8K %n_AC4 = %9K %n_AC5 = %10K %n_AC6 = %11K %n_AC7 = %12K %n_AC8 = %13K %n_AC9 = %14K %n_HOT = %15K %n_CRT = %16K
0xB4000005主動式冷卻裝置 %6 已%8。 %n熱溫區裝置例項: %2 %n主動式冷卻套件: _AC%3 %n命名空間物件: _AL%4 The active cooling device %6 has been turned %8. %nThermal zone device instance: %2 %nActive cooling package: _AC%3 %nNamespace object: _AL%4
0xB4000006主動式冷卻裝置 %6 已%7。 %n熱溫區裝置例項: %2 %n主動式冷卻套件: _AC%3 %n命名空間物件: _AL%4 The active cooling device %6 has been turned %7. %nThermal zone device instance: %2 %nActive cooling package: _AC%3 %nNamespace object: _AL%4
0xB4000007ACPI 方法 %2 評估%3。 ACPI method %2 evaluation has %3.
0xB4000008主動式冷卻裝置 %2 已%3。 The active cooling device %2 has been turned %3.
0xB4000009被動式冷卻裝置 %2 節流已變更為百分之 %3。 The passive cooling device %2 throttle has changed to %3 percent.
0xB400000A裝置 %2 具有下列冷卻狀態。 %n主動式冷卻: %3 %n被動式冷卻: %4%% The device %2 has the following cooling state. %nActive cooling: %3 %nPassive cooling: %4 percent
0xB4000014ACPI 裝置 %2 正在進行 %3。狀態為 %4。 ACPI device %2 is undergoing %3. Status %4.
0xB4000015ACPI 裝置覆寫 - %1 ACPI device OverRide - %1
0xB4000016解譯 AML 程式碼時發生錯誤: 範圍 %1，物件 %2。狀態 %3。 Error occured while interpreting AML code: scope %1, object %2. Status %3.
0xB4000017ACPI 方法 %2 具有高頻率 %3。 ACPI method %2 has high frequency %3.
0xB50003E9NLS 操作失敗，因為無法開啟登錄機碼 %1。錯誤碼是 %2。錯誤訊息: %3 The NLS operation failed because the registry key %1 cannot be opened. Error code is %2. Error message: %3
0xB50003EANLS 操作失敗，因為無法開啟登錄機碼 %1。狀態碼是 %2。 The NLS operation failed because the registry key %1 cannot be opened. Status code is %2.
0xB50003EB字碼頁 %1 的 NLS 字碼頁操作失敗，因為檔案 %2 遺失。若要修正此錯誤，請更換此檔案或修復 Windows 安裝。 NLS codepage operation failed for the codepage %1 because the file %2 is missing. To correct this error, replace this file or repair your Windows installation.
0xB50003EC字碼頁 %1 的 NLS 字碼頁操作失敗，因為檔案 %2 已損毀。若要修正此錯誤，請更換此檔案或修復 Windows 安裝。 NLS codepage operation failed for the codepage %1 because the file %2 is corrupted. To correct this error, replace this file or repair your Windows installation.
0xB50003ED%1 地區設定的 NLS 操作失敗，因為檔案 %2\\globalization\\%1.nlp 遺失。若要修正此問題，請重新安裝此自訂地區設定。 NLS operation failed for %1 locale because the file %2\\globalization\\%1.nlp is missing. To fix this problem, reinstall this custom locale.
0xB50003EE%1 地區設定的 NLS 操作失敗，因為檔案 %2\\globalization\\%1.nlp 已損毀。若要修正此問題，請重新安裝此自訂地區設定。 NLS operation failed for %1 locale because the file %2\\globalization\\%1.nlp is corrupted. To fix this problem, reinstall this custom locale.
0xB50005DC群組原則已禁止處理程序編號 %1 (%2) 變更使用者的標準與格式資訊。 Group Policy has prevented process number %1 (%2) from changing the standards and format information for the user.
0xB50005DD群組原則已禁止變更地理位置。 Group Policy has prevented the geographical location from being changed.
0xB50005DE群組原則已禁止使用者將其使用者地區設定變更為 \"%1\"。 Group Policy has prevented the user from changing their user locale to \"%1\".
0xB50005DF群組原則不允許標準與格式的自訂使用者地區設定。使用者無法選取 \"%1\" 作為其使用者地區設定。 Group Policy does not allow custom user locales for standards and formats. The user was unable to select \"%1\" as their user locale.
0xB50007D0NLS 操作已重新建立登錄機碼 %1。 NLS operation recreated the registry key %1.
0xB50009C4Windows 已偵測到 NLS 內部資料中的不一致。若要修正此問題，請登出 Windows 並再次登入。 Windows has detected inconsistencies in NLS internal data. To correct this problem, log off of Windows and log on again.
0xB5000BB8處理程序編號 %1 (%2) 已成功呼叫 SetLocaleInfo(%3、%4、\"%5\")。 Process number %1 (%2) called SetLocaleInfo(%3, %4, \"%5\") successfully.
0xB5000BB9處理程序編號 %1 (%2) 已成功呼叫 SetCalendarInfo(%3、%4、%5、\"%6\")。 Process number %1 (%2) called SetCalendarInfo(%3, %4, %5, \"%6\") successfully.
0xB5000BBA處理程序編號 %1 (%2) 已成功呼叫 SetUserGeoID(%3)。 Process number %1 (%2) called SetUserGeoID(%3) successfully.
0xB5000BBB系統已更新旗標為 %2 的地區設定 \"%1\"。處理程序編號 %3 (%4)。傳回碼是 %5。 The system updated the locale \"%1\" with flag %2. Process number %3 (%4). Return code is %5.
0xB5002710使用者嘗試以不支援的格式套用自動 XML 檔案 (%1)。理由: %3 (第 %2 行)。系統尚未變更。 The user tried to apply an unattended XML file (%1) in an unsupported format. Reason: %3 (Line %2). The system has not been changed.
0xB5002711在功能上不支援的 XML。 Unsupported XML in function.
0xB5002713使用者地區設定 \"%1\" (由 UserLocale 元素指定) 不是支援的地區設定名稱或是未安裝在系統上。使用者地區設定並未變更。 The user locale \"%1\" (specified by the UserLocale element) is not a supported locale name or is not installed on the system. The user locale was not changed.
0xB5002714不支援的替代排序 \"%1\"。 Unsupported alternate sort \"%1\".
0xB5002715\"%1\" 不是地區設定 \"%2\" 支援的排序次序。 \"%1\" is not a supported sort order for locale \"%2\".
0xB5002716選取的系統地區設定 (由 SystemLocale 元素指定) 未安裝在系統上。系統地區設定並未變更。 The selected system locale (specified by the SystemLocale element) is not installed on the system. The system locale was not changed.
0xB5002717變更系統地區設定 (由 SystemLocale 元素指定) 時發生內部錯誤。 Internal error while changing System locale (specified by the SystemLocale element).
0xB5002718變更 \"%1\" 的鍵盤/輸入法時發生錯誤。 Error while changing keyboard/input method for \"%1\".
0xB5002719變更位置喜好設定 (GeoID) 時發生錯誤: %1。此錯誤可能是由不支援的位置喜好設定 (GeoID) 或群組原則限制所造成。錯誤碼是 %2。錯誤訊息: %3 Error while changing location preference (geoid): %1. This error may be caused by an unsupported location preference (geoid) or a Group Policy restriction. Error code is %2. Error message: %3
0xB500271A無法將 UI 語言變更為 \"%1\"。狀態碼是: %2。 Failed to change UI Language to \"%1\". Status code is: %2.
0xB500271B無法將 UI 語言遞補順序變更為 \"%1\"。狀態碼是: %2。 Failed to change UI Language fallback order to \"%1\". Status code is: %2.
0xB500271C使用者嘗試套用自動 XML 檔案 %1，但該檔案不存在。 The user tried to apply an unattended XML file %1, but the file does not exist.
0xB500271D使用者變更目前使用者地區設定的設定 \"%1\" (值為 \"%2\") 時發生錯誤。錯誤碼是: %3。錯誤訊息: %4 Error while the user changed setting \"%1\" with value \"%2\" for the current user locale. Error code is: %3. Error message: %4
0xB500271E選取的日曆 \"%1;\" (由 Calendar 元素指定) 不是支援的日曆。使用者地區設定並未變更。 The selected calendar \"%1;\" (specified by the Calendar element) is not a supported calendar. The user locale was not changed.
0xB500271F選取的 TwoDigitYearMax \"%1;\" (由 TwoDigitYearMax 元素指定) 不是支援的值。使用者地區設定並未變更。 The selected TwoDigitYearMax \"%1;\" (specified by the TwoDigitYearMax element) is not a supported value. The user locale was not changed.
0xB500277F使用者沒有變更 TwoDigitYearMax 設定的權限 The user does not have permission to change the TwoDigitYearMax setting
0xB5002780使用者沒有將目前的設定複製到預設和/或系統帳戶的權限 The user does not have permission to copy current settings to the Default and/or System Account
0xB5002781使用者沒有變更系統地區設定 (由 SystemLocale 元素指定) 的權限。 The user does not have permission to change the system locale (specified by the SystemLocale element).
0xB5002783使用者沒有變更日曆的權限。 The user does not have permission to change the calendar.
0xB50027E8意外的失敗。堆疊溢位 Unexpected failure. Stack overflow
0xB50027EA意外的失敗。不支援的旗標 Unexpected failure. Unsupported flag
0xB50027EB意外的失敗。不支援的參數 Unexpected failure. Unsupported parameter
0xB50027EC意外的失敗。無法修復的錯誤。 Unexpected failure. Unrecoverable error.
0xB50027ED呼叫內部函式失敗。錯誤碼是: %1 Failed when calling internal function. Error code is: %1
0xB50027EE操作已逾時。 The operation timed out.
0xB500283C群組原則已禁止使用者變更系統地區設定 (由 SystemLocale 元素指定)。 Group Policy has prevented the user from changing the system locale (specified by the SystemLocale element).
0xB50032C8使用者已將其使用者地區設定 (由 UserLocale 元素指定) 變更為 \"%1\"。 The user changed their user locale (specified by the UserLocale element) to \"%1\".
0xB50032C9使用者已將其使用者地區設定 \"%1\" (由 UserLocale 元素指定) 的所有自訂設定重設為系統預設值。 The user reset all customizations for their user locale \"%1\" (specified by the UserLocale element) to the system default.
0xB50032CA使用者已將其使用者地區設定 \"%1\" (由 UserLocale 元素指定) 變更為 \"%2\"。 The user changed their user locale setting \"%1\" (specified by the UserLocale element) to \"%2\".
0xB50032CB地區設定必須變更為目前的地區設定，才能進行自訂。 The locale has to be changed to the current locale in order to make customizations.
0xB50032CC使用者已將其替代排序變更為 \"%1\"。 The user changed their alternate sort to \"%1\".
0xB50032CD使用者已將其日曆變更為 \"%1\"。 The user changed their calendar to \"%1\".
0xB50032CE使用者已將其 TwoDigitYearMax 變更為 %1。 The user changed their TwoDigitYearMax to %1.
0xB50032CF使用者已將其位置喜好設定 (GeoID) 變更為 %1。 The user changed their location preference (geoid) to %1.
0xB50032D0系統地區設定 (由 SystemLocale 元素指定) 已變更為 \"%1\"。 The system locale (specified by the SystemLocale element) was changed to \"%1\".
0xB50032D1目前的使用者設定已複製到預設使用者帳戶。 The current user settings were copied to the default user account.
0xB50032D2目前的使用者設定已複製到系統帳戶。 The current user settings were copied to the system accounts.
0xB50032D3使用者已將其 UI 語言變更為 \"%1\"。 The user has changed their UI Language to \"%1\".
0xB50032D4使用者已將其 UI 語言遞補順序變更為 \"%1\"。 The user has changed their UI Language fallback order to \"%1\".
0xB6000001已過時的模組 %1。 Deprecated module %1.
0xB6000002處理程序 %2 發生嚴重的使用者回呼例外狀況。 Process %2 encountered a fatal user callback exception.
0xB6000004該處理程序可啟動 16 位元的處理程序。 The process launches a 16 bit process.
0xB6000005Windows 元件隨選安裝 %1。 Windows component on demand %1.
0xB6000006載入器從處理程序映像名稱 %1 載入執行緒時發生嚴重錯誤。 The Loader encountered a fatal error while loading a thread from process image name %1.
0xB6000007%1 初始化期間發生嚴重錯誤。 A fatal error occured during initalization of %1.
0xB6000009載入器執行處理程序映像名稱 %1 時發生嚴重錯誤。 The Loader encountered a fatal error running process image name %1.
0xB8000001處理程序在建立子處理程序時，無法處理 ERROR_ELEVATION_REQUIRED。 The process failed to handle ERROR_ELEVATION_REQUIRED during the creation of a child process.
0xB9000001已過時的 COM CLSID %1。 Deprecated COM CLSID %1.
0xBB0007D0MUI 通知操作失敗，狀態碼為 %1。未叫用回呼。 MUI notify operation failed with status code %1. No callbacks were invoked.
0xBB0007D1檔案 %1 的 MUI 回呼失敗，因為無法載入它。若要修正此錯誤，請更換此檔案或修復 Windows 安裝。 MUI Callback failed for file %1 because it can not be loaded. To correct this error, replace this file or repair your Windows installation.
0xBB0007D2註冊為類型 %2 之檔案 %1 的 MUI 回呼失敗，因為 DLL 中沒有 %3 函式。若要修正此錯誤，請更換此檔案或修復登錄項目。 MUI Callback failed for file %1 registered as type %2 because the function %3 does not exist in the dll. To correct this error, replace the file or fix the registry entry.
0xBB0007D3檔案 %1 的 MUI 回呼失敗，因為該檔案並非由 Microsoft 簽署。若要修正此錯誤，請將該檔案更換成此 Windows 安裝隨附的原始檔。 MUI Callback failed for file %1 because it is not signed by Microsoft. To correct this error, replace with the original file that came with this Windows installation.
0xBB0007D4找不到 MUI 回呼檔案 %1。若要修正此錯誤，請修復登錄或將該檔案複製到指定的位置。 MUI Callback file %1 cannot be found. To correct this error, repair the registry or copy the file to the specified location.
0xBB0007D6無法停用 Wow 重新導向。將不會建置新資源快取。 Wow redirection could not be disabled. New resource cache will not be built.
0xBB0007D7無法在可寫入模式下開啟資源快取。將不會建置新資源快取。 Resource cache cannot be opened in writable mode. New resource cache will not be built.
0xBB0007D8無法停用即時資源快取。 Live resource cache could not be disabled.
0xBB0007D9無法從 MUI API 抓取語言設定。將不會建置新資源快取。 Unable to retrieve language settings from MUI API. New resource cache will not be built.
0xBB0007DA無法剖析可快取的檔案清單或寫入資源快取資訊清單。若以命令列參數方式指定設定檔，請確認該檔案存在而且格式正確。將不會建置新資源快取。 Unable to parse the cacheable file list or write to the resource cache manifest. If configuration file was specified as command-line parameter, check that file exists and has correct format. New resource cache will not be built.
0xBB0007DB對資源快取資訊清單所做的變更無法寫入磁碟。將不會建置新資源快取。 Changes made to resource cache manifest cannot be written to disk. New resource cache will not be built.
0xBB0007DC由於發生內部錯誤，無法建置新資源快取: %1。 New resource cache could not be built due to internal error: %1.
0xBB0007DD無法在系統上安裝新建置的資源快取。 Newly built resource cache could not be installed on the system.
0xBB0007DE無法建立資源快取資訊清單。將不會建置新資源快取。 Resource cache manifest could not be created. New resource cache will not be built.
0xBB000BB8已叫用 UI 語言變更的 MUI 通知，且旗標設為 %1，新語言設為 %2，而舊語言則設為 %3。延伸旗標已設為 %4 MUI notification for UI Language change has been invoked with flags set to %1 and the new languages set to %2 and the previous languages set to %3. The extended flags is set to %4
0xBB000BBA%1 中的 MUI 通知回呼 API %2 已傳回執行結果，代碼為 %3。 MUI notification callback API %2 in %1 returned with code %3.
0xBB000BBB已使用以下參數呼叫 MUI 資源快取建立器: %1。 MUI resource cache builder has been called with the following parameters: %1.
0xBB000BBC已更新檔案 %1 的 MUI 資源快取資訊清單項目。親和性: '%2'，順序: %3 以及優先順序: %4 MUI resource cache manifest entry for file %1 has been updated. Affinity: '%2', Sequence: %3, and Priority: %4
0xBB000BBD啟動: %1 Start: %1
0xBB000BBE結束: %1 End: %1
0xBB000BBF已建置新資源快取並安裝在系統上。新快取索引為 %1，即時快取索引為 %2 而 config 已設定為 %3。 New resource cache built and installed on system. New cache index is %1, live cache index is %2 and config is set to %3.
0xBB000BC4因為資源檔 %1 在系統中使用頻率不高，所以將不會快取它。 Resource file %1 will not be cached since it is not used frequently in the system.
0xBB000BC5系統的 RAM、總磁碟空間或可用磁碟空間有限，所以將不會維護 MUI 資源快取。 The system is constrained in RAM, total disk space or free disk space, so the MUI resource cache will not be maintained.
0xBB000FA0無法剖析設定參數。將會略過設定參數。 Unable to parse configuration parameters. The configuration parameters will be ignored.
0xBC00000BBootmgr 之前所經過的時間 (根據 TSC) 是 %1 毫秒。 The time elapsed before Bootmgr, based on the TSC, is %1 ms.
0xBC00001F韌體密碼編譯雜湊提供者初始化的結果狀態為 %1。 Initialization of the firmware crypto hash provider resulted in status %1.
0xBC000021The firmware update capsule (%1) failed to load with status %2. The firmware update capsule (%1) failed to load with status %2.
0xBC000022The PE/COFF image firmware update capsule (%1) failed to load with status %2. The PE/COFF image firmware update capsule (%1) failed to load with status %2.
0xBC000023The Efi UpdateCapsule failed to apply updates with status %1. The Efi UpdateCapsule failed to apply updates with status %1.
0xBC000024Firmware update supported status is %3. The BitLocker device flags are %1 and the PCR bitmap is %2. Firmware update supported status is %3. The BitLocker device flags are %1 and the PCR bitmap is %2.
0xBC000025The firmware update capsule (%1) code integrity check failed with status %2. The firmware update capsule (%1) code integrity check failed with status %2.
0xBC000026Windows 無法載入必要的系統檔 %1，錯誤狀態為 %2。 Windows failed to load the required system file %1 with error status %2.
0xBC000027Windows 無法載入系統登錄檔 %1，錯誤狀態為 %2。 Windows failed to load the system registry file %1 with error status %2.
0xBC000028Windows 無法初始化 ACPI，錯誤狀態為 %1。 Windows failed to initialize the ACPI with error status %1.
0xBC000029Windows 無法載入，錯誤狀態為 %1。 Windows failed to load with error status %1.
0xBC00002AWindows 無法載入從 %1 匯入的映像 %2，錯誤狀態為 %3。 Windows failed to load image %2 imported from %1 with error status %3.
0xBC00002BWindows 無法從映像 %1 匯入 %2，錯誤狀態為 %3。 Windows failed to import %2 from image %1 with error status %3.
0xBC00002CWindows 無法佈建 VSM 識別金鑰。解除密封快取的複本狀態: %1。新的金鑰產生狀態: %2。測量 PCR 狀態: %3。密封與快取狀態: %4。 Windows failed to provision VSM Identity Key. Unsealing cached copy status: %1. New key generation status: %2. Measuring to PCR status: %3. Sealing and caching status: %4.
0xBC00002DVSM 識別金鑰佈建。解除密封快取的複本狀態: %1。新的金鑰產生狀態: %2。測量 PCR 狀態: %3。密封與快取狀態: %4。 VSM Identity Key Provisioning. Unsealing cached copy status: %1. New key generation status: %2. Measuring to PCR status: %3. Sealing and caching status: %4.
0xBC000031Windows 系統完整性原則不允許載入需要的系統檔案 %1，錯誤狀態為 %2。 Windows system integrity policy does not allow to load the required system file %1 with error status %2.
0xBC000032Windows 無法佈建 VSM 主要加密金鑰。使用已快取的複本狀態: %1。解密已快取的複本狀態: %2。新的金鑰產生狀態: %3。加密狀態: %4。TPM PCR 遮罩: %5。由保護裝置協助的解密狀態: %6。由保護裝置協助的重新加密狀態: %7。保護裝置更新狀態: %8。TPM 計數器驗證狀態: %9。TPM 計數器建立狀態: %10。 Windows failed to provision VSM Master Encryption Key. Using cached copy status: %1. Unsealing cached copy status: %2. New key generation status: %3. Sealing status: %4. TPM PCR mask: %5. Protector-assisted unseal status: %6. Protector-assisted re-seal status: %7. Protector update status: %8. Tpm Counter validation status: %9. Tpm Counter creation status: %10.
0xBC000033VSM 主要加密金鑰佈建。使用已快取的複本狀態: %1。解密已快取的複本狀態: %2。新的金鑰產生狀態: %3。加密狀態: %4。TPM PCR 遮罩: %5。由保護裝置協助的解密狀態: %6。由保護裝置協助的重新加密狀態: %7。保護裝置更新狀態: %8。TPM 計數器驗證狀態: %9。TPM 計數器建立狀態: %10。 VSM Master Encryption Key Provisioning. Using cached copy status: %1. Unsealing cached copy status: %2. New key generation status: %3. Sealing status: %4. TPM PCR mask: %5. Protector-assisted unseal status: %6. Protector-assisted re-seal status: %7. Protector update status: %8. Tpm Counter validation status: %9. Tpm Counter creation status: %10.
0xBC000039Windows 無法佈建 TPM 儲存根金鑰，錯誤狀態為: %1。 Windows failed to provision the TPM Storage Root Key with error status:%1.
0xBC00003AWindows 已順利佈建 TPM 儲存根金鑰。此作業花了 %1 毫秒的時間完成。 Windows successfully provisioned the TPM Storage Root Key. This operation took %1 milliseconds.
0xBC00003BWindows 無法佈建 TPM 繫結資訊，錯誤狀態為: %1。 Windows failed to provision TPM binding information with error status:%1.
0xBC000088軟開機無法完成，狀態為: %1，因為 %2 個待處理未要求配置 Soft Restart failed to complete with status: %1 due to %2 outstanding unclaimed allocations
0xBC00008B軟開機無法還原記憶體磁碟分割 %1，狀態為: %2 Soft Restart failed to restore memory partition %1 with status: %2
0xBC00008E「軟開機」無法使用「軟開機」延伸模組來註冊。版本不相容。 Soft Restart failed to register with Soft Restart extension. The versions are not compatible.
0xBC000092軟開機無法使用安全載入來建立連線，狀態為: %1 Soft Restart failed to establish connection with secure load with status: %1
0xBC00009A「開機原則移轉」已使用已驗證的變數。狀態: %1 Boot Policy Migration used an authenticated variable. Status: %1
0xBC00009B「開機原則移轉」已使用未驗證的變數。狀態: %1 Boot Policy Migration used an unauthenticated variable. Status: %1
0xBC00009D資訊: %1 狀態: %2 Info: %1 Status: %2
0xBC00009E錯誤: %1 狀態: %2 Error: %1 Status: %2
0xBE010003%3 填充碼已套用至驅動程式 [%1]。%n%n填充碼來源: %2。%n%n填充碼 GUID: %4。 %3 shim(s) were applied to driver [%1].%n%nShim(s) source: %2.%n%nShim GUID(s): %4.
0xBE010004旗標 [%4] 已套用至裝置 [%1] - 類別 [%2]。%n%n旗標來源: %3。 Flags [%4] were applied to device [%1] - class [%2].%n%nFlags source: %3.
0xBF000001在 %2 時由父系 %3 (以套件 %4 執行，可執行檔為 %5) 啟動的處理程序 %1 是應用程式 %6。 Process %1 started at time %2 by parent %3 running as package %4 with executable %5 is application %6.
0xBF000002%2: 無法為套件 %1 建立處理程序，因為發生錯誤。%3 %2: Cannot create the process for package %1 because an error was encountered. %3
0xBF000003%2: 無法為套件 %1 建立處理程序，因為查詢快速快取時發生錯誤。%3 %2: Cannot create the process for package %1 because an error was encountered while querying the fast cache. %3
0xBF000004%2: 無法為套件 %1 建立處理程序，因為準備應用程式認證時發生錯誤。%3 %2: Cannot create the process for package %1 because an error was encountered while preparing the App credentials. %3
0xBF000005%2: 無法為套件 %1 建立處理程序，因為檢查使用者層級套件狀態時發生錯誤。%3 %2: Cannot create the process for package %1 because an error was encountered while checking the user-level package status. %3
0xBF000006%2: 無法為套件 %1 建立處理程序，因為檢查機器層級套件狀態時發生錯誤。%3 %2: Cannot create the process for package %1 because an error was encountered while checking the machine-level package status. %3
0xBF000007%2: 無法為套件 %1 建立處理程序，因為驗證應用程式認證時發生錯誤。%3 %2: Cannot create the process for package %1 because an error was encountered while verifying the App credentials. %3
0xBF000008應用程式 %1 已終止，錯誤為 %2，原因是應用程式二進位檔案 %3 發生問題。這可能是因為該二進位檔案未經簽署、包含不受信任的簽章、已損毀或已遭竄改。請重新安裝應用程式以修正此問題。 App %1 was terminated with error %2 because of an issue with application binary %3. This could be because the binary is unsigned, contains an untrusted signature, or has been corrupted or tampered with. Reinstall the application to fix this issue.
0xBF00000B應用程式 %1 無法載入產生的二進位檔案 %3，因為發生錯誤 %2。這可能是因為該二進位檔案未經簽署、包含不受信任的簽章、已損毀或已遭竄改。 App %1 prevented the load of generated binary %3 due to error %2. This could be because the binary is unsigned, contains an untrusted signature, or has been corrupted or tampered with.
0xBF00000C應用程式無法載入二進位檔案，因為發生錯誤 %1。這可能是因為該二進位檔案未經簽署、包含不受信任的簽章、已損毀或已遭竄改。 An app prevented the load of a binary due to error %1. This could be because the binary is unsigned, contains an untrusted signature, or has been corrupted or tampered with.
0xBF00000E%2: 套件執行階段資訊 %1 已損毀 (位址=%5，大小=%3，位移=%4，區段=%6，處理程序識別碼=%7)。請重新安裝該套件以修正此問題。 %2: Package runtime information %1 is corrupted (address=%5, size=%3, offset=%4, section=%6, processid=%7). Reinstall the package to fix this issue.
0xBF00000F%2: 套件執行階段資訊 %1 遺失預期的資料 (位址=%4，大小=%3，區段=%5，處理程序識別碼=%6)。請重新安裝該套件以修正此問題。 %2: Package runtime information %1 is missing expected data (address=%4, size=%3, section=%5, processid=%6). Reinstall the package to fix this issue.
0xBF000010%2: 套件執行階段資訊 %1 包含衝突的資料 (位址=%5，大小=%3，位移=%4，區段=%6，處理程序識別碼=%7)。請重新安裝該套件以修正此問題。 %2: Package runtime information %1 contains conflicting data (address=%5, size=%3, offset=%4, section=%6, processid=%7). Reinstall the package to fix this issue.
0xBF000011%2: 套件執行階段資訊 %1 包含未預期的資料 (位址=%5，大小=%3，位移=%4，區段=%6，處理程序識別碼=%7)。請重新安裝該套件以修正此問題。 %2: Package runtime information %1 contains unexpected data (address=%5, size=%3, offset=%4, section=%6, processid=%7). Reinstall the package to fix this issue.
0xBF000012%2: 套件執行階段資訊 %1 無法載入 (處理程序識別碼=%3)。 %2: Package runtime information %1 failed to load (processid=%3).
0xBF000013套件執行階段資訊 %1 無法載入，因為發生例外狀況 %2。 Package runtime information %1 failed to load because exception %2 occurred.
0xBF000014%2: 無法建立套件 %1 的處理程序，因為載入執行階段資訊時發生錯誤。%3 %2: Cannot create the process for package %1 because an error was encountered while loading the runtime information. %3
0xBF000015AppContainer %2 的 CreateAppContainerProfile 失敗，錯誤為 %1。 CreateAppContainerProfile failed for AppContainer %2 with error %1.
0xBF000016AppContainer %2 的 DeleteAppContainerProfile 失敗，錯誤為 %1。 DeleteAppContainerProfile failed for AppContainer %2 with error %1.
0xBF000017AppContainer %2 的 UpdateAppContainerProfile 失敗，錯誤為 %1。 UpdateAppContainerProfile failed for AppContainer %2 with error %1.
0xBF000018CreateAppContainerProfile 失敗 (錯誤為 %1)，因為它無法建立登錄機碼 %2。 CreateAppContainerProfile failed with error %1 because it was unable to create registry key %2.
0xBF000019CreateAppContainerProfile 失敗 (錯誤為 %1)，因為它無法在登錄機碼 %2 上設定安全性。 CreateAppContainerProfile failed with error %1 because it was unable to set security on registry key %2.
0xBF00001AAppContainer 設定檔失敗 (錯誤為 %1)，因為它無法刪除登錄機碼 %2。 AppContainer profile failed with error %1 because it was unable to delete registry key %2.
0xBF00001BCreateAppContainerProfile 失敗 (錯誤為 %1)，因為它無法建立資料夾 %2。 CreateAppContainerProfile failed with error %1 because it was unable to create folder %2.
0xBF00001CCreateAppContainerProfile 失敗 (錯誤為 %1)，因為它無法在資料夾 %2 上設定屬性。 CreateAppContainerProfile failed with error %1 because it was unable to set attributes on folder %2.
0xBF00001DCreateAppContainerProfile 失敗 (錯誤為 %1)，因為它無法驗證登錄機碼 %2 是否存在。 CreateAppContainerProfile failed with error %1 because it was unable to verify the existence of registry key %2.
0xBF00001ECreateAppContainerProfile 失敗 (錯誤為 %1)，因為它無法驗證資料夾 %2 是否存在。 CreateAppContainerProfile failed with error %1 because it was unable to verify the existence of folder %2.
0xBF00001FCreateAppContainerProfile 失敗 (錯誤為 %1)，因為它找不到使用者的本機應用程式資料資料夾。 CreateAppContainerProfile failed with error %1 because it was unable to find the users local app data folder.
0xBF000020AppContainer 設定檔失敗 (錯誤為 %1)，因為它無法刪除資料夾 %2 或其內容。 AppContainer profile failed with error %1 because it was unable to delete folder %2 or its contents.
0xBF000021AppContainer 設定檔失敗 (錯誤為 %1)，因為它無法查詢 AppContainer 名稱。 AppContainer profile failed with error %1 because it was unable to look up the AppContainer name.
0xBF000022AppContainer 設定檔失敗 (錯誤為 %1)，因為它無法查詢 AppContainer 顯示名稱。 AppContainer profile failed with error %1 because it was unable to look up the AppContainer display name.
0xBF000023CreateAppContainerProfile 失敗 (錯誤為 %1)，因為它無法向防火牆登錄。 CreateAppContainerProfile failed with error %1 because it was unable to register with the firewall.
0xBF000024DeleteAppContainerProfile 失敗 (錯誤為 %1)，因為它無法向防火牆解除登錄。 DeleteAppContainerProfile failed with error %1 because it was unable to unregister with the firewall.
0xBF000025應用程式容器設定檔失敗 (錯誤為 %1)，因為它無法登錄 AppContainer SID。 App Container profile failed with error %1 because it was unable to register the AppContainer SID.
0xBF000026DeleteAppContainerProfile 失敗 (錯誤為 %1)，因為它無法解除登錄 AppContainer SID。 DeleteAppContainerProfile failed with error %1 because it was unable to unregister the AppContainer SID.
0xBF000027已順利建立 AppContainer %1。 Successfully created AppContainer %1.
0xBF000028未建立 AppContainer %1，因為它已存在。 AppContainer %1 was not created because it already exists.
0xBF000029已順利刪除 AppContainer %1。 Successfully deleted AppContainer %1.
0xBF00002A已順利更新 AppContainer %1。 Successfully updated AppContainer %1.
0xBF00002C%2: 正在載入套件執行階段資訊 %1 (位址=%4，大小=%3，處理程序識別碼=%5) 時，無法存取應用程式身分識別。 %2: Application identity not accessible while loading package runtime information %1 (address=%4, size=%3, processid=%5).
0xBF00002D在與受限的 AppContainer 互動期間抓取 AppContainer %2 資訊失敗，錯誤為 %1。 Failed with %1 while retrieving AppContainer %2 information during interaction with Restricted AppContainer.
0xBF00002E在與受限的 AppContainer 互動期間抓取 AppContainer 資訊失敗，錯誤為 %1。 Failed with %1 while retrieving AppContainer information during interaction with Restricted AppContainer.
0xBF00002F抓取 AppContainer 資訊失敗，錯誤為 %1。來自此處理程序類型的呼叫無效。 Failed with %1 while retrieving AppContainer information. Call invalid from this process type.
0xBF000030無法為受限的 AppContainer %2 建立共用上下文物件，錯誤為 %1。 Failed to create shared context object for Restricted AppContainer %2 with %1.
0xBF000031無法啟用受限的 AppContainer %2，錯誤為 %1。 Failed to activate Restricted AppContainer %2 with %1.
0xBF000032建立受限的 AppContainer %2 失敗 (錯誤為 %1)，因為指定的功能無效。 Creation of Restricted AppContainer %2 failed with %1 because an invalid capability was specified.
0xBF000033開啟現有受限的 AppContainer %2 失敗 (錯誤為 %1)，因為無法讀取功能存放區值。 Opening existing Restricted AppContainer %2 failed with %1 because the capabilities storage value could not be read.
0xBF000034無法為受限的 AppContainer %2 建立功能存放區值，錯誤為 %1。 Failed to create the capabilities storage value for Restricted AppContainer %2 with %1.
0xBF000035套件 %1 需要驗證。 The package %1 requires validation.
0xBF000036偵測到套件 %1 中發生修改。 Modification was detected in package %1.
0xBF000037無法終止套件為 %1 的應用程式。 Failed to terminate app with package %1.
0xBF000038已順利驗證套件為 %1 的應用程式。 Validation of app with package %1 was successful.
0xBF000039抓取套件 %2 資料夾的信任狀態失敗，狀態為 %1。 Failed with %1 to retrieve the trust state of the package %2 folder.
0xBF00003A正在檢查 %2 時，「應用程式完整性」檢查失敗，錯誤為 %1。 App Integrity check failed with %1 while checking %2.
0xBF00003B「應用程式完整性」已終止應用程式。%2 的完整性檢查傳回 %1。 App Integrity terminated an application. Integrity check for %2 returned %1.
0xBF00003C%1 的「應用程式完整性」檢查逾時。 App Integrity check for %1 timed out.
0xBF00003D%2: 無法建立套件 %1 的處理程序，因為執行完整性檢查時發生錯誤。%3 %2: Cannot create the process for package %1 because an error was encountered while performing the integrity check. %3
0xBF00003E套件 %1 的部署伺服器完整性檢查失敗，狀態為 %2。 Deployment server integrity check of package %1 failed with %2.
0xBF00003F抓取「AppModel 執行階段」群組原則值失敗，錯誤為 %1。 Failed with %1 retrieving AppModel Runtime group policy values.
0xBF000040驗證「AppModel 執行階段」群組原則值失敗，錯誤為 %1。 Failed with %1 validating AppModel Runtime group policy values.
0xBF000041抓取封裝 %2「AppModel 執行階段」狀態失敗，錯誤為 %1。 Failed with %1 retrieving AppModel Runtime status for package %2.
0xBF000042抓取使用者 %3 封裝 %2「AppModel 執行階段」狀態失敗，錯誤為 %1。 Failed with %1 retrieving AppModel Runtime status for package %2 for user %3.
0xBF000043修改封裝 %2「AppModel 執行階段」狀態失敗，錯誤為 %1 (目前狀態 = %4，所需的狀態 = %3)。 Failed with %1 modifying AppModel Runtime status for package %2 (current status = %4, desired status = %3).
0xBF000044封裝 %1「AppModel 執行階段」狀態已成功地更新為 %2 (先前狀態 = %3)。 AppModel Runtime status for package %1 successfully updated to %2 (previous status = %3).
0xBF000045修改使用者 %3 封裝 %2「AppModel 執行階段」狀態失敗，錯誤為 %1 (目前狀態 = %5，所需的狀態 = %4)。 Failed with %1 modifying AppModel Runtime status for package %2 for user %3 (current status = %5, desired status = %4).
0xBF000046使用者 %2 封裝 %1「AppModel 執行階段」狀態已成功地更新為 %3 (先前狀態 = %4)。 AppModel Runtime status for package %1 for user %2 successfully updated to %3 (previous status = %4).
0xBF000047修改「AppModel 執行階段」狀態版本失敗，錯誤為 %1 (內容 = %2)。 Failed with %1 modifying AppModel Runtime status version (context = %2).
0xBF000048已成功地更新「AppModel 執行階段」狀態版本。 AppModel Runtime status version successfully updated.
0xBF000049%2: 無法建立套件 %1 的處理程序，因為建立應用程式資料時發生錯誤。%3 %2: Cannot create the process for package %1 because an error was encountered while performing the app data creation. %3
0xBF00004A無法重新整理套件執行階段資訊 %1，因為作業類型 %3 中發生下列錯誤 %2。 Package runtime information %1 failed to refresh because the following error %2 occurred in operation type %3.
0xBF00004B錯誤%2: 無法登錄%1套件，因為打開 HKEY 使用者登錄機碼時發生下列錯誤:
error %2: Cannot register the %1 package because the following error was encountered while opening the HKEY_USERS registry key
0xBF00004C錯誤%4: 無法登錄%1套件，因為列舉以移除%2\\%3套件系列登錄機碼時發生下列錯誤: error %4: Cannot register the %1 package because the following error was encountered while enumerating to remove the %2\\%3 package family registry key
0xBF00004D錯誤%4: 無法登錄%1套件，因為創建%2\\%3套件系列登錄機碼時發生下列錯誤: error %4 : Cannot register the %1 package because the following error was encountered while creating the %2\\%3 package family registry key
0xBF00004E錯誤%4: 無法登錄%1套件，因為移除%2\\%3套件系列登錄機碼時發生下列錯誤:
error %4: Cannot register the %1 package because the following error was encountered while removing the %2\\%3 package family registry key
0xBF00004F%2: 套件系列 %1 執行階段資訊損毀。正在嘗試修正此問題。 %2: Package family %1 runtime information is corrupted. Attempting to correct the issue.
0xBF000050%2: 套件系列 %1 執行階段資訊損毀，但是目前無法修復。 %2: Package family %1 runtime information is corrupted but we cannot repair it at this time.
0xBF000065正在建立 AppContainer %1。 Creating AppContainer %1.
0xBF000066已完成建立 AppContainer %2 的作業，錯誤碼為 %1。 Finished creating AppContainer %2 with %1.
0xBF000067正在刪除 AppContainer %1。 Deleting AppContainer %1.
0xBF000068已完成刪除 AppContainer %2 的作業，錯誤碼為 %1。 Finished deleting AppContainer %2 with %1.
0xBF000069正在更新 AppContainer %1。 Updating AppContainer %1.
0xBF00006A已完成更新 AppContainer %2 的作業，錯誤碼為 %1。 Finished updating AppContainer %2 with %1.
0xBF00006B正在建立 AppContainer %1 的防火牆規則。 Creating firewall rules for AppContainer %1.
0xBF00006C已完成建立 AppContainer %2 之防火牆規則的作業，錯誤碼為 %1。 Finished creating firewall rules for AppContainer %2 with %1.
0xBF00006D正在刪除 AppContainer %1 的防火牆規則。 Deleting firewall rules for AppContainer %1.
0xBF00006E已完成刪除 AppContainer %2 之防火牆規則的作業，錯誤碼為 %1。 Finished deleting firewall rules for AppContainer %2 with %1.
0xBF00006F正在建立受限的 AppContainer %1。 Creating Restricted AppContainer %1.
0xBF000070已完成建立受限的 AppContainer %2，錯誤碼為 %1。 Finished creating Restricted AppContainer %2 with %1.
0xBF000071正在刪除受限的 AppContainer %1。 Deleting Restricted AppContainer %1.
0xBF000072已完成刪除受限的 AppContainer %2，錯誤碼為 %1。 Finished deleting Restricted AppContainer %2 with %1.
0xBF000073正在開啟受限的 AppContainer %1。 Opening Restricted AppContainer %1.
0xBF000074已完成開啟受限的 AppContainer %2，錯誤碼為 %1。 Finished opening Restricted AppContainer %2 with %1.
0xBF000075正在為 %1 列舉所有受限的 AppContainers。 Enumerating all Restricted AppContainers for %1.
0xBF000076已完成列舉 AppContainer %2 之所有受限的 AppContainers，錯誤碼為 %1。 Finished enumerating all Restricted AppContainers for AppContainer %2 with %1.
0xBF000077正在啟動受限的 AppContainer %1 中的處理程序。 Launching process in Restricted AppContainer %1.
0xBF000078已完成啟動受限的 AppContainer %2 中的處理程序，錯誤碼為 %1。 Finished launching process in Restricted AppContainer %2 with %1.
0xBF000079正在終止受限的 AppContainer %1 中的所有處理程序。 Terminating all processes in Restricted AppContainer %1.
0xBF00007A已完成終止受限的 AppContainer %2 中的所有處理程序，錯誤碼為 %1。 Finished terminating all processes in Restricted AppContainer %2 with %1.
0xBF00007B正在檢查 %1 的套件圖形。 Checking package graph for %1.
0xBF00007C%2 的套件圖形檢查完成，狀態為 %1。 Package graph check for %2 finished with %1.
0xBF00007D正在為套件 %1 執行應用程式完整性檢查。 Performing app integrity check for package %1.
0xBF00007E套件 %2 的應用程式完整性檢查已完成，狀態為 %1。 App integrity check for package %2 finished with %1.
0xBF00007F正在為套件 %1 執行執行階段應用程式完整性檢查。 Performing runtime app integrity check for package %1.
0xBF000080套件 %2 的執行階段應用程式完整性檢查已完成，狀態為 %1。 Runtime app integrity check for package %2 finished with %1.
0xBF000081防火牆服務未執行。正在跳過為 AppContainer %1 建立防火牆規則的作業。 Firewall Service not running. Skipping creation of firewall rules for AppContainer %1.
0xBF000082更新受限的 AppContainer 功能 %1。 Updating Restricted AppContainer Capabilities %1.
0xBF000083已使用 %1 完成更新受限的 AppContainer 功能 %2。 Finished Updating Restricted AppContainer Capabilities %2 with %1.
0xBF0000C9已在套件 %2 中建立應用程式 %4 的處理程序 %1。%5 Created process %1 for application %4 in package %2. %5
0xBF0000CA%4: 因為發生錯誤，所以無法建立套件 %1 的處理程序。%5 %4: Cannot create the process for package %1 because an error was encountered. %5
0xBF0000CB%4: 因為準備啟用時發生錯誤，所以無法建立套件 %1 的處理程序。%5 %4: Cannot create the process for package %1 because an error was encountered while preparing for activation. %5
0xBF0000CC%4: 因為評估權杖時發生錯誤，所以無法建立套件 %1 的處理程序。%5 %4: Cannot create the process for package %1 because an error was encountered while elevating the token. %5
0xBF0000CD%4: 因為桌面 AppX 處理程序不支援 UI 存取，所以無法建立套件 %1 的處理程序。%5 %4: Cannot create the process for package %1 because UI Access is not supported for Desktop AppX processes. %5
0xBF0000CE%4: 因為調整權杖時發生錯誤，所以無法建立套件 %1 的處理程序。%5 %4: Cannot create the process for package %1 because an error was encountered while adjusting the token. %5
0xBF0000CF%4: 因為啟動時發生錯誤，所以無法建立套件 %1 的處理程序。%5 %4: Cannot create the process for package %1 because an error was encountered while launching. %5
0xBF0000D0%4: 因為設定執行階段時發生錯誤，所以無法建立套件 %1 的處理程序。%5 %4: Cannot create the process for package %1 because an error was encountered while configuring runtime. %5
0xBF0000D1%4: 因為繼續進行執行緒時發生錯誤，所以無法建立套件 %1 的處理程序。%5 %4: Cannot create the process for package %1 because an error was encountered while resuming the thread. %5
0xBF0000D2已建立套件 %1 的桌面 AppX 容器 %3。 Created Desktop AppX container %3 for package %1.
0xBF0000D3已將處理程序 %1 新增至套件 %2 的桌面 AppX 容器 %3。 Added process %1 to Desktop AppX container %3 for package %2.
0xBF0000D4%1: 因為發生錯誤，所以無法將處理程序 %2 新增至套件 %3 的桌面 AppX 容器 %4。 %1: Cannot add process %2 to Desktop AppX container %4 for package %3 because an error was encountered.
0xBF0000D5%1: 因為建立工作時發生錯誤，所以無法建立套件 %2 的桌面 AppX 容器。 %1: Cannot create the Desktop AppX container for package %2 because an error was encountered creating the job.
0xBF0000D6%1: 因為建立描述時發生錯誤，所以無法建立套件 %2 的桌面 AppX 容器。 %1: Cannot create the Desktop AppX container for package %2 because an error was encountered creating the description.
0xBF0000D7%1: 因為轉換工作時發生錯誤，所以無法建立套件 %2 的桌面 AppX 容器。 %1: Cannot create the Desktop AppX container for package %2 because an error was encountered converting the job.
0xBF0000D8%1: 因為設定執行階段時發生錯誤，所以無法建立套件 %2 的桌面 AppX 容器。 %1: Cannot create the Desktop AppX container for package %2 because an error was encountered configuring the runtime.
0xBF0000D9已終結套件 %1 的桌面 AppX 容器 %2。 Destroyed Desktop AppX container %2 for package %1.
0xBF0000DA無法終結套件 %1 的桌面 AppX 容器 %2。 Cannot destroy Desktop AppX container %2 for package %1.
0xD1000001開機期間初始化的系統時間 System time initialized during boot
0xD1000002應用程式或系統元件已變更時間 An application or system component changed the time
0xD1000003系統時間已與硬體時鐘同步 System time synchronized with the hardware clock
0xD1000004系統時間已調整為新時區 System time adjusted to the new time zone
0xD4000001開啟 on
0xD4000002關閉 off
0xD4000003已啟動 started
0xD4000004已完成 finished
0xD4000005平台層級裝置重設 Platform-level Device Reset
0xD4000006功能層級裝置重設 Function-level Device Reset
0xD4000007ACPI 覆寫屬性 - MpSleep Acpi Override attribute - MpSleep
0xD4000008ACPI 覆寫屬性 - DisableS1 Acpi Override attribute - DisableS1
0xD4000009ACPI 覆寫屬性 - DisableS2 Acpi Override attribute - DisableS2
0xD400000AACPI 覆寫屬性 - DisableS3 Acpi Override attribute - DisableS3
0xD400000BACPI 覆寫屬性 - DellMaxUlongBugcheck Acpi Override attribute - DellMaxUlongBugcheck
0xD400000CACPI 覆寫屬性 - PciBusNumberTranslation Acpi Override attribute - PciBusNumberTranslation
0xD400000DACPI 覆寫屬性 - RunRegMethodOnPciDevices Acpi Override attribute - RunRegMethodOnPciDevices
0xD400000EACPI 覆寫屬性 - RescanPostDependencies Acpi Override attribute - RescanPostDependencies
0xD400000FACPI 覆寫屬性 - PlatformCheckD3ColdOnSurpriseRemoval Acpi Override attribute - PlatformCheckD3ColdOnSurpriseRemoval
0xD4000010ACPI 覆寫屬性 - PlatformCheckFailResetOnOpenHandles Acpi Override attribute - PlatformCheckFailResetOnOpenHandles
0xDC000001已停用 disabled
0xDC000002已停用 (由於 HyperV 選擇退出) disabled due to HyperV opt-out
0xDC000003已停用 (由於選擇退出 UEFI 變數) disabled due to opt-out UEFI variable
0xDC000004已停用 (由於安全開機已停用) disabled due to secure boot being disabled
0xDC000005已停用 (由於 DMA 保護無法使用) disabled due to DMA protection being unavailable
0xDC000006已停用 (由於 Hypervisor 無法使用) disabled due to the hypervisor being unavailable
0xDC000007已停用 (由於 VBS 初始化失敗) disabled due to VBS initialization failure
0xDC000008已啟用 (由於 VBS 登錄設定) enabled due to VBS registry configuration
0xDC000009已啟用 (由於 HyperV) enabled due to HyperV
0xDC00000A已啟用 (由於 VBS 已鎖定設定) enabled due to VBS locked configuration
0xDC00000BBL_LOG_INFO_NONE: 無資訊 BL_LOG_INFO_NONE: Info none
0xDC00000CBL_LOG_INFO_BLI_IO_INITED: 已在開機程式庫初始化時初始化 IO。 BL_LOG_INFO_BLI_IO_INITED: IO initialized in boot library initialization.
0xDC00000DBL_LOG_INFO_BLI_FINISHED: 已在開機程式庫初始化時完成。 BL_LOG_INFO_BLI_FINISHED: Finished in boot library initialization.
0xDC00000EBL_LOG_INFO_BM_BL_INITED: 已針對 bootmgr 初始化開機程式庫。 BL_LOG_INFO_BM_BL_INITED: The boot library has been initialized for bootmgr.
0xDC00000FBL_LOG_INFO_BM_GET_BOOT_SEQ: 在 bootmgr 中取得開機序列。 BL_LOG_INFO_BM_GET_BOOT_SEQ: Getting boot sequence in bootmgr.
0xDC000010BL_LOG_INFO_BM_LAUNCH_ENTRY: 在 bootmgr 中啟動開機項目。 BL_LOG_INFO_BM_LAUNCH_ENTRY: Launching boot entry in bootmgr.
0xDC000011BL_LOG_INFO_OSL_PREPARE_ENTERED: 已達到 osloader 內的準備目標。 BL_LOG_INFO_OSL_PREPARE_ENTERED: Reached prepare target within osloader.
0xDC000012BL_LOG_INFO_OSL_OPEN_DEVICE: 準備在 osloader 中開啟 OS 裝置。 BL_LOG_INFO_OSL_OPEN_DEVICE: Preparing to open OS device in osloader.
0xDC000013BL_LOG_INFO_OSL_LAUNCH_HYPERV: 準備啟動在 osloader 內指定的 hyper-v。 BL_LOG_INFO_OSL_LAUNCH_HYPERV: Preparing to launch hyper-v if specified within osloader.
0xDC000014BL_LOG_INFO_OSL_LOAD_MODULES: 準備在 osloader 內載入 OS 模組。 BL_LOG_INFO_OSL_LOAD_MODULES: Preparing to load OS modules within osloader.
0xDC000015BL_LOG_INFO_OSL_KERNEL_SETUP: 設定 osloader 內的核心。 BL_LOG_INFO_OSL_KERNEL_SETUP: Setting up kernel within osloader.
0xDC000016BL_LOG_ERROR: 一般錯誤 BL_LOG_ERROR: Generic Error
0xDC000017BL_LOG_ERROR_BLI_NET_INIT: 在 BL 初始化時，BlNetInitialize 失敗。 BL_LOG_ERROR_BLI_NET_INIT: BlNetInitialize failed in BL initialization.
0xDC000018BL_LOG_ERROR_BLI_UTL_INIT: 在 BL 初始化時，BlUtlInitialize 失敗。 BL_LOG_ERROR_BLI_UTL_INIT: BlUtlInitialize failed in BL initialization.
0xDC000019BL_LOG_ERROR_BLI_SEC_BOOT_INIT: 在 BL 初始化時，BlSecureBootInitialize 失敗。 BL_LOG_ERROR_BLI_SEC_BOOT_INIT: BlSecureBootInitialize failed in BL initialization.
0xDC00001ABL_LOG_ERROR_BLI_PDATA_INIT: 在 BL 初始化時，BlpPdInitialize 失敗。 BL_LOG_ERROR_BLI_PDATA_INIT: BlpPdInitialize failed in BL initialization.
0xDC00001BBL_LOG_ERROR_BLI_RES_INIT: 在 BL 初始化時，BlpResourceInitialize 失敗。 BL_LOG_ERROR_BLI_RES_INIT: BlpResourceInitialize failed in BL initialization.
0xDC00001CBL_LOG_ERROR_BM_INIT_MACH_POL: bootmgr 中的 BmSecureBootInitializeMachinePolicy 失敗。 BL_LOG_ERROR_BM_INIT_MACH_POL: BmSecureBootInitializeMachinePolicy failed in bootmgr.
0xDC00001DBL_LOG_ERROR_BM_FW_REG_SYSINT: bootmgr 中的 BmFwRegisterSystemIntegrityPolicies 失敗。 BL_LOG_ERROR_BM_FW_REG_SYSINT: BmFwRegisterSystemIntegrityPolicies failed in bootmgr.
0xDC00001EBL_LOG_ERROR_BM_RES_FIND_HTML: 在 bootmgr 中，BlResourceFindHtml 找不到 BOOTMGR.XSL。 BL_LOG_ERROR_BM_RES_FIND_HTML: BlResourceFindHtml failed to find BOOTMGR.XSL in bootmgr.
0xDC00001FBL_LOG_ERROR_BM_XMI_INIT: bootmgr 中的 BlXmiInitialize 失敗。 BL_LOG_ERROR_BM_XMI_INIT: BlXmiInitialize failed in bootmgr.
0xDC000020BL_LOG_ERROR_BM_OPEN_DATA_STORE: bootmgr 中的 BmOpenDataStore 失敗。 BL_LOG_ERROR_BM_OPEN_DATA_STORE: BmOpenDataStore failed in bootmgr.
0xDC000021BL_LOG_ERROR_BM_SELF_INT_CHK: bootmgr 中的 BmpSelfIntegrityCheck 失敗。 BL_LOG_ERROR_BM_SELF_INT_CHK: BmpSelfIntegrityCheck failed in bootmgr.
0xDC000022BL_LOG_ERROR_BM_FW_REG_REV_LIST: bootmgr 中的 BmFwRegisterRevocationList 失敗。 BL_LOG_ERROR_BM_FW_REG_REV_LIST: BmFwRegisterRevocationList failed in bootmgr.
0xDC000023BL_LOG_ERROR_BM_RESUME_HIBER: bootmgr 中的 BmResumeFromHibernate 失敗。 BL_LOG_ERROR_BM_RESUME_HIBER: BmResumeFromHibernate failed in bootmgr.
0xDC000024BL_LOG_ERROR_BM_PURGE_OPT_START_SEQ: bootmgr 中的 BL_ERROR_BM_PURGE_OPT_START_SEQ 失敗。 BL_LOG_ERROR_BM_PURGE_OPT_START_SEQ: BL_ERROR_BM_PURGE_OPT_START_SEQ failed in bootmgr.
0xDC000025BL_LOG_ERROR_BM_PURGE_OPT_BOOT_SEQ: bootmgr 中的 BmPurgeOption 針對 BCDE_BOOTMGR_TYPE_BOOT_SEQUENCE 失敗。 BL_LOG_ERROR_BM_PURGE_OPT_BOOT_SEQ: BmPurgeOption failed for BCDE_BOOTMGR_TYPE_BOOT_SEQUENCE in bootmgr.
0xDC000026BL_LOG_ERROR_BM_REOPEN_DATA_STORE: bootmgr 中的 BmOpenDataStore 在重新開啟時失敗。 BL_LOG_ERROR_BM_REOPEN_DATA_STORE: BmOpenDataStore failed on reopen in bootmgr.
0xDC000027BL_LOG_ERROR_BM_UPDATE_APP_OPTS: bootmgr 中的 BmpUpdateApplicationOptions 失敗。 BL_LOG_ERROR_BM_UPDATE_APP_OPTS: BmpUpdateApplicationOptions failed in bootmgr.
0xDC000028BL_LOG_ERROR_BM_LAUNCH_BOOT_ENTRY: bootmgr 中的 BmpLaunchBootEntry 失敗。 BL_LOG_ERROR_BM_LAUNCH_BOOT_ENTRY: BmpLaunchBootEntry failed in bootmgr.
0xDC000029BL_LOG_ERROR_BM_CREATE_DEVICES: bootmgr 中的 BmpCreateDevices 失敗。 BL_LOG_ERROR_BM_CREATE_DEVICES: BmpCreateDevices failed in bootmgr.
0xDC00002ABL_LOG_ERROR_BM_LAUNCH_FLIGHT_BM: bootmgr 中的 BmFwLaunchFlightedBootmgr 失敗。 BL_LOG_ERROR_BM_LAUNCH_FLIGHT_BM: BmFwLaunchFlightedBootmgr failed in bootmgr.
0xDC00002BBL_LOG_ERROR_BM_FE_BOOTAPP_LD: 嚴重錯誤: 無法載入 bootmgr 中的開機應用程式。 BL_LOG_ERROR_BM_FE_BOOTAPP_LD: Fatal error: failure to load boot app in bootmgr.
0xDC00002CBL_LOG_ERROR_BM_FE_CONFIG_DATA: 嚴重錯誤: 嘗試讀取 bootmgr 中的開機組態檔時失敗。 BL_LOG_ERROR_BM_FE_CONFIG_DATA: Fatal error: failure attempting to read boot config file in bootmgr.
0xDC00002DBL_LOG_ERROR_BM_FE_NO_VALID_OS_ENTRY: 嚴重錯誤: 在 bootmgr 中，找不到有效的 OS 項目。 BL_LOG_ERROR_BM_FE_NO_VALID_OS_ENTRY: Fatal error: no valid os entires found in bootmgr.
0xDC00002EBL_LOG_ERROR_BM_FE_NO_VALID_PXE_ENTRY: 嚴重錯誤: 在 bootmgr 中，找不到來自 PXE 伺服器的有效項目。 BL_LOG_ERROR_BM_FE_NO_VALID_PXE_ENTRY: Fatal error: no valid entries found from PXE server in bootmgr.
0xDC00002FBL_LOG_ERROR_BM_FE_FAILURE_STATUS: 嚴重錯誤: bootmgr 中的失敗狀態。 BL_LOG_ERROR_BM_FE_FAILURE_STATUS: Fatal error: failure status in bootmgr.
0xDC000030BL_LOG_ERROR_BM_FE_BOOT_DEVICE: 嚴重錯誤: 在 bootmgr 中無法存取開機裝置。 BL_LOG_ERROR_BM_FE_BOOT_DEVICE: Fatal error: boot device inaccessible in bootmgr.
0xDC000031BL_LOG_ERROR_BM_FE_RAMDISK_MEM: 嚴重錯誤: bootmgr 中 ramdisk 裝置建立的記憶體不足。 BL_LOG_ERROR_BM_FE_RAMDISK_MEM: Fatal error: ramdisk device creation had insufficient memory in bootmgr.
0xDC000032BL_LOG_ERROR_BM_FE_INVALID_BCD_STORE: 嚴重錯誤: bootmgr 中的 BCD 無效。 BL_LOG_ERROR_BM_FE_INVALID_BCD_STORE: Fatal error: BCD is invalid in bootmgr.
0xDC000033BL_LOG_ERROR_BM_FE_INVALID_BCD_ENTRY: 嚴重錯誤: bootmgr 中的 BCD 項目無效。 BL_LOG_ERROR_BM_FE_INVALID_BCD_ENTRY: Fatal error: Invalid BCD entry in bootmgr.
0xDC000034BL_LOG_ERROR_BM_FE_NO_SECUREBOOT_POL: 嚴重錯誤: 在 bootmgr 中找不到預設安全開機原則。 BL_LOG_ERROR_BM_FE_NO_SECUREBOOT_POL: Fatal error: Default Secure Boot policy not found in bootmgr.
0xDC000035BL_LOG_ERROR_BM_FE_NO_PAE_SUPPORT: 嚴重錯誤: CPU 不支援 bootmgr 中的 PAE。 BL_LOG_ERROR_BM_FE_NO_PAE_SUPPORT: Fatal error: CPU does not support PAE in bootmgr.
0xDC000036BL_LOG_ERROR_BM_FE_UNSEAL_NOT_POS: 嚴重錯誤: 無法解密 bootmgr 中的敏感性資料。 BL_LOG_ERROR_BM_FE_UNSEAL_NOT_POS: Fatal error: Cannot unseal sensitive data in bootmgr.
0xDC000037BL_LOG_ERROR_BM_FE_GENERIC: 嚴重錯誤: bootmgr 中的一般失敗。 BL_LOG_ERROR_BM_FE_GENERIC: Fatal error: Generic failure in bootmgr.
0xDC000038BL_LOG_ERROR_OSL_REM_INTERN_APP_OPTS: osloader 中的 OslpRemoveInternalApplicationOptions 失敗。 BL_LOG_ERROR_OSL_REM_INTERN_APP_OPTS: OslpRemoveInternalApplicationOptions failed in osloader.
0xDC000039BL_LOG_ERROR_OSL_GET_APP_OPT_DEVICE: osloader 中的 BlGetApplicationOptionDevice 針對 BCDE_OSLOADER_TYPE_OS_DEVICE 失敗。 BL_LOG_ERROR_OSL_GET_APP_OPT_DEVICE: BlGetApplicationOptionDevice failed for BCDE_OSLOADER_TYPE_OS_DEVICE in osloader.
0xDC00003ABL_LOG_ERROR_OSL_GET_APP_OPT_STR: osloader 中的 BlGetApplicationOptionString 針對 BCDE_OSLOADER_TYPE_SYSTEM_ROOT 失敗。 BL_LOG_ERROR_OSL_GET_APP_OPT_STR: BlGetApplicationOptionString failed for BCDE_OSLOADER_TYPE_SYSTEM_ROOT in osloader.
0xDC00003BBL_LOG_ERROR_OSL_FORCED_FAIL: osloader 中的 OslpCheckForcedFailure 失敗，表示強制失敗。 BL_LOG_ERROR_OSL_FORCED_FAIL: OslpCheckForcedFailure failed implying a forced failure in osloader.
0xDC00003CBL_LOG_ERROR_OSL_DISABLE_VGA: osloader 中的 BlAppendApplicationOptionBoolean 針對 BCDE_OSLOADER_TYPE_DISABLE_VGA_MODE 失敗。 BL_LOG_ERROR_OSL_DISABLE_VGA: BlAppendApplicationOptionBoolean for BCDE_OSLOADER_TYPE_DISABLE_VGA_MODE failed in osloader.
0xDC00003DBL_LOG_ERROR_OSL_OPEN_OS_DEVICE: osloader 中的 BlDeviceOpen 針對 OS 裝置失敗。 BL_LOG_ERROR_OSL_OPEN_OS_DEVICE: BlDeviceOpen failed for os device in osloader.
0xDC00003EBL_LOG_ERROR_OSL_LOAD_SYS_HIVE: osloader 中的 OslpLoadSystemHive 失敗。 BL_LOG_ERROR_OSL_LOAD_SYS_HIVE: OslpLoadSystemHive failed in osloader.
0xDC00003FBL_LOG_ERROR_OSL_CREATE_OS_LD_OPTS: osloader 中的 AhCreateLoadOptionsString 失敗。 BL_LOG_ERROR_OSL_CREATE_OS_LD_OPTS: AhCreateLoadOptionsString failed in osloader.
0xDC000040BL_LOG_ERROR_OSL_DISPLAY_INIT: osloader 中的 OslDisplayInitialize 失敗。 BL_LOG_ERROR_OSL_DISPLAY_INIT: OslDisplayInitialize failed in osloader.
0xDC000041BL_LOG_ERROR_OSL_PROCESS_SI_POLICY: osloader 中的 OslpProcessSIPolicy 失敗。 BL_LOG_ERROR_OSL_PROCESS_SI_POLICY: OslpProcessSIPolicy failed in osloader.
0xDC000042BL_LOG_ERROR_OSL_DISP_ADV_OPT: osloader 中的 OslDisplayAdvancedOptionsProcess 失敗。 BL_LOG_ERROR_OSL_DISP_ADV_OPT: OslDisplayAdvancedOptionsProcess failed in osloader.
0xDC000043BL_LOG_ERROR_OSL_ARCH_HV_SETUP: osloader 中的 OslArchHypervisorSetup 失敗。 BL_LOG_ERROR_OSL_ARCH_HV_SETUP: OslArchHypervisorSetup failed in osloader.
0xDC000044BL_LOG_ERROR_OSL_ARCH_HYPERCALL_SETUP: osloader 中的 OslArchHypercallSetup 失敗。 BL_LOG_ERROR_OSL_ARCH_HYPERCALL_SETUP: OslArchHypercallSetup failed in osloader.
0xDC000045BL_LOG_ERROR_OSL_INIT_RESUME_CONTEXT: osloader 中的 OslInitializeResumeContext 失敗。 BL_LOG_ERROR_OSL_INIT_RESUME_CONTEXT: OslInitializeResumeContext failed in osloader.
0xDC000046BL_LOG_ERROR_OSL_INIT_LDR_BLOCK: osloader 中的 OslInitializeLoaderBlock 失敗。 BL_LOG_ERROR_OSL_INIT_LDR_BLOCK: OslInitializeLoaderBlock failed in osloader.
0xDC000047BL_LOG_ERROR_OSL_PROC_INIT_MACH_CONFIG: osloader 中的 OslpProcessInitialMachineConfiguration 失敗。 BL_LOG_ERROR_OSL_PROC_INIT_MACH_CONFIG: OslpProcessInitialMachineConfiguration failed in osloader.
0xDC000048BL_LOG_ERROR_OSL_ENUM_DISKS: osloader 中的 OslEnumerateDisks 針對載入器區塊失敗。 BL_LOG_ERROR_OSL_ENUM_DISKS: OslEnumerateDisks failed for the loader block in osloader.
0xDC000049BL_LOG_ERROR_OSL_REINIT_SYS_HIVE: osloader 中的 OslpReinitializeSystemHive 失敗。 BL_LOG_ERROR_OSL_REINIT_SYS_HIVE: OslpReinitializeSystemHive failed in osloader.
0xDC00004ABL_LOG_ERROR_OSL_INIT_CODE_INT: osloader 中的 OslInitializeCodeIntegrity 失敗。 BL_LOG_ERROR_OSL_INIT_CODE_INT: OslInitializeCodeIntegrity failed in osloader.
0xDC00004BBL_LOG_ERROR_OSL_INIT_CODE_INT_LD_BLOCK: osloader 中的 OslBuildCodeIntegrityLoaderBlock 失敗。 BL_LOG_ERROR_OSL_INIT_CODE_INT_LD_BLOCK: OslBuildCodeIntegrityLoaderBlock failed in osloader.
0xDC00004CBL_LOG_ERROR_OSL_SECURE_BOOT_VARS: osloader 中的 OslFwProtectSecureBootVariables 失敗。 BL_LOG_ERROR_OSL_SECURE_BOOT_VARS: OslFwProtectSecureBootVariables failed in osloader.
0xDC00004DBL_LOG_ERROR_OSL_LD_MODULES: osloader 中的 OslpLoadAllModules 失敗。 BL_LOG_ERROR_OSL_LD_MODULES: OslpLoadAllModules failed in osloader.
0xDC00004EBL_LOG_ERROR_OSL_LD_FW_DRIVERS: osloader 中的 OslFwLoadFirmwareDrivers 失敗。 BL_LOG_ERROR_OSL_LD_FW_DRIVERS: OslFwLoadFirmwareDrivers failed in osloader.
0xDC00004FBL_LOG_ERROR_OSL_VSM_CHK_ENCRYPT_KEY: osloader 中的 BlVsmCheckSystemPolicy 針對主要 sncrupt 金鑰佈建失敗。 BL_LOG_ERROR_OSL_VSM_CHK_ENCRYPT_KEY: BlVsmCheckSystemPolicy failed for master sncrupt key provisioning in osloader.
0xDC000050BL_LOG_ERROR_OSL_VSM_CHK_PHASE_0: osloader 中的 BlVsmCheckSystemPolicy 針對階段 0 失敗。 BL_LOG_ERROR_OSL_VSM_CHK_PHASE_0: BlVsmCheckSystemPolicy failed for phase 0 in osloader.
0xDC000051BL_LOG_ERROR_OSL_SET_SEIL_SIGN_POL: osloader 中的 OslSetSeILSigningPolicy 失敗。 BL_LOG_ERROR_OSL_SET_SEIL_SIGN_POL: OslSetSeILSigningPolicy failed in osloader.
0xDC000052BL_LOG_ERROR_OSL_CMS_PROV_IDK: osloader 中的 BlVsmCheckSystemPolicy 在 VSM 身分識別關鍵工作期間失敗。 BL_LOG_ERROR_OSL_CMS_PROV_IDK: BlVsmCheckSystemPolicy failed during VSM Idendity key work in osloader.
0xDC000053BL_LOG_ERROR_OSL_ARCH_KERNEL_SETUP_0: osloader 中的 OslArchKernelSetup 針對 0 失敗。 BL_LOG_ERROR_OSL_ARCH_KERNEL_SETUP_0: OslArchKernelSetup failed for 0 in osloader.
0xDC000054BL_LOG_ERROR_OSL_FW_KERNEL_SETUP: osloader 中的 OslFwKernelSetup 針對 0 失敗。 BL_LOG_ERROR_OSL_FW_KERNEL_SETUP: OslFwKernelSetup failed for 0 in osloader.
0xDC000055BL_LOG_ERROR_OSL_PROC_EV_STORE: osloader 中的 OslpProcessEVStore 失敗。 BL_LOG_ERROR_OSL_PROC_EV_STORE: OslpProcessEVStore failed in osloader.
0xDC000056BL_LOG_ERROR_OSL_COPY_BOOT_OPTS: osloader 中的 BlCopyBootOptions 失敗。 BL_LOG_ERROR_OSL_COPY_BOOT_OPTS: BlCopyBootOptions failed in osloader.
0xDC000057BL_LOG_ERROR_OSL_FVE_SEC_BOOT_REST_ONE: osloader 中的 BlFveSecureBootRestrictToOne 失敗。 BL_LOG_ERROR_OSL_FVE_SEC_BOOT_REST_ONE: BlFveSecureBootRestrictToOne failed in osloader.
0xDC000058BL_LOG_ERROR_OSL_NET_UNDI_CLOSE: osloader 中的 BlNetUndiClose 失敗。 BL_LOG_ERROR_OSL_NET_UNDI_CLOSE: BlNetUndiClose failed in osloader.
0xDC000059BL_LOG_ERROR_OSL_PROC_APP_PDATA: osloader 中的 OslProcessApplicationPersistentData 失敗。 BL_LOG_ERROR_OSL_PROC_APP_PDATA: OslProcessApplicationPersistentData failed in osloader.
0xDC00005ABL_LOG_ERROR_OSL_BLD_MEM_CACHE_REQ_LIST: osloader 中的 OslFwBuildMemoryCachingRequirementsList 失敗。 BL_LOG_ERROR_OSL_BLD_MEM_CACHE_REQ_LIST: OslFwBuildMemoryCachingRequirementsList failed in osloader.
0xDC00005BBL_LOG_ERROR_OSL_BLD_RT_MEM_MAP: osloader 中的 OslFwBuildRuntimeMemoryMap 失敗。 BL_LOG_ERROR_OSL_BLD_RT_MEM_MAP: OslFwBuildRuntimeMemoryMap failed in osloader.
0xDC00005CBL_LOG_ERROR_OSL_VSM_SETUP: osloader 中的 OslVsmSetup 針對 1 失敗。 BL_LOG_ERROR_OSL_VSM_SETUP: OslVsmSetup failed for 1 in osloader.
0xDC00005DBL_LOG_ERROR_OSL_BLD_KERNEL_MEM_MAP: osloader 中的 BlTraceBuildKernelMemoryMapStop 失敗。 BL_LOG_ERROR_OSL_BLD_KERNEL_MEM_MAP: BlTraceBuildKernelMemoryMapStop failed in osloader.
0xDC00005EBL_LOG_ERROR_OSL_ARCH_KERNEL_SETUP_1: osloader 中的 OslArchKernelSetup 針對 1 失敗。 BL_LOG_ERROR_OSL_ARCH_KERNEL_SETUP_1: OslArchKernelSetup failed for 1 in osloader.
0xDC00005FBL_LOG_ERROR_OSL_SET_VSM_POL_SYS_HIVE: osloader 中的 OslSetVsmPolicy 失敗。 BL_LOG_ERROR_OSL_SET_VSM_POL_SYS_HIVE: OslSetVsmPolicy failed in osloader.
0xDC000060BL_LOG_ERROR_OSL_ENUM_ENCLAVE_PAGES: osloader 中的 OslEnumerateEnclavePageRegions 失敗。 BL_LOG_ERROR_OSL_ENUM_ENCLAVE_PAGES: OslEnumerateEnclavePageRegions failed in osloader.
0xDC000061BL_LOG_ERROR_OSL_GATHER_ENTROPY: osloader 中的 OslGatherEntropy 失敗。 BL_LOG_ERROR_OSL_GATHER_ENTROPY: OslGatherEntropy failed in osloader.
0xDE000001已透過登錄套用 applied through registry
0xDE000002已透過相容性資料庫套用 applied through compatibility database
0xF2000001PackageId PackageId
0xFC000001無 None
0xFC000002VBS 已啟用 VBS Enabled
0xFC000003需要 VSM VSM Required
0xFC000004安全開機 Secure Boot
0xFC000005Iommu 保護 Iommu Protection
0xFC000006Mmio Nx Mmio Nx
0xFC000007強式 MSR 篩選 Strong MSR Filtering
0xFC000008必要 Mandatory
0xFC000009Hvci Hvci
0xFC00000AHvci 強制 Hvci Strict
0xFC00000B開機鏈結簽署者軟強制 Boot Chain Signer Soft Enforced
0xFC00000C開機鏈結簽署者硬強制 Boot Chain Signer Hard Enforced

EXIF

File Name:microsoft-windows-system-events.dll.mui
Directory:%WINDIR%\WinSxS\amd64_microsoft-windows-s..container.resources_31bf3856ad364e35_10.0.15063.0_zh-tw_c9c68eeaa7153552\
File Size:67 kB
File Permissions:rw-rw-rw-
File Type:Win32 DLL
File Type Extension:dll
MIME Type:application/octet-stream
Machine Type:Intel 386 or later, and compatibles
Time Stamp:0000:00:00 00:00:00
PE Type:PE32
Linker Version:14.10
Code Size:0
Initialized Data Size:68096
Uninitialized Data Size:0
Entry Point:0x0000
OS Version:10.0
Image Version:10.0
Subsystem Version:6.0
Subsystem:Windows GUI
File Version Number:10.0.15063.0
Product Version Number:10.0.15063.0
File Flags Mask:0x003f
File Flags:(none)
File OS:Windows NT 32-bit
Object File Type:Executable application
File Subtype:0
Language Code:Chinese (Traditional)
Character Set:Unicode
Company Name:Microsoft Corporation
File Description:Microsoft-Windows-System-Events 資源
File Version:10.0.15063.0 (WinBuild.160101.0800)
Internal Name:microsoft-windows-system-events.dll
Legal Copyright:© Microsoft Corporation. All rights reserved.
Original File Name:microsoft-windows-system-events.dll.mui
Product Name:Microsoft® Windows® Operating System
Product Version:10.0.15063.0

What is microsoft-windows-system-events.dll.mui?

microsoft-windows-system-events.dll.mui is Multilingual User Interface resource file that contain Chinese (Traditional) language for file microsoft-windows-system-events.dll (Microsoft-Windows-System-Events 資源).

File version info

File Description:Microsoft-Windows-System-Events 資源
File Version:10.0.15063.0 (WinBuild.160101.0800)
Company Name:Microsoft Corporation
Internal Name:microsoft-windows-system-events.dll
Legal Copyright:© Microsoft Corporation. All rights reserved.
Original Filename:microsoft-windows-system-events.dll.mui
Product Name:Microsoft® Windows® Operating System
Product Version:10.0.15063.0
Translation:0x404, 1200