microsoft-windows-system-events.dll.mui Microsoft Windows 系统事件资源 bb797f3e76c56172784600f23bf5df2e

  1. File Info
  2. MUI

File info

File name: microsoft-windows-system-events.dll.mui
Size: 67584 byte
MD5: bb797f3e76c56172784600f23bf5df2e
SHA1: dd4a048eb41ad7293c5c3d69c8a4a500a4c3cf1b
SHA256: 6b2bc1fc1456d08aef16e28e0f21e2b9deb8c8aad40a48bfb8286f5af597adf7
Operating systems: Windows 10
Extension: MUI

Translations messages and strings

If an error occurred or the following message in Chinese (Simplified) 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 (Simplified) 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尝试修改注册表项 %4 时，可执行文件 %2 收到“访问被拒绝”错误。 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.
0x205TCPv4: 已从 %4:%6 到 %3:%5 重新传输了 %2 字节。 TCPv4: %2 bytes retransmitted from %4:%6 to %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.
0x211TCPv6: 已从 %4:%6 到 %3:%5 重新传输了 %2 字节。 TCPv6: %2 bytes retransmitted from %4:%6 to %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已从磁盘 %1 中的 %5 读取了 %3 字节。 %3 bytes read from disk %1 at %5.
0x25A已向磁盘 %1 中的 %5 写入了 %3 字节。 %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 的完整性检查失败，原因是 %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已向 Windows 事件跟踪注册了提供程序 %1。 Provider %1 was registered with Event Tracing for Windows.
0x38F已从 Windows 事件跟踪注销了提供程序 %1。 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
0x3B4OS 版本不匹配 OS version mismatch
0x3B5指针大小不匹配 Pointer size mismatch
0x3B6BufferSize 不受支持 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
0x3C7由于在相关设备上已检测到并已处理的数据损坏实例重复发生，因而删除了 ReadyBoost 缓存。尽管 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.
0x3C8由于在相关设备上重复发生 I/O 故障，因而删除了 ReadyBoost 缓存。通常在删除设备(例如，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 字节)。虚拟机监控程序: 主要: %3 字节。次要: %4 字节。 Sizing Workflow: Estimation. NT: %2 bytes (Minimum %1 bytes). Hypervisor: Primary %3 bytes. Secondary %4 bytes.
0x475“调整大小”工作流: 分配。NT: %1 字节。虚拟机监控程序: 主要: %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不允许 %1 尝试从当前目录加载依赖关系 %2。找到了另一个 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不允许 %1 尝试从当前目录加载依赖项 %2。未找到其他 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)是状态为 %1 的 %2 Virtualization-based security (policies: %3) is %2 with status: %1
0x0F000009由于 Windows 二进制文件 %3 出现问题，因此应用 %1 已终止，错误为 %2。这可能是因为该二进制文件未签名、包含不受信任的签名或者已被损坏或篡改。请恢复电脑以解决此问题。 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
0x16000007无法加载 DLL。 A dll failed to load.
0x16000008启动 16 位应用程序 Launch 16bit application
0x16000009按需 Windows 组件。 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.
0x30000011为 SEM 配置的方案数超过了所允许的最大方案数。 The SEM is configured with more scenarios than the maximum allowed count.
0x30000012为 SEM 配置的方案中包含过多上下文提供程序。 The SEM is configured with a scenario with too many context providers.
0x30000013为 SEM 配置的方案中包含过多结束事件。 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 (事件 ID %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 (事件 ID %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 (事件 ID %2)中正在实施的方案超时，并且已由方案事件映射器自动停止。 An in-flight scenario from provider %1 (event ID %2) timed out and was stopped automatically by the Scenario Event Mapper.
0xB0000023方案事件映射器无法启动提供程序 %1 (事件 ID %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 (事件 ID %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 (事件 ID %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 (事件 ID %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 (事件 ID %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 (事件 ID %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 (事件 ID %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系统时间已从 %1 更改为 %2。 The system time has changed to %1 from %2.
0xB2000001在时间 %2 由父进程 %3 启动的进程 %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 已由运行在名为 %6 的会话 %4 中的父级 %3 在 %2 时启动。 Enumerated process %1 had started at time %2 by parent %3 running in session %4 with name %6.
0xB2010001在时间 %2 由父进程 %3 启动的进程 %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 的温度更改通知(Notify(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 的跳变点更改通知(Notify(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无法将界面语言更改为“%1”。状态代码为: %2。 Failed to change UI Language to \"%1\". Status code is: %2.
0xB500271B无法将界面语言回退顺序更改为“%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用户使用值“%2”更改当前用户区域设置“%1”时出错。错误代码为: %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用户已将其界面语言更改为“%1”。 The user has changed their UI Language to \"%1\".
0xB50032D4用户已将其界面语言回退顺序更改为“%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.
0xB6000005按需 Windows 组件 %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在标志设置为 %1、新语言设置为 %2、以前的语言设置为 %3 的情况下，调用了用户界面语言更改的 MUI 通知。扩展标志已设置为 %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，且配置已设置为 %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.
0xBC00000B在 Bootmgr 之前的用时(基于 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.
0xBC00002D正在预配 VSM 标识密钥。解封缓存副本状态: %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.
0xBC000033正在预配 VSM 主加密密钥。使用缓存的副本状态: %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由于 %2 个无人认领的分配未处理，软重启无法完成，状态: %1 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已由父进程 %3 在时间 %2 启动且作为带有可执行文件 %5 的程序包 %4 运行的进程 %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由于应用程序二进制文件 %3 出现问题，应用 %1 已终止，错误为 %2。这可能是因为该二进制文件未签名、包含不受信任的签名或者已被损坏或篡改。请重新安装该应用程序以解决此问题。 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由于错误 %2，应用 %1 禁止加载生成的二进制文件 %3。这可能是因为该二进制文件未签名、包含不受信任的签名或者已被损坏或篡改。 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、进程 ID=%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、进程 ID=%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、进程 ID=%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、进程 ID=%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 (进程 ID=%3)。 %2: Package runtime information %1 failed to load (processid=%3).
0xBF000013由于发生了异常 %2，因此无法加载程序包运行时信息 %1。 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，进程 ID=%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).
0xBF000048AppModel 运行时状态版本已成功更新。 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由于在操作类型 %3 中发生了以下错误(%2)，无法刷新程序包运行时信息 %1。 Package runtime information %1 failed to refresh because the following error %2 occurred in operation type %3.
0xBF00004B错误 %2: 在打开 HKEY_USERS 注册表项时遇到以下错误，因此无法注册 %1 程序包 error %2: Cannot register the %1 package because the following error was encountered while opening the HKEY_USERS registry key
0xBF00004C错误 %4: 在枚举以删除 %2\\%3 程序包系列注册表项时遇到以下错误，因此无法注册 %1 程序包 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: 在创建 %2\\%3 程序包系列注册表项时遇到以下错误，因此无法注册 %1 程序包 error %4 : Cannot register the %1 package because the following error was encountered while creating the %2\\%3 package family registry key
0xBF00004E错误 %4: 在删除 %2\\%3 程序包系列注册表项时遇到以下错误，因此无法注册 %1 程序包 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 的所有受限制 AppContainer。 Enumerating all Restricted AppContainers for %1.
0xBF000076已完成枚举 AppContainer %2 的所有受限制 AppContainer，并显示 %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已完成受限 AppContainer 功能 %2 的更新，并显示 %1。 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: 无法为程序包 %1 创建进程，因为桌面 AppX 进程不支持 UI 访问。%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
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因虚拟机监控程序不可用而禁用 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: 已在 OS 加载程序内达到准备目标。 BL_LOG_INFO_OSL_PREPARE_ENTERED: Reached prepare target within osloader.
0xDC000012BL_LOG_INFO_OSL_OPEN_DEVICE: 正在 OS 加载程序内准备打开 OS 设备。 BL_LOG_INFO_OSL_OPEN_DEVICE: Preparing to open OS device in osloader.
0xDC000013BL_LOG_INFO_OSL_LAUNCH_HYPERV: 正在 OS 加载程序内准备启动 Hyper-v (如果指定)。 BL_LOG_INFO_OSL_LAUNCH_HYPERV: Preparing to launch hyper-v if specified within osloader.
0xDC000014BL_LOG_INFO_OSL_LOAD_MODULES: 正在 OS 加载程序内准备加载 OS 模块。 BL_LOG_INFO_OSL_LOAD_MODULES: Preparing to load OS modules within osloader.
0xDC000015BL_LOG_INFO_OSL_KERNEL_SETUP: 正在 OS 加载程序内设置内核。 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: BlNetInitialize 在 BL 初始化中失败。 BL_LOG_ERROR_BLI_NET_INIT: BlNetInitialize failed in BL initialization.
0xDC000018BL_LOG_ERROR_BLI_UTL_INIT: BlUtlInitialize 在 BL 初始化中失败。 BL_LOG_ERROR_BLI_UTL_INIT: BlUtlInitialize failed in BL initialization.
0xDC000019BL_LOG_ERROR_BLI_SEC_BOOT_INIT: BlSecureBootInitialize 在 BL 初始化中失败。 BL_LOG_ERROR_BLI_SEC_BOOT_INIT: BlSecureBootInitialize failed in BL initialization.
0xDC00001ABL_LOG_ERROR_BLI_PDATA_INIT: BlpPdInitialize 在 BL 初始化中失败。 BL_LOG_ERROR_BLI_PDATA_INIT: BlpPdInitialize failed in BL initialization.
0xDC00001BBL_LOG_ERROR_BLI_RES_INIT: BlpResourceInitialize 在 BL 初始化中失败。 BL_LOG_ERROR_BLI_RES_INIT: BlpResourceInitialize failed in BL initialization.
0xDC00001CBL_LOG_ERROR_BM_INIT_MACH_POL: BmSecureBootInitializeMachinePolicy 在 bootmgr 中失败。 BL_LOG_ERROR_BM_INIT_MACH_POL: BmSecureBootInitializeMachinePolicy failed in bootmgr.
0xDC00001DBL_LOG_ERROR_BM_FW_REG_SYSINT: BmFwRegisterSystemIntegrityPolicies 在 bootmgr 中失败。 BL_LOG_ERROR_BM_FW_REG_SYSINT: BmFwRegisterSystemIntegrityPolicies failed in bootmgr.
0xDC00001EBL_LOG_ERROR_BM_RES_FIND_HTML: BlResourceFindHtml 无法在 bootmgr 中找到 BOOTMGR.XSL。 BL_LOG_ERROR_BM_RES_FIND_HTML: BlResourceFindHtml failed to find BOOTMGR.XSL in bootmgr.
0xDC00001FBL_LOG_ERROR_BM_XMI_INIT: BlXmiInitialize 在 bootmgr 中失败。 BL_LOG_ERROR_BM_XMI_INIT: BlXmiInitialize failed in bootmgr.
0xDC000020BL_LOG_ERROR_BM_OPEN_DATA_STORE: BmOpenDataStore 在 bootmgr 中失败。 BL_LOG_ERROR_BM_OPEN_DATA_STORE: BmOpenDataStore failed in bootmgr.
0xDC000021BL_LOG_ERROR_BM_SELF_INT_CHK: BmpSelfIntegrityCheck 在 bootmgr 中失败。 BL_LOG_ERROR_BM_SELF_INT_CHK: BmpSelfIntegrityCheck failed in bootmgr.
0xDC000022BL_LOG_ERROR_BM_FW_REG_REV_LIST: BmFwRegisterRevocationList 在 bootmgr 中失败。 BL_LOG_ERROR_BM_FW_REG_REV_LIST: BmFwRegisterRevocationList failed in bootmgr.
0xDC000023BL_LOG_ERROR_BM_RESUME_HIBER: BmResumeFromHibernate 在 bootmgr 中失败。 BL_LOG_ERROR_BM_RESUME_HIBER: BmResumeFromHibernate failed in bootmgr.
0xDC000024BL_LOG_ERROR_BM_PURGE_OPT_START_SEQ: BL_ERROR_BM_PURGE_OPT_START_SEQ 在 bootmgr 中失败。 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: BmPurgeOption 在 bootmgr 中对 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: BmOpenDataStore 在 bootmgr 中执行重新打开操作时失败。 BL_LOG_ERROR_BM_REOPEN_DATA_STORE: BmOpenDataStore failed on reopen in bootmgr.
0xDC000027BL_LOG_ERROR_BM_UPDATE_APP_OPTS: BmpUpdateApplicationOptions 在 bootmgr 中失败。 BL_LOG_ERROR_BM_UPDATE_APP_OPTS: BmpUpdateApplicationOptions failed in bootmgr.
0xDC000028BL_LOG_ERROR_BM_LAUNCH_BOOT_ENTRY: BmpLaunchBootEntry 在 bootmgr 中失败。 BL_LOG_ERROR_BM_LAUNCH_BOOT_ENTRY: BmpLaunchBootEntry failed in bootmgr.
0xDC000029BL_LOG_ERROR_BM_CREATE_DEVICES: BmpCreateDevices 在 bootmgr 中失败。 BL_LOG_ERROR_BM_CREATE_DEVICES: BmpCreateDevices failed in bootmgr.
0xDC00002ABL_LOG_ERROR_BM_LAUNCH_FLIGHT_BM: BmFwLaunchFlightedBootmgr 在 bootmgr 中失败。 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: OslpRemoveInternalApplicationOptions 在 OS 加载程序中失败。 BL_LOG_ERROR_OSL_REM_INTERN_APP_OPTS: OslpRemoveInternalApplicationOptions failed in osloader.
0xDC000039BL_LOG_ERROR_OSL_GET_APP_OPT_DEVICE: BlGetApplicationOptionDevice 在 OS 加载程序中对 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: BlGetApplicationOptionString 在 OS 加载程序中对 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: OslpCheckForcedFailure 失败，表明 OS 加载程序中发生强制失败。 BL_LOG_ERROR_OSL_FORCED_FAIL: OslpCheckForcedFailure failed implying a forced failure in osloader.
0xDC00003CBL_LOG_ERROR_OSL_DISABLE_VGA: 用于 BCDE_OSLOADER_TYPE_DISABLE_VGA_MODE 的 BlAppendApplicationOptionBoolean 在 OS 加载程序中失败。 BL_LOG_ERROR_OSL_DISABLE_VGA: BlAppendApplicationOptionBoolean for BCDE_OSLOADER_TYPE_DISABLE_VGA_MODE failed in osloader.
0xDC00003DBL_LOG_ERROR_OSL_OPEN_OS_DEVICE: BlDeviceOpen 在 OS 加载程序中对 OS 设备失败。 BL_LOG_ERROR_OSL_OPEN_OS_DEVICE: BlDeviceOpen failed for os device in osloader.
0xDC00003EBL_LOG_ERROR_OSL_LOAD_SYS_HIVE: OslpLoadSystemHive 在 OS 加载程序中失败。 BL_LOG_ERROR_OSL_LOAD_SYS_HIVE: OslpLoadSystemHive failed in osloader.
0xDC00003FBL_LOG_ERROR_OSL_CREATE_OS_LD_OPTS: AhCreateLoadOptionsString 在 OS 加载程序中失败。 BL_LOG_ERROR_OSL_CREATE_OS_LD_OPTS: AhCreateLoadOptionsString failed in osloader.
0xDC000040BL_LOG_ERROR_OSL_DISPLAY_INIT: OslDisplayInitialize 在 OS 加载程序中失败。 BL_LOG_ERROR_OSL_DISPLAY_INIT: OslDisplayInitialize failed in osloader.
0xDC000041BL_LOG_ERROR_OSL_PROCESS_SI_POLICY: OslpProcessSIPolicy 在 OS 加载程序中失败。 BL_LOG_ERROR_OSL_PROCESS_SI_POLICY: OslpProcessSIPolicy failed in osloader.
0xDC000042BL_LOG_ERROR_OSL_DISP_ADV_OPT: OslDisplayAdvancedOptionsProcess 在 OS 加载程序中失败。 BL_LOG_ERROR_OSL_DISP_ADV_OPT: OslDisplayAdvancedOptionsProcess failed in osloader.
0xDC000043BL_LOG_ERROR_OSL_ARCH_HV_SETUP: OslArchHypervisorSetup 在 OS 加载程序中失败。 BL_LOG_ERROR_OSL_ARCH_HV_SETUP: OslArchHypervisorSetup failed in osloader.
0xDC000044BL_LOG_ERROR_OSL_ARCH_HYPERCALL_SETUP: OslArchHypercallSetup 在 OS 加载程序中失败。 BL_LOG_ERROR_OSL_ARCH_HYPERCALL_SETUP: OslArchHypercallSetup failed in osloader.
0xDC000045BL_LOG_ERROR_OSL_INIT_RESUME_CONTEXT: OslInitializeResumeContext 在 OS 加载程序中失败。 BL_LOG_ERROR_OSL_INIT_RESUME_CONTEXT: OslInitializeResumeContext failed in osloader.
0xDC000046BL_LOG_ERROR_OSL_INIT_LDR_BLOCK: OslInitializeLoaderBlock 在 OS 加载程序中失败。 BL_LOG_ERROR_OSL_INIT_LDR_BLOCK: OslInitializeLoaderBlock failed in osloader.
0xDC000047BL_LOG_ERROR_OSL_PROC_INIT_MACH_CONFIG: OslpProcessInitialMachineConfiguration 在 OS 加载程序中失败。 BL_LOG_ERROR_OSL_PROC_INIT_MACH_CONFIG: OslpProcessInitialMachineConfiguration failed in osloader.
0xDC000048BL_LOG_ERROR_OSL_ENUM_DISKS: OslEnumerateDisks 在 OS 加载程序中对加载程序块失败。 BL_LOG_ERROR_OSL_ENUM_DISKS: OslEnumerateDisks failed for the loader block in osloader.
0xDC000049BL_LOG_ERROR_OSL_REINIT_SYS_HIVE: OslpReinitializeSystemHive 在 OS 加载程序中失败。 BL_LOG_ERROR_OSL_REINIT_SYS_HIVE: OslpReinitializeSystemHive failed in osloader.
0xDC00004ABL_LOG_ERROR_OSL_INIT_CODE_INT: OslInitializeCodeIntegrity 在 OS 加载程序中失败。 BL_LOG_ERROR_OSL_INIT_CODE_INT: OslInitializeCodeIntegrity failed in osloader.
0xDC00004BBL_LOG_ERROR_OSL_INIT_CODE_INT_LD_BLOCK: OslBuildCodeIntegrityLoaderBlock 在 OS 加载程序中失败。 BL_LOG_ERROR_OSL_INIT_CODE_INT_LD_BLOCK: OslBuildCodeIntegrityLoaderBlock failed in osloader.
0xDC00004CBL_LOG_ERROR_OSL_SECURE_BOOT_VARS: OslFwProtectSecureBootVariables 在 OS 加载程序中失败。 BL_LOG_ERROR_OSL_SECURE_BOOT_VARS: OslFwProtectSecureBootVariables failed in osloader.
0xDC00004DBL_LOG_ERROR_OSL_LD_MODULES: OslpLoadAllModules 在 OS 加载程序中失败。 BL_LOG_ERROR_OSL_LD_MODULES: OslpLoadAllModules failed in osloader.
0xDC00004EBL_LOG_ERROR_OSL_LD_FW_DRIVERS: OslFwLoadFirmwareDrivers 在 OS 加载程序中失败。 BL_LOG_ERROR_OSL_LD_FW_DRIVERS: OslFwLoadFirmwareDrivers failed in osloader.
0xDC00004FBL_LOG_ERROR_OSL_VSM_CHK_ENCRYPT_KEY: BlVsmCheckSystemPolicy 在 OS 加载程序中对主 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: BlVsmCheckSystemPolicy 在 OS 加载程序中的 0 阶段失败。 BL_LOG_ERROR_OSL_VSM_CHK_PHASE_0: BlVsmCheckSystemPolicy failed for phase 0 in osloader.
0xDC000051BL_LOG_ERROR_OSL_SET_SEIL_SIGN_POL: OslSetSeILSigningPolicy 在 OS 加载程序中失败。 BL_LOG_ERROR_OSL_SET_SEIL_SIGN_POL: OslSetSeILSigningPolicy failed in osloader.
0xDC000052BL_LOG_ERROR_OSL_CMS_PROV_IDK: BlVsmCheckSystemPolicy 在 VSM Idendity 密钥运行期间在 OS 加载程序中失败。 BL_LOG_ERROR_OSL_CMS_PROV_IDK: BlVsmCheckSystemPolicy failed during VSM Idendity key work in osloader.
0xDC000053BL_LOG_ERROR_OSL_ARCH_KERNEL_SETUP_0: OslArchKernelSetup 在 OS 加载程序中对 0 失败。 BL_LOG_ERROR_OSL_ARCH_KERNEL_SETUP_0: OslArchKernelSetup failed for 0 in osloader.
0xDC000054BL_LOG_ERROR_OSL_FW_KERNEL_SETUP: OslFwKernelSetup 在 OS 加载程序中对 0 失败。 BL_LOG_ERROR_OSL_FW_KERNEL_SETUP: OslFwKernelSetup failed for 0 in osloader.
0xDC000055BL_LOG_ERROR_OSL_PROC_EV_STORE: OslpProcessEVStore 在 OS 加载程序中失败。 BL_LOG_ERROR_OSL_PROC_EV_STORE: OslpProcessEVStore failed in osloader.
0xDC000056BL_LOG_ERROR_OSL_COPY_BOOT_OPTS: BlCopyBootOptions 在 OS 加载程序中失败。 BL_LOG_ERROR_OSL_COPY_BOOT_OPTS: BlCopyBootOptions failed in osloader.
0xDC000057BL_LOG_ERROR_OSL_FVE_SEC_BOOT_REST_ONE: BlFveSecureBootRestrictToOne 在 OS 加载程序中失败。 BL_LOG_ERROR_OSL_FVE_SEC_BOOT_REST_ONE: BlFveSecureBootRestrictToOne failed in osloader.
0xDC000058BL_LOG_ERROR_OSL_NET_UNDI_CLOSE: BlNetUndiClose 在 OS 加载程序中失败。 BL_LOG_ERROR_OSL_NET_UNDI_CLOSE: BlNetUndiClose failed in osloader.
0xDC000059BL_LOG_ERROR_OSL_PROC_APP_PDATA: OslProcessApplicationPersistentData 在 OS 加载程序中失败。 BL_LOG_ERROR_OSL_PROC_APP_PDATA: OslProcessApplicationPersistentData failed in osloader.
0xDC00005ABL_LOG_ERROR_OSL_BLD_MEM_CACHE_REQ_LIST: OslFwBuildMemoryCachingRequirementsList 在 OS 加载程序中失败。 BL_LOG_ERROR_OSL_BLD_MEM_CACHE_REQ_LIST: OslFwBuildMemoryCachingRequirementsList failed in osloader.
0xDC00005BBL_LOG_ERROR_OSL_BLD_RT_MEM_MAP: OslFwBuildRuntimeMemoryMap 在 OS 加载程序中失败。 BL_LOG_ERROR_OSL_BLD_RT_MEM_MAP: OslFwBuildRuntimeMemoryMap failed in osloader.
0xDC00005CBL_LOG_ERROR_OSL_VSM_SETUP: OslVsmSetup 在 OS 加载程序中对 1 失败。 BL_LOG_ERROR_OSL_VSM_SETUP: OslVsmSetup failed for 1 in osloader.
0xDC00005DBL_LOG_ERROR_OSL_BLD_KERNEL_MEM_MAP: BlTraceBuildKernelMemoryMapStop 在 OS 加载程序中失败。 BL_LOG_ERROR_OSL_BLD_KERNEL_MEM_MAP: BlTraceBuildKernelMemoryMapStop failed in osloader.
0xDC00005EBL_LOG_ERROR_OSL_ARCH_KERNEL_SETUP_1: OslArchKernelSetup 在 OS 加载程序中对 1 失败。 BL_LOG_ERROR_OSL_ARCH_KERNEL_SETUP_1: OslArchKernelSetup failed for 1 in osloader.
0xDC00005FBL_LOG_ERROR_OSL_SET_VSM_POL_SYS_HIVE: OslSetVsmPolicy 在 OS 加载程序中失败。 BL_LOG_ERROR_OSL_SET_VSM_POL_SYS_HIVE: OslSetVsmPolicy failed in osloader.
0xDC000060BL_LOG_ERROR_OSL_ENUM_ENCLAVE_PAGES: OslEnumerateEnclavePageRegions 在 OS 加载程序中失败。 BL_LOG_ERROR_OSL_ENUM_ENCLAVE_PAGES: OslEnumerateEnclavePageRegions failed in osloader.
0xDC000061BL_LOG_ERROR_OSL_GATHER_ENTROPY: OslGatherEntropy 在 OS 加载程序中失败。 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-cn_c5ca5194a9a458e2\
File Size:66 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:67072
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 (Simplified)
Character Set:Unicode
Company Name:Microsoft Corporation
File Description:Microsoft Windows 系统事件资源
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 (Simplified) language for file microsoft-windows-system-events.dll (Microsoft Windows 系统事件资源).

File version info

File Description:Microsoft Windows 系统事件资源
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:0x804, 1200