microsoft-windows-system-events.dll.mui Microsoft-Windows-System-Events Resources a930d09ac0e50336edc8936cecd125cd

File info

File name: microsoft-windows-system-events.dll.mui
Size: 117760 byte
MD5: a930d09ac0e50336edc8936cecd125cd
SHA1: a656642d937a3b27e9ab454b63fed24d0d3b0e6e
SHA256: b9137578dfa35cd52272beeee9ab981af2615d47c8b6f3ecf4b0863e40384bad
Operating systems: Windows 10
Extension: MUI

Translations messages and strings

If an error occurred or the following message in English (U.S.) 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 English (U.S.) English
0x1Possible 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 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
0x2Possible 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 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
0x136The executable %2 received an access denied error when trying to modify the registry key %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
0x1F5Data sent. Data sent.
0x1F6Data received. Data received.
0x1F7Connection attempted. Connection attempted.
0x1F8Disconnect issued. Disconnect issued.
0x1F9Data retransmitted. Data retransmitted.
0x1FAConnection accepted. Connection accepted.
0x1FBReconnect attempted. Reconnect attempted.
0x1FCTCP connection attempt failed. TCP connection attempt failed.
0x1FDProtocol copied data on behalf of user. Protocol copied data on behalf of user.
0x1FEData sent over UDP protocol. Data sent over UDP protocol.
0x1FFData received over UDP protocol. Data received over UDP protocol.
0x200UDP connection attempt failed. UDP connection attempt failed.
0x201TCPv4: %2 bytes transmitted from %4:%6 to %3:%5. TCPv4: %2 bytes transmitted from %4:%6 to %3:%5.
0x202TCPv4: %2 bytes received from %4:%6 to %3:%5. TCPv4: %2 bytes received from %4:%6 to %3:%5.
0x203TCPv4: Connection attempted between %4:%6 and %3:%5. TCPv4: Connection attempted between %4:%6 and %3:%5.
0x204TCPv4: Connection closed between %4:%6 and %3:%5. TCPv4: Connection closed between %4:%6 and %3:%5.
0x205TCPv4: %2 bytes retransmitted from %4:%6 to %3:%5. TCPv4: %2 bytes retransmitted from %4:%6 to %3:%5.
0x206TCPv4: Connection established between %4:%6 and %3:%5. TCPv4: Connection established between %4:%6 and %3:%5.
0x207TCPv4: Reconnect attempt between %4:%6 and %3:%5. TCPv4: Reconnect attempt between %4:%6 and %3:%5.
0x208TCPv4: Connection attempt failed with error code %2. TCPv4: Connection attempt failed with error code %2.
0x209TCPv4: %2 bytes copied in protocol on behalf of user for connection between %4:%6 and %3:%5. TCPv4: %2 bytes copied in protocol on behalf of user for connection between %4:%6 and %3:%5.
0x20AUDPv4: %2 bytes transmitted from %4:%6 to %3:%5. UDPv4: %2 bytes transmitted from %4:%6 to %3:%5.
0x20BUDPv4: %2 bytes received from %4:%6 to %3:%5. UDPv4: %2 bytes received from %4:%6 to %3:%5.
0x20CUDPv4: Connection attempt failed with error code %2. UDPv4: Connection attempt failed with error code %2.
0x20DTCPv6: %2 bytes transmitted from %4:%6 to %3:%5. TCPv6: %2 bytes transmitted from %4:%6 to %3:%5.
0x20ETCPv6: %2 bytes received from %4:%6 to %3:%5. TCPv6: %2 bytes received from %4:%6 to %3:%5.
0x20FTCPv6: Connection attempted between %4:%6 and %3:%5. TCPv6: Connection attempted between %4:%6 and %3:%5.
0x210TCPv6: Connection closed between %4:%6 and %3:%5. TCPv6: Connection closed between %4:%6 and %3:%5.
0x211TCPv6: %2 bytes retransmitted from %4:%6 to %3:%5. TCPv6: %2 bytes retransmitted from %4:%6 to %3:%5.
0x212TCPv6: Connection established between %4:%6 and %3:%5. TCPv6: Connection established between %4:%6 and %3:%5.
0x213TCPv6: Reconnect attempt between %4:%6 and %3:%5. TCPv6: Reconnect attempt between %4:%6 and %3:%5.
0x214TCPv6: %2 bytes copied in protocol on behalf of user for connection between %4:%6 and %3:%5. TCPv6: %2 bytes copied in protocol on behalf of user for connection between %4:%6 and %3:%5.
0x215UDPv6: %2 bytes transmitted from %4:%6 to %3:%5. UDPv6: %2 bytes transmitted from %4:%6 to %3:%5.
0x216UDPv6: %2 bytes received from %4:%6 to %3:%5. UDPv6: %2 bytes received from %4:%6 to %3:%5.
0x258Microsoft-Windows-Kernel-Disk Microsoft-Windows-Kernel-Disk
0x259%3 bytes read from disk %1 at %5. %3 bytes read from disk %1 at %5.
0x25A%3 bytes written to disk %1 at %5. %3 bytes written to disk %1 at %5.
0x25BBuffers flushed to disk %1. Buffers flushed to disk %1.
0x2BCMicrosoft-Windows-Kernel-Boot Microsoft-Windows-Kernel-Boot
0x2BDSystem was booted in %1x%2@%3bpp. System was booted in %1x%2@%3bpp.
0x2BEBootUX screen was displayed in %1x%2@%3bpp. BootUX screen was displayed in %1x%2@%3bpp.
0x2BFVideo bit transfer rate is %1 bytes per ms. Video bit transfer rate is %1 bytes per ms.
0x2C0Boot library accessed file %2 on Device %1. Read %3 bytes and wrote %4 bytes. Boot library accessed file %2 on Device %1. Read %3 bytes and wrote %4 bytes.
0x2C1File IO for boot application %1: Total Bytes Read = %2, Total Bytes Written = %3. File IO for boot application %1: Total Bytes Read = %2, Total Bytes Written = %3.
0x2C2Image %1 failed IntegrityCheck reason is %3. Image flags are %2. Error ignored due to debugger %4. Image %1 failed IntegrityCheck reason is %3. Image flags are %2. Error ignored due to debugger %4.
0x2C3Bootmgr duration is %1 milliseconds. Bootmgr duration is %1 milliseconds.
0x2C4Image %1 is not self-signed. Image %1 is not self-signed.
0x2C5A device (%1) that was enumerated by the BIOS was inaccessible to the boot environment. A device (%1) that was enumerated by the BIOS was inaccessible to the boot environment.
0x2C6Variable %1 requires %2 bytes and was set with status %3. Variable %1 requires %2 bytes and was set with status %3.
0x2C7Element %2 of application %1 was not in policy. Element %2 of application %1 was not in policy.
0x2C8A Secure Boot Policy update resulted in status %1. A Secure Boot Policy update resulted in status %1.
0x2C9A Secure Boot Revocation List update resulted in status %1. A Secure Boot Revocation List update resulted in status %1.
0x2CARetrieving the driver list took %1 milliseconds. Retrieving the driver list took %1 milliseconds.
0x2CBLoading the drivers took %1 milliseconds. Loading the drivers took %1 milliseconds.
0x2CCLoading hive %1 took %2 milliseconds. Loading hive %1 took %2 milliseconds.
0x2CDThe time elapsed loading %1 was %2 ms. The time elapsed loading %1 was %2 ms.
0x2CEThe time elapsed executing %1 was %2 ms. The time elapsed executing %1 was %2 ms.
0x2CFBuilding chunk table for WIM compressed file %2 failed with status: %1 Building chunk table for WIM compressed file %2 failed with status: %1
0x2D0Soft Restart failed to prepare target Operating System. Operation status: %1 failure point: %2 Soft Restart failed to prepare target Operating System. Operation status: %1 failure point: %2
0x2D1Boot application failed to process persistent data with status: %1 Boot application failed to process persistent data with status: %1
0x320Microsoft-Windows-Kernel-File Microsoft-Windows-Kernel-File
0x352Error setting traits on Provider %1. Error: %2 Error setting traits on Provider %1. Error: %2
0x353A registration for Provider %1 has joined Provider Group %2 A registration for Provider %1 has joined Provider Group %2
0x354Enable Info Enable Info
0x355Set Provider Traits Set Provider Traits
0x356Join Provider Group Join Provider Group
0x385Microsoft-Windows-Kernel-EventTracing Microsoft-Windows-Kernel-EventTracing
0x386Session \"%1\" failed to write to log file \"%2\" with the following error: %3 Session \"%1\" failed to write to log file \"%2\" with the following error: %3
0x387The 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. 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.
0x388Session \"%1\" failed to start with the following error: %3 Session \"%1\" failed to start with the following error: %3
0x389Session \"%1\" stopped due to the following error: %3 Session \"%1\" stopped due to the following error: %3
0x38AThe 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. 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.
0x38BAn error was encountered while tracing session \"%2\" was switching to the \"%1\" event log file. Error: %3 An error was encountered while tracing session \"%2\" was switching to the \"%1\" event log file. Error: %3
0x38EProvider %1 was registered with Event Tracing for Windows. Provider %1 was registered with Event Tracing for Windows.
0x38FProvider %1 was unregistered from Event Tracing for Windows. Provider %1 was unregistered from Event Tracing for Windows.
0x390Session \"%3\" was started. Session \"%3\" was started.
0x391Session \"%3\" was stopped. Session \"%3\" was stopped.
0x392The configuration of session \"%3\" has been modified. The configuration of session \"%3\" has been modified.
0x393The events from session \"%3\" have been flushed. The events from session \"%3\" have been flushed.
0x394Provider %1 has been enabled to session \"%2\". Provider %1 has been enabled to session \"%2\".
0x395Provider %1 is no longer enabled to session \"%2\". Provider %1 is no longer enabled to session \"%2\".
0x396The security settings of provider %1 have been modified from %2 to %3. The security settings of provider %1 have been modified from %2 to %3.
0x397The security descriptor for session \"%3\" has been updated. The security descriptor for session \"%3\" has been updated.
0x398Provider Provider
0x399Session Session
0x39BLogging Logging
0x39DStop Stop
0x39EStart Start
0x39FDisable Disable
0x3A0Enable Enable
0x3A1Unregister Unregister
0x3A2Register Register
0x3A3Flush Flush
0x3A4Configure Configure
0x3A7Write Buffer Write Buffer
0x3A8File Switch File Switch
0x3ACStack correlation event. This event contains a call stack which is associated with a prior event which is correlated by the MatchId. Stack correlation event. This event contains a call stack which is associated with a prior event which is correlated by the MatchId.
0x3ADStack Trace Stack Trace
0x3AEUser Mode Stack Trace User Mode Stack Trace
0x3AFMicrosoft-Windows-Kernel-EventTracing/Analytic Microsoft-Windows-Kernel-EventTracing/Analytic
0x3B0Microsoft-Windows-Kernel-EventTracing/Admin Microsoft-Windows-Kernel-EventTracing/Admin
0x3B1Lost Event Lost Event
0x3B3Logger mode incompatible with Append mode Logger mode incompatible with Append mode
0x3B4OS version mismatch OS version mismatch
0x3B5Pointer size mismatch Pointer size mismatch
0x3B6Unsupported BufferSize Unsupported BufferSize
0x3B7BufferSize mismatch BufferSize mismatch
0x3B8Preallocate mode is incompatible with Append mode Preallocate mode is incompatible with Append mode
0x3B9File size query failed File size query failed
0x3BAMaximum file size reached Maximum file size reached
0x3BBNumber of buffers written is zero Number of buffers written is zero
0x3BCNumberf of processors mismatch Numberf of processors mismatch
0x3BDError saving soft restart persisted log \"%1\" Error: %5 Error saving soft restart persisted log \"%1\" Error: %5
0x3BEGUID Entry GUID Entry
0x3BFProvider Group Entry Provider Group Entry
0x3C0Microsoft-Windows-Kernel-StoreMgr Microsoft-Windows-Kernel-StoreMgr
0x3C1Microsoft-Windows-Kernel-StoreMgr/Operational Microsoft-Windows-Kernel-StoreMgr/Operational
0x3C2%5%n%nVirtual Address: %2%nPhysical Address: %3%nCorruption Window Size: %4 %5%n%nVirtual Address: %2%nPhysical Address: %3%nCorruption Window Size: %4
0x3C3A memory corruption was detected and handled. Memory diagnostics should be run on this machine and, if necessary, memory chips should be replaced. A memory corruption was detected and handled. Memory diagnostics should be run on this machine and, if necessary, memory chips should be replaced.
0x3C4A 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. 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.
0x3C5A 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. 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%nDevice name: %4%nCache path: %6 %1%n%nDevice name: %4%nCache path: %6
0x3C7A 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. 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.
0x3C8A 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. 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
0x44ELive Dump Capture Dump Data API Live Dump Capture Dump Data API
0x44FSizing Workflow Sizing Workflow
0x450Capture Pages Workflow Capture Pages Workflow
0x451Live Dump Write Deferred Dump Data API Live Dump Write Deferred Dump Data API
0x452Live Dump Discard Deferred Dump Data API Live Dump Discard Deferred Dump Data API
0x453Sizing Workflow: Mirroring started. Sizing Workflow: Mirroring started.
0x454Sizing Workflow: Mirroring Phase 0 ended. Sizing Workflow: Mirroring Phase 0 ended.
0x455Sizing Workflow: Mirroring Phase 1 ended. Sizing Workflow: Mirroring Phase 1 ended.
0x456Sizing Workflow: System Quiesce started. Sizing Workflow: System Quiesce started.
0x457Sizing Workflow: System Quiesce ended. Sizing Workflow: System Quiesce ended.
0x458Capture Pages Workflow: Mirroring started. Capture Pages Workflow: Mirroring started.
0x459Capture Pages Workflow: Mirroring Phase 0 ended. Capture Pages Workflow: Mirroring Phase 0 ended.
0x45ACapture Pages Workflow: Mirroring Phase 1 ended. Capture Pages Workflow: Mirroring Phase 1 ended.
0x45BCapture Pages Workflow: System Quiesce started. Capture Pages Workflow: System Quiesce started.
0x45CCapture Pages Workflow: System Quiesce ended. Capture Pages Workflow: System Quiesce ended.
0x45DCapture Pages Workflow: Copy memory pages started. Capture Pages Workflow: Copy memory pages started.
0x45ECapture Pages Workflow: Copy memory pages ended. Capture Pages Workflow: Copy memory pages ended.
0x45FLive Dump Capture Dump Data API started. Live Dump Capture Dump Data API started.
0x460Live Dump Capture Dump Data API ended. NT Status: %1. Live Dump Capture Dump Data API ended. NT Status: %1.
0x461Writing dump file started. Writing dump file started.
0x462Writing dump file ended. NT Status: %1. Total %2 bytes (Header|Primary|Secondary: %3|%4|%5 bytes). Writing dump file ended. NT Status: %1. Total %2 bytes (Header|Primary|Secondary: %3|%4|%5 bytes).
0x463API Start API Start
0x464API End API End
0x465Dump File Write Start Dump File Write Start
0x466Dump File Write End Dump File Write End
0x467Mirroring Start Mirroring Start
0x468Mirroring Phase 0 End Mirroring Phase 0 End
0x469Mirroring Phase 1 End Mirroring Phase 1 End
0x46ASystem Quiesce Start System Quiesce Start
0x46BSystem Quiesce End System Quiesce End
0x46CCopying Memory Pages Start Copying Memory Pages Start
0x46DCopying Memory Pages End Copying Memory Pages End
0x46ELive Dump Write Deferred Dump Data API started. Live Dump Write Deferred Dump Data API started.
0x46FLive Dump Write Deferred Dump Data API ended. NT Status: %1. Live Dump Write Deferred Dump Data API ended. NT Status: %1.
0x470Write deferred dump data to file started. Write deferred dump data to file started.
0x471Write deferred dump data to file ended. NT Status: %1. Total %2 bytes (Header|Primary|Secondary: %3|%4|%5 bytes). Write deferred dump data to file ended. NT Status: %1. Total %2 bytes (Header|Primary|Secondary: %3|%4|%5 bytes).
0x472Live Dump Discard Deferred Dump Data API started. Live Dump Discard Deferred Dump Data API started.
0x473Live Dump Discard Deferred Dump Data API ended. NT Status: %1. Live Dump Discard Deferred Dump Data API ended. NT Status: %1.
0x474Sizing Workflow: Estimation. NT: %2 bytes (Minimum %1 bytes). Hypervisor: Primary %3 bytes. Secondary %4 bytes. Sizing Workflow: Estimation. NT: %2 bytes (Minimum %1 bytes). Hypervisor: Primary %3 bytes. Secondary %4 bytes.
0x475Sizing Workflow: Allocation. NT: %1 bytes. Hypervisor: Primary %2 bytes. Secondary %3 bytes. Sizing Workflow: Allocation. NT: %1 bytes. Hypervisor: Primary %2 bytes. Secondary %3 bytes.
0x476Buffer Estimation Data Buffer Estimation Data
0x477Buffer Allocation Data Buffer Allocation Data
0x478Sizing Workflow: RemovePages Callbacks started. Sizing Workflow: RemovePages Callbacks started.
0x479Sizing Workflow: RemovePages Callbacks ended. Sizing Workflow: RemovePages Callbacks ended.
0x47ASizing Workflow: RemovePages Callback %1 started. Sizing Workflow: RemovePages Callback %1 started.
0x47BSizing Workflow: RemovePages Callback %1 ended. Sizing Workflow: RemovePages Callback %1 ended.
0x47CSizing Workflow: RemovePages Callback %1 failed. NT Status: %2. Sizing Workflow: RemovePages Callback %1 failed. NT Status: %2.
0x47DRemove Pages Callbacks Remove Pages Callbacks
0x47ELive Dump request aborted due to memory pressure on system Live Dump request aborted due to memory pressure on system
0x4B0Windows has started processing the volume mount request.%n%n Volume GUID: %1%n Volume Name: %3%n Windows has started processing the volume mount request.%n%n Volume GUID: %1%n Volume Name: %3%n
0x4B1The volume has been successfully mounted.%n%n Volume GUID: %1%n Volume Name: %3%n The volume has been successfully mounted.%n%n Volume GUID: %1%n Volume Name: %3%n
0x4B2Windows failed to mount the volume.%n%n Status: %4%n Volume GUID: %1%n Volume Name: %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 is configured to block legacy file system filters.%n%n Filter name: %2%n Windows is configured to block legacy file system filters.%n%n Filter name: %2%n
0x4B6Legacy file system filters cannot attach to byte addressable volumes.%n%n Filter name: %2%n Volume name: %4%n Legacy file system filters cannot attach to byte addressable volumes.%n%n Filter name: %2%n Volume name: %4%n
0x4B7Dumps 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 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
0x4B8An internal error occurred An internal error occurred
0x4B9Public Key or Thumbprint registry missing Public Key or Thumbprint registry missing
0x4BAInvalid Public Key Invalid Public Key
0x4BBUnsupported Public Key Size 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
0x70AAccess to the a resource has been denied for a less privileged app container at %1 (StackHash: %2). Access to the a resource has been denied for a less privileged app container at %1 (StackHash: %2).
0x01000001The system time has changed to %1 from %2.%n%nChange Reason: %3. The system time has changed to %1 from %2.%n%nChange Reason: %3.
0x01000002License policy-cache corruption detected. License policy-cache corruption detected.
0x01000003License policy-cache corruption has been fixed. License policy-cache corruption has been fixed.
0x01000004License policy-cache has expired because it was not updated within expected duration. License policy-cache has expired because it was not updated within expected duration.
0x01000005{Registry Hive Recovered} Registry hive (file): '%3' was corrupted and it has been recovered. Some data might have been lost. {Registry Hive Recovered} Registry hive (file): '%3' was corrupted and it has been recovered. Some data might have been lost.
0x01000006An I/O operation initiated by the Registry failed unrecoverably.The Registry could not flush hive (file): '%3'. An I/O operation initiated by the Registry failed unrecoverably.The Registry could not flush hive (file): '%3'.
0x0100000BTxR init phase for hive %2 (TM: %3, RM: %4) finished with result=%5 (Internal code=%6). TxR init phase for hive %2 (TM: %3, RM: %4) finished with result=%5 (Internal code=%6).
0x0100000CThe operating system started at system time %7. The operating system started at system time %7.
0x0100000DThe operating system is shutting down at system time %1. The operating system is shutting down at system time %1.
0x0100000FHive %2 was reorganized with a starting size of %3 bytes and an ending size of %4 bytes. Hive %2 was reorganized with a starting size of %3 bytes and an ending size of %4 bytes.
0x01000010The access history in hive %2 was cleared updating %3 keys and creating %4 modified pages. The access history in hive %2 was cleared updating %3 keys and creating %4 modified pages.
0x01000012The operating system is starting after soft restart. 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.
0x0600000BLoading 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. 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.
0x0600000CLoading 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. 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.
0x0A000032Access to %1 is monitored by policy rule %2. Access to %1 is monitored by policy rule %2.
0x0A000361Access to %1 has been restricted by your Administrator by the default software restriction policy level. Access to %1 has been restricted by your Administrator by the default software restriction policy level.
0x0A000362Access to %1 has been restricted by your Administrator by location with policy rule %2 placed on path %3. Access to %1 has been restricted by your Administrator by location with policy rule %2 placed on path %3.
0x0A000363Access to %1 has been restricted by your Administrator by software publisher policy. Access to %1 has been restricted by your Administrator by software publisher policy.
0x0A000364Access to %1 has been restricted by your Administrator by policy rule %2. Access to %1 has been restricted by your Administrator by policy rule %2.
0x0C00000AThe system firmware has allocated a memory region previously determined to be unreliable. This has the potential to cause system instability and/or data corruption. 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 failed to resume from hibernate with error status %1. Windows failed to resume from hibernate with error status %1.
0x0C000011The boot manager multi OS selection screen was displayed. The boot manager multi OS selection screen was displayed.
0x0C000012There are %1 boot options on this system. There are %1 boot options on this system.
0x0C000013There are %1 boot tool options on this system. There are %1 boot tool options on this system.
0x0C000014The last shutdown's success status was %1. The last boot's success status was %2. The last shutdown's success status was %1. The last boot's success status was %2.
0x0C000015The OS loader advanced options menu was displayed and the user selected option %1. The OS loader advanced options menu was displayed and the user selected option %1.
0x0C000016The OS loader edit options menu was displayed. The OS loader edit options menu was displayed.
0x0C000017The Windows key was pressed during boot. The Windows key was pressed during boot.
0x0C000018The F8 key was pressed during boot. The F8 key was pressed during boot.
0x0C000019The boot menu policy was %1. The boot menu policy was %1.
0x0C00001AA one-time boot sequence was used during this boot. A one-time boot sequence was used during this boot.
0x0C00001BThe boot type was %1. The boot type was %1.
0x0C00001DWindows failed fast startup with error status %1. Windows failed fast startup with error status %1.
0x0C00001EThe firmware reported boot metrics. The firmware reported boot metrics.
0x0C000020The bootmgr spent %1 ms waiting for user input. The bootmgr spent %1 ms waiting for user input.
0x0C00007CThe virtualization-based security enablement policy check at phase %1 failed with status: %2 The virtualization-based security enablement policy check at phase %1 failed with status: %2
0x0C000099Virtualization-based security (policies: %3) is %2. Virtualization-based security (policies: %3) is %2.
0x0C00009CVirtualization-based security (policies: %3) is %2 with status: %1 Virtualization-based security (policies: %3) is %2 with status: %1
0x0F000009App %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. 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.
0x10000001Structured State Structured State
0x10000002Unstructured Reset Unstructured Reset
0x10000003Out Of Memory Out Of Memory
0x10000004Apiset Error Apiset Error
0x10000005WinRT WinRT
0x10000006Low-level Data Store Error Low-level Data Store Error
0x1000000AFailure to load the application settings for package %1. Error Code: %2 Failure to load the application settings for package %1. Error Code: %2
0x1000000BFailure to read an application setting for package %1. Error Code: %2 Failure to read an application setting for package %1. Error Code: %2
0x1000000CFailure to write an application setting for package %1. Error Code: %2 Failure to write an application setting for package %1. Error Code: %2
0x1000000DFailure to instantiate storage folder %1 for package %2 with Error Code: %3 Failure to instantiate storage folder %1 for package %2 with Error Code: %3
0x10000014Triggered repair because operation %1 against package %2 hit error %3. Triggered repair because operation %1 against package %2 hit error %3.
0x10000015Repair for operation %1 against package %2 with error %3 returned Error Code: %4 Repair for operation %1 against package %2 with error %3 returned Error Code: %4
0x10000016Folder path %1 failed access check: Error Code: %2 Folder path %1 failed access check: Error Code: %2
0x10000021Verbose context events Verbose context events
0x10000022Scenario trigger events Scenario trigger events
0x10000034SQM SQM
0x11000005Time Time
0x16000005Deprecated dlls Deprecated dlls
0x16000006Fatal user callback exception Fatal user callback exception
0x16000007A dll failed to load. A dll failed to load.
0x16000008Launch 16bit application Launch 16bit application
0x16000009Windows component on demand. Windows component on demand.
0x1600000AThe Loader encountered a fatal error. The Loader encountered a fatal error.
0x17000031Response Time Response Time
0x19000005Deprecated COM interfaces Deprecated COM interfaces
0x1F000001Process Process
0x1F000002AppContainer AppContainer
0x1F000003DesktopAppXProcess DesktopAppXProcess
0x1F000004DesktopAppXContainer DesktopAppXContainer
0x3000000AScenario start enables context providers to the WDI context logger. Scenario start enables context providers to the WDI context logger.
0x3000000BScenario end disables context providers to the WDI context logger. Scenario end disables context providers to the WDI context logger.
0x3000000CWhen a scenario has remained in-flight beyond the maximum time window it is automatically terminated by the SEM. When a scenario has remained in-flight beyond the maximum time window it is automatically terminated by the SEM.
0x3000000DA scenario start attempt failed in the SEM. A scenario start attempt failed in the SEM.
0x3000000EA scenario end attempt failed in the SEM. A scenario end attempt failed in the SEM.
0x3000000FThe SEM received a request to start a new scenario, but the maximum number of scenarios were already in-flight. The SEM received a request to start a new scenario, but the maximum number of scenarios were already in-flight.
0x30000010There is an invalid configuration parameter in the SEM registry namespace. There is an invalid configuration parameter in the SEM registry namespace.
0x30000011The SEM is configured with more scenarios than the maximum allowed count. The SEM is configured with more scenarios than the maximum allowed count.
0x30000012The SEM is configured with a scenario with too many context providers. The SEM is configured with a scenario with too many context providers.
0x30000013The SEM is configured with a scenario that has too many end events. The SEM is configured with a scenario that has too many end events.
0x30000014The number of providers specified across all scenarios is above the maximum allowed amount. The number of providers specified across all scenarios is above the maximum allowed amount.
0x31000000Info Info
0x3500001ENLS data table operations NLS data table operations
0x3500001FNLS initialization NLS initialization
0x35000020NLS configuration changes NLS configuration changes
0x35000021NLS operations NLS operations
0x35000022NLS clean-up operations NLS clean-up operations
0x3B00001FInvoke callback function Invoke callback function
0x3B000020Disable live cache Disable live cache
0x3B000021Update resource cache manifest Update resource cache manifest
0x3B000022Build resource cache Build resource cache
0x3B000024End End
0x50000002Error Error
0x50000003Warning Warning
0x50000004Information Information
0x55000001Critical Critical
0x55000005Verbose Verbose
0x70000009SEM Scenario Lifecycle SEM Scenario Lifecycle
0x7000000ASEM Initialization SEM Initialization
0x73000001This group of events tracks the performance of mounting hives from existing files. This group of events tracks the performance of mounting hives from existing files.
0x73000002This group of events tracks the performance of unloading hives. This group of events tracks the performance of unloading hives.
0x73000003This group of events tracks the performance of flushing hives. This group of events tracks the performance of flushing hives.
0x73000004This group of events tracks the performance of registry shutdown. This group of events tracks the performance of registry shutdown.
0x73000005This group of events tracks the performance of loading hives. This group of events tracks the performance of loading hives.
0x73000006This group of events tracks the performance of restoring hives. This group of events tracks the performance of restoring hives.
0x73000007This group of events tracks the performance of exporting hives. This group of events tracks the performance of exporting hives.
0x7500001ENLS code page functions NLS code page functions
0x75000020NLS date/time functions NLS date/time functions
0x75000021NLS Unattended Regional and Language Options NLS Unattended Regional and Language Options
0x75000022NLS group policy NLS group policy
0x75000023NLS locale functions NLS locale functions
0x7B00001EMUI NotifyUILanguageChange task MUI NotifyUILanguageChange task
0x7B00001FMUI resource cache builder 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
0x91000002System 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
0x96000002Application 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
0xB0000001Error while deleting file: %1. Error Code: %2 Error while deleting file: %1. Error Code: %2
0xB0000002Error while deleting directory: %1. Error Code: %2 Error while deleting directory: %1. Error Code: %2
0xB0000003Error while allocating memory Error while allocating memory
0xB0000004ApiSet Function: %1 returned with Error Code: %2 ApiSet Function: %1 returned with Error Code: %2
0xB0000005Low-level data store access error. Function: %1 returned with Error Code: %2 Low-level data store access error. Function: %1 returned with Error Code: %2
0xB0000006Cleanup of temporary state has been skipped due to low disk usage. Cleanup of temporary state has been skipped due to low disk usage.
0xB0000007Cleanup of temporary state has completed. Cleanup of temporary state has completed.
0xB0000008Cleanup of temporary state was unable to enumerate the user profiles. Object: %1, Error Code: %2. Cleanup of temporary state was unable to enumerate the user profiles. Object: %1, Error Code: %2.
0xB0000009Cleanup of temporary state has aborted unexpectedly. Cleanup of temporary state has aborted unexpectedly.
0xB000000ENeed to update state locations of package %1 for user %2 because the schema is not found. Error Code: %3 Need to update state locations of package %1 for user %2 because the schema is not found. Error Code: %3
0xB000000FNeed to update state locations of package %1 for user %2 because the package is not found. Error Code: %3 Need to update state locations of package %1 for user %2 because the package is not found. Error Code: %3
0xB0000010Need to update state locations of package %1 for user %2 because the package full name has changed. Error Code: %3 Need to update state locations of package %1 for user %2 because the package full name has changed. Error Code: %3
0xB0000011Need to update state locations of package %1 for user %2 because the schema version has changed. Error Code: %3 Need to update state locations of package %1 for user %2 because the schema version has changed. Error Code: %3
0xB0000012Succeeded to fix state locations for package %1. Succeeded to fix state locations for package %1.
0xB0000013Failure to fix state locations for package %1. Error Code: %2 Failure to fix state locations for package %1. Error Code: %2
0xB0000020The Scenario Event Mapper started a scenario for provider %1 (event ID %2) with %4 context providers. The context logger dropped event count was %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.
0xB0000021The Scenario Event Mapper stopped a scenario for provider %1 (event ID %2) with %4 context providers. The context logger dropped event count was %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.
0xB0000022An in-flight scenario from provider %1 (event ID %2) timed out and was stopped automatically by the Scenario Event Mapper. An in-flight scenario from provider %1 (event ID %2) timed out and was stopped automatically by the Scenario Event Mapper.
0xB0000023The 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. 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.
0xB0000024The Scenario Event Mapper was unable to start a scenario for provider %1 (event ID %2). The error code was %3. The Scenario Event Mapper was unable to start a scenario for provider %1 (event ID %2). The error code was %3.
0xB0000025The Scenario Event Mapper was unable to stop a scenario for provider %1 (event ID %2). The error code was %3. The Scenario Event Mapper was unable to stop a scenario for provider %1 (event ID %2). The error code was %3.
0xB0000026The Scenario Event Mapper is configured with more than the maximum number of scenarios. The scenario for provider %1 (event ID %2) will be ignored. 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.
0xB0000027The 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. 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.
0xB0000028The 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. 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.
0xB0000029The Scenario Event Mapper is configured with more than the maximum number of providers. The provider %1 will be ignored. The Scenario Event Mapper is configured with more than the maximum number of providers. The provider %1 will be ignored.
0xB000002AThe 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. 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.
0xB1000001The system time has changed to %1 from %2. The system time has changed to %1 from %2.
0xB2000001Process %1 started at time %2 by parent %3 running in session %4 with name %5. Process %1 started at time %2 by parent %3 running in session %4 with name %5.
0xB2000002Process %1 (which started at time %2) stopped at time %3 with exit code %4. Process %1 (which started at time %2) stopped at time %3 with exit code %4.
0xB2000003Thread %2 (in Process %1) started. Thread %2 (in Process %1) started.
0xB2000004Thread %2 (in Process %1) stopped. Thread %2 (in Process %1) stopped.
0xB2000005Process %3 had an image loaded with name %7. Process %3 had an image loaded with name %7.
0xB2000006Process %3 had an image unloaded with name %7. Process %3 had an image unloaded with name %7.
0xB2000007Base CPU priority of thread %2 in process %1 was changed from %3 to %4. Base CPU priority of thread %2 in process %1 was changed from %3 to %4.
0xB2000008CPU priority of thread %2 in process %1 was changed from %3 to %4. CPU priority of thread %2 in process %1 was changed from %3 to %4.
0xB2000009Page priority of thread %2 in process %1 was changed from %3 to %4. Page priority of thread %2 in process %1 was changed from %3 to %4.
0xB200000AI/O priority of thread %2 in process %1 was changed from %3 to %4. I/O priority of thread %2 in process %1 was changed from %3 to %4.
0xB200000BExecution of the process %1 has been suspended. Execution of the process %1 has been suspended.
0xB200000CExecution of the process %1 has been resumed. Execution of the process %1 has been resumed.
0xB200000DJob %1 started with status code %2. Job %1 started with status code %2.
0xB200000EJob %1 terminated with status code %2. Job %1 terminated with status code %2.
0xB200000FEnumerated process %1 had started at time %2 by parent %3 running in session %4 with name %6. Enumerated process %1 had started at time %2 by parent %3 running in session %4 with name %6.
0xB2010001Process %1 started at time %2 by parent %3 running in session %4 with name %6. Process %1 started at time %2 by parent %3 running in session %4 with name %6.
0xB4000001A memory range descriptor has been marked as reserved. A memory range descriptor has been marked as reserved.
0xB4000002Unexpected GPE event was fired on GPE bits that should be disabled. Unexpected GPE event was fired on GPE bits that should be disabled.
0xB4000003A 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 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
0xB4000004A 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 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
0xB4000005The active cooling device %6 has been turned %8. %nThermal zone device instance: %2 %nActive cooling package: _AC%3 %nNamespace object: _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
0xB4000006The active cooling device %6 has been turned %7. %nThermal zone device instance: %2 %nActive cooling package: _AC%3 %nNamespace object: _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 method %2 evaluation has %3. ACPI method %2 evaluation has %3.
0xB4000008The active cooling device %2 has been turned %3. The active cooling device %2 has been turned %3.
0xB4000009The passive cooling device %2 throttle has changed to %3 percent. The passive cooling device %2 throttle has changed to %3 percent.
0xB400000AThe device %2 has the following cooling state. %nActive cooling: %3 %nPassive cooling: %4 percent The device %2 has the following cooling state. %nActive cooling: %3 %nPassive cooling: %4 percent
0xB4000014ACPI device %2 is undergoing %3. Status %4. ACPI device %2 is undergoing %3. Status %4.
0xB4000015ACPI device OverRide - %1 ACPI device OverRide - %1
0xB4000016Error occured while interpreting AML code: scope %1, object %2. Status %3. Error occured while interpreting AML code: scope %1, object %2. Status %3.
0xB4000017ACPI method %2 has high frequency %3. ACPI method %2 has high frequency %3.
0xB50003E9The NLS operation failed because the registry key %1 cannot be opened. Error code is %2. Error message: %3 The NLS operation failed because the registry key %1 cannot be opened. Error code is %2. Error message: %3
0xB50003EAThe NLS operation failed because the registry key %1 cannot be opened. Status code is %2. The NLS operation failed because the registry key %1 cannot be opened. Status code is %2.
0xB50003EBNLS 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. 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.
0xB50003ECNLS 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. 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.
0xB50003EDNLS operation failed for %1 locale because the file %2\\globalization\\%1.nlp is missing. To fix this problem, reinstall this custom locale. NLS operation failed for %1 locale because the file %2\\globalization\\%1.nlp is missing. To fix this problem, reinstall this custom locale.
0xB50003EENLS operation failed for %1 locale because the file %2\\globalization\\%1.nlp is corrupted. To fix this problem, reinstall this custom locale. NLS operation failed for %1 locale because the file %2\\globalization\\%1.nlp is corrupted. To fix this problem, reinstall this custom locale.
0xB50005DCGroup Policy has prevented process number %1 (%2) from changing the standards and format information for the user. Group Policy has prevented process number %1 (%2) from changing the standards and format information for the user.
0xB50005DDGroup Policy has prevented the geographical location from being changed. Group Policy has prevented the geographical location from being changed.
0xB50005DEGroup Policy has prevented the user from changing their user locale to \"%1\". Group Policy has prevented the user from changing their user locale to \"%1\".
0xB50005DFGroup Policy does not allow custom user locales for standards and formats. The user was unable to select \"%1\" as their user locale. Group Policy does not allow custom user locales for standards and formats. The user was unable to select \"%1\" as their user locale.
0xB50007D0NLS operation recreated the registry key %1. NLS operation recreated the registry key %1.
0xB50009C4Windows has detected inconsistencies in NLS internal data. To correct this problem, log off of Windows and log on again. Windows has detected inconsistencies in NLS internal data. To correct this problem, log off of Windows and log on again.
0xB5000BB8Process number %1 (%2) called SetLocaleInfo(%3, %4, \"%5\") successfully. Process number %1 (%2) called SetLocaleInfo(%3, %4, \"%5\") successfully.
0xB5000BB9Process number %1 (%2) called SetCalendarInfo(%3, %4, %5, \"%6\") successfully. Process number %1 (%2) called SetCalendarInfo(%3, %4, %5, \"%6\") successfully.
0xB5000BBAProcess number %1 (%2) called SetUserGeoID(%3) successfully. Process number %1 (%2) called SetUserGeoID(%3) successfully.
0xB5000BBBThe system updated the locale \"%1\" with flag %2. Process number %3 (%4). Return code is %5. The system updated the locale \"%1\" with flag %2. Process number %3 (%4). Return code is %5.
0xB5002710The user tried to apply an unattended XML file (%1) in an unsupported format. Reason: %3 (Line %2). The system has not been changed. The user tried to apply an unattended XML file (%1) in an unsupported format. Reason: %3 (Line %2). The system has not been changed.
0xB5002711Unsupported XML in function. Unsupported XML in function.
0xB5002713The 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. 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.
0xB5002714Unsupported alternate sort \"%1\". Unsupported alternate sort \"%1\".
0xB5002715\"%1\" is not a supported sort order for locale \"%2\". \"%1\" is not a supported sort order for locale \"%2\".
0xB5002716The selected system locale (specified by the SystemLocale element) is not installed on the system. The system locale was not changed. The selected system locale (specified by the SystemLocale element) is not installed on the system. The system locale was not changed.
0xB5002717Internal error while changing System locale (specified by the SystemLocale element). Internal error while changing System locale (specified by the SystemLocale element).
0xB5002718Error while changing keyboard/input method for \"%1\". Error while changing keyboard/input method for \"%1\".
0xB5002719Error 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 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
0xB500271AFailed to change UI Language to \"%1\". Status code is: %2. Failed to change UI Language to \"%1\". Status code is: %2.
0xB500271BFailed to change UI Language fallback order to \"%1\". Status code is: %2. Failed to change UI Language fallback order to \"%1\". Status code is: %2.
0xB500271CThe user tried to apply an unattended XML file %1, but the file does not exist. The user tried to apply an unattended XML file %1, but the file does not exist.
0xB500271DError while the user changed setting \"%1\" with value \"%2\" for the current user locale. Error code is: %3. Error message: %4 Error while the user changed setting \"%1\" with value \"%2\" for the current user locale. Error code is: %3. Error message: %4
0xB500271EThe selected calendar \"%1;\" (specified by the Calendar element) is not a supported calendar. The user locale was not changed. The selected calendar \"%1;\" (specified by the Calendar element) is not a supported calendar. The user locale was not changed.
0xB500271FThe selected TwoDigitYearMax \"%1;\" (specified by the TwoDigitYearMax element) is not a supported value. The user locale was not changed. The selected TwoDigitYearMax \"%1;\" (specified by the TwoDigitYearMax element) is not a supported value. The user locale was not changed.
0xB500277FThe user does not have permission to change the TwoDigitYearMax setting The user does not have permission to change the TwoDigitYearMax setting
0xB5002780The user does not have permission to copy current settings to the Default and/or System Account The user does not have permission to copy current settings to the Default and/or System Account
0xB5002781The user does not have permission to change the system locale (specified by the SystemLocale element). The user does not have permission to change the system locale (specified by the SystemLocale element).
0xB5002783The user does not have permission to change the calendar. The user does not have permission to change the calendar.
0xB50027E8Unexpected failure. Stack overflow Unexpected failure. Stack overflow
0xB50027EAUnexpected failure. Unsupported flag Unexpected failure. Unsupported flag
0xB50027EBUnexpected failure. Unsupported parameter Unexpected failure. Unsupported parameter
0xB50027ECUnexpected failure. Unrecoverable error. Unexpected failure. Unrecoverable error.
0xB50027EDFailed when calling internal function. Error code is: %1 Failed when calling internal function. Error code is: %1
0xB50027EEThe operation timed out. The operation timed out.
0xB500283CGroup Policy has prevented the user from changing the system locale (specified by the SystemLocale element). Group Policy has prevented the user from changing the system locale (specified by the SystemLocale element).
0xB50032C8The user changed their user locale (specified by the UserLocale element) to \"%1\". The user changed their user locale (specified by the UserLocale element) to \"%1\".
0xB50032C9The user reset all customizations for their user locale \"%1\" (specified by the UserLocale element) to the system default. The user reset all customizations for their user locale \"%1\" (specified by the UserLocale element) to the system default.
0xB50032CAThe user changed their user locale setting \"%1\" (specified by the UserLocale element) to \"%2\". The user changed their user locale setting \"%1\" (specified by the UserLocale element) to \"%2\".
0xB50032CBThe locale has to be changed to the current locale in order to make customizations. The locale has to be changed to the current locale in order to make customizations.
0xB50032CCThe user changed their alternate sort to \"%1\". The user changed their alternate sort to \"%1\".
0xB50032CDThe user changed their calendar to \"%1\". The user changed their calendar to \"%1\".
0xB50032CEThe user changed their TwoDigitYearMax to %1. The user changed their TwoDigitYearMax to %1.
0xB50032CFThe user changed their location preference (geoid) to %1. The user changed their location preference (geoid) to %1.
0xB50032D0The system locale (specified by the SystemLocale element) was changed to \"%1\". The system locale (specified by the SystemLocale element) was changed to \"%1\".
0xB50032D1The current user settings were copied to the default user account. The current user settings were copied to the default user account.
0xB50032D2The current user settings were copied to the system accounts. The current user settings were copied to the system accounts.
0xB50032D3The user has changed their UI Language to \"%1\". The user has changed their UI Language to \"%1\".
0xB50032D4The user has changed their UI Language fallback order to \"%1\". The user has changed their UI Language fallback order to \"%1\".
0xB6000001Deprecated module %1. Deprecated module %1.
0xB6000002Process %2 encountered a fatal user callback exception. Process %2 encountered a fatal user callback exception.
0xB6000004The process launches a 16 bit process. The process launches a 16 bit process.
0xB6000005Windows component on demand %1. Windows component on demand %1.
0xB6000006The Loader encountered a fatal error while loading a thread from process image name %1. The Loader encountered a fatal error while loading a thread from process image name %1.
0xB6000007A fatal error occured during initalization of %1. A fatal error occured during initalization of %1.
0xB6000009The Loader encountered a fatal error running process image name %1. The Loader encountered a fatal error running process image name %1.
0xB8000001The process failed to handle ERROR_ELEVATION_REQUIRED during the creation of a child process. The process failed to handle ERROR_ELEVATION_REQUIRED during the creation of a child process.
0xB9000001Deprecated COM CLSID %1. Deprecated COM CLSID %1.
0xBB0007D0MUI notify operation failed with status code %1. No callbacks were invoked. MUI notify operation failed with status code %1. No callbacks were invoked.
0xBB0007D1MUI Callback failed for file %1 because it can not be loaded. To correct this error, replace this file or repair your Windows installation. MUI Callback failed for file %1 because it can not be loaded. To correct this error, replace this file or repair your Windows installation.
0xBB0007D2MUI 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. 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.
0xBB0007D3MUI 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. 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.
0xBB0007D4MUI Callback file %1 cannot be found. To correct this error, repair the registry or copy the file to the specified location. MUI Callback file %1 cannot be found. To correct this error, repair the registry or copy the file to the specified location.
0xBB0007D6Wow redirection could not be disabled. New resource cache will not be built. Wow redirection could not be disabled. New resource cache will not be built.
0xBB0007D7Resource cache cannot be opened in writable mode. New resource cache will not be built. Resource cache cannot be opened in writable mode. New resource cache will not be built.
0xBB0007D8Live resource cache could not be disabled. Live resource cache could not be disabled.
0xBB0007D9Unable to retrieve language settings from MUI API. New resource cache will not be built. Unable to retrieve language settings from MUI API. New resource cache will not be built.
0xBB0007DAUnable 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. 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.
0xBB0007DBChanges made to resource cache manifest cannot be written to disk. New resource cache will not be built. Changes made to resource cache manifest cannot be written to disk. New resource cache will not be built.
0xBB0007DCNew resource cache could not be built due to internal error: %1. New resource cache could not be built due to internal error: %1.
0xBB0007DDNewly built resource cache could not be installed on the system. Newly built resource cache could not be installed on the system.
0xBB0007DEResource cache manifest could not be created. New resource cache will not be built. Resource cache manifest could not be created. New resource cache will not be built.
0xBB000BB8MUI 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 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
0xBB000BBAMUI notification callback API %2 in %1 returned with code %3. MUI notification callback API %2 in %1 returned with code %3.
0xBB000BBBMUI resource cache builder has been called with the following parameters: %1. MUI resource cache builder has been called with the following parameters: %1.
0xBB000BBCMUI resource cache manifest entry for file %1 has been updated. Affinity: '%2', Sequence: %3, and Priority: %4 MUI resource cache manifest entry for file %1 has been updated. Affinity: '%2', Sequence: %3, and Priority: %4
0xBB000BBDStart: %1 Start: %1
0xBB000BBEEnd: %1 End: %1
0xBB000BBFNew resource cache built and installed on system. New cache index is %1, live cache index is %2 and config is set to %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.
0xBB000BC4Resource file %1 will not be cached since it is not used frequently in the system. Resource file %1 will not be cached since it is not used frequently in the system.
0xBB000BC5The system is constrained in RAM, total disk space or free disk space, so the MUI resource cache will not be maintained. The system is constrained in RAM, total disk space or free disk space, so the MUI resource cache will not be maintained.
0xBB000FA0Unable to parse configuration parameters. The configuration parameters will be ignored. Unable to parse configuration parameters. The configuration parameters will be ignored.
0xBC00000BThe time elapsed before Bootmgr, based on the TSC, is %1 ms. The time elapsed before Bootmgr, based on the TSC, is %1 ms.
0xBC00001FInitialization of the firmware crypto hash provider resulted in status %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 failed to load the required system file %1 with error status %2. Windows failed to load the required system file %1 with error status %2.
0xBC000027Windows failed to load the system registry file %1 with error status %2. Windows failed to load the system registry file %1 with error status %2.
0xBC000028Windows failed to initialize the ACPI with error status %1. Windows failed to initialize the ACPI with error status %1.
0xBC000029Windows failed to load with error status %1. Windows failed to load with error status %1.
0xBC00002AWindows failed to load image %2 imported from %1 with error status %3. Windows failed to load image %2 imported from %1 with error status %3.
0xBC00002BWindows failed to import %2 from image %1 with error status %3. Windows failed to import %2 from image %1 with error status %3.
0xBC00002CWindows 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. 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 Identity Key Provisioning. Unsealing cached copy status: %1. New key generation status: %2. Measuring to PCR status: %3. Sealing and caching status: %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 system integrity policy does not allow to load the required system file %1 with error status %2. Windows system integrity policy does not allow to load the required system file %1 with error status %2.
0xBC000032Windows 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. 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 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. 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 failed to provision the TPM Storage Root Key with error status:%1. Windows failed to provision the TPM Storage Root Key with error status:%1.
0xBC00003AWindows successfully provisioned the TPM Storage Root Key. This operation took %1 milliseconds. Windows successfully provisioned the TPM Storage Root Key. This operation took %1 milliseconds.
0xBC00003BWindows failed to provision TPM binding information with error status:%1. Windows failed to provision TPM binding information with error status:%1.
0xBC000088Soft Restart failed to complete with status: %1 due to %2 outstanding unclaimed allocations Soft Restart failed to complete with status: %1 due to %2 outstanding unclaimed allocations
0xBC00008BSoft Restart failed to restore memory partition %1 with status: %2 Soft Restart failed to restore memory partition %1 with status: %2
0xBC00008ESoft Restart failed to register with Soft Restart extension. The versions are not compatible. Soft Restart failed to register with Soft Restart extension. The versions are not compatible.
0xBC000092Soft Restart failed to establish connection with secure load with status: %1 Soft Restart failed to establish connection with secure load with status: %1
0xBC00009ABoot Policy Migration used an authenticated variable. Status: %1 Boot Policy Migration used an authenticated variable. Status: %1
0xBC00009BBoot Policy Migration used an unauthenticated variable. Status: %1 Boot Policy Migration used an unauthenticated variable. Status: %1
0xBC00009DInfo: %1 Status: %2 Info: %1 Status: %2
0xBC00009EError: %1 Status: %2 Error: %1 Status: %2
0xBE010003%3 shim(s) were applied to driver [%1].%n%nShim(s) source: %2.%n%nShim GUID(s): %4. %3 shim(s) were applied to driver [%1].%n%nShim(s) source: %2.%n%nShim GUID(s): %4.
0xBE010004Flags [%4] were applied to device [%1] - class [%2].%n%nFlags source: %3. Flags [%4] were applied to device [%1] - class [%2].%n%nFlags source: %3.
0xBF000001Process %1 started at time %2 by parent %3 running as package %4 with executable %5 is application %6. Process %1 started at time %2 by parent %3 running as package %4 with executable %5 is application %6.
0xBF000002%2: Cannot create the process for package %1 because an error was encountered. %3 %2: Cannot create the process for package %1 because an error was encountered. %3
0xBF000003%2: Cannot create the process for package %1 because an error was encountered while querying the fast cache. %3 %2: Cannot create the process for package %1 because an error was encountered while querying the fast cache. %3
0xBF000004%2: Cannot create the process for package %1 because an error was encountered while preparing the App credentials. %3 %2: Cannot create the process for package %1 because an error was encountered while preparing the App credentials. %3
0xBF000005%2: Cannot create the process for package %1 because an error was encountered while checking the user-level package status. %3 %2: Cannot create the process for package %1 because an error was encountered while checking the user-level package status. %3
0xBF000006%2: Cannot create the process for package %1 because an error was encountered while checking the machine-level package status. %3 %2: Cannot create the process for package %1 because an error was encountered while checking the machine-level package status. %3
0xBF000007%2: Cannot create the process for package %1 because an error was encountered while verifying the App credentials. %3 %2: Cannot create the process for package %1 because an error was encountered while verifying the App credentials. %3
0xBF000008App %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. 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.
0xBF00000BApp %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. 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.
0xBF00000CAn 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. 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: Package runtime information %1 is corrupted (address=%5, size=%3, offset=%4, section=%6, processid=%7). Reinstall the package to fix this issue. %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: Package runtime information %1 is missing expected data (address=%4, size=%3, section=%5, processid=%6). Reinstall the package to fix this issue. %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: Package runtime information %1 contains conflicting data (address=%5, size=%3, offset=%4, section=%6, processid=%7). Reinstall the package to fix this issue. %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: Package runtime information %1 contains unexpected data (address=%5, size=%3, offset=%4, section=%6, processid=%7). Reinstall the package to fix this issue. %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: Package runtime information %1 failed to load (processid=%3). %2: Package runtime information %1 failed to load (processid=%3).
0xBF000013Package runtime information %1 failed to load because exception %2 occurred. Package runtime information %1 failed to load because exception %2 occurred.
0xBF000014%2: Cannot create the process for package %1 because an error was encountered while loading the runtime information. %3 %2: Cannot create the process for package %1 because an error was encountered while loading the runtime information. %3
0xBF000015CreateAppContainerProfile failed for AppContainer %2 with error %1. CreateAppContainerProfile failed for AppContainer %2 with error %1.
0xBF000016DeleteAppContainerProfile failed for AppContainer %2 with error %1. DeleteAppContainerProfile failed for AppContainer %2 with error %1.
0xBF000017UpdateAppContainerProfile failed for AppContainer %2 with error %1. UpdateAppContainerProfile failed for AppContainer %2 with error %1.
0xBF000018CreateAppContainerProfile failed with error %1 because it was unable to create registry key %2. CreateAppContainerProfile failed with error %1 because it was unable to create registry key %2.
0xBF000019CreateAppContainerProfile failed with error %1 because it was unable to set security on registry key %2. CreateAppContainerProfile failed with error %1 because it was unable to set security on registry key %2.
0xBF00001AAppContainer profile failed with error %1 because it was unable to delete registry key %2. AppContainer profile failed with error %1 because it was unable to delete registry key %2.
0xBF00001BCreateAppContainerProfile failed with error %1 because it was unable to create folder %2. CreateAppContainerProfile failed with error %1 because it was unable to create folder %2.
0xBF00001CCreateAppContainerProfile failed with error %1 because it was unable to set attributes on folder %2. CreateAppContainerProfile failed with error %1 because it was unable to set attributes on folder %2.
0xBF00001DCreateAppContainerProfile failed with error %1 because it was unable to verify the existence of registry key %2. CreateAppContainerProfile failed with error %1 because it was unable to verify the existence of registry key %2.
0xBF00001ECreateAppContainerProfile failed with error %1 because it was unable to verify the existence of folder %2. CreateAppContainerProfile failed with error %1 because it was unable to verify the existence of folder %2.
0xBF00001FCreateAppContainerProfile failed with error %1 because it was unable to find the users local app data folder. CreateAppContainerProfile failed with error %1 because it was unable to find the users local app data folder.
0xBF000020AppContainer profile failed with error %1 because it was unable to delete folder %2 or its contents. AppContainer profile failed with error %1 because it was unable to delete folder %2 or its contents.
0xBF000021AppContainer profile failed with error %1 because it was unable to look up the AppContainer name. AppContainer profile failed with error %1 because it was unable to look up the AppContainer name.
0xBF000022AppContainer profile failed with error %1 because it was unable to look up the AppContainer display name. AppContainer profile failed with error %1 because it was unable to look up the AppContainer display name.
0xBF000023CreateAppContainerProfile failed with error %1 because it was unable to register with the firewall. CreateAppContainerProfile failed with error %1 because it was unable to register with the firewall.
0xBF000024DeleteAppContainerProfile failed with error %1 because it was unable to unregister with the firewall. DeleteAppContainerProfile failed with error %1 because it was unable to unregister with the firewall.
0xBF000025App Container profile failed with error %1 because it was unable to register the AppContainer SID. App Container profile failed with error %1 because it was unable to register the AppContainer SID.
0xBF000026DeleteAppContainerProfile failed with error %1 because it was unable to unregister the AppContainer SID. DeleteAppContainerProfile failed with error %1 because it was unable to unregister the AppContainer SID.
0xBF000027Successfully created AppContainer %1. Successfully created AppContainer %1.
0xBF000028AppContainer %1 was not created because it already exists. AppContainer %1 was not created because it already exists.
0xBF000029Successfully deleted AppContainer %1. Successfully deleted AppContainer %1.
0xBF00002ASuccessfully updated AppContainer %1. Successfully updated AppContainer %1.
0xBF00002C%2: Application identity not accessible while loading package runtime information %1 (address=%4, size=%3, processid=%5). %2: Application identity not accessible while loading package runtime information %1 (address=%4, size=%3, processid=%5).
0xBF00002DFailed with %1 while retrieving AppContainer %2 information during interaction with Restricted AppContainer. Failed with %1 while retrieving AppContainer %2 information during interaction with Restricted AppContainer.
0xBF00002EFailed with %1 while retrieving AppContainer information during interaction with Restricted AppContainer. Failed with %1 while retrieving AppContainer information during interaction with Restricted AppContainer.
0xBF00002FFailed with %1 while retrieving AppContainer information. Call invalid from this process type. Failed with %1 while retrieving AppContainer information. Call invalid from this process type.
0xBF000030Failed to create shared context object for Restricted AppContainer %2 with %1. Failed to create shared context object for Restricted AppContainer %2 with %1.
0xBF000031Failed to activate Restricted AppContainer %2 with %1. Failed to activate Restricted AppContainer %2 with %1.
0xBF000032Creation of Restricted AppContainer %2 failed with %1 because an invalid capability was specified. Creation of Restricted AppContainer %2 failed with %1 because an invalid capability was specified.
0xBF000033Opening existing Restricted AppContainer %2 failed with %1 because the capabilities storage value could not be read. Opening existing Restricted AppContainer %2 failed with %1 because the capabilities storage value could not be read.
0xBF000034Failed to create the capabilities storage value for Restricted AppContainer %2 with %1. Failed to create the capabilities storage value for Restricted AppContainer %2 with %1.
0xBF000035The package %1 requires validation. The package %1 requires validation.
0xBF000036Modification was detected in package %1. Modification was detected in package %1.
0xBF000037Failed to terminate app with package %1. Failed to terminate app with package %1.
0xBF000038Validation of app with package %1 was successful. Validation of app with package %1 was successful.
0xBF000039Failed with %1 to retrieve the trust state of the package %2 folder. Failed with %1 to retrieve the trust state of the package %2 folder.
0xBF00003AApp Integrity check failed with %1 while checking %2. App Integrity check failed with %1 while checking %2.
0xBF00003BApp Integrity terminated an application. Integrity check for %2 returned %1. App Integrity terminated an application. Integrity check for %2 returned %1.
0xBF00003CApp Integrity check for %1 timed out. App Integrity check for %1 timed out.
0xBF00003D%2: Cannot create the process for package %1 because an error was encountered while performing the integrity check. %3 %2: Cannot create the process for package %1 because an error was encountered while performing the integrity check. %3
0xBF00003EDeployment server integrity check of package %1 failed with %2. Deployment server integrity check of package %1 failed with %2.
0xBF00003FFailed with %1 retrieving AppModel Runtime group policy values. Failed with %1 retrieving AppModel Runtime group policy values.
0xBF000040Failed with %1 validating AppModel Runtime group policy values. Failed with %1 validating AppModel Runtime group policy values.
0xBF000041Failed with %1 retrieving AppModel Runtime status for package %2. Failed with %1 retrieving AppModel Runtime status for package %2.
0xBF000042Failed with %1 retrieving AppModel Runtime status for package %2 for user %3. Failed with %1 retrieving AppModel Runtime status for package %2 for user %3.
0xBF000043Failed with %1 modifying AppModel Runtime status for package %2 (current status = %4, desired status = %3). Failed with %1 modifying AppModel Runtime status for package %2 (current status = %4, desired status = %3).
0xBF000044AppModel Runtime status for package %1 successfully updated to %2 (previous status = %3). AppModel Runtime status for package %1 successfully updated to %2 (previous status = %3).
0xBF000045Failed with %1 modifying AppModel Runtime status for package %2 for user %3 (current status = %5, desired status = %4). Failed with %1 modifying AppModel Runtime status for package %2 for user %3 (current status = %5, desired status = %4).
0xBF000046AppModel Runtime status for package %1 for user %2 successfully updated to %3 (previous status = %4). AppModel Runtime status for package %1 for user %2 successfully updated to %3 (previous status = %4).
0xBF000047Failed with %1 modifying AppModel Runtime status version (context = %2). Failed with %1 modifying AppModel Runtime status version (context = %2).
0xBF000048AppModel Runtime status version successfully updated. AppModel Runtime status version successfully updated.
0xBF000049%2: Cannot create the process for package %1 because an error was encountered while performing the app data creation. %3 %2: Cannot create the process for package %1 because an error was encountered while performing the app data creation. %3
0xBF00004APackage runtime information %1 failed to refresh because the following error %2 occurred in operation type %3. Package runtime information %1 failed to refresh because the following error %2 occurred in operation type %3.
0xBF00004Berror %2: Cannot register the %1 package because the following error was encountered while opening the HKEY_USERS registry key error %2: Cannot register the %1 package because the following error was encountered while opening the HKEY_USERS registry key
0xBF00004Cerror %4: Cannot register the %1 package because the following error was encountered while enumerating to remove the %2\\%3 package family registry key error %4: Cannot register the %1 package because the following error was encountered while enumerating to remove the %2\\%3 package family registry key
0xBF00004Derror %4 : Cannot register the %1 package because the following error was encountered while creating the %2\\%3 package family registry key error %4 : Cannot register the %1 package because the following error was encountered while creating the %2\\%3 package family registry key
0xBF00004Eerror %4: Cannot register the %1 package because the following error was encountered while removing the %2\\%3 package family registry key error %4: Cannot register the %1 package because the following error was encountered while removing the %2\\%3 package family registry key
0xBF00004F%2: Package family %1 runtime information is corrupted. Attempting to correct the issue. %2: Package family %1 runtime information is corrupted. Attempting to correct the issue.
0xBF000050%2: Package family %1 runtime information is corrupted but we cannot repair it at this time. %2: Package family %1 runtime information is corrupted but we cannot repair it at this time.
0xBF000065Creating AppContainer %1. Creating AppContainer %1.
0xBF000066Finished creating AppContainer %2 with %1. Finished creating AppContainer %2 with %1.
0xBF000067Deleting AppContainer %1. Deleting AppContainer %1.
0xBF000068Finished deleting AppContainer %2 with %1. Finished deleting AppContainer %2 with %1.
0xBF000069Updating AppContainer %1. Updating AppContainer %1.
0xBF00006AFinished updating AppContainer %2 with %1. Finished updating AppContainer %2 with %1.
0xBF00006BCreating firewall rules for AppContainer %1. Creating firewall rules for AppContainer %1.
0xBF00006CFinished creating firewall rules for AppContainer %2 with %1. Finished creating firewall rules for AppContainer %2 with %1.
0xBF00006DDeleting firewall rules for AppContainer %1. Deleting firewall rules for AppContainer %1.
0xBF00006EFinished deleting firewall rules for AppContainer %2 with %1. Finished deleting firewall rules for AppContainer %2 with %1.
0xBF00006FCreating Restricted AppContainer %1. Creating Restricted AppContainer %1.
0xBF000070Finished creating Restricted AppContainer %2 with %1. Finished creating Restricted AppContainer %2 with %1.
0xBF000071Deleting Restricted AppContainer %1. Deleting Restricted AppContainer %1.
0xBF000072Finished deleting Restricted AppContainer %2 with %1. Finished deleting Restricted AppContainer %2 with %1.
0xBF000073Opening Restricted AppContainer %1. Opening Restricted AppContainer %1.
0xBF000074Finished opening Restricted AppContainer %2 with %1. Finished opening Restricted AppContainer %2 with %1.
0xBF000075Enumerating all Restricted AppContainers for %1. Enumerating all Restricted AppContainers for %1.
0xBF000076Finished enumerating all Restricted AppContainers for AppContainer %2 with %1. Finished enumerating all Restricted AppContainers for AppContainer %2 with %1.
0xBF000077Launching process in Restricted AppContainer %1. Launching process in Restricted AppContainer %1.
0xBF000078Finished launching process in Restricted AppContainer %2 with %1. Finished launching process in Restricted AppContainer %2 with %1.
0xBF000079Terminating all processes in Restricted AppContainer %1. Terminating all processes in Restricted AppContainer %1.
0xBF00007AFinished terminating all processes in Restricted AppContainer %2 with %1. Finished terminating all processes in Restricted AppContainer %2 with %1.
0xBF00007BChecking package graph for %1. Checking package graph for %1.
0xBF00007CPackage graph check for %2 finished with %1. Package graph check for %2 finished with %1.
0xBF00007DPerforming app integrity check for package %1. Performing app integrity check for package %1.
0xBF00007EApp integrity check for package %2 finished with %1. App integrity check for package %2 finished with %1.
0xBF00007FPerforming runtime app integrity check for package %1. Performing runtime app integrity check for package %1.
0xBF000080Runtime app integrity check for package %2 finished with %1. Runtime app integrity check for package %2 finished with %1.
0xBF000081Firewall Service not running. Skipping creation of firewall rules for AppContainer %1. Firewall Service not running. Skipping creation of firewall rules for AppContainer %1.
0xBF000082Updating Restricted AppContainer Capabilities %1. Updating Restricted AppContainer Capabilities %1.
0xBF000083Finished Updating Restricted AppContainer Capabilities %2 with %1. Finished Updating Restricted AppContainer Capabilities %2 with %1.
0xBF0000C9Created process %1 for application %4 in package %2. %5 Created process %1 for application %4 in package %2. %5
0xBF0000CA%4: Cannot create the process for package %1 because an error was encountered. %5 %4: Cannot create the process for package %1 because an error was encountered. %5
0xBF0000CB%4: Cannot create the process for package %1 because an error was encountered while preparing for activation. %5 %4: Cannot create the process for package %1 because an error was encountered while preparing for activation. %5
0xBF0000CC%4: Cannot create the process for package %1 because an error was encountered while elevating the token. %5 %4: Cannot create the process for package %1 because an error was encountered while elevating the token. %5
0xBF0000CD%4: Cannot create the process for package %1 because UI Access is not supported for Desktop AppX processes. %5 %4: Cannot create the process for package %1 because UI Access is not supported for Desktop AppX processes. %5
0xBF0000CE%4: Cannot create the process for package %1 because an error was encountered while adjusting the token. %5 %4: Cannot create the process for package %1 because an error was encountered while adjusting the token. %5
0xBF0000CF%4: Cannot create the process for package %1 because an error was encountered while launching. %5 %4: Cannot create the process for package %1 because an error was encountered while launching. %5
0xBF0000D0%4: Cannot create the process for package %1 because an error was encountered while configuring runtime. %5 %4: Cannot create the process for package %1 because an error was encountered while configuring runtime. %5
0xBF0000D1%4: Cannot create the process for package %1 because an error was encountered while resuming the thread. %5 %4: Cannot create the process for package %1 because an error was encountered while resuming the thread. %5
0xBF0000D2Created Desktop AppX container %3 for package %1. Created Desktop AppX container %3 for package %1.
0xBF0000D3Added process %1 to Desktop AppX container %3 for package %2. Added process %1 to Desktop AppX container %3 for package %2.
0xBF0000D4%1: Cannot add process %2 to Desktop AppX container %4 for package %3 because an error was encountered. %1: Cannot add process %2 to Desktop AppX container %4 for package %3 because an error was encountered.
0xBF0000D5%1: Cannot create the Desktop AppX container for package %2 because an error was encountered creating the job. %1: Cannot create the Desktop AppX container for package %2 because an error was encountered creating the job.
0xBF0000D6%1: Cannot create the Desktop AppX container for package %2 because an error was encountered creating the description. %1: Cannot create the Desktop AppX container for package %2 because an error was encountered creating the description.
0xBF0000D7%1: Cannot create the Desktop AppX container for package %2 because an error was encountered converting the job. %1: Cannot create the Desktop AppX container for package %2 because an error was encountered converting the job.
0xBF0000D8%1: Cannot create the Desktop AppX container for package %2 because an error was encountered configuring the runtime. %1: Cannot create the Desktop AppX container for package %2 because an error was encountered configuring the runtime.
0xBF0000D9Destroyed Desktop AppX container %2 for package %1. Destroyed Desktop AppX container %2 for package %1.
0xBF0000DACannot destroy Desktop AppX container %2 for package %1. Cannot destroy Desktop AppX container %2 for package %1.
0xD1000001System time initialized during boot System time initialized during boot
0xD1000002An application or system component changed the time An application or system component changed the time
0xD1000003System time synchronized with the hardware clock System time synchronized with the hardware clock
0xD1000004System time adjusted to the new time zone System time adjusted to the new time zone
0xD4000001on on
0xD4000002off off
0xD4000003started started
0xD4000004finished finished
0xD4000005Platform-level Device Reset Platform-level Device Reset
0xD4000006Function-level Device Reset Function-level Device Reset
0xD4000007Acpi Override attribute - MpSleep Acpi Override attribute - MpSleep
0xD4000008Acpi Override attribute - DisableS1 Acpi Override attribute - DisableS1
0xD4000009Acpi Override attribute - DisableS2 Acpi Override attribute - DisableS2
0xD400000AAcpi Override attribute - DisableS3 Acpi Override attribute - DisableS3
0xD400000BAcpi Override attribute - DellMaxUlongBugcheck Acpi Override attribute - DellMaxUlongBugcheck
0xD400000CAcpi Override attribute - PciBusNumberTranslation Acpi Override attribute - PciBusNumberTranslation
0xD400000DAcpi Override attribute - RunRegMethodOnPciDevices Acpi Override attribute - RunRegMethodOnPciDevices
0xD400000EAcpi Override attribute - RescanPostDependencies Acpi Override attribute - RescanPostDependencies
0xD400000FAcpi Override attribute - PlatformCheckD3ColdOnSurpriseRemoval Acpi Override attribute - PlatformCheckD3ColdOnSurpriseRemoval
0xD4000010Acpi Override attribute - PlatformCheckFailResetOnOpenHandles Acpi Override attribute - PlatformCheckFailResetOnOpenHandles
0xDC000001disabled disabled
0xDC000002disabled due to HyperV opt-out disabled due to HyperV opt-out
0xDC000003disabled due to opt-out UEFI variable disabled due to opt-out UEFI variable
0xDC000004disabled due to secure boot being disabled disabled due to secure boot being disabled
0xDC000005disabled due to DMA protection being unavailable disabled due to DMA protection being unavailable
0xDC000006disabled due to the hypervisor being unavailable disabled due to the hypervisor being unavailable
0xDC000007disabled due to VBS initialization failure disabled due to VBS initialization failure
0xDC000008enabled due to VBS registry configuration enabled due to VBS registry configuration
0xDC000009enabled due to HyperV enabled due to HyperV
0xDC00000Aenabled due to VBS locked configuration enabled due to VBS locked configuration
0xDC00000BBL_LOG_INFO_NONE: Info none BL_LOG_INFO_NONE: Info none
0xDC00000CBL_LOG_INFO_BLI_IO_INITED: IO initialized in boot library initialization. BL_LOG_INFO_BLI_IO_INITED: IO initialized in boot library initialization.
0xDC00000DBL_LOG_INFO_BLI_FINISHED: Finished in boot library initialization. BL_LOG_INFO_BLI_FINISHED: Finished in boot library initialization.
0xDC00000EBL_LOG_INFO_BM_BL_INITED: The boot library has been initialized for bootmgr. BL_LOG_INFO_BM_BL_INITED: The boot library has been initialized for bootmgr.
0xDC00000FBL_LOG_INFO_BM_GET_BOOT_SEQ: Getting boot sequence in bootmgr. BL_LOG_INFO_BM_GET_BOOT_SEQ: Getting boot sequence in bootmgr.
0xDC000010BL_LOG_INFO_BM_LAUNCH_ENTRY: Launching boot entry in bootmgr. BL_LOG_INFO_BM_LAUNCH_ENTRY: Launching boot entry in bootmgr.
0xDC000011BL_LOG_INFO_OSL_PREPARE_ENTERED: Reached prepare target within osloader. BL_LOG_INFO_OSL_PREPARE_ENTERED: Reached prepare target within osloader.
0xDC000012BL_LOG_INFO_OSL_OPEN_DEVICE: Preparing to open OS device in osloader. BL_LOG_INFO_OSL_OPEN_DEVICE: Preparing to open OS device in osloader.
0xDC000013BL_LOG_INFO_OSL_LAUNCH_HYPERV: Preparing to launch hyper-v if specified within osloader. BL_LOG_INFO_OSL_LAUNCH_HYPERV: Preparing to launch hyper-v if specified within osloader.
0xDC000014BL_LOG_INFO_OSL_LOAD_MODULES: Preparing to load OS modules within osloader. BL_LOG_INFO_OSL_LOAD_MODULES: Preparing to load OS modules within osloader.
0xDC000015BL_LOG_INFO_OSL_KERNEL_SETUP: Setting up kernel within osloader. BL_LOG_INFO_OSL_KERNEL_SETUP: Setting up kernel within osloader.
0xDC000016BL_LOG_ERROR: Generic Error BL_LOG_ERROR: Generic Error
0xDC000017BL_LOG_ERROR_BLI_NET_INIT: BlNetInitialize failed in BL initialization. BL_LOG_ERROR_BLI_NET_INIT: BlNetInitialize failed in BL initialization.
0xDC000018BL_LOG_ERROR_BLI_UTL_INIT: BlUtlInitialize failed in BL initialization. BL_LOG_ERROR_BLI_UTL_INIT: BlUtlInitialize failed in BL initialization.
0xDC000019BL_LOG_ERROR_BLI_SEC_BOOT_INIT: BlSecureBootInitialize failed in BL initialization. BL_LOG_ERROR_BLI_SEC_BOOT_INIT: BlSecureBootInitialize failed in BL initialization.
0xDC00001ABL_LOG_ERROR_BLI_PDATA_INIT: BlpPdInitialize failed in BL initialization. BL_LOG_ERROR_BLI_PDATA_INIT: BlpPdInitialize failed in BL initialization.
0xDC00001BBL_LOG_ERROR_BLI_RES_INIT: BlpResourceInitialize failed in BL initialization. BL_LOG_ERROR_BLI_RES_INIT: BlpResourceInitialize failed in BL initialization.
0xDC00001CBL_LOG_ERROR_BM_INIT_MACH_POL: BmSecureBootInitializeMachinePolicy failed in bootmgr. BL_LOG_ERROR_BM_INIT_MACH_POL: BmSecureBootInitializeMachinePolicy failed in bootmgr.
0xDC00001DBL_LOG_ERROR_BM_FW_REG_SYSINT: BmFwRegisterSystemIntegrityPolicies failed in bootmgr. BL_LOG_ERROR_BM_FW_REG_SYSINT: BmFwRegisterSystemIntegrityPolicies failed in bootmgr.
0xDC00001EBL_LOG_ERROR_BM_RES_FIND_HTML: BlResourceFindHtml failed to find BOOTMGR.XSL in bootmgr. BL_LOG_ERROR_BM_RES_FIND_HTML: BlResourceFindHtml failed to find BOOTMGR.XSL in bootmgr.
0xDC00001FBL_LOG_ERROR_BM_XMI_INIT: BlXmiInitialize failed in bootmgr. BL_LOG_ERROR_BM_XMI_INIT: BlXmiInitialize failed in bootmgr.
0xDC000020BL_LOG_ERROR_BM_OPEN_DATA_STORE: BmOpenDataStore failed in bootmgr. BL_LOG_ERROR_BM_OPEN_DATA_STORE: BmOpenDataStore failed in bootmgr.
0xDC000021BL_LOG_ERROR_BM_SELF_INT_CHK: BmpSelfIntegrityCheck failed in bootmgr. BL_LOG_ERROR_BM_SELF_INT_CHK: BmpSelfIntegrityCheck failed in bootmgr.
0xDC000022BL_LOG_ERROR_BM_FW_REG_REV_LIST: BmFwRegisterRevocationList failed in bootmgr. BL_LOG_ERROR_BM_FW_REG_REV_LIST: BmFwRegisterRevocationList failed in bootmgr.
0xDC000023BL_LOG_ERROR_BM_RESUME_HIBER: BmResumeFromHibernate failed in 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 failed in 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 failed for BCDE_BOOTMGR_TYPE_BOOT_SEQUENCE in bootmgr. 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 failed on reopen in bootmgr. BL_LOG_ERROR_BM_REOPEN_DATA_STORE: BmOpenDataStore failed on reopen in bootmgr.
0xDC000027BL_LOG_ERROR_BM_UPDATE_APP_OPTS: BmpUpdateApplicationOptions failed in bootmgr. BL_LOG_ERROR_BM_UPDATE_APP_OPTS: BmpUpdateApplicationOptions failed in bootmgr.
0xDC000028BL_LOG_ERROR_BM_LAUNCH_BOOT_ENTRY: BmpLaunchBootEntry failed in bootmgr. BL_LOG_ERROR_BM_LAUNCH_BOOT_ENTRY: BmpLaunchBootEntry failed in bootmgr.
0xDC000029BL_LOG_ERROR_BM_CREATE_DEVICES: BmpCreateDevices failed in bootmgr. BL_LOG_ERROR_BM_CREATE_DEVICES: BmpCreateDevices failed in bootmgr.
0xDC00002ABL_LOG_ERROR_BM_LAUNCH_FLIGHT_BM: BmFwLaunchFlightedBootmgr failed in bootmgr. BL_LOG_ERROR_BM_LAUNCH_FLIGHT_BM: BmFwLaunchFlightedBootmgr failed in bootmgr.
0xDC00002BBL_LOG_ERROR_BM_FE_BOOTAPP_LD: Fatal error: failure to load boot app in bootmgr. BL_LOG_ERROR_BM_FE_BOOTAPP_LD: Fatal error: failure to load boot app in bootmgr.
0xDC00002CBL_LOG_ERROR_BM_FE_CONFIG_DATA: Fatal error: failure attempting to read boot config file in 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: Fatal error: no valid os entires found in bootmgr. 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: Fatal error: no valid entries found from PXE server in bootmgr. 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: Fatal error: failure status in bootmgr. BL_LOG_ERROR_BM_FE_FAILURE_STATUS: Fatal error: failure status in bootmgr.
0xDC000030BL_LOG_ERROR_BM_FE_BOOT_DEVICE: Fatal error: boot device inaccessible in bootmgr. BL_LOG_ERROR_BM_FE_BOOT_DEVICE: Fatal error: boot device inaccessible in bootmgr.
0xDC000031BL_LOG_ERROR_BM_FE_RAMDISK_MEM: Fatal error: ramdisk device creation had insufficient memory in bootmgr. 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: Fatal error: BCD is invalid in bootmgr. BL_LOG_ERROR_BM_FE_INVALID_BCD_STORE: Fatal error: BCD is invalid in bootmgr.
0xDC000033BL_LOG_ERROR_BM_FE_INVALID_BCD_ENTRY: Fatal error: Invalid BCD entry in bootmgr. BL_LOG_ERROR_BM_FE_INVALID_BCD_ENTRY: Fatal error: Invalid BCD entry in bootmgr.
0xDC000034BL_LOG_ERROR_BM_FE_NO_SECUREBOOT_POL: Fatal error: Default Secure Boot policy not found in 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: Fatal error: CPU does not support PAE in bootmgr. 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: Fatal error: Cannot unseal sensitive data in bootmgr. BL_LOG_ERROR_BM_FE_UNSEAL_NOT_POS: Fatal error: Cannot unseal sensitive data in bootmgr.
0xDC000037BL_LOG_ERROR_BM_FE_GENERIC: Fatal error: Generic failure in bootmgr. BL_LOG_ERROR_BM_FE_GENERIC: Fatal error: Generic failure in bootmgr.
0xDC000038BL_LOG_ERROR_OSL_REM_INTERN_APP_OPTS: OslpRemoveInternalApplicationOptions failed in osloader. BL_LOG_ERROR_OSL_REM_INTERN_APP_OPTS: OslpRemoveInternalApplicationOptions failed in osloader.
0xDC000039BL_LOG_ERROR_OSL_GET_APP_OPT_DEVICE: BlGetApplicationOptionDevice failed for BCDE_OSLOADER_TYPE_OS_DEVICE in osloader. 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 failed for BCDE_OSLOADER_TYPE_SYSTEM_ROOT in osloader. 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 failed implying a forced failure in osloader. BL_LOG_ERROR_OSL_FORCED_FAIL: OslpCheckForcedFailure failed implying a forced failure in osloader.
0xDC00003CBL_LOG_ERROR_OSL_DISABLE_VGA: BlAppendApplicationOptionBoolean for BCDE_OSLOADER_TYPE_DISABLE_VGA_MODE failed in osloader. 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 failed for os device in osloader. BL_LOG_ERROR_OSL_OPEN_OS_DEVICE: BlDeviceOpen failed for os device in osloader.
0xDC00003EBL_LOG_ERROR_OSL_LOAD_SYS_HIVE: OslpLoadSystemHive failed in osloader. BL_LOG_ERROR_OSL_LOAD_SYS_HIVE: OslpLoadSystemHive failed in osloader.
0xDC00003FBL_LOG_ERROR_OSL_CREATE_OS_LD_OPTS: AhCreateLoadOptionsString failed in osloader. BL_LOG_ERROR_OSL_CREATE_OS_LD_OPTS: AhCreateLoadOptionsString failed in osloader.
0xDC000040BL_LOG_ERROR_OSL_DISPLAY_INIT: OslDisplayInitialize failed in osloader. BL_LOG_ERROR_OSL_DISPLAY_INIT: OslDisplayInitialize failed in osloader.
0xDC000041BL_LOG_ERROR_OSL_PROCESS_SI_POLICY: OslpProcessSIPolicy failed in osloader. BL_LOG_ERROR_OSL_PROCESS_SI_POLICY: OslpProcessSIPolicy failed in osloader.
0xDC000042BL_LOG_ERROR_OSL_DISP_ADV_OPT: OslDisplayAdvancedOptionsProcess failed in osloader. BL_LOG_ERROR_OSL_DISP_ADV_OPT: OslDisplayAdvancedOptionsProcess failed in osloader.
0xDC000043BL_LOG_ERROR_OSL_ARCH_HV_SETUP: OslArchHypervisorSetup failed in osloader. BL_LOG_ERROR_OSL_ARCH_HV_SETUP: OslArchHypervisorSetup failed in osloader.
0xDC000044BL_LOG_ERROR_OSL_ARCH_HYPERCALL_SETUP: OslArchHypercallSetup failed in osloader. BL_LOG_ERROR_OSL_ARCH_HYPERCALL_SETUP: OslArchHypercallSetup failed in osloader.
0xDC000045BL_LOG_ERROR_OSL_INIT_RESUME_CONTEXT: OslInitializeResumeContext failed in osloader. BL_LOG_ERROR_OSL_INIT_RESUME_CONTEXT: OslInitializeResumeContext failed in osloader.
0xDC000046BL_LOG_ERROR_OSL_INIT_LDR_BLOCK: OslInitializeLoaderBlock failed in osloader. BL_LOG_ERROR_OSL_INIT_LDR_BLOCK: OslInitializeLoaderBlock failed in osloader.
0xDC000047BL_LOG_ERROR_OSL_PROC_INIT_MACH_CONFIG: OslpProcessInitialMachineConfiguration failed in osloader. BL_LOG_ERROR_OSL_PROC_INIT_MACH_CONFIG: OslpProcessInitialMachineConfiguration failed in osloader.
0xDC000048BL_LOG_ERROR_OSL_ENUM_DISKS: OslEnumerateDisks failed for the loader block in osloader. BL_LOG_ERROR_OSL_ENUM_DISKS: OslEnumerateDisks failed for the loader block in osloader.
0xDC000049BL_LOG_ERROR_OSL_REINIT_SYS_HIVE: OslpReinitializeSystemHive failed in osloader. BL_LOG_ERROR_OSL_REINIT_SYS_HIVE: OslpReinitializeSystemHive failed in osloader.
0xDC00004ABL_LOG_ERROR_OSL_INIT_CODE_INT: OslInitializeCodeIntegrity failed in osloader. BL_LOG_ERROR_OSL_INIT_CODE_INT: OslInitializeCodeIntegrity failed in osloader.
0xDC00004BBL_LOG_ERROR_OSL_INIT_CODE_INT_LD_BLOCK: OslBuildCodeIntegrityLoaderBlock failed in osloader. BL_LOG_ERROR_OSL_INIT_CODE_INT_LD_BLOCK: OslBuildCodeIntegrityLoaderBlock failed in osloader.
0xDC00004CBL_LOG_ERROR_OSL_SECURE_BOOT_VARS: OslFwProtectSecureBootVariables failed in osloader. BL_LOG_ERROR_OSL_SECURE_BOOT_VARS: OslFwProtectSecureBootVariables failed in osloader.
0xDC00004DBL_LOG_ERROR_OSL_LD_MODULES: OslpLoadAllModules failed in osloader. BL_LOG_ERROR_OSL_LD_MODULES: OslpLoadAllModules failed in osloader.
0xDC00004EBL_LOG_ERROR_OSL_LD_FW_DRIVERS: OslFwLoadFirmwareDrivers failed in osloader. BL_LOG_ERROR_OSL_LD_FW_DRIVERS: OslFwLoadFirmwareDrivers failed in osloader.
0xDC00004FBL_LOG_ERROR_OSL_VSM_CHK_ENCRYPT_KEY: BlVsmCheckSystemPolicy failed for master sncrupt key provisioning in osloader. 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 failed for phase 0 in osloader. BL_LOG_ERROR_OSL_VSM_CHK_PHASE_0: BlVsmCheckSystemPolicy failed for phase 0 in osloader.
0xDC000051BL_LOG_ERROR_OSL_SET_SEIL_SIGN_POL: OslSetSeILSigningPolicy failed in osloader. BL_LOG_ERROR_OSL_SET_SEIL_SIGN_POL: OslSetSeILSigningPolicy failed in osloader.
0xDC000052BL_LOG_ERROR_OSL_CMS_PROV_IDK: BlVsmCheckSystemPolicy failed during VSM Idendity key work in osloader. 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 failed for 0 in osloader. BL_LOG_ERROR_OSL_ARCH_KERNEL_SETUP_0: OslArchKernelSetup failed for 0 in osloader.
0xDC000054BL_LOG_ERROR_OSL_FW_KERNEL_SETUP: OslFwKernelSetup failed for 0 in osloader. BL_LOG_ERROR_OSL_FW_KERNEL_SETUP: OslFwKernelSetup failed for 0 in osloader.
0xDC000055BL_LOG_ERROR_OSL_PROC_EV_STORE: OslpProcessEVStore failed in osloader. BL_LOG_ERROR_OSL_PROC_EV_STORE: OslpProcessEVStore failed in osloader.
0xDC000056BL_LOG_ERROR_OSL_COPY_BOOT_OPTS: BlCopyBootOptions failed in osloader. BL_LOG_ERROR_OSL_COPY_BOOT_OPTS: BlCopyBootOptions failed in osloader.
0xDC000057BL_LOG_ERROR_OSL_FVE_SEC_BOOT_REST_ONE: BlFveSecureBootRestrictToOne failed in osloader. BL_LOG_ERROR_OSL_FVE_SEC_BOOT_REST_ONE: BlFveSecureBootRestrictToOne failed in osloader.
0xDC000058BL_LOG_ERROR_OSL_NET_UNDI_CLOSE: BlNetUndiClose failed in osloader. BL_LOG_ERROR_OSL_NET_UNDI_CLOSE: BlNetUndiClose failed in osloader.
0xDC000059BL_LOG_ERROR_OSL_PROC_APP_PDATA: OslProcessApplicationPersistentData failed in osloader. BL_LOG_ERROR_OSL_PROC_APP_PDATA: OslProcessApplicationPersistentData failed in osloader.
0xDC00005ABL_LOG_ERROR_OSL_BLD_MEM_CACHE_REQ_LIST: OslFwBuildMemoryCachingRequirementsList failed in osloader. BL_LOG_ERROR_OSL_BLD_MEM_CACHE_REQ_LIST: OslFwBuildMemoryCachingRequirementsList failed in osloader.
0xDC00005BBL_LOG_ERROR_OSL_BLD_RT_MEM_MAP: OslFwBuildRuntimeMemoryMap failed in osloader. BL_LOG_ERROR_OSL_BLD_RT_MEM_MAP: OslFwBuildRuntimeMemoryMap failed in osloader.
0xDC00005CBL_LOG_ERROR_OSL_VSM_SETUP: OslVsmSetup failed for 1 in osloader. BL_LOG_ERROR_OSL_VSM_SETUP: OslVsmSetup failed for 1 in osloader.
0xDC00005DBL_LOG_ERROR_OSL_BLD_KERNEL_MEM_MAP: BlTraceBuildKernelMemoryMapStop failed in osloader. BL_LOG_ERROR_OSL_BLD_KERNEL_MEM_MAP: BlTraceBuildKernelMemoryMapStop failed in osloader.
0xDC00005EBL_LOG_ERROR_OSL_ARCH_KERNEL_SETUP_1: OslArchKernelSetup failed for 1 in osloader. BL_LOG_ERROR_OSL_ARCH_KERNEL_SETUP_1: OslArchKernelSetup failed for 1 in osloader.
0xDC00005FBL_LOG_ERROR_OSL_SET_VSM_POL_SYS_HIVE: OslSetVsmPolicy failed in osloader. BL_LOG_ERROR_OSL_SET_VSM_POL_SYS_HIVE: OslSetVsmPolicy failed in osloader.
0xDC000060BL_LOG_ERROR_OSL_ENUM_ENCLAVE_PAGES: OslEnumerateEnclavePageRegions failed in osloader. BL_LOG_ERROR_OSL_ENUM_ENCLAVE_PAGES: OslEnumerateEnclavePageRegions failed in osloader.
0xDC000061BL_LOG_ERROR_OSL_GATHER_ENTROPY: OslGatherEntropy failed in osloader. BL_LOG_ERROR_OSL_GATHER_ENTROPY: OslGatherEntropy failed in osloader.
0xDE000001applied through registry applied through registry
0xDE000002applied through compatibility database applied through compatibility database
0xF2000001PackageId PackageId
0xFC000001None None
0xFC000002VBS Enabled VBS Enabled
0xFC000003VSM Required VSM Required
0xFC000004Secure Boot Secure Boot
0xFC000005Iommu Protection Iommu Protection
0xFC000006Mmio Nx Mmio Nx
0xFC000007Strong MSR Filtering Strong MSR Filtering
0xFC000008Mandatory Mandatory
0xFC000009Hvci Hvci
0xFC00000AHvci Strict Hvci Strict
0xFC00000BBoot Chain Signer Soft Enforced Boot Chain Signer Soft Enforced
0xFC00000CBoot Chain Signer Hard Enforced 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_en-us_6643e726c2827ed0\
File Size:115 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:117248
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:English (U.S.)
Character Set:Unicode
Company Name:Microsoft Corporation
File Description:Microsoft-Windows-System-Events Resources
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 English (U.S.) language for file microsoft-windows-system-events.dll (Microsoft-Windows-System-Events Resources).

File version info

File Description:Microsoft-Windows-System-Events Resources
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:0x409, 1200