microsoft-windows-system-events.dll
Associated Error Codes
Below lists error codes and symbolic names found for this module.
| Code | Found in | Description |
|---|---|---|
| 0x1 | 1011 | Possible detection of CVE: %1 Additional Information: %2 This Event is generated when an attempt to exploit a known vulnerability (%1) is detected. This Event is raised by a User mode process. |
| 0x2 | 1011 | Possible detection of CVE: %1 Additional Information: %2 This Event is generated when an attempt to exploit a known vulnerability (%1) is detected. This Event is raised by a kernel mode driver. |
| 0x12c | 1011 | Microsoft-Windows-Kernel-AppCompat |
| 0x12d | 1011 | Microsoft-Windows-AIT |
| 0x12e | 1011 | Microsoft-Windows-Kernel-ApphelpCache |
| 0x12f | 1011 | Microsoft-Windows-AeSwitchBack |
| 0x130 | 1011 | Microsoft-Windows-AeLookupServiceTrigger |
| 0x133 | 1011 | %1 |
| 0x134 | 1011 | %1 |
| 0x135 | 1011 | %1 |
| 0x136 | 1011 | The executable %2 received an access denied error when trying to modify the registry key %4. |
| 0x1f4 | 1011 | Microsoft-Windows-Kernel-Network |
| 0x1f5 | 1011 | Data sent. |
| 0x1f6 | 1011 | Data received. |
| 0x1f7 | 1011 | Connection attempted. |
| 0x1f8 | 1011 | Disconnect issued. |
| 0x1f9 | 1011 | Data retransmitted. |
| 0x1fa | 1011 | Connection accepted. |
| 0x1fb | 1011 | Reconnect attempted. |
| 0x1fc | 1011 | TCP connection attempt failed. |
| 0x1fd | 1011 | Protocol copied data on behalf of user. |
| 0x1fe | 1011 | Data sent over UDP protocol. |
| 0x1ff | 1011 | Data received over UDP protocol. |
| 0x200 | 1011 | UDP connection attempt failed. |
| 0x201 | 1011 | TCPv4: %2 bytes transmitted from %4:%6 to %3:%5. |
| 0x202 | 1011 | TCPv4: %2 bytes received from %4:%6 to %3:%5. |
| 0x203 | 1011 | TCPv4: Connection attempted between %4:%6 and %3:%5. |
| 0x204 | 1011 | TCPv4: Connection closed between %4:%6 and %3:%5. |
| 0x205 | 1011 | TCPv4: %2 bytes retransmitted from %4:%6 to %3:%5. |
| 0x206 | 1011 | TCPv4: Connection established between %4:%6 and %3:%5. |
| 0x207 | 1011 | TCPv4: Reconnect attempt between %4:%6 and %3:%5. |
| 0x208 | 1011 | TCPv4: Connection attempt failed with error code %2. |
| 0x209 | 1011 | TCPv4: %2 bytes copied in protocol on behalf of user for connection between %4:%6 and %3:%5. |
| 0x20a | 1011 | UDPv4: %2 bytes transmitted from %4:%6 to %3:%5. |
| 0x20b | 1011 | UDPv4: %2 bytes received from %4:%6 to %3:%5. |
| 0x20c | 1011 | UDPv4: Connection attempt failed with error code %2. |
| 0x20d | 1011 | TCPv6: %2 bytes transmitted from %4:%6 to %3:%5. |
| 0x20e | 1011 | TCPv6: %2 bytes received from %4:%6 to %3:%5. |
| 0x20f | 1011 | TCPv6: Connection attempted between %4:%6 and %3:%5. |
| 0x210 | 1011 | TCPv6: Connection closed between %4:%6 and %3:%5. |
| 0x211 | 1011 | TCPv6: %2 bytes retransmitted from %4:%6 to %3:%5. |
| 0x212 | 1011 | TCPv6: Connection established between %4:%6 and %3:%5. |
| 0x213 | 1011 | TCPv6: Reconnect attempt between %4:%6 and %3:%5. |
| 0x214 | 1011 | TCPv6: %2 bytes copied in protocol on behalf of user for connection between %4:%6 and %3:%5. |
| 0x215 | 1011 | UDPv6: %2 bytes transmitted from %4:%6 to %3:%5. |
| 0x216 | 1011 | UDPv6: %2 bytes received from %4:%6 to %3:%5. |
| 0x258 | 1011 | Microsoft-Windows-Kernel-Disk |
| 0x259 | 1011 | %3 bytes read from disk %1 at %5. |
| 0x25a | 1011 | %3 bytes written to disk %1 at %5. |
| 0x25b | 1011 | Buffers flushed to disk %1. |
| 0x2bc | 1011 | Microsoft-Windows-Kernel-Boot |
| 0x2bd | 1011 | System was booted in %1x%2@%3bpp. |
| 0x2be | 1011 | BootUX screen was displayed in %1x%2@%3bpp. |
| 0x2bf | 1011 | Video bit transfer rate is %1 bytes per ms. |
| 0x2c0 | 1011 | Boot library accessed file %2 on Device %1. Read %3 bytes and wrote %4 bytes. |
| 0x2c1 | 1011 | File IO for boot application %1: Total Bytes Read = %2, Total Bytes Written = %3. |
| 0x2c2 | 1011 | Image %1 failed IntegrityCheck reason is %3. Image flags are %2. Error ignored due to debugger %4. |
| 0x2c3 | 1011 | Bootmgr duration is %1 milliseconds. |
| 0x2c4 | 1011 | Image %1 is not self-signed. |
| 0x2c5 | 1011 | A device (%1) that was enumerated by the BIOS was inaccessible to the boot environment. |
| 0x2c6 | 1011 | Variable %1 requires %2 bytes and was set with status %3. |
| 0x2c7 | 1011 | Element %2 of application %1 was not in policy. |
| 0x2c8 | 1011 | A Secure Boot Policy update resulted in status %1. |
| 0x2c9 | 1011 | A Secure Boot Revocation List update resulted in status %1. |
| 0x2ca | 1011 | Retrieving the driver list took %1 milliseconds. |
| 0x2cb | 1011 | Loading the drivers took %1 milliseconds. |
| 0x2cc | 1011 | Loading hive %1 took %2 milliseconds. |
| 0x2cd | 1011 | The time elapsed loading %1 was %2 ms. |
| 0x2ce | 1011 | The time elapsed executing %1 was %2 ms. |
| 0x2cf | 1011 | Building chunk table for WIM compressed file %2 failed with status: %1 |
| 0x2d0 | 1011 | Soft Restart failed to prepare target Operating System. Operation status: %1 failure point: %2 |
| 0x2d1 | 1011 | Boot application failed to process persistent data with status: %1 |
| 0x320 | 1011 | Microsoft-Windows-Kernel-File |
| 0x352 | 1011 | Error setting traits on Provider %1. Error: %2 |
| 0x353 | 1011 | A registration for Provider %1 has joined Provider Group %2 |
| 0x354 | 1011 | Enable Info |
| 0x355 | 1011 | Set Provider Traits |
| 0x356 | 1011 | Join Provider Group |
| 0x385 | 1011 | Microsoft-Windows-Kernel-EventTracing |
| 0x386 | 1011 | Session "%1" failed to write to log file "%2" with the following error: %3 |
| 0x387 | 1011 | The backing-file for the real-time session "%1" has reached its maximum size. As a result, new events will not be logged to this session until space becomes available. This error is often caused by starting a trace session in real-time mode without having any real-time consumers. |
| 0x388 | 1011 | Session "%1" failed to start with the following error: %3 |
| 0x389 | 1011 | Session "%1" stopped due to the following error: %3 |
| 0x38a | 1011 | The maximum file size for session "%1" has been reached. As a result, events might be lost (not logged) to file "%2". The maximum files size is currently set to %5 bytes. |
| 0x38b | 1011 | An error was encountered while tracing session "%2" was switching to the "%1" event log file. Error: %3 |
| 0x38e | 1011 | Provider %1 was registered with Event Tracing for Windows. |
| 0x38f | 1011 | Provider %1 was unregistered from Event Tracing for Windows. |
| 0x390 | 1011 | Session "%3" was started. |
| 0x391 | 1011 | Session "%3" was stopped. |
| 0x392 | 1011 | The configuration of session "%3" has been modified. |
| 0x393 | 1011 | The events from session "%3" have been flushed. |
| 0x394 | 1011 | Provider %1 has been enabled to session "%2". |
| 0x395 | 1011 | Provider %1 is no longer enabled to session "%2". |
| 0x396 | 1011 | The security settings of provider %1 have been modified from %2 to %3. |
| 0x397 | 1011 | The security descriptor for session "%3" has been updated. |
| 0x398 | 1011 | Provider |
| 0x399 | 1011 | Session |
| 0x39b | 1011 | Logging |
| 0x39d | 1011 | Stop |
| 0x39e | 1011 | Start |
| 0x39f | 1011 | Disable |
| 0x3a0 | 1011 | Enable |
| 0x3a1 | 1011 | Unregister |
| 0x3a2 | 1011 | Register |
| 0x3a3 | 1011 | Flush |
| 0x3a4 | 1011 | Configure |
| 0x3a7 | 1011 | Write Buffer |
| 0x3a8 | 1011 | File Switch |
| 0x3aa | 1011 | Provider |
| 0x3ab | 1011 | Session |
| 0x3ac | 1011 | Stack correlation event. This event contains a call stack which is associated with a prior event which is correlated by the MatchId. |
| 0x3ad | 1011 | Stack Trace |
| 0x3ae | 1011 | User Mode Stack Trace |
| 0x3af | 1011 | Microsoft-Windows-Kernel-EventTracing/Analytic |
| 0x3b0 | 1011 | Microsoft-Windows-Kernel-EventTracing/Admin |
| 0x3b1 | 1011 | Lost Event |
| 0x3b2 | 1011 | Lost Event |
| 0x3b3 | 1011 | Logger mode incompatible with Append mode |
| 0x3b4 | 1011 | OS version mismatch |
| 0x3b5 | 1011 | Pointer size mismatch |
| 0x3b6 | 1011 | Unsupported BufferSize |
| 0x3b7 | 1011 | BufferSize mismatch |
| 0x3b8 | 1011 | Preallocate mode is incompatible with Append mode |
| 0x3b9 | 1011 | File size query failed |
| 0x3ba | 1011 | Maximum file size reached |
| 0x3bb | 1011 | Number of buffers written is zero |
| 0x3bc | 1011 | Numberf of processors mismatch |
| 0x3bd | 1011 | Error saving soft restart persisted log "%1" Error: %5 |
| 0x3be | 1011 | GUID Entry |
| 0x3bf | 1011 | Provider Group Entry |
| 0x3c0 | 1011 | Microsoft-Windows-Kernel-StoreMgr |
| 0x3c1 | 1011 | Microsoft-Windows-Kernel-StoreMgr/Operational |
| 0x3c2 | 1011 | %5 Virtual Address: %2 Physical Address: %3 Corruption Window Size: %4 |
| 0x3c3 | 1011 | A memory corruption was detected and handled. Memory diagnostics should be run on this machine and, if necessary, memory chips should be replaced. |
| 0x3c4 | 1011 | 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. |
| 0x3c5 | 1011 | 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 | 1011 | %1 Device name: %4 Cache path: %6 |
| 0x3c7 | 1011 | A ReadyBoost cache was deleted due to repeated data corruption instances on the associated device that have been detected and handled. While ReadyBoost will always detect and handle these errors, repeated corruption instances may mean that the ReadyBoost device has worn out which reduces its performance. You should consider replacing the ReadyBoost device. |
| 0x3c8 | 1011 | 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. |
| 0x3e8 | 1011 | Microsoft-Windows-LicensingStartServiceTrigger |
| 0x3f2 | 1011 | Microsoft-Windows-WSServiceStartServiceTrigger |
| 0x44c | 1011 | Microsoft-Windows-Kernel-LiveDump |
| 0x44d | 1011 | Microsoft-Windows-Kernel-LiveDump/Analytic |
| 0x44e | 1011 | Live Dump Capture Dump Data API |
| 0x44f | 1011 | Sizing Workflow |
| 0x450 | 1011 | Capture Pages Workflow |
| 0x451 | 1011 | Live Dump Write Deferred Dump Data API |
| 0x452 | 1011 | Live Dump Discard Deferred Dump Data API |
| 0x453 | 1011 | Sizing Workflow: Mirroring started. |
| 0x454 | 1011 | Sizing Workflow: Mirroring Phase 0 ended. |
| 0x455 | 1011 | Sizing Workflow: Mirroring Phase 1 ended. |
| 0x456 | 1011 | Sizing Workflow: System Quiesce started. |
| 0x457 | 1011 | Sizing Workflow: System Quiesce ended. |
| 0x458 | 1011 | Capture Pages Workflow: Mirroring started. |
| 0x459 | 1011 | Capture Pages Workflow: Mirroring Phase 0 ended. |
| 0x45a | 1011 | Capture Pages Workflow: Mirroring Phase 1 ended. |
| 0x45b | 1011 | Capture Pages Workflow: System Quiesce started. |
| 0x45c | 1011 | Capture Pages Workflow: System Quiesce ended. |
| 0x45d | 1011 | Capture Pages Workflow: Copy memory pages started. |
| 0x45e | 1011 | Capture Pages Workflow: Copy memory pages ended. |
| 0x45f | 10 | Live Dump Capture Dump Data API started. |
| 0x460 | 10 | Live Dump Capture Dump Data API ended. NT Status: %1. |
| 0x461 | 1011 | Writing dump file started. |
| 0x462 | 10 | Writing dump file ended. NT Status: %1. Total %2 bytes (Header|Primary|Secondary: %3|%4|%5 bytes). |
| 0x463 | 1011 | API Start |
| 0x464 | 1011 | API End |
| 0x465 | 1011 | Dump File Write Start |
| 0x466 | 1011 | Dump File Write End |
| 0x467 | 1011 | Mirroring Start |
| 0x468 | 1011 | Mirroring Phase 0 End |
| 0x469 | 1011 | Mirroring Phase 1 End |
| 0x46a | 1011 | System Quiesce Start |
| 0x46b | 1011 | System Quiesce End |
| 0x46c | 1011 | Copying Memory Pages Start |
| 0x46d | 1011 | Copying Memory Pages End |
| 0x46e | 1011 | Live Dump Write Deferred Dump Data API started. |
| 0x46f | 10 | Live Dump Write Deferred Dump Data API ended. NT Status: %1. |
| 0x470 | 1011 | Write deferred dump data to file started. |
| 0x471 | 10 | Write deferred dump data to file ended. NT Status: %1. Total %2 bytes (Header|Primary|Secondary: %3|%4|%5 bytes). |
| 0x472 | 1011 | Live Dump Discard Deferred Dump Data API started. |
| 0x473 | 10 | Live Dump Discard Deferred Dump Data API ended. NT Status: %1. |
| 0x474 | 1011 | Sizing Workflow: Estimation. NT: %2 bytes (Minimum %1 bytes). Hypervisor: Primary %3 bytes. Secondary %4 bytes. |
| 0x475 | 1011 | Sizing Workflow: Allocation. NT: %1 bytes. Hypervisor: Primary %2 bytes. Secondary %3 bytes. |
| 0x476 | 1011 | Buffer Estimation Data |
| 0x477 | 1011 | Buffer Allocation Data |
| 0x478 | 1011 | Sizing Workflow: RemovePages Callbacks started. |
| 0x479 | 1011 | Sizing Workflow: RemovePages Callbacks ended. |
| 0x47a | 1011 | Sizing Workflow: RemovePages Callback %1 started. |
| 0x47b | 1011 | Sizing Workflow: RemovePages Callback %1 ended. |
| 0x47c | 1011 | Sizing Workflow: RemovePages Callback %1 failed. NT Status: %2. |
| 0x47d | 1011 | Remove Pages Callbacks |
| 0x47e | 1011 | Live Dump request aborted due to memory pressure on system |
| 0x47f | 1011 | Microsoft-Windows-Kernel-LiveDump/Operational |
| 0x480 | 10 | Sizing workflow: %1 pages estimated to be allocated and %2 pages allocated. Limit dump file size: %3. Dump file size limit: %4 bytes. Dump file size limit reached: %5. |
| 0x481 | 10 | Sizing Workflow: Estimation. NT: %2 bytes (Minimum %1 bytes). Hypervisor: Primary %3 bytes. Secondary %4 bytes. SecureKernel: %5 bytes. MemoryEstimationDuration: %6ms. SystemQuiescedDuration: %7ms. EndMirroringPhasesDuration: %8ms. TotalMirrorPhysicalMemoryCallbackDuration: %9ms. TotalMirrorPhysicalMemoryCallbackBytes: %10 bytes. HvlCalculateLiveDumpSizeDuration: %11ms. |
| 0x482 | 1011 | Sizing Workflow: Allocation. NT: %1 bytes. Hypervisor: Primary %2 bytes. Secondary %3 bytes. SecureKernel: %4 bytes. AllocateDumpBuffersDuration: %5ms. AllocateExtraBuffersDuration: %6ms. HvlPrepareLivedumpDescriptorDuration: %7ms. |
| 0x483 | 1011 | Sizing Workflow: Query Hvl for dump size failed. NT Status: %1. |
| 0x484 | 10 | Sizing Workflow: Open VM memory partition failed. Buffer allocation scheme: %1. NT Status: %2 |
| 0x485 | 10 | Sizing Workflow: Buffer allocation from the VM memory partition failed. Buffer allocation scheme: %1. NT Status: %2 |
| 0x486 | 1011 | Sizing Workflow: Capture processor context when the system is quiesced. Duration: %1ms. |
| 0x487 | 1011 | Sizing Workflow: Mark required dump data when system is quiesced. Duration: %1ms. |
| 0x488 | 1011 | Sizing Workflow: Mark important dump data when system is quiesced. Duration: %1ms. |
| 0x489 | 1011 | Sizing Workflow: Populate bitmap for dump when system is quiesced. PopulateBitmapForDumpDuration: %1ms. RemoveSystemCacheFromDumpDuration %2ms. |
| 0x48a | 1011 | Capture Pages Workflow: Capture processor context when the system is quiesced. Duration: %1ms. |
| 0x48b | 1011 | Capture Pages Workflow: Mark required dump data when system is quiesced. Duration: %1ms. |
| 0x48c | 1011 | Capture Pages Workflow: Mark important dump data when system is quiesced. Duration: %1ms. |
| 0x48d | 1011 | Capture Pages Workflow: Populate bitmap for dump when system is quiesced. PopulateBitmapForDumpDuration: %1ms. RemoveSystemCacheFromDumpDuration %2ms. |
| 0x48e | 10 | Capture Pages Workflow: Collect Hvl dump when system is quiesced. Duration: %1ms. |
| 0x48f | 10 | Capture Pages Workflow: Generate Ipt secondary data when system is quiesced. Duration: %1ms. |
| 0x490 | 10 | Capture Pages Workflow: Initiate state change to copy contents of marked pages when system is quiesced. Duration: %1ms. |
| 0x491 | 10 | Capture Processor Context |
| 0x492 | 10 | Mark Required Dump Data |
| 0x493 | 10 | Mark Important DumpData |
| 0x494 | 10 | Populate Bitmap For Dump |
| 0x495 | 10 | Hvl Collect LiveDump |
| 0x496 | 10 | Generate Ipt Secondary Data |
| 0x497 | 10 | Dump Data Buffering |
| 0x498 | 10 | Sizing Workflow: Corral processors to quiesce the system. CorralDuration: %1ms. DisableInterruptsDuration: %2ms. SaveSupervisorStateDuration: %3ms. SuspendClockTimerDuration: %4ms. |
| 0x499 | 10 | Capture Pages Workflow: Corral processors to quiesce the system. CorralDuration: %1ms. DisableInterruptsDuration: %2ms. SaveSupervisorStateDuration: %3ms. SuspendClockTimerDuration: %4ms. |
| 0x49a | 10 | Sizing Workflow: Uncorral processors to quiesce the system. UncorralDuration: %1ms. EnableInterruptsDuration: %2ms. RestoreSupervisorStateDuration: %3ms. ResumeClockTimerDuration: %4ms. |
| 0x49b | 10 | Capture Pages Workflow: Uncorral processors to quiesce the system. UncorralDuration: %1ms. EnableInterruptsDuration: %2ms. RestoreSupervisorStateDuration: %3ms. ResumeClockTimerDuration: %4ms. |
| 0x49c | 10 | Capture Pages Workflow: Capture memory pages. MemoryCaptureDuration: %1ms. SystemQuiescedDuration: %2ms. EndMirroringPhasesDuration: %3ms. TotalMirrorPhysicalMemoryCallbackDuration: %4ms. TotalMirrorPhysicalMemoryCallbackBytes: %5 bytes. HvlCollectLivedumpDuration: %6ms. DumpDataBufferingDuration: %7ms. |
| 0x49d | 10 | Corral Processors |
| 0x49e | 10 | Uncorral Processors |
| 0x49f | 10 | Capture Memory Pages |
| 0x4a0 | 10 | Sizing Workflow: MmDuplicateMemory failed. NT Status: %1. MirrorInProgress: %2. |
| 0x4a1 | 10 | Capture Pages Workflow: MmDuplicateMemory failed. NT Status: %1. MirrorInProgress: %2. |
| 0x4a2 | 10 | MmDuplicateMemory Failure |
| 0x4b0 | 1011 | Windows has started processing the volume mount request. Volume GUID: %1 Volume Name: %3 |
| 0x4b1 | 1011 | The volume has been successfully mounted. Volume GUID: %1 Volume Name: %3 |
| 0x4b2 | 1011 | Windows failed to mount the volume. Status: %4 Volume GUID: %1 Volume Name: %3 |
| 0x4b3 | 1011 | Microsoft-Windows-Kernel-IO |
| 0x4b4 | 1011 | Microsoft-Windows-Kernel-IO/Operational |
| 0x4b5 | 1011 | Windows is configured to block legacy file system filters. Filter name: %2 |
| 0x4b6 | 1011 | Legacy file system filters cannot attach to byte addressable volumes. Filter name: %2 Volume name: %4 |
| 0x4b7 | 1011 | Dumps are disabled on the machine since there was an error enabling dump encryption: %1. See http://go.microsoft.com/fwlink/?LinkId=824149 for more information on dump encryption |
| 0x4b8 | 1011 | An internal error occurred |
| 0x4b9 | 1011 | Public Key or Thumbprint registry missing |
| 0x4ba | 1011 | Invalid Public Key |
| 0x4bb | 1011 | Unsupported Public Key Size |
| 0x514 | 1011 | Microsoft-Windows-Kernel-Audit-API-Calls |
| 0x578 | 1011 | Microsoft-Windows-Audit-CVE |
| 0x5dc | 1011 | Microsoft-Windows-User-Diagnostic |
| 0x640 | 1011 | Microsoft-Windows-Heap-Snapshot |
| 0x6a4 | 1011 | Microsoft-Windows-Threat-Intelligence |
| 0x708 | 1011 | Microsoft-Windows-Security-LessPrivilegedAppContainer/Operational |
| 0x709 | 1011 | Microsoft-Windows-Security-LessPrivilegedAppContainer |
| 0x70a | 1011 | Access to the a resource has been denied for a less privileged app container at %1 (StackHash: %2). |
| 0x76c | 1011 | Microsoft-Windows-Security-Mitigations |
| 0x76d | 1011 | Kernel Mode |
| 0x76e | 1011 | User Mode |
| 0x76f | 1011 | Process '%2' (PID %5) would have been blocked from generating dynamic code. |
| 0x770 | 1011 | Process '%2' (PID %5) was blocked from generating dynamic code. |
| 0x771 | 1011 | Process '%2' (PID %5) would have been blocked from creating a child process '%14' with command line '%16'. |
| 0x772 | 1011 | Process '%2' (PID %5) was blocked from creating a child process '%14' with command line '%16'. |
| 0x773 | 1011 | Process '%2' (PID %5) would have been blocked from loading the low-integrity binary '%14'. |
| 0x774 | 1011 | Process '%2' (PID %5) was blocked from loading the low-integrity binary '%14'. |
| 0x775 | 1011 | Process '%2' (PID %5) would have been blocking from loading a binary from a remote share. |
| 0x776 | 1011 | Process '%2' (PID %5) was blocked from loading a binary from a remote share. |
| 0x777 | 1011 | Process '%2' (PID %5) would have been blocked from making system calls to Win32k.sys. |
| 0x778 | 1011 | Process '%2' (PID %5) was blocked from making system calls to Win32k.sys. |
| 0x779 | 1011 | Process '%2' (PID %5) would have been blocked from loading the non-Microsoft-signed binary '%16'. |
| 0x77a | 1011 | Process '%2' (PID %5) was blocked from loading the non-Microsoft-signed binary '%16'. |
| 0x77b | 1011 | Process '%2' (PID %3) would have been blocked from accessing the Export Address Table for module '%8'. |
| 0x77c | 1011 | Process '%2' (PID %3) was blocked from accessing the Export Address Table for module '%8'. |
| 0x77d | 1011 | Process '%2' (PID %3) would have been blocked from accessing the Import Address Table for API '%10'. |
| 0x77e | 1011 | Process '%2' (PID %3) was blocked from accessing the Import Address Table for API '%10'. |
| 0x77f | 1011 | Process '%2' (PID %3) would have been blocked from calling the API '%4' due to return-oriented programming (ROP) exploit indications. |
| 0x780 | 1011 | Process '%2' (PID %3) was blocked from calling the API '%4' due to return-oriented programming (ROP) exploit indications. |
| 0x781 | 1011 | Process '%2' (PID %5) has encountered a shadow stack return address mismatch. The process will be allowed to continue execution. Return instruction executed from module '%12'. Attempting to return to module '%14'. |
| 0x782 | 1011 | Process '%2' (PID %5) has encountered a shadow stack return address mismatch. The process will be terminated. Return instruction executed from module '%12'. Attempting to return to module '%14'. |
| 0x783 | 1011 | Process '%2' (PID %5) would have been blocked from setting context due to instruction pointer validation failure when user-mode shadow stack is enabled. |
| 0x784 | 1011 | Process '%2' (PID %5) was blocked from setting context due to instruction pointer validation failure when user-mode shadow stack is enabled. |
| 0x785 | 1011 | Process '%2' (PID %5) has encountered a shadow stack return address mismatch. The process will be allowed to continue execution. Process shadow stack strict mode: %15 Return instruction executed from module '%12'. Attempting to return to module '%14'. |
| 0x786 | 1011 | Process '%2' (PID %5) has encountered a shadow stack return address mismatch. The process will be terminated. Process shadow stack strict mode: %15 Return instruction executed from module '%12'. Attempting to return to module '%14'. |
| 0x787 | 1011 | Process '%2' (PID %5) would have been blocked from loading an image binary due to the binary not being compatible with shadow stacks and/or missing exception handling continuation data. Process requires binaries to also contain exception handling continuation data: %15 Binary path: %12 Binary compatible with shadow stacks: %13 Binary contains exception handling continuation data: %14 |
| 0x788 | 1011 | Process '%2' (PID %5) was blocked from loading an image binary due to the binary not being compatible with shadow stacks and/or missing exception handling continuation data. Process requires binaries to also contain exception handling continuation data: %15 Binary path: %12 Binary compatible with shadow stacks: %13 Binary contains exception handling continuation data: %14 |
| 0x789 | 1011 | Process '%2' (PID %5) would have been blocked from following an untrusted redirection: Binary path: %2 Arguments: %4 Redirection Type: %11 Operation Path: %13 Impersonating: %14 |
| 0x78a | 1011 | Process '%2' (PID %5) was blocked from following an untrusted redirection: Binary path: %2 Arguments: %4 Redirection Type: %11 Operation Path: %13 Impersonating: %14 |
| 0x78b | 1011 | Process '%2' (PID %5) would have been blocked from setting context due to instruction pointer validation failure when user-mode shadow stack is enabled. Process set context validation strict mode: %13 Set context type: %14 Set context target module '%12'. |
| 0x78c | 1011 | Process '%2' (PID %5) was blocked from setting context due to instruction pointer validation failure when user-mode shadow stack is enabled. Process set context validation strict mode: %13 Set context type: %14 Set context target module '%12'. |
| 0x78d | 1011 | Exception handling unwind |
| 0x78e | 1011 | Context resumption without unwind semantics |
| 0x78f | 1011 | Longjump unwind |
| 0x790 | 1011 | Set thread context |
| 0x791 | 1011 | Unknown redirection type |
| 0x792 | 1011 | NTFS mount point |
| 0x793 | 1011 | NTFS symlink |
| 0x794 | 10 | Process '%2' (PID %5) would have been blocked from making the NtFsControlFile system call. |
| 0x795 | 10 | Process '%2' (PID %5) was blocked from making the NtFsControlFile system call. |
| 0x7d0 | 10 | Microsoft-Windows-Security-Adminless/Operational |
| 0x7d1 | 10 | Microsoft-Windows-Security-Adminless |
| 0x7d2 | 10 | Access to a resource would have been denied if run with the adminless restriction at %1 (StackHash: %2). |
| 0x9c4 | 1011 | {Remote Registy Service} Access Denied to key: %2 under parent key: %4 as the parent is mentioned under AllowedExactPaths and hence subkey cannot be accessed. |
| 0x1000001 | 10 | The system time has changed to %1 from %2. Change Reason: %3. Process: '%4' (PID %5). |
| 0x1000002 | 1011 | License policy-cache corruption detected. |
| 0x1000003 | 1011 | License policy-cache corruption has been fixed. |
| 0x1000004 | 1011 | License policy-cache has expired because it was not updated within expected duration. |
| 0x1000005 | 1011 | {Registry Hive Recovered} Registry hive (file): '%3' was corrupted and it has been recovered. Some data might have been lost. |
| 0x1000006 | 1011 | An I/O operation initiated by the Registry failed unrecoverably.The Registry could not flush hive (file): '%3'. |
| 0x100000b | 1011 | TxR init phase for hive %2 (TM: %3, RM: %4) finished with result=%5 (Internal code=%6). |
| 0x100000c | 1011 | The operating system started at system time %7. |
| 0x100000d | 1011 | The operating system is shutting down at system time %1. |
| 0x100000f | 1011 | Hive %2 was reorganized with a starting size of %3 bytes and an ending size of %4 bytes. |
| 0x1000010 | 1011 | The access history in hive %2 was cleared updating %3 keys and creating %4 modified pages. |
| 0x1000012 | 10 | The operating system is starting after soft restart. |
| 0x1000014 | 1011 | The leap second configuration has been updated. Reason: %1 Leap seconds enabled: %2 New leap second count: %3 Old leap second count: %4 |
| 0x1000015 | 1011 | Failed to update leap second data from the registry. Reason: %1 |
| 0x1000016 | 1011 | The time zone bias has changed to %1 from %2. |
| 0x1000018 | 1011 | The time zone information was refreshed with exit reason %1. Current time zone bias is %2. |
| 0x500000a | 1011 | Error status code %1 returned when %3 attempted to load dependency %2. |
| 0x500000b | 1011 | 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. |
| 0x500000c | 1011 | 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. |
| 0x9000032 | 1011 | Access to %1 is monitored by policy rule %2. |
| 0x9000361 | 1011 | Access to %1 has been restricted by your Administrator by the default software restriction policy level. |
| 0x9000362 | 1011 | Access to %1 has been restricted by your Administrator by location with policy rule %2 placed on path %3. |
| 0x9000363 | 1011 | Access to %1 has been restricted by your Administrator by software publisher policy. |
| 0x9000364 | 1011 | Access to %1 has been restricted by your Administrator by policy rule %2. |
| 0x9000372 | 1011 | Access to %1 has been restricted by your Administrator by policy rule %2. |
| 0xc00000a | 1011 | 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. |
| 0xc000010 | 1011 | Windows failed to resume from hibernate with error status %1. |
| 0xc000011 | 1011 | The boot manager multi OS selection screen was displayed. |
| 0xc000012 | 1011 | There are %1 boot options on this system. |
| 0xc000013 | 1011 | There are %1 boot tool options on this system. |
| 0xc000014 | 1011 | The last shutdown's success status was %1. The last boot's success status was %2. |
| 0xc000015 | 1011 | The OS loader advanced options menu was displayed and the user selected option %1. |
| 0xc000016 | 1011 | The OS loader edit options menu was displayed. |
| 0xc000017 | 1011 | The Windows key was pressed during boot. |
| 0xc000018 | 1011 | The F8 key was pressed during boot. |
| 0xc000019 | 1011 | The boot menu policy was %1. |
| 0xc00001a | 1011 | A one-time boot sequence was used during this boot. |
| 0xc00001b | 1011 | The boot type was %1. |
| 0xc00001d | 1011 | Windows failed fast startup with error status %1. |
| 0xc00001e | 1011 | The firmware reported boot metrics. |
| 0xc000020 | 1011 | The bootmgr spent %1 ms waiting for user input. |
| 0xc000073 | 1011 | Soft reboot cancellation started: %1 |
| 0xc000074 | 1011 | Soft reboot cancellation finished: %1. |
| 0xc00007c | 1011 | The virtualization-based security enablement policy check at phase %1 failed with status: %2 |
| 0xc000099 | 1011 | Virtualization-based security (policies: %3) is %2. |
| 0xc00009c | 1011 | Virtualization-based security (policies: %3) is %2 with status: %1 |
| 0xc0000d6 | 1011 | Soft reboot prepare started (complete requested: %1). |
| 0xc0000d7 | 1011 | Soft reboot prepare finished: %1. |
| 0xc0000d8 | 1011 | Soft reboot complete prepare started. |
| 0xc0000d9 | 1011 | Soft reboot complete prepare finished: %1. |
| 0xc0000da | 1011 | Soft reboot call to %1 failed: %2 (checkpoint: %3). |
| 0xc0000dd | 1011 | System drivers need update to support VBS launch. |
| 0xc0000de | 1011 | SMM configuration failed validation. Reason: %1 |
| 0xc0000ee | 10 | EFI time zone bias: %1. Daylight flags: %2 |
| 0xc000112 | 1011 | Bootmgr Security Version Number check failed. Svn Value: %1, Previous SVN Value: %2. |
| 0xf000009 | 10 | App %1 was terminated with error %2 because of an issue with Windows binary %3. This could be because the binary is unsigned, contains an untrusted signature, or has been corrupted or tampered with. Refresh your PC to fix this issue. |
| 0x10000001 | 10 | Structured State |
| 0x10000002 | 10 | Unstructured Reset |
| 0x10000003 | 10 | Out Of Memory |
| 0x10000004 | 10 | Apiset Error |
| 0x10000005 | 10 | WinRT |
| 0x10000006 | 10 | Low-level Data Store Error |
| 0x1000000a | 10 | Failure to load the application settings for package %1. Error Code: %2 |
| 0x1000000b | 10 | Failure to read an application setting for package %1. Error Code: %2 |
| 0x1000000c | 10 | Failure to write an application setting for package %1. Error Code: %2 |
| 0x1000000d | 10 | Failure to instantiate storage folder %1 for package %2 with Error Code: %3 |
| 0x10000014 | 10 | Triggered repair because operation %1 against package %2 hit error %3. |
| 0x10000015 | 10 | Repair for operation %1 against package %2 with error %3 returned Error Code: %4 |
| 0x10000016 | 10 | Folder path %1 failed access check: Error Code: %2 |
| 0x10000017 | 10 | Triggered repair of state locations because operation %1 against package %2 hit error %3. |
| 0x10000018 | 10 | Repair of state locations for operation %1 against package %2 with error %3 returned Error Code: %4 |
| 0x10000021 | 1011 | Verbose context events |
| 0x10000022 | 1011 | Scenario trigger events |
| 0x10000034 | 1011 | SQM |
| 0x11000005 | 1011 | Time |
| 0x15000005 | 1011 | Deprecated dlls |
| 0x15000006 | 1011 | Fatal user callback exception |
| 0x15000007 | 1011 | A dll failed to load. |
| 0x15000008 | 1011 | Launch 16bit application |
| 0x15000009 | 1011 | Windows component on demand. |
| 0x1500000a | 1011 | The Loader encountered a fatal error. |
| 0x16000031 | 1011 | Response Time |
| 0x18000005 | 1011 | Deprecated COM interfaces |
| 0x1f000001 | 10 | Process |
| 0x1f000002 | 10 | AppContainer |
| 0x1f000003 | 10 | DesktopAppXProcess |
| 0x1f000004 | 10 | DesktopAppXContainer |
| 0x3000000a | 1011 | Scenario start enables context providers to the WDI context logger. |
| 0x3000000b | 1011 | Scenario end disables context providers to the WDI context logger. |
| 0x3000000c | 1011 | When a scenario has remained in-flight beyond the maximum time window it is automatically terminated by the SEM. |
| 0x3000000d | 1011 | A scenario start attempt failed in the SEM. |
| 0x3000000e | 1011 | A scenario end attempt failed in the SEM. |
| 0x3000000f | 1011 | The SEM received a request to start a new scenario, but the maximum number of scenarios were already in-flight. |
| 0x30000010 | 1011 | There is an invalid configuration parameter in the SEM registry namespace. |
| 0x30000011 | 1011 | The SEM is configured with more scenarios than the maximum allowed count. |
| 0x30000012 | 1011 | The SEM is configured with a scenario with too many context providers. |
| 0x30000013 | 1011 | The SEM is configured with a scenario that has too many end events. |
| 0x30000014 | 1011 | The number of providers specified across all scenarios is above the maximum allowed amount. |
| 0x31000000 | 1011 | Info |
| 0x32000001 | 1011 | Start |
| 0x32000002 | 1011 | Stop |
| 0x3a00001e | 1011 | Start |
| 0x3a00001f | 1011 | Invoke callback function |
| 0x3a000020 | 1011 | Disable live cache |
| 0x3a000021 | 1011 | Update resource cache manifest |
| 0x3a000022 | 1011 | Build resource cache |
| 0x3a000023 | 1011 | Start |
| 0x3a000024 | 1011 | End |
| 0x50000002 | 1011 | Error |
| 0x50000003 | 1011 | Warning |
| 0x50000004 | 1011 | Information |
| 0x55000001 | 1011 | Critical |
| 0x5b000005 | 1011 | Verbose |
| 0x70000009 | 1011 | SEM Scenario Lifecycle |
| 0x7000000a | 1011 | SEM Initialization |
| 0x73000001 | 1011 | This group of events tracks the performance of mounting hives from existing files. |
| 0x73000002 | 1011 | This group of events tracks the performance of unloading hives. |
| 0x73000003 | 1011 | This group of events tracks the performance of flushing hives. |
| 0x73000004 | 1011 | This group of events tracks the performance of registry shutdown. |
| 0x73000005 | 1011 | This group of events tracks the performance of loading hives. |
| 0x73000006 | 1011 | This group of events tracks the performance of restoring hives. |
| 0x73000007 | 1011 | This group of events tracks the performance of exporting hives. |
| 0x7a00001e | 1011 | MUI NotifyUILanguageChange task |
| 0x7a00001f | 1011 | MUI resource cache builder |
| 0x90000001 | 1011 | Microsoft-Windows-Kernel-WDI |
| 0x90000002 | 1011 | Microsoft-Windows-Kernel-WDI/Analytic |
| 0x90000003 | 1011 | Microsoft-Windows-Kernel-WDI/Debug |
| 0x90000004 | 1011 | Microsoft-Windows-Kernel-WDI/Operational |
| 0x90000005 | 10 | Microsoft-Windows-AppModel-State |
| 0x90000006 | 10 | Microsoft-Windows-AppModel-State/Debug |
| 0x90000007 | 10 | Microsoft-Windows-AppModel-State/Diagnostic |
| 0x91000001 | 1011 | Microsoft-Windows-Kernel-General |
| 0x91000002 | 1011 | System |
| 0x92000001 | 1011 | Microsoft-Windows-Kernel-Process |
| 0x93000001 | 1011 | Microsoft-Windows-Kernel-Registry |
| 0x94000001 | 1011 | Microsoft-Windows-Kernel-Acpi |
| 0x95000001 | 1011 | Microsoft-Windows-User-Loader |
| 0x95000002 | 1011 | Application |
| 0x96000001 | 1011 | Microsoft-Windows-Kernel-BootDiagnostics |
| 0x97000001 | 1011 | Microsoft-Windows-UAC |
| 0x97000002 | 1011 | Microsoft-Windows-UAC/Operational |
| 0x98000001 | 1011 | Microsoft-Windows-COM |
| 0x99000001 | 1011 | Microsoft-Windows-SoftwareRestrictionPolicies |
| 0x9a000001 | 1011 | Microsoft-Windows-MUI |
| 0x9a000002 | 1011 | Microsoft-Windows-MUI/Operational |
| 0x9a000003 | 1011 | Microsoft-Windows-MUI/Admin |
| 0x9a000004 | 1011 | Microsoft-Windows-MUI/Analytic |
| 0x9a000005 | 1011 | Microsoft-Windows-MUI/Debug |
| 0x9d000001 | 10 | Microsoft-Windows-PCI |
| 0x9e000001 | 10 | Microsoft-Windows-Kernel-ShimEngine |
| 0x9e000002 | 10 | Microsoft-Windows-Kernel-ShimEngine/Operational |
| 0x9f000001 | 10 | Microsoft-Windows-AppModel-Runtime |
| 0x9f000002 | 10 | Microsoft-Windows-AppModel-Runtime/Analytic |
| 0xb0000001 | 10 | Error while deleting file: %1. Error Code: %2 |
| 0xb0000002 | 10 | Error while deleting directory: %1. Error Code: %2 |
| 0xb0000003 | 10 | Error while allocating memory |
| 0xb0000004 | 10 | ApiSet Function: %1 returned with Error Code: %2 |
| 0xb0000005 | 10 | Low-level data store access error. Function: %1 returned with Error Code: %2 |
| 0xb0000006 | 10 | Cleanup of temporary state has been skipped due to low disk usage. |
| 0xb0000007 | 10 | Cleanup of temporary state has completed. |
| 0xb0000008 | 10 | Cleanup of temporary state was unable to enumerate the user profiles. Object: %1, Error Code: %2. |
| 0xb0000009 | 10 | Cleanup of temporary state has aborted unexpectedly. |
| 0xb000000e | 10 | Need to update state locations of package %1 for user %2 because the schema is not found. Error Code: %3 |
| 0xb000000f | 10 | Need to update state locations of package %1 for user %2 because the package is not found. Error Code: %3 |
| 0xb0000010 | 10 | Need to update state locations of package %1 for user %2 because the package full name has changed. Error Code: %3 |
| 0xb0000011 | 10 | Need to update state locations of package %1 for user %2 because the schema version has changed. Error Code: %3 |
| 0xb0000012 | 10 | Succeeded to fix state locations for package %1. |
| 0xb0000013 | 10 | Failure to fix state locations for package %1. Error Code: %2 |
| 0xb0000020 | 1011 | The Scenario Event Mapper started a scenario for provider %1 (event ID %2) with %4 context providers. The context logger dropped event count was %3. |
| 0xb0000021 | 1011 | The Scenario Event Mapper stopped a scenario for provider %1 (event ID %2) with %4 context providers. The context logger dropped event count was %3. |
| 0xb0000022 | 1011 | An in-flight scenario from provider %1 (event ID %2) timed out and was stopped automatically by the Scenario Event Mapper. |
| 0xb0000023 | 1011 | The Scenario Event Mapper was unable to start a new scenario for provider %1 (event ID %2) because the maximum number of scenarios are already in flight. |
| 0xb0000024 | 1011 | The Scenario Event Mapper was unable to start a scenario for provider %1 (event ID %2). The error code was %3. |
| 0xb0000025 | 1011 | The Scenario Event Mapper was unable to stop a scenario for provider %1 (event ID %2). The error code was %3. |
| 0xb0000026 | 1011 | The Scenario Event Mapper is configured with more than the maximum number of scenarios. The scenario for provider %1 (event ID %2) will be ignored. |
| 0xb0000027 | 1011 | The Scenario Event Mapper is configured with more than the maximum number of context providers for the scenario with provider %1 (event ID %2). The scenario will be ignored. |
| 0xb0000028 | 1011 | The Scenario Event Mapper is configured with more than the maximum number of end events for the scenario with provider %1 (event ID %2). The scenario will be ignored. |
| 0xb0000029 | 1011 | The Scenario Event Mapper is configured with more than the maximum number of providers. The provider %1 will be ignored. |
| 0xb000002a | 1011 | The Scenario Event Mapper is configured with an unsupported scenario. The scenario for provider %1 (event ID %2) encountered error code %3 and will be ignored. |
| 0xb1000001 | 1011 | The system time has changed to %1 from %2. |
| 0xb1010001 | 1011 | The system time has changed to %1 from %2. Change Reason: %3. |
| 0xb2000001 | 1011 | Process %1 started at time %2 by parent %3 running in session %4 with name %5. |
| 0xb2000002 | 1011 | Process %1 (which started at time %3) stopped at time %4 with exit code %5. |
| 0xb2000003 | 1011 | Thread %2 (in Process %1) started. |
| 0xb2000004 | 1011 | Thread %2 (in Process %1) stopped. |
| 0xb2000005 | 1011 | Process %3 had an image loaded with name %7. |
| 0xb2000006 | 1011 | Process %3 had an image unloaded with name %7. |
| 0xb2000007 | 1011 | Base CPU priority of thread %2 in process %1 was changed from %3 to %4. |
| 0xb2000008 | 1011 | CPU priority of thread %2 in process %1 was changed from %3 to %4. |
| 0xb2000009 | 1011 | Page priority of thread %2 in process %1 was changed from %3 to %4. |
| 0xb200000a | 1011 | I/O priority of thread %2 in process %1 was changed from %3 to %4. |
| 0xb200000b | 1011 | Execution of the process %1 has been suspended. |
| 0xb200000c | 1011 | Execution of the process %1 has been resumed. |
| 0xb200000d | 1011 | Job %1 started with status code %2. |
| 0xb200000e | 1011 | Job %1 terminated with status code %2. |
| 0xb200000f | 1011 | Enumerated process %1 had started at time %2 by parent %3 running in session %4 with name %6. |
| 0xb2010001 | 1011 | Process %1 started at time %2 by parent %3 running in session %4 with name %6. |
| 0xb2010002 | 1011 | Process %1 (which started at time %2) stopped at time %3 with exit code %4. |
| 0xb201000f | 1011 | Enumerated process %1 had started at time %3 by parent %4 running in session %6 with name %11. |
| 0xb2020001 | 1011 | Process %1 started at time %2 by parent %3 running in session %4 with name %6. |
| 0xb2030001 | 1011 | Process %1 started at time %3 by parent %4 running in session %6 with name %11. |
| 0xb4000001 | 1011 | A memory range descriptor has been marked as reserved. |
| 0xb4000002 | 1011 | Unexpected GPE event was fired on GPE bits that should be disabled. |
| 0xb4000003 | 1011 | A temperature change notification (Notify(thermal_zone, 0x80)) for ACPI thermal zone %2 has been received. _TMP = %3K _PSV = %4K _AC0 = %5K _AC1 = %6K _AC2 = %7K _AC3 = %8K _AC4 = %9K _AC5 = %10K _AC6 = %11K _AC7 = %12K _AC8 = %13K _AC9 = %14K _HOT = %15K _CRT = %16K |
| 0xb4000004 | 1011 | A trip point change notification (Notify(thermal_zone, 0x81)) for ACPI thermal zone %2 has been received. _TMP = %3K _PSV = %4K _AC0 = %5K _AC1 = %6K _AC2 = %7K _AC3 = %8K _AC4 = %9K _AC5 = %10K _AC6 = %11K _AC7 = %12K _AC8 = %13K _AC9 = %14K _HOT = %15K _CRT = %16K |
| 0xb4000005 | 1011 | The active cooling device %6 has been turned %8. Thermal zone device instance: %2 Active cooling package: _AC%3 Namespace object: _AL%4 |
| 0xb4000006 | 1011 | The active cooling device %6 has been turned %7. Thermal zone device instance: %2 Active cooling package: _AC%3 Namespace object: _AL%4 |
| 0xb4000007 | 1011 | ACPI method %2 evaluation has %3. |
| 0xb4000008 | 1011 | The active cooling device %2 has been turned %3. |
| 0xb4000009 | 1011 | The passive cooling device %2 throttle has changed to %3 percent. |
| 0xb400000a | 1011 | The device %2 has the following cooling state. Active cooling: %3 Passive cooling: %4 percent |
| 0xb4000014 | 1011 | ACPI device %2 is undergoing %3. Status %4. |
| 0xb4000015 | 1011 | ACPI device OverRide - %1 |
| 0xb4000016 | 1011 | Error occured while interpreting AML code: scope %1, object %2. Status %3. |
| 0xb4000017 | 1011 | ACPI method %2 has high frequency %3. |
| 0xb5000001 | 1011 | Deprecated module %1. |
| 0xb5000002 | 1011 | Process %2 encountered a fatal user callback exception. |
| 0xb5000004 | 1011 | The process launches a 16 bit process. |
| 0xb5000005 | 1011 | Windows component on demand %1. |
| 0xb5000006 | 1011 | The Loader encountered a fatal error while loading a thread from process image name %1. |
| 0xb5000007 | 1011 | A fatal error occured during initalization of %1. |
| 0xb5000009 | 1011 | The Loader encountered a fatal error running process image name %1. |
| 0xb7000001 | 1011 | The process failed to handle ERROR_ELEVATION_REQUIRED during the creation of a child process. |
| 0xb8000001 | 1011 | Deprecated COM CLSID %1. |
| 0xba0007d0 | 1011 | MUI notify operation failed with status code %1. No callbacks were invoked. |
| 0xba0007d1 | 1011 | MUI Callback failed for file %1 because it can not be loaded. To correct this error, replace this file or repair your Windows installation. |
| 0xba0007d2 | 1011 | 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. |
| 0xba0007d3 | 1011 | 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. |
| 0xba0007d4 | 1011 | MUI Callback file %1 cannot be found. To correct this error, repair the registry or copy the file to the specified location. |
| 0xba0007d6 | 1011 | Wow redirection could not be disabled. New resource cache will not be built. |
| 0xba0007d7 | 1011 | Resource cache cannot be opened in writable mode. New resource cache will not be built. |
| 0xba0007d8 | 1011 | Live resource cache could not be disabled. |
| 0xba0007d9 | 1011 | Unable to retrieve language settings from MUI API. New resource cache will not be built. |
| 0xba0007da | 1011 | 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. |
| 0xba0007db | 1011 | Changes made to resource cache manifest cannot be written to disk. New resource cache will not be built. |
| 0xba0007dc | 1011 | New resource cache could not be built due to internal error: %1. |
| 0xba0007dd | 1011 | Newly built resource cache could not be installed on the system. |
| 0xba0007de | 1011 | Resource cache manifest could not be created. New resource cache will not be built. |
| 0xba000bb8 | 1011 | 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 |
| 0xba000bba | 1011 | MUI notification callback API %2 in %1 returned with code %3. |
| 0xba000bbb | 1011 | MUI resource cache builder has been called with the following parameters: %1. |
| 0xba000bbc | 1011 | MUI resource cache manifest entry for file %1 has been updated. Affinity: '%2', Sequence: %3, and Priority: %4 |
| 0xba000bbd | 1011 | Start: %1 |
| 0xba000bbe | 1011 | End: %1 |
| 0xba000bbf | 1011 | New resource cache built and installed on system. New cache index is %1, live cache index is %2 and config is set to %3. |
| 0xba000bc4 | 1011 | Resource file %1 will not be cached since it is not used frequently in the system. |
| 0xba000bc5 | 1011 | The system is constrained in RAM, total disk space or free disk space, so the MUI resource cache will not be maintained. |
| 0xba000fa0 | 1011 | Unable to parse configuration parameters. The configuration parameters will be ignored. |
| 0xbc00000b | 1011 | The time elapsed before Bootmgr, based on the TSC, is %1 ms. |
| 0xbc00001f | 1011 | Initialization of the firmware crypto hash provider resulted in status %1. |
| 0xbc000021 | 1011 | The firmware update capsule (%1) failed to load with status %2. |
| 0xbc000022 | 1011 | The PE/COFF image firmware update capsule (%1) failed to load with status %2. |
| 0xbc000023 | 1011 | The Efi UpdateCapsule failed to apply updates with status %1. |
| 0xbc000024 | 1011 | Firmware update supported status is %3. The BitLocker device flags are %1 and the PCR bitmap is %2. |
| 0xbc000025 | 1011 | The firmware update capsule (%1) code integrity check failed with status %2. |
| 0xbc000026 | 1011 | Windows failed to load the required system file %1 with error status %2. |
| 0xbc000027 | 1011 | Windows failed to load the system registry file %1 with error status %2. |
| 0xbc000028 | 1011 | Windows failed to initialize the ACPI with error status %1. |
| 0xbc000029 | 1011 | Windows failed to load with error status %1. |
| 0xbc00002a | 1011 | Windows failed to load image %2 imported from %1 with error status %3. |
| 0xbc00002b | 1011 | Windows failed to import %2 from image %1 with error status %3. |
| 0xbc00002c | 1011 | Windows failed to provision VSM Identity Key. Unsealing cached copy status: %1. New key generation status: %2. Measuring to PCR status: %3. Sealing and caching status: %4. |
| 0xbc00002d | 1011 | VSM Identity Key Provisioning. Unsealing cached copy status: %1. New key generation status: %2. Measuring to PCR status: %3. Sealing and caching status: %4. |
| 0xbc000031 | 1011 | Windows system integrity policy does not allow to load the required system file %1 with error status %2. |
| 0xbc000032 | 1011 | 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. Backup sealed blob used: %11. |
| 0xbc000033 | 1011 | 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. Backup sealed blob used: %11. |
| 0xbc000039 | 10 | Windows failed to provision the TPM Storage Root Key with error status:%1. |
| 0xbc00003a | 10 | Windows successfully provisioned the TPM Storage Root Key. This operation took %1 milliseconds. |
| 0xbc00003b | 1011 | Windows failed to provision TPM binding information with error status:%1. |
| 0xbc00003c | 1011 | NFIT ACPI table is not properly formed, and could not be parsed. |
| 0xbc00003e | 1011 | Previous error detected while attempting to execute Measured Launch Environment. TXT error code: %1. |
| 0xbc000049 | 1011 | Firmware provided SINIT ACM not used. %1 |
| 0xbc00004a | 1011 | Windows failed to provision DRTM-bound VSM Master Encryption Key . Using cached copy status: %1. New key generation status: %2. Sealing status: %3. UEFI keys provided to Secure Kernel status: %4. |
| 0xbc00004b | 1011 | Windows successfully provisioned DRTM-bound VSM Master Encryption Key. Using cached copy status: %1. New key generation status: %2. Sealing status: %3. UEFI keys provided to Secure Kernel status: %4. |
| 0xbc000051 | 1011 | Windows skipped provisioning the TPM Storage Root Key because the NoAutoProvision registry value was set. |
| 0xbc000088 | 1011 | Soft Restart failed to complete with status: %1 due to %2 outstanding unclaimed allocations |
| 0xbc00008b | 1011 | Soft Restart failed to restore memory partition %1 with status: %2 |
| 0xbc00008e | 1011 | Soft Restart failed to register with Soft Restart extension. The versions are not compatible. |
| 0xbc000092 | 1011 | Soft Restart failed to establish connection with secure load with status: %1 |
| 0xbc00009a | 1011 | Boot Policy Migration used an authenticated variable. Status: %1 |
| 0xbc00009b | 1011 | Boot Policy Migration used an unauthenticated variable. Status: %1 |
| 0xbc00009d | 1011 | Info: %1 Status: %2 |
| 0xbc00009e | 1011 | Error: %1 Status: %2 |
| 0xbc0000b5 | 1011 | Soft Restart driver failed to register itself as a filter with status: %1 |
| 0xbc0000c8 | 1011 | A command was submitted to the TPM. Command code: %1. Response code: %2. Elapsed time: %3ms. |
| 0xbc0000ca | 1011 | A command could not be submitted to the TPM. Command code: %1. Error code: %2. Elapsed time: %3ms. |
| 0xbc0000cc | 1011 | The TPM was found not to be useable for BitLocker. Flags: %1. |
| 0xbc0000cf | 1011 | Measured Boot library was initialized. Phase: %1, StatusCode: %2. |
| 0xbc0000d0 | 1011 | Measured Boot library encountered a failure and entered insecure state. InitState: %1, StatusCode: %2, Failure Address: %3, Reference Address: %4, Reason: %5. |
| 0xbc0000d1 | 1011 | DRTM Security Version Number check failed. SvnCounterId: %1, StatusCode: %2, Svn Value: %3, Previous SVN Value: %4. |
| 0xbc0000d2 | 1011 | Intel TXT SENTER time: %1 ms. |
| 0xbc0000d4 | 1011 | File modification detected after load: %1. |
| 0xbc0000d5 | 1011 | Registry modification detected after load: %1. |
| 0xbc0000db | 1011 | Intel TXT prepared. ACM date: %2/%1/%3. |
| 0xbc0000dc | 1011 | System Guard enabled but not supported. Reason: %1 |
| 0xbc0000e1 | 1011 | VBS is configured to disallow trustlets. |
| 0xbc0000e7 | 1011 | Boot menu timer canceled due to key press. |
| 0xbc0000eb | 1011 | Windows boot environment failed to initialize TPM device. StatusCode: %1, Position: %2. |
| 0xbc0000ec | 1011 | SMM isolation level decreased. Reason: %1 |
| 0xbc0000ed | 1011 | Hardware memory mirroring is not supported. MirrorStatus: %1 |
| 0xbc00010f | 1011 | TPRs are supported, TPR setup will be requested while attempting to execute Measured Launch Environment. |
| 0xbc000111 | 10 | BCD Option '%1' was not applied due to Secure Boot being enabled. |
| 0xbc000114 | 1011 | Windows boot manager revocation policy version %1 is applied. |
| 0xbc000115 | 1011 | Windows boot manager revocation policy version %1 was not found. It is recommended that it be redeployed. |
| 0xbc000123 | 1011 | Succeeded in updating the SBAT value in FW. |
| 0xbc000124 | 1011 | Failed to update the SBAT value in FW. |
| 0xbc010032 | 10 | Windows failed to provision VSM Master Encryption Key. Using cached copy status: %1. Primary Blob Unseal Status: %2. Backup Blob Unseal Status: %3. Kickback Backup Blob Unseal Status: %4. Backup Blob Validity Check Status: %5. Backup Blob Validity Check Result: %6. Kickback Backup Blob Validity Check Status: %7. Kickback Backup Blob Validity Check Result: %8. Primary Blob Reseal Status: %9. Backup Blob Reseal Status: %10. Kickback Backup Blob Reseal Status: %11. New key generation status: %12. Sealing status: %13. TPM PCR mask: %14. Tpm Counter validation status: %15. Tpm Counter creation status: %16. Backup sealed blob used: %17. Kickback Backup sealed blob cleaned up post upgrade status: %18. |
| 0xbc010033 | 10 | VSM Master Encryption Key Provisioning. Using cached copy status: %1. Primary Blob Unseal Status: %2. Backup Blob Unseal Status: %3. Kickback Backup Blob Unseal Status: %4. Backup Blob Validity Check Status: %5. Backup Blob Validity Check Result: %6. Kickback Backup Blob Validity Check Status: %7. Kickback Backup Blob Validity Check Result: %8. Primary Blob Reseal Status: %9. Backup Blob Reseal Status: %10. Kickback Backup Blob Reseal Status: %11. New key generation status: %12. Sealing status: %13. TPM PCR mask: %14. Tpm Counter validation status: %15. Tpm Counter creation status: %16. Backup sealed blob used: %17. Kickback Backup sealed blob cleaned up post upgrade status: %18. |
| 0xbe010003 | 10 | %3 shim(s) were applied to driver [%1]. Shim(s) source: %2. Shim GUID(s): %4. |
| 0xbe010004 | 10 | Flags [%4] were applied to device [%1] - class [%2]. Flags source: %3. |
| 0xbf000001 | 10 | Process %1 started at time %2 by parent %3 running as package %4 with executable %5 is application %6. |
| 0xbf000002 | 10 | %2: Cannot create the process for package %1 because an error was encountered. %3 |
| 0xbf000003 | 10 | %2: Cannot create the process for package %1 because an error was encountered while querying the fast cache. %3 |
| 0xbf000004 | 10 | %2: Cannot create the process for package %1 because an error was encountered while preparing the App credentials. %3 |
| 0xbf000005 | 10 | %2: Cannot create the process for package %1 because an error was encountered while checking the user-level package status. %3 |
| 0xbf000006 | 10 | %2: Cannot create the process for package %1 because an error was encountered while checking the machine-level package status. %3 |
| 0xbf000007 | 10 | %2: Cannot create the process for package %1 because an error was encountered while verifying the App credentials. %3 |
| 0xbf000008 | 10 | App %1 was terminated with error %2 because of an issue with application binary %3. This could be because the binary is unsigned, contains an untrusted signature, or has been corrupted or tampered with. Reinstall the application to fix this issue. |
| 0xbf00000b | 10 | App %1 prevented the load of generated binary %3 due to error %2. This could be because the binary is unsigned, contains an untrusted signature, or has been corrupted or tampered with. |
| 0xbf00000c | 10 | 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 | 10 | %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 | 10 | %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 | 10 | %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 | 10 | %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 | 10 | %2: Package runtime information %1 failed to load (processid=%3). |
| 0xbf000013 | 10 | Package runtime information %1 failed to load because exception %2 occurred. |
| 0xbf000014 | 10 | %2: Cannot create the process for package %1 because an error was encountered while loading the runtime information. %3 |
| 0xbf000015 | 10 | CreateAppContainerProfile failed for AppContainer %2 with error %1. |
| 0xbf000016 | 10 | DeleteAppContainerProfile failed for AppContainer %2 with error %1. |
| 0xbf000017 | 10 | UpdateAppContainerProfile failed for AppContainer %2 with error %1. |
| 0xbf000018 | 10 | CreateAppContainerProfile failed with error %1 because it was unable to create registry key %2. |
| 0xbf000019 | 10 | CreateAppContainerProfile failed with error %1 because it was unable to set security on registry key %2. |
| 0xbf00001a | 10 | AppContainer profile failed with error %1 because it was unable to delete registry key %2. |
| 0xbf00001b | 10 | CreateAppContainerProfile failed with error %1 because it was unable to create folder %2. |
| 0xbf00001c | 10 | CreateAppContainerProfile failed with error %1 because it was unable to set attributes on folder %2. |
| 0xbf00001d | 10 | CreateAppContainerProfile failed with error %1 because it was unable to verify the existence of registry key %2. |
| 0xbf00001e | 10 | CreateAppContainerProfile failed with error %1 because it was unable to verify the existence of folder %2. |
| 0xbf00001f | 10 | CreateAppContainerProfile failed with error %1 because it was unable to find the users local app data folder. |
| 0xbf000020 | 10 | AppContainer profile failed with error %1 because it was unable to delete folder %2 or its contents. |
| 0xbf000021 | 10 | AppContainer profile failed with error %1 because it was unable to look up the AppContainer name. |
| 0xbf000022 | 10 | AppContainer profile failed with error %1 because it was unable to look up the AppContainer display name. |
| 0xbf000023 | 10 | CreateAppContainerProfile failed with error %1 because it was unable to register with the firewall. |
| 0xbf000024 | 10 | DeleteAppContainerProfile failed with error %1 because it was unable to unregister with the firewall. |
| 0xbf000025 | 10 | App Container profile failed with error %1 because it was unable to register the AppContainer SID. |
| 0xbf000026 | 10 | DeleteAppContainerProfile failed with error %1 because it was unable to unregister the AppContainer SID. |
| 0xbf000027 | 10 | Successfully created AppContainer %1. |
| 0xbf000028 | 10 | AppContainer %1 was not created because it already exists. |
| 0xbf000029 | 10 | Successfully deleted AppContainer %1. |
| 0xbf00002a | 10 | Successfully updated AppContainer %1. |
| 0xbf00002b | 10 | %2: Package runtime information %1 is missing expected data (address=%4, size=%3, section=%5, processid=%6). Reinstall the package to fix this issue. |
| 0xbf00002c | 10 | %2: Application identity not accessible while loading package runtime information %1 (address=%4, size=%3, processid=%5). |
| 0xbf00002d | 10 | Failed with %1 while retrieving AppContainer %2 information during interaction with Restricted AppContainer. |
| 0xbf00002e | 10 | Failed with %1 while retrieving AppContainer information during interaction with Restricted AppContainer. |
| 0xbf00002f | 10 | Failed with %1 while retrieving AppContainer information. Call invalid from this process type. |
| 0xbf000030 | 10 | Failed to create shared context object for Restricted AppContainer %2 with %1. |
| 0xbf000031 | 10 | Failed to activate Restricted AppContainer %2 with %1. |
| 0xbf000032 | 10 | Creation of Restricted AppContainer %2 failed with %1 because an invalid capability was specified. |
| 0xbf000033 | 10 | Opening existing Restricted AppContainer %2 failed with %1 because the capabilities storage value could not be read. |
| 0xbf000034 | 10 | Failed to create the capabilities storage value for Restricted AppContainer %2 with %1. |
| 0xbf000035 | 10 | The package %1 requires validation. |
| 0xbf000036 | 10 | Modification was detected in package %1. |
| 0xbf000037 | 10 | Failed to terminate app with package %1. |
| 0xbf000038 | 10 | Validation of app with package %1 was successful. |
| 0xbf000039 | 10 | Failed with %1 to retrieve the trust state of the package %2 folder. |
| 0xbf00003a | 10 | App Integrity check failed with %1 while checking %2. |
| 0xbf00003b | 10 | App Integrity terminated an application. Integrity check for %2 returned %1. |
| 0xbf00003c | 10 | App Integrity check for %1 timed out. |
| 0xbf00003d | 10 | %2: Cannot create the process for package %1 because an error was encountered while performing the integrity check. %3 |
| 0xbf00003e | 10 | Deployment server integrity check of package %1 failed with %2. |
| 0xbf00003f | 10 | Failed with %1 retrieving AppModel Runtime group policy values. |
| 0xbf000040 | 10 | Failed with %1 validating AppModel Runtime group policy values. |
| 0xbf000041 | 10 | Failed with %1 retrieving AppModel Runtime status for package %2. |
| 0xbf000042 | 10 | Failed with %1 retrieving AppModel Runtime status for package %2 for user %3. |
| 0xbf000043 | 10 | Failed with %1 modifying AppModel Runtime status for package %2 (current status = %4, desired status = %3). |
| 0xbf000044 | 10 | AppModel Runtime status for package %1 successfully updated to %2 (previous status = %3). |
| 0xbf000045 | 10 | Failed with %1 modifying AppModel Runtime status for package %2 for user %3 (current status = %5, desired status = %4). |
| 0xbf000046 | 10 | AppModel Runtime status for package %1 for user %2 successfully updated to %3 (previous status = %4). |
| 0xbf000047 | 10 | Failed with %1 modifying AppModel Runtime status version (context = %2). |
| 0xbf000048 | 10 | AppModel Runtime status version successfully updated. |
| 0xbf000049 | 10 | %2: Cannot create the process for package %1 because an error was encountered while performing the app data creation. %3 |
| 0xbf00004a | 10 | Package runtime information %1 failed to refresh because the following error %2 occurred in operation type %3. |
| 0xbf00004b | 10 | error %2: Cannot register the %1 package because the following error was encountered while opening the HKEY_USERS registry key |
| 0xbf00004c | 10 | error %4: Cannot register the %1 package because the following error was encountered while enumerating to remove the %2\%3 package family registry key |
| 0xbf00004d | 10 | error %4 : Cannot register the %1 package because the following error was encountered while creating the %2\%3 package family registry key |
| 0xbf00004e | 10 | error %4: Cannot register the %1 package because the following error was encountered while removing the %2\%3 package family registry key |
| 0xbf00004f | 10 | %2: Package family %1 runtime information is corrupted. Attempting to correct the issue. |
| 0xbf000050 | 10 | %2: Package family %1 runtime information is corrupted but we cannot repair it at this time. |
| 0xbf000051 | 10 | Failed with %1 to get IsPackageStageInPlace info from State Repository cache for package %2. The app will by default require integrity check. |
| 0xbf000065 | 10 | Creating AppContainer %1. |
| 0xbf000066 | 10 | Finished creating AppContainer %2 with %1. |
| 0xbf000067 | 10 | Deleting AppContainer %1. |
| 0xbf000068 | 10 | Finished deleting AppContainer %2 with %1. |
| 0xbf000069 | 10 | Updating AppContainer %1. |
| 0xbf00006a | 10 | Finished updating AppContainer %2 with %1. |
| 0xbf00006b | 10 | Creating firewall rules for AppContainer %1. |
| 0xbf00006c | 10 | Finished creating firewall rules for AppContainer %2 with %1. |
| 0xbf00006d | 10 | Deleting firewall rules for AppContainer %1. |
| 0xbf00006e | 10 | Finished deleting firewall rules for AppContainer %2 with %1. |
| 0xbf00006f | 10 | Creating Restricted AppContainer %1. |
| 0xbf000070 | 10 | Finished creating Restricted AppContainer %2 with %1. |
| 0xbf000071 | 10 | Deleting Restricted AppContainer %1. |
| 0xbf000072 | 10 | Finished deleting Restricted AppContainer %2 with %1. |
| 0xbf000073 | 10 | Opening Restricted AppContainer %1. |
| 0xbf000074 | 10 | Finished opening Restricted AppContainer %2 with %1. |
| 0xbf000075 | 10 | Enumerating all Restricted AppContainers for %1. |
| 0xbf000076 | 10 | Finished enumerating all Restricted AppContainers for AppContainer %2 with %1. |
| 0xbf000077 | 10 | Launching process in Restricted AppContainer %1. |
| 0xbf000078 | 10 | Finished launching process in Restricted AppContainer %2 with %1. |
| 0xbf000079 | 10 | Terminating all processes in Restricted AppContainer %1. |
| 0xbf00007a | 10 | Finished terminating all processes in Restricted AppContainer %2 with %1. |
| 0xbf00007b | 10 | Checking package graph for %1. |
| 0xbf00007c | 10 | Package graph check for %2 finished with %1. |
| 0xbf00007d | 10 | Performing app integrity check for package %1. |
| 0xbf00007e | 10 | App integrity check for package %2 finished with %1. |
| 0xbf00007f | 10 | Performing runtime app integrity check for package %1. |
| 0xbf000080 | 10 | Runtime app integrity check for package %2 finished with %1. |
| 0xbf000081 | 10 | Firewall Service not running. Skipping creation of firewall rules for AppContainer %1. |
| 0xbf000082 | 10 | Updating Restricted AppContainer Capabilities %1. |
| 0xbf000083 | 10 | Finished Updating Restricted AppContainer Capabilities %2 with %1. |
| 0xbf0000c9 | 10 | Created process %1 for application %4 in package %2. %5 |
| 0xbf0000ca | 10 | %4: Cannot create the process for package %1 because an error was encountered. %5 |
| 0xbf0000cb | 10 | %4: Cannot create the process for package %1 because an error was encountered while preparing for activation. %5 |
| 0xbf0000cc | 10 | %4: Cannot create the process for package %1 because an error was encountered while elevating the token. %5 |
| 0xbf0000cd | 10 | %4: Cannot create the process for package %1 because UI Access is not supported for Desktop AppX processes. %5 |
| 0xbf0000ce | 10 | %4: Cannot create the process for package %1 because an error was encountered while adjusting the token. %5 |
| 0xbf0000cf | 10 | %4: Cannot create the process for package %1 because an error was encountered while launching. %5 |
| 0xbf0000d0 | 10 | %4: Cannot create the process for package %1 because an error was encountered while configuring runtime. %5 |
| 0xbf0000d1 | 10 | %4: Cannot create the process for package %1 because an error was encountered while resuming the thread. %5 |
| 0xbf0000d2 | 10 | Created Desktop AppX container %3 for package %1. |
| 0xbf0000d3 | 10 | Added process %1 to Desktop AppX container %3 for package %2. |
| 0xbf0000d4 | 10 | %1: Cannot add process %2 to Desktop AppX container %4 for package %3 because an error was encountered. |
| 0xbf0000d5 | 10 | %1: Cannot create the Desktop AppX container for package %2 because an error was encountered creating the job. |
| 0xbf0000d6 | 10 | %1: Cannot create the Desktop AppX container for package %2 because an error was encountered creating the description. |
| 0xbf0000d7 | 10 | %1: Cannot create the Desktop AppX container for package %2 because an error was encountered converting the job. |
| 0xbf0000d8 | 10 | %1: Cannot create the Desktop AppX container for package %2 because an error was encountered configuring the runtime. |
| 0xbf0000d9 | 10 | Destroyed Desktop AppX container %2 for package %1. |
| 0xbf0000da | 10 | Cannot destroy Desktop AppX container %2 for package %1. |
| 0xd1000001 | 1011 | System time initialized during boot |
| 0xd1000002 | 1011 | An application or system component changed the time |
| 0xd1000003 | 1011 | System time synchronized with the hardware clock |
| 0xd1000004 | 1011 | System time adjusted to the new time zone |
| 0xd1000005 | 1011 | Leap second data initialized from registry during boot |
| 0xd1000006 | 1011 | Leap second data updated from registry |
| 0xd1000007 | 1011 | Registry value invalid format or size |
| 0xd1000008 | 1011 | Too many leap seconds |
| 0xd1000009 | 1011 | Cannot decrease the number of leap seconds while the system is running |
| 0xd100000a | 1011 | An invalid leap second was found |
| 0xd100000b | 1011 | The list of leap seconds must be strictly increasing |
| 0xd100000c | 1011 | Cannot modify the existing leap seconds while the system is running |
| 0xd100000d | 1011 | Other reason |
| 0xd4000001 | 1011 | on |
| 0xd4000002 | 1011 | off |
| 0xd4000003 | 1011 | started |
| 0xd4000004 | 1011 | finished |
| 0xd4000005 | 1011 | Platform-level Device Reset |
| 0xd4000006 | 1011 | Function-level Device Reset |
| 0xd4000007 | 1011 | Acpi Override attribute - MpSleep |
| 0xd4000008 | 1011 | Acpi Override attribute - DisableS1 |
| 0xd4000009 | 1011 | Acpi Override attribute - DisableS2 |
| 0xd400000a | 1011 | Acpi Override attribute - DisableS3 |
| 0xd400000b | 1011 | Acpi Override attribute - DellMaxUlongBugcheck |
| 0xd400000c | 1011 | Acpi Override attribute - PciBusNumberTranslation |
| 0xd400000d | 1011 | Acpi Override attribute - RunRegMethodOnPciDevices |
| 0xd400000e | 1011 | Acpi Override attribute - RescanPostDependencies |
| 0xd400000f | 1011 | Acpi Override attribute - PlatformCheckD3ColdOnSurpriseRemoval |
| 0xd4000010 | 1011 | Acpi Override attribute - PlatformCheckFailResetOnOpenHandles |
| 0xdc000001 | 1011 | disabled |
| 0xdc000002 | 1011 | disabled due to HyperV opt-out |
| 0xdc000003 | 1011 | disabled due to opt-out UEFI variable |
| 0xdc000004 | 1011 | disabled due to secure boot being disabled |
| 0xdc000005 | 1011 | disabled due to DMA protection being unavailable |
| 0xdc000006 | 1011 | disabled due to the hypervisor being unavailable |
| 0xdc000007 | 1011 | disabled due to VBS initialization failure |
| 0xdc000008 | 10 | disabled due to VBS anti-rollback policy is missing |
| 0xdc000009 | 10 | enabled due to VBS registry configuration |
| 0xdc00000a | 10 | enabled due to HyperV |
| 0xdc00000b | 10 | enabled due to VBS locked configuration |
| 0xdc00000c | 10 | enabled due to Code Integrity policy |
| 0xdc00000d | 10 | enabled due to Velocity |
| 0xdc00000e | 10 | BL_LOG_INFO_NONE: Info none |
| 0xdc00000f | 10 | BL_LOG_INFO_BLI_IO_INITED: IO initialized in boot library initialization. |
| 0xdc000010 | 10 | BL_LOG_INFO_BLI_FINISHED: Finished in boot library initialization. |
| 0xdc000011 | 10 | BL_LOG_INFO_BM_BL_INITED: The boot library has been initialized for bootmgr. |
| 0xdc000012 | 10 | BL_LOG_INFO_BM_GET_BOOT_SEQ: Getting boot sequence in bootmgr. |
| 0xdc000013 | 10 | BL_LOG_INFO_BM_LAUNCH_ENTRY: Launching boot entry in bootmgr. |
| 0xdc000014 | 10 | BL_LOG_INFO_OSL_PREPARE_ENTERED: Reached prepare target within osloader. |
| 0xdc000015 | 10 | BL_LOG_INFO_OSL_OPEN_DEVICE: Preparing to open OS device in osloader. |
| 0xdc000016 | 10 | BL_LOG_INFO_OSL_LAUNCH_HYPERV: Preparing to launch hyper-v if specified within osloader. |
| 0xdc000017 | 10 | BL_LOG_INFO_OSL_LOAD_MODULES: Preparing to load OS modules within osloader. |
| 0xdc000018 | 10 | BL_LOG_INFO_OSL_KERNEL_SETUP: Setting up kernel within osloader. |
| 0xdc000019 | 10 | BL_LOG_INFO_OSL_PRELOAD_HYPERV: Preloading hyper-v if specified within osloader. |
| 0xdc00001a | 10 | BL_LOG_INFO_OSL_BOOT_CANCELLED: Boot was cancelled. |
| 0xdc00001b | 10 | BL_LOG_INFO_TCB_LAUNCH_HYPERV: Preparing to launch hyper-v. |
| 0xdc00001c | 10 | BL_LOG_ERROR: Generic Error |
| 0xdc00001d | 10 | BL_LOG_ERROR_BLI_NET_INIT: BlNetInitialize failed in BL initialization. |
| 0xdc00001e | 10 | BL_LOG_ERROR_BLI_UTL_INIT: BlUtlInitialize failed in BL initialization. |
| 0xdc00001f | 10 | BL_LOG_ERROR_BLI_SEC_BOOT_INIT: BlSecureBootInitialize failed in BL initialization. |
| 0xdc000020 | 10 | BL_LOG_ERROR_BLI_PDATA_INIT: BlpPdInitialize failed in BL initialization. |
| 0xdc000021 | 10 | BL_LOG_ERROR_BLI_RES_INIT: BlpResourceInitialize failed in BL initialization. |
| 0xdc000022 | 10 | BL_LOG_ERROR_BLI_SEC_LAUNCH_INIT: BlpTcbLaunchInitialize failed in BL initialization. |
| 0xdc000023 | 10 | BL_LOG_ERROR_BM_INIT_MACH_POL: BmSecureBootInitializeMachinePolicy failed in bootmgr. |
| 0xdc000024 | 10 | BL_LOG_ERROR_BM_FW_REG_SYSINT: BmFwRegisterSystemIntegrityPolicies failed in bootmgr. |
| 0xdc000025 | 10 | BL_LOG_ERROR_BM_RES_FIND_HTML: BlResourceFindHtml failed to find BOOTMGR.XSL in bootmgr. |
| 0xdc000026 | 10 | BL_LOG_ERROR_BM_XMI_INIT: BlXmiInitialize failed in bootmgr. |
| 0xdc000027 | 10 | BL_LOG_ERROR_BM_OPEN_DATA_STORE: BmOpenDataStore failed in bootmgr. |
| 0xdc000028 | 10 | BL_LOG_ERROR_BM_SELF_INT_CHK: BmpSelfIntegrityCheck failed in bootmgr. |
| 0xdc000029 | 10 | BL_LOG_ERROR_BM_FW_REG_REV_LIST: BmFwRegisterRevocationList failed in bootmgr. |
| 0xdc00002a | 10 | BL_LOG_ERROR_BM_RESUME_HIBER: BmResumeFromHibernate failed in bootmgr. |
| 0xdc00002b | 10 | BL_LOG_ERROR_BM_PURGE_OPT_START_SEQ: BL_ERROR_BM_PURGE_OPT_START_SEQ failed in bootmgr. |
| 0xdc00002c | 10 | BL_LOG_ERROR_BM_PURGE_OPT_BOOT_SEQ: BmPurgeOption failed for BCDE_BOOTMGR_TYPE_BOOT_SEQUENCE in bootmgr. |
| 0xdc00002d | 10 | BL_LOG_ERROR_BM_REOPEN_DATA_STORE: BmOpenDataStore failed on reopen in bootmgr. |
| 0xdc00002e | 10 | BL_LOG_ERROR_BM_UPDATE_APP_OPTS: BmpUpdateApplicationOptions failed in bootmgr. |
| 0xdc00002f | 10 | BL_LOG_ERROR_BM_LAUNCH_BOOT_ENTRY: BmpLaunchBootEntry failed in bootmgr. |
| 0xdc000030 | 10 | BL_LOG_ERROR_BM_CREATE_DEVICES: BmpCreateDevices failed in bootmgr. |
| 0xdc000031 | 10 | BL_LOG_ERROR_BM_LAUNCH_FLIGHT_BM: BmFwLaunchFlightedBootmgr failed in bootmgr. |
| 0xdc000032 | 10 | BL_LOG_ERROR_BM_FE_BOOTAPP_LD: Fatal error: failure to load boot app in bootmgr. |
| 0xdc000033 | 10 | BL_LOG_ERROR_BM_FE_CONFIG_DATA: Fatal error: failure attempting to read boot config file in bootmgr. |
| 0xdc000034 | 10 | BL_LOG_ERROR_BM_FE_NO_VALID_OS_ENTRY: Fatal error: no valid os entires found in bootmgr. |
| 0xdc000035 | 10 | BL_LOG_ERROR_BM_FE_NO_VALID_PXE_ENTRY: Fatal error: no valid entries found from PXE server in bootmgr. |
| 0xdc000036 | 10 | BL_LOG_ERROR_BM_FE_FAILURE_STATUS: Fatal error: failure status in bootmgr. |
| 0xdc000037 | 10 | BL_LOG_ERROR_BM_FE_BOOT_DEVICE: Fatal error: boot device inaccessible in bootmgr. |
| 0xdc000038 | 10 | BL_LOG_ERROR_BM_FE_RAMDISK_MEM: Fatal error: ramdisk device creation had insufficient memory in bootmgr. |
| 0xdc000039 | 10 | BL_LOG_ERROR_BM_FE_INVALID_BCD_STORE: Fatal error: BCD is invalid in bootmgr. |
| 0xdc00003a | 10 | BL_LOG_ERROR_BM_FE_INVALID_BCD_ENTRY: Fatal error: Invalid BCD entry in bootmgr. |
| 0xdc00003b | 10 | BL_LOG_ERROR_BM_FE_NO_SECUREBOOT_POL: Fatal error: Default Secure Boot policy not found in bootmgr. |
| 0xdc00003c | 10 | BL_LOG_ERROR_BM_FE_NO_PAE_SUPPORT: Fatal error: CPU does not support PAE in bootmgr. |
| 0xdc00003d | 10 | BL_LOG_ERROR_BM_FE_UNSEAL_NOT_POS: Fatal error: Cannot unseal sensitive data in bootmgr. |
| 0xdc00003e | 10 | BL_LOG_ERROR_BM_FE_GENERIC: Fatal error: Generic failure in bootmgr. |
| 0xdc00003f | 10 | BL_LOG_ERROR_BM_FAILED_SVN_CHECK: Bootmgr SVN check failed. |
| 0xdc000040 | 10 | BL_LOG_ERROR_BM_FAILED_CHAINLOAD_SVN_CHECK: SVN check failed while chainloading bootmgr. |
| 0xdc000041 | 10 | BL_LOG_ERROR_OSL_REM_INTERN_APP_OPTS: OslpRemoveInternalApplicationOptions failed in osloader. |
| 0xdc000042 | 10 | BL_LOG_ERROR_OSL_GET_APP_OPT_DEVICE: BlGetApplicationOptionDevice failed for BCDE_OSLOADER_TYPE_OS_DEVICE in osloader. |
| 0xdc000043 | 10 | BL_LOG_ERROR_OSL_GET_SYSTEM_ROOT: Failed to get SystemRoot in osloader. |
| 0xdc000044 | 10 | BL_LOG_ERROR_OSL_FORCED_FAIL: OslpCheckForcedFailure failed implying a forced failure in osloader. |
| 0xdc000045 | 10 | BL_LOG_ERROR_OSL_DISABLE_VGA: BlAppendApplicationOptionBoolean for BCDE_OSLOADER_TYPE_DISABLE_VGA_MODE failed in osloader. |
| 0xdc000046 | 10 | BL_LOG_ERROR_OSL_OPEN_OS_DEVICE: BlDeviceOpen failed for os device in osloader. |
| 0xdc000047 | 10 | BL_LOG_ERROR_OSL_LOAD_SYS_HIVE: OslpLoadSystemHive failed in osloader. |
| 0xdc000048 | 10 | BL_LOG_ERROR_OSL_CREATE_OS_LD_OPTS: AhCreateLoadOptionsString failed in osloader. |
| 0xdc000049 | 10 | BL_LOG_ERROR_OSL_DISPLAY_INIT: OslDisplayInitialize failed in osloader. |
| 0xdc00004a | 10 | BL_LOG_ERROR_OSL_PROCESS_SI_POLICY: OslpProcessSIPolicy failed in osloader. |
| 0xdc00004b | 10 | BL_LOG_ERROR_OSL_DISP_ADV_OPT: OslDisplayAdvancedOptionsProcess failed in osloader. |
| 0xdc00004c | 10 | BL_LOG_ERROR_OSL_ARCH_HV_SETUP: OslArchHypervisorSetup failed in osloader. |
| 0xdc00004d | 10 | BL_LOG_ERROR_OSL_ARCH_HYPERCALL_SETUP: OslArchHypercallSetup failed in osloader. |
| 0xdc00004e | 10 | BL_LOG_ERROR_OSL_INIT_RESUME_CONTEXT: OslInitializeResumeContext failed in osloader. |
| 0xdc00004f | 10 | BL_LOG_ERROR_OSL_INIT_LDR_BLOCK: OslInitializeLoaderBlock failed in osloader. |
| 0xdc000050 | 10 | BL_LOG_ERROR_OSL_PROC_INIT_MACH_CONFIG: OslpProcessInitialMachineConfiguration failed in osloader. |
| 0xdc000051 | 10 | BL_LOG_ERROR_OSL_ENUM_DISKS: OslEnumerateDisks failed for the loader block in osloader. |
| 0xdc000052 | 10 | BL_LOG_ERROR_OSL_REINIT_SYS_HIVE: OslpReinitializeSystemHive failed in osloader. |
| 0xdc000053 | 10 | BL_LOG_ERROR_OSL_INIT_CODE_INT: OslInitializeCodeIntegrity failed in osloader. |
| 0xdc000054 | 10 | BL_LOG_ERROR_OSL_INIT_CODE_INT_LD_BLOCK: OslBuildCodeIntegrityLoaderBlock failed in osloader. |
| 0xdc000055 | 10 | BL_LOG_ERROR_OSL_SECURE_BOOT_VARS: OslFwProtectSecureBootVariables failed in osloader. |
| 0xdc000056 | 10 | BL_LOG_ERROR_OSL_LD_MODULES: OslpLoadAllModules failed in osloader. |
| 0xdc000057 | 10 | BL_LOG_ERROR_OSL_LD_FW_DRIVERS: OslFwLoadFirmwareDrivers failed in osloader. |
| 0xdc000058 | 10 | BL_LOG_ERROR_OSL_VSM_CHK_ENCRYPT_KEY: BlVsmCheckSystemPolicy failed for master sncrupt key provisioning in osloader. |
| 0xdc000059 | 10 | BL_LOG_ERROR_OSL_VSM_PHASE_0: Fatal VSM Phase 0 initializatin failure in osloader. |
| 0xdc00005a | 10 | BL_LOG_ERROR_OSL_SET_SEIL_SIGN_POL: OslSetSeILSigningPolicy failed in osloader. |
| 0xdc00005b | 10 | BL_LOG_ERROR_OSL_CMS_PROV_IDK: BlVsmCheckSystemPolicy failed during VSM Idendity key work in osloader. |
| 0xdc00005c | 10 | BL_LOG_ERROR_OSL_ARCH_KERNEL_SETUP_0: OslArchKernelSetup failed for 0 in osloader. |
| 0xdc00005d | 10 | BL_LOG_ERROR_OSL_FW_KERNEL_SETUP: OslFwKernelSetup failed for 0 in osloader. |
| 0xdc00005e | 10 | BL_LOG_ERROR_OSL_PROC_EV_STORE: OslpProcessEVStore failed in osloader. |
| 0xdc00005f | 10 | BL_LOG_ERROR_OSL_COPY_BOOT_OPTS: BlCopyBootOptions failed in osloader. |
| 0xdc000060 | 10 | BL_LOG_ERROR_OSL_FVE_SEC_BOOT_REST_ONE: BlFveSecureBootRestrictToOne failed in osloader. |
| 0xdc000061 | 10 | BL_LOG_ERROR_OSL_NET_UNDI_CLOSE: BlNetUndiClose failed in osloader. |
| 0xdc000062 | 10 | BL_LOG_ERROR_OSL_PROC_APP_PDATA: OslProcessApplicationPersistentData failed in osloader. |
| 0xdc000063 | 10 | BL_LOG_ERROR_OSL_BLD_MEM_CACHE_REQ_LIST: OslFwBuildMemoryCachingRequirementsList failed in osloader. |
| 0xdc000064 | 10 | BL_LOG_ERROR_OSL_BLD_RT_MEM_MAP: OslFwBuildRuntimeMemoryMap failed in osloader. |
| 0xdc000065 | 10 | BL_LOG_ERROR_OSL_VSM_SETUP_1: OslVsmSetup failed for 1 in osloader. |
| 0xdc000066 | 10 | BL_LOG_ERROR_OSL_BLD_KERNEL_MEM_MAP: BlTraceBuildKernelMemoryMapStop failed in osloader. |
| 0xdc000067 | 10 | BL_LOG_ERROR_OSL_ARCH_KERNEL_SETUP_1: OslArchKernelSetup failed for 1 in osloader. |
| 0xdc000068 | 10 | BL_LOG_ERROR_OSL_SET_VSM_POL_SYS_HIVE: OslSetVsmPolicy failed in osloader. |
| 0xdc000069 | 10 | BL_LOG_ERROR_OSL_ENUM_ENCLAVE_PAGES: OslEnumerateEnclavePageRegions failed in osloader. |
| 0xdc00006a | 10 | BL_LOG_ERROR_OSL_GATHER_ENTROPY: OslGatherEntropy failed in osloader. |
| 0xdc00006b | 10 | BL_LOG_ERROR_OSL_VSM_SETUP_0: OslVsmSetup failed for 0 in osloader. |
| 0xdc00006c | 10 | BL_LOG_ERROR_OSL_VSM_CANNOT_BE_DISABLED_BY_KSR: VSM must not be disabled through KSR |
| 0xdc00006d | 10 | BL_LOG_ERROR_OSL_VSM_PHASE0_ALLOCATE_PAGES_FAILED |
| 0xdc00006e | 10 | BL_LOG_ERROR_OSL_VSM_PHASE0_LOAD_MODULES_FAILED |
| 0xdc00006f | 10 | BL_LOG_ERROR_OSL_VSM_PHASE0_LOAD_CIDATA_FAILED |
| 0xdc000070 | 10 | BL_LOG_ERROR_OSL_VSM_PHASE0_COPY_VSM_KEYS_FAILED |
| 0xdc000071 | 10 | BL_LOG_ERROR_OSL_VSM_PHASE0_COPY_ACPI_TABLES_FAILED |
| 0xdc000072 | 10 | BL_LOG_ERROR_OSL_VSM_PHASE0_ARCH_SETUP_FAILED |
| 0xdc000073 | 10 | BL_LOG_ERROR_OSL_VSM_PHASE0_BUILD_PAGE_TABLES_FAILED |
| 0xdc000074 | 10 | BL_LOG_ERROR_OSL_BUILD_BSD_LOCATION_FAILED: OslpBuildBsdLogLocation failed in osloader. |
| 0xdc000075 | 10 | BL_LOG_ERROR_OSL_GET_APP_OPT_DEVICE_OSDATA: BlGetApplicationOptionDevice failed for BCDE_OSLOADER_TYPE_OS_DATA_DEVICE in osloader. |
| 0xdc000076 | 10 | BL_LOG_ERROR_OSL_OPEN_OSDATA_DEVICE: BlDeviceOpen failed for osdata device in osloader. |
| 0xdc000077 | 10 | BL_LOG_ERROR_OSL_ENUMERATE_PERSISTENT_MEMORY: OslEnumeratePersistentMemory failed in osloader. |
| 0xdc000078 | 10 | BL_LOG_ERROR_OSL_HVCI_CANNOT_BE_ENABLED_BY_KSR: HVCI must not be enabled through KSR |
| 0xdc000079 | 10 | BL_LOG_ERROR_OSL_PROCESS_PRESERVED_MEMORY: Error while processing preserved memory. |
| 0xdc00007a | 10 | BL_LOG_ERROR_OSL_LOAD_DEVICES_HIVE: OslpLoadDevicesHive failed in osloader. |
| 0xdc00007b | 10 | BL_LOG_ERROR_OSL_LOAD_OSBOOT_HIVE: OslpLoadOsBootHive failed in osloader. |
| 0xdc00007c | 10 | BL_LOG_ERROR_OSL_LOAD_DRIVER_STORES: OslpLoadDriverStoreNodes failed in osloader. |
| 0xdc00007d | 10 | BL_LOG_ERROR_OSL_CMS_PROV_HBK: BlVsmCheckSystemPolicy failed during VSM Hibernation key work in osloader. |
| 0xdc00007e | 10 | BL_LOG_ERROR_OSL_ALLOC_LDR_BLOCK: OslAllocateLoaderBlock failed in osloader. |
| 0xdc00007f | 10 | BL_LOG_ERROR_OSL_ARCH_TCB_LAUNCH_0: OslTcbLaunch(0) failed in osloader. |
| 0xdc000080 | 10 | BL_LOG_ERROR_OSL_HVCI_CANNOT_BE_DISABLED_BY_KSR: HVCI must not be disabled through KSR |
| 0xdc000081 | 10 | BL_LOG_ERROR_OSL_GET_APP_OPT_DEVICE_BSP: BlGetApplicationOptionDevice failed for BCDE_OSLOADER_TYPE_BSP_DEVICE in osloader. |
| 0xdc000082 | 10 | BL_LOG_ERROR_OSL_OPEN_BSP_DEVICE: BlDeviceOpen failed for bsp device in osloader. |
| 0xdc000083 | 10 | BL_LOG_ERROR_OSL_VSM_PHASE0_VBS_POLICY_NOT_PRESENT |
| 0xdc000084 | 10 | BL_LOG_ERROR_KSR_KSEG0: InitializeRebootAddressRange failed in SK extension. |
| 0xdc000085 | 10 | BL_LOG_ERROR_KSR_OUT_OF_MEMORY: Memory allocation failed in SK KSR extension. |
| 0xdc000086 | 10 | BL_LOG_ERROR_KSR_IMAGE_VALIDATION: Image validation failed in SK KSR extension. |
| 0xdc000087 | 10 | BL_LOG_ERROR_KSR_IMAGE_RELOCATION: Image relocation failed in SK KSR extension. |
| 0xdc000088 | 10 | BL_LOG_ERROR_KSR_BIND_IMPORT: Failed to bind imports to image in SK KSR extension. |
| 0xdc000089 | 10 | BL_LOG_ERROR_KSR_LOADER_ENTRY_POINT: SK loader entry point returned failure. |
| 0xdc00008a | 10 | BL_LOG_ERROR_KSR_RESERVE_EFI_RUNTIME: SK loader failed to reserve EFI runtime VA range. |
| 0xdc00008b | 10 | BL_LOG_ERROR_TCB_SI_POLICY_CHECK: Failed to validate and measure SI policy. |
| 0xdc00008c | 10 | BL_LOG_ERROR_TCB_LOAD_TCBLOADER: Failed to load tcbloader.dll. |
| 0xdc00008d | 10 | BL_LOG_ERROR_TCB_LOAD: Failed to perform load action. |
| 0xdc00008e | 10 | BL_LOG_ERROR_TCB_RESUME: Failed to perform resume action. |
| 0xdc00008f | 10 | BL_LOG_ERROR_TCB_INVALID_ATTRIBUTES: Invalid tcblaunch application attributes. |
| 0xdc000090 | 10 | BL_LOG_ERROR_TCB_REGISTER_EVENT_HANDLER: Failed to register launch notificaiton handler. |
| 0xdc000091 | 10 | BL_LOG_ERROR_TCB_OPEN_DEVICE: Failed to open application device. |
| 0xdc000092 | 10 | BL_LOG_ERROR_TCB_GET_DEVICE: Failed to query application device. |
| 0xdc000093 | 10 | BL_LOG_ERROR_GET_SYSTEM_ROOT: Failed to get SystemRoot value. |
| 0xdc000094 | 10 | BL_LOG_ERROR_OSL_PROCESS_BOOTSTAT_DATA: Failed to process bootstat data. |
| 0xdc000095 | 10 | BL_LOG_ERROR_OSL_VIRT_SETUP_0: Failed to perform virtual setup phase 0. |
| 0xdc000096 | 10 | BL_LOG_ERROR_OSL_VIRT_SETUP_1: Failed to perform virtual setup phase 1. |
| 0xdc000097 | 10 | BL_LOG_ERROR_OSL_PRELOAD_SI_POLICY: Failed to preload SI policies from OS volume. |
| 0xdc000098 | 10 | BL_LOG_ERROR_OSL_ARCH_TCB_LAUNCH_1: OslTcbLaunch(1) failed in osloader. |
| 0xdc000099 | 10 | ERROR_TCB_PLATORM_INIT: Failed to initialize TCB platform. |
| 0xdc00009a | 10 | BL_LOG_ERROR_OSL_INITIALIZE_FEATURE_CONFIGURATION: OslInitializeFeatureConfiguration failed in osloader. |
| 0xdc00009b | 10 | BL_LOG_ERROR_RES_OPEN_HIBERFILE: Failed to open the hiberfile. |
| 0xdc00009c | 10 | BL_LOG_ERROR_RES_INIT_DISPLAY: Failed to initialize display. |
| 0xdc00009d | 10 | BL_LOG_ERROR_RES_INVALID_PAGEFILE: Page file is invalide for hibernate resume. |
| 0xdc00009e | 10 | BL_LOG_ERROR_RES_HW_CHANGE: Hardware or firmware settings have changes since hibernate. |
| 0xdc00009f | 10 | BL_LOG_ERROR_RES_INVALID_HIBERFILE: Hiberfile is invalid. |
| 0xdc0000a0 | 10 | BL_LOG_ERROR_RES_GET_CONTEXT_FAILED: Failed to get the resume context. |
| 0xdc0000a1 | 10 | BL_LOG_ERROR_RES_INVALID_MEM_MAP: The memory map has changed since associated cold boot. |
| 0xdc0000a2 | 10 | BL_LOG_ERROR_RES_FIRMWARE_PHASE_0: Failed phase 0 of firmware setup for resume. |
| 0xdc0000a3 | 10 | BL_LOG_ERROR_RES_USB_HANDOFF: Failed setup for legacy usb handoff. |
| 0xdc0000a4 | 10 | BL_LOG_ERROR_RES_SMBIOS: Failed to get SMBIOS data. |
| 0xdc0000a5 | 10 | BL_LOG_ERROR_RES_TCB_ALLOCATE: Failed to allocate space for TCB resume. |
| 0xdc0000a6 | 10 | BL_LOG_ERROR_RES_TCB_PREPARE: Failed to prepare TCB data. |
| 0xdc0000a7 | 10 | BL_LOG_ERROR_RES_INIT_PREALLOCATION: Failed to initialize the preallocation. |
| 0xdc0000a8 | 10 | BL_LOG_ERROR_RES_INIT_TRANSITION_SPACE: Failed to intialize transition space. |
| 0xdc0000a9 | 10 | BL_LOG_ERROR_RES_INIT_PAGE_ALLOCATOR: Failed to initialize the free page allocator. |
| 0xdc0000aa | 10 | BL_LOG_ERROR_RES_RELOC_PROC_CONTEXT: Failed to relocate the processor context page. |
| 0xdc0000ab | 10 | BL_LOG_ERROR_RES_LOAD_SECURE_DATA: Failed to load secure data from the hiberfile. |
| 0xdc0000ac | 10 | BL_LOG_ERROR_RES_RESTORE_IMAGE: Failed to restore image from the hiberfile. |
| 0xdc0000ad | 10 | BL_LOG_ERROR_RES_SECURE_DECRYPT_0: Failed phase 0 of secure data decryption. |
| 0xdc0000ae | 10 | BL_LOG_ERROR_RES_FVE_RESTRICT: Failed to restrict bitlocker to resuming OS. |
| 0xdc0000af | 10 | BL_LOG_ERROR_RES_TCB_PREP_DATA: Failed to prepare data for TCB resume. |
| 0xdc0000b0 | 10 | None |
| 0xdc0000b1 | 10 | Processor is not supported. |
| 0xdc0000b2 | 10 | VMX is not supported. |
| 0xdc0000b3 | 10 | SMX is not supported. |
| 0xdc0000b4 | 10 | TXT is disabled by the BIOS in MSR_FEATURE_CONTROL. |
| 0xdc0000b5 | 10 | Required GETSEC[CAPABILITIES] are not available. |
| 0xdc0000b6 | 10 | TPM 2.0 is not available. |
| 0xdc0000b7 | 10 | Memory Attributes Table (MAT) not available. |
| 0xdc0000b8 | 10 | No SINIT ACM module type found at the SINIT base address. |
| 0xdc0000b9 | 10 | The ACM UUID does not match well known value. |
| 0xdc0000ba | 10 | The ACM client/server flags do not match the bios data. |
| 0xdc0000bb | 10 | The ACM debug flag does not match platform. |
| 0xdc0000bc | 10 | The ACM does not support the chipset. |
| 0xdc0000bd | 10 | The ACM does not support the processor. |
| 0xdc0000be | 10 | A more up to date ACM is available on the system. |
| 0xdc0000bf | 10 | No compatible ACM found on the system. |
| 0xdc0000c0 | 10 | The system does not support DMA remapping in the DMAR table. |
| 0xdc0000c1 | 10 | TPM does not meet provisioning requirements. |
| 0xdc0000c2 | 10 | System does not meet required configuration to validate SMM. |
| 0xdc0000c3 | 10 | A VMX failure was encountered. |
| 0xdc0000c4 | 10 | Call to retrieve SMM information failed. |
| 0xdc0000c5 | 10 | SMM has access to OS memory regions. |
| 0xdc0000c6 | 10 | SMM signature is missing or corrupt. |
| 0xdc0000c7 | 10 | SMM signature check failed. |
| 0xdc0000c8 | 10 | SMM has access to a MSR that is not allowed by policy level. |
| 0xdc0000c9 | 10 | SMM has access to an IO port that is not allowed by policy level. |
| 0xdc0000ca | 10 | SMM has access to IOMMU structures. |
| 0xdc0000cb | 10 | ACM layout corruption. |
| 0xdc0000cc | 10 | None. |
| 0xdc0000cd | 10 | Failed to reserve scratch VA. |
| 0xdc0000ce | 10 | Failed to get connection parameters. |
| 0xdc0000cf | 10 | Debugging blocked by BitLocker. |
| 0xdc0000d0 | 10 | Failed to initialize debug device descriptor. |
| 0xdc0000d1 | 10 | Failed to setup debugging device. |
| 0xdc0000d2 | 10 | Failed to initialize debug transport. |
| 0xdc0000d3 | 10 | Failed to setup debug traps. |
| 0xdc0000d4 | 10 | Failed to load debugger transport module. |
| 0xdc0000d5 | 10 | Failed to allocate scratch buffer. |
| 0xdc0000d6 | 10 | Failed to get debugger transport extension name. |
| 0xdc0000d7 | 10 | truncatememory |
| 0xdc0000d8 | 10 | avoidlowmemory |
| 0xdc0000d9 | 10 | testsigning |
| 0xdc0000da | 10 | nointegritychecks |
| 0xdc0000db | 10 | Undefined |
| 0xdc0000dc | 10 | Available |
| 0xdc0000dd | 10 | Applied |
| 0xdc0000de | 10 | Rejected |
| 0xdc0000df | 10 | NotFound |
| 0xde000001 | 10 | applied through registry |
| 0xde000002 | 10 | applied through compatibility database |
| 0xde000003 | 10 | applied through registry |
| 0xde000004 | 10 | applied through compatibility database |
| 0xf2000001 | 1011 | PackageId |
| 0xfc000001 | 1011 | None |
| 0xfc000002 | 1011 | VBS Enabled |
| 0xfc000003 | 1011 | VSM Required |
| 0xfc000004 | 1011 | Secure Boot |
| 0xfc000005 | 1011 | Iommu Protection |
| 0xfc000006 | 1011 | Mmio Nx |
| 0xfc000007 | 1011 | Strong MSR Filtering |
| 0xfc000008 | 1011 | Mandatory |
| 0xfc000009 | 1011 | Hvci |
| 0xfc00000a | 1011 | Hvci Strict |
| 0xfc00000b | 1011 | Boot Chain Signer Soft Enforced |
| 0xfc00000c | 1011 | Boot Chain Signer Hard Enforced |
| 0xfc00000d | 1011 | Measured Launch |
| 0x137 | 11 | The executable %3 is removing the UIAccess flag on a token. |
| 0x348 | 11 | Session "%3" could not be started because LOGGER_FLAG_LARGE_MDL_PAGES is not supported. |
| 0x349 | 11 | Session "%1" could not be started because because the maximum %2 logging sessions are already active on the system. |
| 0x34a | 11 | Session "%1" could not be started because because the maximum %2 EVENT_TRACE_SYSTEM_LOGGER_MODE logging sessions are already active on the system. |
| 0x34b | 11 | Session "%1" could not be started because the process failed its access check to the SessionGuid. |
| 0x34c | 11 | Session "%1" could not be started because the Memory Partition Handle %2 is invalid. |
| 0x34d | 11 | Session "%1" failed to create file %2 with error %3. |
| 0x34e | 11 | Session "%1" could not be started because the process lacks the profiling privilege. |
| 0x34f | 11 | Group Mask could not be updated for Session "%1", because the requested Group Mask is not supported. |
| 0x350 | 11 | Capture state requested for provider %1 on session "%2". |
| 0x351 | 11 | Capture State |
| 0x35c | 11 | Lost TraceLogging Event |
| 0x35d | 11 | Lost WPP Event |
| 0x35e | 11 | Lost System Event |
| 0x383 | 11 | The enable state for Provider %1 is about to change on session "%2". |
| 0x384 | 11 | Provider %1 is about to be disabled from session "%2". |
| 0x45f | 11 | Live Dump Capture Dump Data API started. Flags: %1. AddPagesControl: %2 |
| 0x460 | 11 | Live Dump Capture Dump Data API ended. NT Status: %1. BugcheckCode: %2. BugcheckParameter1: %3. BugcheckParameter2: %4. BugcheckParameter3: %5. BugcheckParameter4: %6. AbortIfMemoryPressure: %7. DumpCaptureDuration: %8ms. SelectiveDump: %9. DynamicLowMemoryThreshold: %10 bytes. AvailablePhysicalMemory: %11 bytes. TotalPhysicalMemory: %12 bytes. IOSpaceEnabled: %13. |
| 0x462 | 11 | Writing dump file ended. NT Status: %1. Total %2 bytes (Header|Primary|Secondary: %3|%4|%5 bytes). DumpWriteDuration: %6ms. |
| 0x46f | 11 | Live Dump Write Deferred Dump Data API ended. NT Status: %1. BugcheckCode: %2. BugcheckParameter1: %3. BugcheckParameter2: %4. BugcheckParameter3: %5. BugcheckParameter4: %6. DumpWriteDuration: %8ms. SelectiveDump: %9. DynamicLowMemoryThreshold: %10 bytes. AvailablePhysicalMemory: %11 bytes. TotalPhysicalMemory: %12 bytes. IOSpaceEnabled: %13. |
| 0x471 | 11 | Write deferred dump data to file ended. NT Status: %1. Total %2 bytes (Header|Primary|Secondary: %3|%4|%5 bytes). DumpWriteDuration: %6ms. |
| 0x473 | 11 | Live Dump Discard Deferred Dump Data API ended. NT Status: %1. BugcheckCode: %2. BugcheckParameter1: %3. BugcheckParameter2: %4. BugcheckParameter3: %5. BugcheckParameter4: %6. |
| 0x480 | 11 | Sizing workflow: %1 pages estimated to be allocated and %2 pages allocated (VM memory partition's IOSpace|VM memory partition|System partition's IOSpace|System partition: %3|%4|%5|%6 pages). Limit dump file size: %7. Dump file size limit: %8 bytes. Dump file size limit reached: %9. Aborted while buffer allocation: %10. |
| 0x481 | 11 | Sizing Workflow: Estimation. NT: %2 bytes (Minimum %1 bytes). Hypervisor: Primary %3 bytes. Secondary %4 bytes. SecureKernel: %5 bytes. MemoryEstimationDuration: %6ms. SystemQuiescedDuration: %7ms. EndMirroringPhasesDuration: %8ms. MirrorPhysicalMemoryDuration: %9ms. MirrorPhysicalMemorySizeInBytes: %10 bytes. HvlCalculateLiveDumpSizeDuration: %11ms. |
| 0x484 | 11 | Sizing Workflow: Open VM memory partition failed. NT Status: %1 |
| 0x485 | 11 | Sizing Workflow: Buffer allocation from the VM memory partition failed. NT Status: %1 |
| 0x48e | 11 | Capture Pages Workflow: Generate Ipt secondary data when system is quiesced. Duration: %1ms. |
| 0x48f | 11 | Capture Processor Context |
| 0x490 | 11 | Mark Required Dump Data |
| 0x491 | 11 | Mark Important DumpData |
| 0x492 | 11 | Populate Bitmap For Dump |
| 0x493 | 11 | Generate Ipt Secondary Data |
| 0x494 | 11 | Sizing Workflow: Corral processors to quiesce the system. CorralDuration: %1ms. DisableInterruptsDuration: %2ms. SaveSupervisorStateDuration: %3ms. SuspendClockTimerDuration: %4ms. |
| 0x495 | 11 | Capture Pages Workflow: Corral processors to quiesce the system. CorralDuration: %1ms. DisableInterruptsDuration: %2ms. SaveSupervisorStateDuration: %3ms. SuspendClockTimerDuration: %4ms. |
| 0x496 | 11 | Sizing Workflow: Uncorral processors to quiesce the system. UncorralDuration: %1ms. EnableInterruptsDuration: %2ms. RestoreSupervisorStateDuration: %3ms. ResumeClockTimerDuration: %4ms. |
| 0x497 | 11 | Capture Pages Workflow: Uncorral processors to quiesce the system. UncorralDuration: %1ms. EnableInterruptsDuration: %2ms. RestoreSupervisorStateDuration: %3ms. ResumeClockTimerDuration: %4ms. |
| 0x498 | 11 | Capture Pages Workflow: Capture memory pages. MemoryCaptureDuration: %1ms. SystemQuiescedDuration: %2ms. EndMirroringPhasesDuration: %3ms. MirrorPhysicalMemoryDuration: %4ms. MirrorPhysicalMemorySizeInBytes: %5 bytes. HvlCollectLivedumpDuration: %6ms. DumpDataBufferingDuration: %7ms. |
| 0x499 | 11 | Corral Processors |
| 0x49a | 11 | Uncorral Processors |
| 0x49b | 11 | Capture Memory Pages |
| 0x49c | 11 | Sizing Workflow: MmDuplicateMemory failed. NT Status: %1. MirrorInProgress: %2. |
| 0x49d | 11 | Capture Pages Workflow: MmDuplicateMemory failed. NT Status: %1. MirrorInProgress: %2. |
| 0x49e | 11 | MmDuplicateMemory Failure |
| 0x49f | 11 | AllowLiveDump policy: %1. |
| 0x4a0 | 11 | AllowLiveDump policy value changed (AllowLiveDump = %1). Configure live dump. NT status: %2 |
| 0x4a1 | 11 | LiveDump disabled on boot by policy (AllowLiveDump = %1). |
| 0x4a2 | 11 | Live Dump Policy |
| 0x4a3 | 11 | Policy Operation Failed |
| 0x4a4 | 11 | Policy Value Changed |
| 0x4a5 | 11 | LiveDump Disabled On Boot |
| 0x4a6 | 11 | IO space utilization disabled when HV/SK pages requested, NoSecrets mode disabled, and SK running. |
| 0x4a7 | 11 | LiveDump Disable IOSpace Utilization |
| 0x4a8 | 11 | LiveDump Feature Callout |
| 0x4a9 | 11 | Callout for %1 (included %2). |
| 0x4aa | 11 | Sizing Workflow: Call to Hvl for preparing livedump descriptor failed. NT Status: %1 |
| 0x4ab | 11 | HvlPrepareLiveDumpDescriptor Failure |
| 0x4ac | 11 | LiveDump Event Generic |
| 0x4bc | 11 | Failed to automatically attach a VHD during system startup. VHD name: %2 Status: %3 |
| 0x4bd | 11 | This volume is configured to block legacy file system filters. Filter name: %2 Volume name: %4 |
| 0x794 | 11 | Process '%2' (PID %5) has encountered a shadow stack return address mismatch. The process will be allowed to continue execution because: %17. Process shadow stack strict mode: %15 Appcompat options: %16 Return instruction executed from module '%12'. (Instruction address: %18, module offset: %19, module compatible with shadow stacks: %20) Attempting to return to module '%14'. (Instruction address: %21, module offset: %22, module compatible with shadow stacks: %23) |
| 0x795 | 11 | Process '%2' (PID %5) has encountered a shadow stack return address mismatch. The process will be terminated. Process shadow stack strict mode: %15 Appcompat options: %16 Return instruction executed from module '%12'. (Instruction address: %18, module offset: %19, module compatible with shadow stacks: %20) Attempting to return to module '%14'. (Instruction address: %21, module offset: %22, module compatible with shadow stacks: %23) |
| 0x796 | 11 | the process is running in audit mode |
| 0x797 | 11 | the process is running in compatibility mode, and the mismatch occurred in a module that is not compatible with shadow stacks |
| 0x798 | 11 | The system has encountered a kernel-mode shadow stack return address mismatch. The system will be allowed to continue execution because: %5. Return instruction executed from module '%2'. (Instruction address: %6, module offset: %7) Attempting to return to module '%4'. (Instruction address: %9, module offset: %10) |
| 0x799 | 11 | The system has encountered a kernel-mode shadow stack return address mismatch. The system will be terminated. Return instruction executed from module '%2'. (Instruction address: %6, module offset: %7) Attempting to return to module '%4'. (Instruction address: %9, module offset: %10) |
| 0x79a | 11 | the system is running in audit mode |
| 0x79b | 11 | Process '%2' (PID %5) would have been blocked from making the NtFsControlFile system call. |
| 0x79c | 11 | Process '%2' (PID %5) was blocked from making the NtFsControlFile system call. |
| 0x834 | 11 | Microsoft-Windows-Kernel-Dump |
| 0x835 | 11 | Microsoft-Windows-Kernel-Dump/Operational |
| 0x836 | 11 | CrashDump Policy |
| 0x837 | 11 | AllowCrashDump policy: %1. |
| 0x838 | 11 | AllowCrashDump policy value changed (AllowCrashDump = %1). Configure crash dump. NT status: %2 |
| 0x839 | 11 | CrashDump disabled on boot by policy (AllowCrashDump = %1). |
| 0x83a | 11 | Policy Operation Failed |
| 0x83b | 11 | Policy Value Changed |
| 0x83c | 11 | CrashDump Disabled On Boot |
| 0x83d | 11 | CrashDump Config |
| 0x83e | 11 | Crash dump disable failed. NT status: %1. |
| 0x83f | 11 | Crash dump initialization failed. NT status: %1. |
| 0x840 | 11 | Crash dump load driver failed. NT status: %1. |
| 0x841 | 11 | Crash dump dump stack initialization failed. NT status: %1. |
| 0x842 | 11 | Crash dump free dump stack failed. NT status: %1. |
| 0x843 | 11 | Crash dump load dump stack failed. NT status: %1. |
| 0x844 | 11 | Dump Disable Failed |
| 0x845 | 11 | Dump Initialization Failed. |
| 0x846 | 11 | Dump Load Driver Failed. |
| 0x847 | 11 | Dump Stack Initialization Failed |
| 0x848 | 11 | Free Dump Stack Failed |
| 0x849 | 11 | Load Dump Stack Failed |
| 0x84a | 11 | Crash dump disabled. |
| 0x84b | 11 | Dump Disabled |
| 0x84c | 11 | Crash dump reconfigured. NT status: %1. |
| 0x84d | 11 | Dump Reconfigured |
| 0x84e | 11 | Dump disabled forcefully (ForceDumpDisabled: %1). |
| 0x84f | 11 | Dump disabled forcefully |
| 0x850 | 11 | Dump Config |
| 0x898 | 11 | Microsoft-Windows-Kernel-CPU-Starvation |
| 0x899 | 11 | Microsoft-Windows-Kernel-CPU-Starvation/Operational |
| 0x89a | 11 | DPC Soft Timeout |
| 0x89b | 11 | CPU %3 exceeded its single DPC soft timeout of %5 clock ticks. A single DPC in module %7, with key %1, ran for %4 clock ticks on the thread with TID %2. |
| 0x89c | 11 | CPU %2 exceeded its cumulative DPC soft timeout of %4 clock ticks, by running at an IRQL greater than or equal to DISPATCH_LEVEL for %3 clock ticks on the thread with TID %1. |
| 0x89d | 11 | Single DPC Soft Timeout Reached |
| 0x89e | 11 | Cumulative DPC Soft Timeout Reached |
| 0x89f | 11 | DPC Profiling |
| 0x8a0 | 11 | Capture DPC sequence number %1 at tick %2. |
| 0x8a1 | 11 | Thread %1 on CPU %2 exceeded the threshold of %4 ticks running at DISPATCH_LEVEL or higher, profiling started with sequence number %3. |
| 0x8a2 | 11 | DPC Profiling Stack Capture |
| 0x8a3 | 11 | DPC Profiling Threshold Reached |
| 0x8a4 | 11 | Microsoft-Windows-Kernel-Prm |
| 0x8a5 | 11 | Microsoft-Windows-Kernel-Prm/Operational |
| 0x8a6 | 11 | PRM has been invoked. |
| 0x8a7 | 11 | PRM module update failed. Module GUID %1, module version %2, status %3. |
| 0x8a8 | 11 | PRM invocation failed. Handler GUID %1, module GUID %2, module version %3, interface status %4, handler status %5. |
| 0x8a9 | 11 | Excessive PRM handler runtime. Handler GUID %1, module GUID %2, module version %3, duration %4 us. |
| 0x8aa | 11 | Execution at elevated IRQL reached threshold of %2 ticks (DPC ticks: %3 ticks, total ticks: %4 ticks), sequence number %1 for %5. |
| 0x8ab | 11 | cumulative execution |
| 0x8ac | 11 | single Dpc execution |
| 0x8fc | 11 | Pool Tracked Tables |
| 0x8fd | 11 | Processes |
| 0x8fe | 11 | Session Space Structure |
| 0x8ff | 11 | Triage Dump Data |
| 0x900 | 11 | PFN Database |
| 0x901 | 11 | IPT Trace Buffer |
| 0x960 | 11 | Microsoft-Windows-Kernel-CPU-Partition |
| 0x961 | 11 | Microsoft-Windows-Kernel-CPU-Partition/Analytic |
| 0x962 | 11 | CPU Partition violation |
| 0x963 | 11 | An affinitization request (Kernel = %1) for the thread with TID %2 violated CPU Partitions with the following affinity: %4. |
| 0x964 | 11 | A DPC (Pointer = %1) was scheduled on processor %2, across CPU Partition reservations. |
| 0x965 | 11 | A DPC (Pointer = %1) was scheduled as a generic DPC call, across CPU Partition reservations. |
| 0x966 | 11 | An affinitization request violated CPU Partitions |
| 0x967 | 11 | A DPC scheduling request violated CPU Partitions |
| 0x968 | 11 | A generic DPC call request violated CPU Partitions |
| 0xa28 | 11 | Microsoft-Windows-DriverProxy |
| 0xa29 | 11 | Dirver Proxy Performance |
| 0xa2a | 11 | Driver Proxy Operational |
| 0xa2b | 11 | Serviceability |
| 0xa2c | 11 | Performance |
| 0xa2d | 11 | Log |
| 0xa2e | 11 | Driver %2 Average Hot-Swap acquire rundown time in last log period(us):%3; Average Hot-Swap acquire rundown time(us):%4; Total rundown acquire count:%5; Total rundown acquire failure:%6; |
| 0xa2f | 11 | Driver %2 Last Hot-Swap result:%3 (LKG phase=%4); Last Hot-Swap total time (us):%5; Last Hot-Swap pre-process time (us):%6; Last Hot-Swap acquire rundown time (us):%7; Last Hot-Swap driver callback time with rundown lock held (us):%8; Last Hot-Swap post-process time (us):%9; |
| 0xa30 | 11 | Driver %2: %3 |
| 0xbb8 | 11 | Microsoft-Windows-PCI |
| 0xbb9 | 11 | PCI Diagnostic |
| 0xbba | 11 | PCI Operational |
| 0xc1c | 11 | Diagnostic |
| 0xc80 | 11 | Log |
| 0xce4 | 11 | %6 |
| 0x1000001 | 11 | The system time has changed to %1 from %2. Time Delta: %3 ms Change Reason: %4. Process: '%5' (PID %6). RTC time: %7 Current time zone bias: %8 RTC time is in UTC: %9 System time was based on RTC time: %10 |
| 0x1000012 | 11 | The operating system is starting after soft restart. BugcheckRecovery: %4 |
| 0x1000019 | 11 | The system time was initialized to %1. Loader time: %2 Internal boot flags: %3 HAL RTC error code: %4 RTC time is in UTC: %5 Soft boot: %6 Success: %7 Phase: %8 |
| 0x100001a | 11 | Token information was queried for TokenIsAppContainer. |
| 0x100001b | 11 | A Learning Mode policy violation was reported. Process: %1 (PID %2, sequence %3). Category: %4. Denied: %5. |
| 0xc0000ee | 11 | EFI time zone bias: %1. Daylight flags: %2. Firmware time: %3. |
| 0xc0000f2 | 11 | SMM isolation detected. Level: %1 |
| 0xc0000f7 | 11 | Unable to load Pluton-Windows firmware. StatusCode: %1, Reason: %2 |
| 0xc000100 | 11 | AMD DRTM Firmware Anti-Rollback Disabled. |
| 0xc000110 | 11 | PPAM Manifest Info: %1 |
| 0xe000009 | 11 | 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. |
| 0xf00000a | 11 | Failure to load the application settings for package %1. Error Code: %2 |
| 0xf00000b | 11 | Failure to read an application setting for package %1. Error Code: %2 |
| 0xf00000c | 11 | Failure to write an application setting for package %1. Error Code: %2 |
| 0xf00000d | 11 | Failure to instantiate storage folder %1 for package %2 with Error Code: %3 |
| 0xf000014 | 11 | Triggered repair because operation %1 against package %2 hit error %3. |
| 0xf000015 | 11 | Repair for operation %1 against package %2 with error %3 returned Error Code: %4 |
| 0xf000016 | 11 | Folder path %1 failed access check: Error Code: %2 |
| 0xf000017 | 11 | Triggered repair of state locations because operation %1 against package %2 hit error %3. |
| 0xf000018 | 11 | Repair of state locations for operation %1 against package %2 with error %3 returned Error Code: %4 |
| 0x1e000001 | 11 | Process |
| 0x1e000002 | 11 | AppContainer |
| 0x1e000003 | 11 | DesktopAppXProcess |
| 0x1e000004 | 11 | DesktopAppXContainer |
| 0x1f000001 | 11 | Structured State |
| 0x1f000002 | 11 | Unstructured Reset |
| 0x1f000003 | 11 | Out Of Memory |
| 0x1f000004 | 11 | Apiset Error |
| 0x1f000005 | 11 | WinRT |
| 0x1f000006 | 11 | Low-level Data Store Error |
| 0x9d000001 | 11 | Microsoft-Windows-Kernel-ShimEngine |
| 0x9d000002 | 11 | Microsoft-Windows-Kernel-ShimEngine/Operational |
| 0x9e000001 | 11 | Microsoft-Windows-AppModel-Runtime |
| 0x9e000002 | 11 | Microsoft-Windows-AppModel-Runtime/Analytic |
| 0x9f000001 | 11 | Microsoft-Windows-AppModel-State |
| 0x9f000002 | 11 | Microsoft-Windows-AppModel-State/Debug |
| 0x9f000003 | 11 | Microsoft-Windows-AppModel-State/Diagnostic |
| 0xb1000012 | 11 | The operating system is starting after soft restart. |
| 0xb1020001 | 11 | The system time has changed to %1 from %2. Change Reason: %3. Process: '%4' (PID %5). |
| 0xb1030001 | 11 | The system time has changed to %1 from %2. Change Reason: %3. Process: '%4' (PID %5). RTC time: %6 Current time zone bias: %7 RTC time is in UTC: %8 System time was based on RTC time: %9 |
| 0xb202000f | 11 | Enumerated process %1 had started at time %3 by parent %4 running in session %6 with name %11. Enabled security mitigations: %16. |
| 0xb2040001 | 11 | Process %1 started at time %3 by parent %4 running in session %6 with name %11. Enabled security mitigations: %16. |
| 0xb4000018 | 11 | A button notification for ACPI button %2 has been received. Capabilities = %3, EventMask = %4. |
| 0xb4000019 | 11 | A button IRP for ACPI button %2 has been completed. EventMask = %3, IRP = %4. |
| 0xb4000022 | 11 | The strict S4 enforcement _DSM failed evaluation. Status %1. |
| 0xbb00001e | 11 | Provider %1 from process %3 does not have permission to write events to session "%2". Error: %4 |
| 0xbb000020 | 11 | Failed to read debug info for WPP provider %1 from process %3 for session "%2". Error: %4. The image registering the provider may be malformed or may be an unsupported format (e.g. managed C++). ETW traces for this session will not include the image's debug information. |
| 0xbc000039 | 11 | Windows failed to provision the TPM Storage Root Key with error status:%1. Reading SrkPolicy status: %2. SrkSymKeyPolicy value: %3. TPM symmetric key capability: %4. AES bits used: %5. SrkAsymKeyPolicy value: %6. TPM asymmetric key capability: %7. Rsa bits used: %8. |
| 0xbc00003a | 11 | Windows successfully provisioned the TPM Storage Root Key. This operation took %1 milliseconds. Reading SrkPolicy status: %2. SrkSymKeyPolicy value: %3. TPM symmetric key capability: %4. AES bits used: %5. SrkAsymKeyPolicy value: %6. TPM asymmetric key capability: %7. Rsa bits used: %8. |
| 0xbc000052 | 11 | Trace point: Function:%1 Point:%2 Status:%3 |
| 0xbc000053 | 11 | VSM Master Key Array Package Read and Unseal From Disk Status: %1 OsDeviceId: %2 SystemRoot: %3 VsmLKeyRelPath: %4 LatchedUnsealPolicyRelPath: %5 UnlatchedUnsealPolicyRelPath: %6 LatchedPrimaryProtectorVariableName: %7 LatchedSecondaryProtectorVariableName: %8 UnlatchedPrimaryProtectorVariableName: %9 UnlatchedSecondaryProtectorVariableName: %10 LatchedProtectorUsedLocal: %11 LatchTheUnlatchedLocal: %12 UnsupportedRollbackLocal: %13 UpgradedAntirollbackPolicyExistsLocal: %14 PkgWasCorruptOrUnavailableLocal: %15 CreationStateVerifiedLocal: %16 PrimaryProtectorTargetPcrSealMaskLocal: %17 LatchedProtectorExists: %18 UnlatchedProtectorExists: %19 KeyPkgIdTpmCounterValue: %20 ActivePolicyVersion: %21 UseUnlatchedProtector: %22 NeedToResealPrimaryProtector: %23 NeedToResealSecondaryProtector: %24 NeedToResealPca2023Protector: %25 Substatus PrimaryBlobUnsealStatus: %26 BackupBlobUnsealStatus: %27 Pca2023ProtectorUnsealStatus: %28 BackupBlobValidityCheckStatus: %29 BackupBlobStillValid: %30 Pca2023ProtectorValidityCheckStatus: %31 Pca2023ProtectorStillValid: %32 PrimaryBlobResealStatus: %33 BackupBlobResealStatus: %34 Pca2023ProtectorResealStatus: %35 V2ProtectorsUsed: %36 LegacyUefiVarQueryStatus: %37 LegacyUefiVarCleanupStatus: %38 ActivePolicyVersion: %39 LatchedPolicyVersion: %40 UnlatchedPolicyVersion: %41 LatchedUnsealPolicyValid: %42 Latched unseal policy Version: %43 VarDataOffset: %44 StructureSize: %45 PolicyVersion: %46 PolicyHashLength: %47 WinloadSVN: %48 WinresumeSVN: %49 BootmgrSVN: %50 LKeyPkgId: %51 UnlatchedUnsealPolicyValid: %52 Unlatched unseal policy Version: %53 VarDataOffset: %54 StructureSize: %55 PolicyVersion: %56 PolicyHashLength: %57 WinloadSVN: %58 WinresumeSVN: %59 BootmgrSVN: %60 LKeyPkgId: %61 |
| 0xbc000054 | 11 | Seal and Store on Disk Status Status: %1 OsDeviceId: %2 SystemRoot: %3 PcrSealMask: %4 LatchTheUnlatched: %5 UpgradedAntirollbackPolicyExists: %6 EncryptionStatus: %7 KeyPkgIdTpmCounterValue: %8 EncryptedLKeyArrayPkgSize: %9 EncryptedLKeyPkgPdGuid: %10 UnlatchedUnsealPolicySize: %11 UnlatchedProtectorExists: %12 LatchedUnsealPolicySize: %13 LatchedProtectorExists: %14 Latched unseal policy Version: %15 VarDataOffset: %16 StructureSize: %17 PolicyVersion: %18 PolicyHashLength: %19 WinloadSVN: %20 WinresumeSVN: %21 BootmgrSVN: %22 LKeyPkgId: %23 Unlatched unseal policy Version: %24 VarDataOffset: %25 StructureSize: %26 PolicyVersion: %27 PolicyHashLength: %28 WinloadSVN: %29 WinresumeSVN: %30 BootmgrSVN: %31 LKeyPkgId: %32 |
| 0xbc000055 | 11 | Read and Unseal Master Key Array Package Status Status: %1 PrimarySealedBlobName: %2 SecondaryProtectorVariableName: %3 BlobFromUefiVariableSize: %4 UefiContentIsSealed: %5 UnsealedBlobSize: %6 Pcr7SealingUsed: %7 PkgTpmSealMaskLocal: %8 PkgTpmCreationMaskLocal: %9 NeedToResealKeyPkg: %10 NeedToResealBackup: %11 NeedToResealPca2023Backup: %12 PlaintextBlobSize: %13 PlaintextIsLegacyFormat: %14 UefiBlobIsCorrupt: %15 NewKeyID: %16 VerifiedMicrosoftAuthority: %17 ContainsAuthorityData: %18 BootmgrAuthorityEventCount: %19 Authority: %20 Substatus PrimaryBlobUnsealStatus: %21 BackupBlobUnsealStatus: %22 Pca2023ProtectorUnsealStatus: %23 BackupBlobValidityCheckStatus: %24 BackupBlobStillValid: %25 Pca2023ProtectorValidityCheckStatus: %26 Pca2023ProtectorStillValid: %27 PrimaryBlobResealStatus: %28 BackupBlobResealStatus: %29 Pca2023ProtectorResealStatus: %30 V2ProtectorsUsed: %31 LegacyUefiVarQueryStatus: %32 LegacyUefiVarCleanupStatus: %33 ActivePolicyVersion: %34 LatchedPolicyVersion: %35 UnlatchedPolicyVersion: %36 |
| 0xbc000056 | 11 | Get Plaintext Master Key Array Status Status: %1 SecondaryProtectorVariableName: %2 NeedToResealPrimaryProtector: %3 NeedToResealSecondaryProtector: %4 NeedToResealPca2023Protector: %5 SealedBackupEncryptionKeySize: %6 SealedPca2023EncryptionKeySize: %7 UefiBlobIsCorrupt: %8 Pcr7SealingUsed: %9 CreationStateVerifiedLocal: %10 VerifiedMicrosoftAuthority: %11 ContainsAuthorityData: %12 BootmgrAuthorityEventCount: %13 PrimaryProtectorTargetPcrSealMaskLocal: %14 Authority: %15 Substatus PrimaryBlobUnsealStatus: %16 BackupBlobUnsealStatus: %17 Pca2023ProtectorUnsealStatus: %18 BackupBlobValidityCheckStatus: %19 BackupBlobStillValid: %20 Pca2023ProtectorValidityCheckStatus: %21 Pca2023ProtectorStillValid: %22 PrimaryBlobResealStatus: %23 BackupBlobResealStatus: %24 Pca2023ProtectorResealStatus: %25 V2ProtectorsUsed: %26 LegacyUefiVarQueryStatus: %27 LegacyUefiVarCleanupStatus: %28 ActivePolicyVersion: %29 LatchedPolicyVersion: %30 UnlatchedPolicyVersion: %31 Validated Unseal Policy Version: %32 VarDataOffset: %33 StructureSize: %34 PolicyVersion: %35 PolicyHashLength: %36 WinloadSVN: %37 WinresumeSVN: %38 BootmgrSVN: %39 LKeyPkgId: %40 |
| 0xbc000057 | 11 | Read and Unseal Master Key Array Package error LegacyMainBlobVariableName: %1 LegacySecondaryProtectorVariableName: %2 PkgWasCorruptOrUnavailableLocal: %3 KeysAreLegacyLocal: %4 CreationStateVerifiedLocal: %5 PrimaryProtectorTargetPcrSealMaskLocal: %6 Substatus PrimaryBlobUnsealStatus: %7 BackupBlobUnsealStatus: %8 Pca2023ProtectorUnsealStatus: %9 BackupBlobValidityCheckStatus: %10 BackupBlobStillValid: %11 Pca2023ProtectorValidityCheckStatus: %12 Pca2023ProtectorStillValid: %13 PrimaryBlobResealStatus: %14 BackupBlobResealStatus: %15 Pca2023ProtectorResealStatus: %16 V2ProtectorsUsed: %17 LegacyUefiVarQueryStatus: %18 LegacyUefiVarCleanupStatus: %19 ActivePolicyVersion: %20 LatchedPolicyVersion: %21 UnlatchedPolicyVersion: %22 |
| 0xbc000058 | 11 | Read and Unseal Master Key Array Package Status Status: %1 OsDeviceId: %2 OsDataDeviceId: %3 SystemRoot: %4 VsmLKeyRelPath: %5 LatchedUnsealPolicyRelPath: %6 UnlatchedUnsealPolicyRelPath: %7 LatchedPrimaryProtectorVariableName: %8 LatchedSecondaryProtectorVariableName: %9 UnlatchedPrimaryProtectorVariableName: %10 UnlatchedSecondaryProtectorVariableName: %11 LegacyMainBlobVariableName: %12 LegacySecondaryProtectorVariableName: %13 LatchedProtectorUsedLocal: %14 LatchTheUnlatchedLocal: %15 UnsupportedRollbackLocal: %16 UpgradedAntirollbackPolicyExistsLocal: %17 FirstWriteToDiskLocal: %18 WritePkgToUefiLocal: %19 PkgWasCorruptOrUnavailableLocal: %20 KeysAreLegacyLocal: %21 CreationStateVerifiedLocal: %22 PrimaryProtectorTargetPcrSealMaskLocal: %23 Substatus PrimaryBlobUnsealStatus: %24 BackupBlobUnsealStatus: %25 Pca2023ProtectorUnsealStatus: %26 BackupBlobValidityCheckStatus: %27 BackupBlobStillValid: %28 Pca2023ProtectorValidityCheckStatus: %29 Pca2023ProtectorStillValid: %30 PrimaryBlobResealStatus: %31 BackupBlobResealStatus: %32 Pca2023ProtectorResealStatus: %33 V2ProtectorsUsed: %34 LegacyUefiVarQueryStatus: %35 LegacyUefiVarCleanupStatus: %36 ActivePolicyVersion: %37 LatchedPolicyVersion: %38 UnlatchedPolicyVersion: %39 |
| 0xbc000059 | 11 | Create Sealed Encrypt Key Status Status: %1 PcrMask: %2 UnsealPolicyPdGuid: %3 SealingProtectorFixedBufferSize: %4 SealingProtectorUsedBufferSize: %5 SealedSecretBufferSize: %6 PcrInfoArrayElCount: %7 Unseal policy Version: %8 VarDataOffset: %9 StructureSize: %10 PolicyVersion: %11 PolicyHashLength: %12 WinloadSVN: %13 WinresumeSVN: %14 BootmgrSVN: %15 LKeyPkgId: %16 |
| 0xbc00005a | 11 | Get Sealed Protector Status Status: %1 ProtectorName: %2 SealedEncryptionKeySize: %3 ProtectorBlobFromUefiVariableSize: %4 |
| 0xbc00005b | 11 | SRTM PCR Values algId: %1 digestLength:%2 PcrIndex: %3 PcrValue: %4 |
| 0xbc0000aa | 11 | Measured Boot Measurement Failure. Status: %1 |
| 0xbc0000ab | 11 | TPM Measurement Failure. Status: %1 |
| 0xbc0000ac | 11 | Failure to close TCG log. Status: %1 |
| 0xbc0000b9 | 11 | Soft Restart driver failed to store BCD store when BCDCache is enabled with status: %1 |
| 0xbc0000ba | 11 | Soft Restart driver failed to query MEMDISK configuration from the current OS with status: %1 |
| 0xbc0000ee | 11 | EFI time zone bias: %1. Daylight flags: %2. |
| 0xbc0000f3 | 11 | Hardware memory mirroring support is enabled. |
| 0xbc0000f8 | 11 | Previous error detected while attempting to execute Measured Launch Environment. Source: %1 Error code: %2. |
| 0xbc0000fc | 11 | This system has not supplied a valid framebuffer and the graphical boot menu is not used. |
| 0xbc0000fd | 11 | HotPatch %4 failed to apply with Status: %2 at failure point: %1. |
| 0xbc000101 | 11 | Failed to build image path for dump stack module %1. Status: %2. |
| 0xbc000102 | 11 | Failed to load dump stack module %1. Status: %2. |
| 0xbc000103 | 11 | Early dump stack succesfully loaded by OS loader. |
| 0xbc000104 | 11 | Early boot crash dump generation is not supported. |
| 0xbc000105 | 11 | Soft restart prepare was vetoed by component %2 with status %1. |
| 0xbc000106 | 11 | Soft restart finalize was vetoed by component %2 with status %1. |
| 0xbc000107 | 11 | Early crash dump support is disabled by registry configuration. |
| 0xbc000108 | 11 | Failed to query early dump enablement information from the registry with status %1. |
| 0xbc000109 | 11 | Failed to query dedicated dump file name for the target OS with status %1. Early crash dump functinality will not be loaded. |
| 0xbc00010a | 11 | Dedicated dump file names do not match (%1, %2). Early crash dump functinality will not be loaded. |
| 0xbc00010b | 11 | Failed to query dump module list. Status: %1. |
| 0xbc00010c | 11 | Boot Application %1 dropped %2 events during logging. |
| 0xbc00010e | 11 | Cached boot BCD store was loaded by the boot environment. |
| 0xbc000111 | 11 | BCD Option '%1' was not applied due to Secure Boot being enabled. Option: %2 |
| 0xbc000113 | 11 | ACM InfoTable version used: %1. |
| 0xbc000127 | 11 | Secure Boot revoked boot app %4 with SVN %1. Min SVN required: %2. Status: %3. |
| 0xbc000138 | 11 | Failed to compose API Set schema extension with status: %1 |
| 0xbc010032 | 11 | Windows failed to provision VSM Master Encryption Key. Using cached copy status: %1. Primary Blob Unseal Status: %2. Backup Blob Unseal Status: %3. Pca2023 Protector Unseal Status: %4. Backup Blob Validity Check Status: %5. Backup Blob Validity Check Result: %6. Pca2023 Protector Validity Check Status: %7. Pca2023 Protector Validity Check Result: %8. Primary Blob Reseal Status: %9. Backup Blob Reseal Status: %10. Pca2023 Protector Reseal Status: %11. New key generation status: %12. Sealing status: %13. TPM PCR mask: %14. Tpm Counter validation status: %15. Tpm Counter creation status: %16. Backup sealed blob used: %17. Pca2023 Protector cleaned up post upgrade status: %18. |
| 0xbc010033 | 11 | VSM Master Encryption Key Provisioning. Using cached copy status: %1. Primary Blob Unseal Status: %2. Backup Blob Unseal Status: %3. Pca2023 Protector Unseal Status: %4. Backup Blob Validity Check Status: %5. Backup Blob Validity Check Result: %6. Pca2023 Protector Validity Check Status: %7. Pca2023 Protector Validity Check Result: %8. Primary Blob Reseal Status: %9. Backup Blob Reseal Status: %10. Pca2023 Protector Reseal Status: %11. New key generation status: %12. Sealing status: %13. TPM PCR mask: %14. Tpm Counter validation status: %15. Tpm Counter creation status: %16. Backup sealed blob used: %17. Pca2023 Protector cleaned up post upgrade status: %18. |
| 0xbc01004a | 11 | Windows failed to provision DRTM-bound VSM Master Encryption Key . Using cached copy status: %1. New key generation status: %2. Sealing status: %3. UEFI keys provided to Secure Kernel status: %4. UnLatchedCiPolicy version: %5. LatchedCiPolicyVersion: %6. LatchedAntiRollbackCounterValue: %7. CurrentCiPolicyVersion: %8. CurrentAntiRollbackCounterValue: %9. MinimumUnsealCiPolicyVersion: %10. AuthorizationIsDelegated: %11. |
| 0xbc01004b | 11 | Windows successfully provisioned DRTM-bound VSM Master Encryption Key. Using cached copy status: %1. New key generation status: %2. Sealing status: %3. UEFI keys provided to Secure Kernel status: %4. UnLatchedCiPolicy version: %5. LatchedCiPolicyVersion: %6. LatchedAntiRollbackCounterValue: %7. CurrentCiPolicyVersion: %8. CurrentAntiRollbackCounterValue: %9. MinimumUnsealCiPolicyVersion: %10. AuthorizationIsDelegated: %11. |
| 0xbc010050 | 11 | FASR Platform Verification. FASR cert present: %1. FASR cert signature validation status: %2. BootmgrAuthorityEventCount: %3. VerifiedMicrosoftAuthority: %4. FASR PCR values validation status: %5. PCR mismatch index: %6. FASR cert size: %7. FASR cert: %8. FASR signature size: %9. FASR signature: %10. |
| 0xbc01008e | 11 | Soft Restart failed to register with Soft Restart extension. The versions are not compatible. Status: %1, Vtl: %4 |
| 0xbc0100f8 | 11 | Previous error detected while attempting to execute Measured Launch Environment. AMDSL error code: %1. |
| 0xbc020032 | 11 | Windows failed to provision VSM Master Encryption Key. Using cached copy status: %1. Primary Blob Unseal Status: %2. Backup Blob Unseal Status: %3. Pca2023 Protector Unseal Status: %4. Backup Blob Validity Check Status: %5. Backup Blob Validity Check Result: %6. Pca2023 Protector Validity Check Status: %7. Pca2023 Protector Validity Check Result: %8. Primary Blob Reseal Status: %9. Backup Blob Reseal Status: %10. Pca2023 Protector Reseal Status: %11. New key generation status: %12. Sealing status: %13. TPM PCR mask: %14. Tpm Counter validation status: %15. Tpm Counter creation status: %16. Backup sealed blob used: %17. Pca2023 Protector cleaned up post upgrade status: %18. Need To Roll Lkey: %19. CreationState Verified: %20. V2 Protectors Used: %21. Legacy UEFI Var Query Status: %22. Legacy UEFI Var Cleanup Status: %23. VBS Data Protection Enabled: %24. Vbs Data Protection Opted In Registry: %25. Vbs Data Protection TPM Counter Status: %26. First Pkg Write To Disk: %27. Write Pkg To UEFI: %28. Latched Protector Used: %29. Update Latched Protectors: %30. Unsupported Rollback: %31. Upgraded VBS Policy Exists: %32. TPM Counter Increment Status: %33. Active Policy Version: %34. Latched Policy Version: %35. Unlatched Policy Version: %36. Latched Primary Blob Reseal Status: %37. Latched Backup Blob Reseal Status: %38. Latched Pca2023 Protector Reseal Status: %39. Latched Pca2023 Protector Cleanup PostUpgrade Status: %40. Unlatched Primary Blob Reseal Status: %41. Unlatched Backup Blob Reseal Status: %42. Unlatched Pca2023 Protector Reseal Status: %43. Unlatched Pca2023 Protector Cleanup PostUpgrade Status: %44. |
| 0xbc020033 | 11 | VSM Master Encryption Key Provisioning. Using cached copy status: %1. Primary Blob Unseal Status: %2. Backup Blob Unseal Status: %3. Pca2023 Protector Unseal Status: %4. Backup Blob Validity Check Status: %5. Backup Blob Validity Check Result: %6. Pca2023 Protector Validity Check Status: %7. Pca2023 Protector Validity Check Result: %8. Primary Blob Reseal Status: %9. Backup Blob Reseal Status: %10. Pca2023 Protector Reseal Status: %11. New key generation status: %12. Sealing status: %13. TPM PCR mask: %14. Tpm Counter validation status: %15. Tpm Counter creation status: %16. Backup sealed blob used: %17. Pca2023 Protector cleaned up post upgrade status: %18. Need To Roll Lkey: %19. CreationState Verified: %20. V2 Protectors Used: %21. Legacy UEFI Var Query Status: %22. Legacy UEFI Var Cleanup Status: %23. VBS Data Protection Enabled: %24. Vbs Data Protection Opted In Registry: %25. Vbs Data Protection TPM Counter Status: %26. First Pkg Write To Disk: %27. Write Pkg To UEFI: %28. Latched Protector Used: %29. Update Latched Protectors: %30. Unsupported Rollback: %31. Upgraded VBS Policy Exists: %32. TPM Counter Increment Status: %33. Active Policy Version: %34. Latched Policy Version: %35. Unlatched Policy Version: %36. Latched Primary Blob Reseal Status: %37. Latched Backup Blob Reseal Status: %38. Latched Pca2023 Protector Reseal Status: %39. Latched Pca2023 Protector Cleanup PostUpgrade Status: %40. Unlatched Primary Blob Reseal Status: %41. Unlatched Backup Blob Reseal Status: %42. Unlatched Pca2023 Protector Reseal Status: %43. Unlatched Pca2023 Protector Cleanup PostUpgrade Status: %44. |
| 0xbc030032 | 11 | Windows failed to provision VSM Master Encryption Key. Using cached copy status: %1. Primary Blob Unseal Status: %2. Backup Blob Unseal Status: %3. Pca2023 Protector Unseal Status: %4. LostOemPk Protector Unseal Status: %5. Backup Blob Validity Check Status: %6. Backup Blob Validity Check Result: %7. Pca2023 Protector Validity Check Status: %8. Pca2023 Protector Validity Check Result: %9. Primary Blob Reseal Status: %10. Backup Blob Reseal Status: %11. Pca2023 Protector Reseal Status: %12. New key generation status: %13. Sealing status: %14. TPM PCR mask: %15. Tpm Counter validation status: %16. Tpm Counter creation status: %17. Backup sealed blob used: %18. Pca2023 Protector cleaned up post upgrade status: %19. |
| 0xbc030033 | 11 | VSM Master Encryption Key Provisioning. Using cached copy status: %1. Primary Blob Unseal Status: %2. Backup Blob Unseal Status: %3. Pca2023 Protector Unseal Status: %4. LostOemPk Protector Unseal Status: %5. Backup Blob Validity Check Status: %6. Backup Blob Validity Check Result: %7. Pca2023 Protector Validity Check Status: %8. Pca2023 Protector Validity Check Result: %9. Primary Blob Reseal Status: %10. Backup Blob Reseal Status: %11. Pca2023 Protector Reseal Status: %12. New key generation status: %13. Sealing status: %14. TPM PCR mask: %15. Tpm Counter validation status: %16. Tpm Counter creation status: %17. Backup sealed blob used: %18. Pca2023 Protector cleaned up post upgrade status: %19. |
| 0xbd010003 | 11 | %3 shim(s) were applied to driver [%1]. Shim(s) source: %2. Shim GUID(s): %4. |
| 0xbd010004 | 11 | Flags [%4] were applied to device [%1] - class [%2]. Flags source: %3. |
| 0xbe000001 | 11 | Process %1 started at time %2 by parent %3 running as package %4 with executable %5 is application %6. |
| 0xbe000002 | 11 | %2: Cannot create the process for package %1 because an error was encountered. %3 |
| 0xbe000003 | 11 | %2: Cannot create the process for package %1 because an error was encountered while querying the fast cache. %3 |
| 0xbe000004 | 11 | %2: Cannot create the process for package %1 because an error was encountered while preparing the App credentials. %3 |
| 0xbe000005 | 11 | %2: Cannot create the process for package %1 because an error was encountered while checking the user-level package status. %3 |
| 0xbe000006 | 11 | %2: Cannot create the process for package %1 because an error was encountered while checking the machine-level package status. %3 |
| 0xbe000007 | 11 | %2: Cannot create the process for package %1 because an error was encountered while verifying the App credentials. %3 |
| 0xbe000008 | 11 | 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. |
| 0xbe00000b | 11 | 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. |
| 0xbe00000c | 11 | 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. |
| 0xbe00000e | 11 | %2: Package runtime information %1 is corrupted (address=%5, size=%3, offset=%4, section=%6, processid=%7). Reinstall the package to fix this issue. |
| 0xbe00000f | 11 | %2: Package runtime information %1 is missing expected data (address=%4, size=%3, section=%5, processid=%6). Reinstall the package to fix this issue. |
| 0xbe000010 | 11 | %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. |
| 0xbe000011 | 11 | %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. |
| 0xbe000012 | 11 | %2: Package runtime information %1 failed to load (processid=%3). |
| 0xbe000013 | 11 | Package runtime information %1 failed to load because exception %2 occurred. |
| 0xbe000014 | 11 | %2: Cannot create the process for package %1 because an error was encountered while loading the runtime information. %3 |
| 0xbe000015 | 11 | CreateAppContainerProfile failed for AppContainer %2 with error %1. |
| 0xbe000016 | 11 | DeleteAppContainerProfile failed for AppContainer %2 with error %1. |
| 0xbe000017 | 11 | UpdateAppContainerProfile failed for AppContainer %2 with error %1. |
| 0xbe000018 | 11 | CreateAppContainerProfile failed with error %1 because it was unable to create registry key %2. |
| 0xbe000019 | 11 | CreateAppContainerProfile failed with error %1 because it was unable to set security on registry key %2. |
| 0xbe00001a | 11 | AppContainer profile failed with error %1 because it was unable to delete registry key %2. |
| 0xbe00001b | 11 | CreateAppContainerProfile failed with error %1 because it was unable to create folder %2. |
| 0xbe00001c | 11 | CreateAppContainerProfile failed with error %1 because it was unable to set attributes on folder %2. |
| 0xbe00001d | 11 | CreateAppContainerProfile failed with error %1 because it was unable to verify the existence of registry key %2. |
| 0xbe00001e | 11 | CreateAppContainerProfile failed with error %1 because it was unable to verify the existence of folder %2. |
| 0xbe00001f | 11 | CreateAppContainerProfile failed with error %1 because it was unable to find the users local app data folder. |
| 0xbe000020 | 11 | AppContainer profile failed with error %1 because it was unable to delete folder %2 or its contents. |
| 0xbe000021 | 11 | AppContainer profile failed with error %1 because it was unable to look up the AppContainer name. |
| 0xbe000022 | 11 | AppContainer profile failed with error %1 because it was unable to look up the AppContainer display name. |
| 0xbe000023 | 11 | CreateAppContainerProfile failed with error %1 because it was unable to register with the firewall. |
| 0xbe000024 | 11 | DeleteAppContainerProfile failed with error %1 because it was unable to unregister with the firewall. |
| 0xbe000025 | 11 | App Container profile failed with error %1 because it was unable to register the AppContainer SID. |
| 0xbe000026 | 11 | DeleteAppContainerProfile failed with error %1 because it was unable to unregister the AppContainer SID. |
| 0xbe000027 | 11 | Successfully created AppContainer %1. |
| 0xbe000028 | 11 | AppContainer %1 was not created because it already exists. |
| 0xbe000029 | 11 | Successfully deleted AppContainer %1. |
| 0xbe00002a | 11 | Successfully updated AppContainer %1. |
| 0xbe00002b | 11 | %2: Package runtime information %1 is missing expected data (address=%4, size=%3, section=%5, processid=%6). Reinstall the package to fix this issue. |
| 0xbe00002c | 11 | %2: Application identity not accessible while loading package runtime information %1 (address=%4, size=%3, processid=%5). |
| 0xbe00002d | 11 | Failed with %1 while retrieving AppContainer %2 information during interaction with Restricted AppContainer. |
| 0xbe00002e | 11 | Failed with %1 while retrieving AppContainer information during interaction with Restricted AppContainer. |
| 0xbe00002f | 11 | Failed with %1 while retrieving AppContainer information. Call invalid from this process type. |
| 0xbe000030 | 11 | Failed to create shared context object for Restricted AppContainer %2 with %1. |
| 0xbe000031 | 11 | Failed to activate Restricted AppContainer %2 with %1. |
| 0xbe000032 | 11 | Creation of Restricted AppContainer %2 failed with %1 because an invalid capability was specified. |
| 0xbe000033 | 11 | Opening existing Restricted AppContainer %2 failed with %1 because the capabilities storage value could not be read. |
| 0xbe000034 | 11 | Failed to create the capabilities storage value for Restricted AppContainer %2 with %1. |
| 0xbe000035 | 11 | The package %1 requires validation. |
| 0xbe000036 | 11 | Modification was detected in package %1. |
| 0xbe000037 | 11 | Failed to terminate app with package %1. |
| 0xbe000038 | 11 | Validation of app with package %1 was successful. |
| 0xbe000039 | 11 | Failed with %1 to retrieve the trust state of the package %2 folder. |
| 0xbe00003a | 11 | App Integrity check failed with %1 while checking %2. |
| 0xbe00003b | 11 | App Integrity terminated an application. Integrity check for %2 returned %1. |
| 0xbe00003c | 11 | App Integrity check for %1 timed out. |
| 0xbe00003d | 11 | %2: Cannot create the process for package %1 because an error was encountered while performing the integrity check. %3 |
| 0xbe00003e | 11 | Deployment server integrity check of package %1 failed with %2. |
| 0xbe00003f | 11 | Failed with %1 retrieving AppModel Runtime group policy values. |
| 0xbe000040 | 11 | Failed with %1 validating AppModel Runtime group policy values. |
| 0xbe000041 | 11 | Failed with %1 retrieving AppModel Runtime status for package %2. |
| 0xbe000042 | 11 | Failed with %1 retrieving AppModel Runtime status for package %2 for user %3. |
| 0xbe000043 | 11 | Failed with %1 modifying AppModel Runtime status for package %2 (current status = %4, desired status = %3). |
| 0xbe000044 | 11 | AppModel Runtime status for package %1 successfully updated to %2 (previous status = %3). |
| 0xbe000045 | 11 | Failed with %1 modifying AppModel Runtime status for package %2 for user %3 (clear=%4, set=%5). |
| 0xbe000046 | 11 | Successfully updated AppModel Runtime status for package %1 for user %2 (clear=%3, set=%4). |
| 0xbe000047 | 11 | Failed with %1 modifying AppModel Runtime status version (context = %2). |
| 0xbe000048 | 11 | AppModel Runtime status version successfully updated. |
| 0xbe000049 | 11 | %2: Cannot create the process for package %1 because an error was encountered while performing the app data creation. %3 |
| 0xbe00004a | 11 | Package runtime information %1 failed to refresh because the following error %2 occurred in operation type %3. |
| 0xbe00004b | 11 | error %2: Cannot register the %1 package because the following error was encountered while opening the HKEY_USERS registry key |
| 0xbe00004c | 11 | error %4: Cannot register the %1 package because the following error was encountered while enumerating to remove the %2\%3 package family registry key |
| 0xbe00004d | 11 | error %4 : Cannot register the %1 package because the following error was encountered while creating the %2\%3 package family registry key |
| 0xbe00004e | 11 | error %4: Cannot register the %1 package because the following error was encountered while removing the %2\%3 package family registry key |
| 0xbe00004f | 11 | %2: Package family %1 runtime information is corrupted. Attempting to correct the issue. |
| 0xbe000050 | 11 | %2: Package family %1 runtime information is corrupted but we cannot repair it at this time. |
| 0xbe000051 | 11 | Failed with %1 to get IsPackageStageInPlace info from State Repository cache for package %2. The app will by default require integrity check. |
| 0xbe000065 | 11 | Creating AppContainer %1. |
| 0xbe000066 | 11 | Finished creating AppContainer %2 with %1. |
| 0xbe000067 | 11 | Deleting AppContainer %1. |
| 0xbe000068 | 11 | Finished deleting AppContainer %2 with %1. |
| 0xbe000069 | 11 | Updating AppContainer %1. |
| 0xbe00006a | 11 | Finished updating AppContainer %2 with %1. |
| 0xbe00006b | 11 | Creating firewall rules for AppContainer %1. |
| 0xbe00006c | 11 | Finished creating firewall rules for AppContainer %2 with %1. |
| 0xbe00006d | 11 | Deleting firewall rules for AppContainer %1. |
| 0xbe00006e | 11 | Finished deleting firewall rules for AppContainer %2 with %1. |
| 0xbe00006f | 11 | Creating Restricted AppContainer %1. |
| 0xbe000070 | 11 | Finished creating Restricted AppContainer %2 with %1. |
| 0xbe000071 | 11 | Deleting Restricted AppContainer %1. |
| 0xbe000072 | 11 | Finished deleting Restricted AppContainer %2 with %1. |
| 0xbe000073 | 11 | Opening Restricted AppContainer %1. |
| 0xbe000074 | 11 | Finished opening Restricted AppContainer %2 with %1. |
| 0xbe000075 | 11 | Enumerating all Restricted AppContainers for %1. |
| 0xbe000076 | 11 | Finished enumerating all Restricted AppContainers for AppContainer %2 with %1. |
| 0xbe000077 | 11 | Launching process in Restricted AppContainer %1. |
| 0xbe000078 | 11 | Finished launching process in Restricted AppContainer %2 with %1. |
| 0xbe000079 | 11 | Terminating all processes in Restricted AppContainer %1. |
| 0xbe00007a | 11 | Finished terminating all processes in Restricted AppContainer %2 with %1. |
| 0xbe00007b | 11 | Checking package graph for %1. |
| 0xbe00007c | 11 | Package graph check for %2 finished with %1. |
| 0xbe00007d | 11 | Performing app integrity check for package %1. |
| 0xbe00007e | 11 | App integrity check for package %2 finished with %1. |
| 0xbe00007f | 11 | Performing runtime app integrity check for package %1. |
| 0xbe000080 | 11 | Runtime app integrity check for package %2 finished with %1. |
| 0xbe000081 | 11 | Firewall Service not running. Skipping creation of firewall rules for AppContainer %1. |
| 0xbe000082 | 11 | Updating Restricted AppContainer Capabilities %1. |
| 0xbe000083 | 11 | Finished Updating Restricted AppContainer Capabilities %2 with %1. |
| 0xbe0000c9 | 11 | Created process %1 for application %4 in package %2. %5 |
| 0xbe0000ca | 11 | %4: Cannot create the process for package %1 because an error was encountered. %5 |
| 0xbe0000cb | 11 | %4: Cannot create the process for package %1 because an error was encountered while preparing for activation. %5 |
| 0xbe0000cc | 11 | %4: Cannot create the process for package %1 because an error was encountered while elevating the token. %5 |
| 0xbe0000cd | 11 | %4: Cannot create the process for package %1 because UI Access is not supported for Desktop AppX processes. %5 |
| 0xbe0000ce | 11 | %4: Cannot create the process for package %1 because an error was encountered while adjusting the token. %5 |
| 0xbe0000cf | 11 | %4: Cannot create the process for package %1 because an error was encountered while launching. %5 |
| 0xbe0000d0 | 11 | %4: Cannot create the process for package %1 because an error was encountered while configuring runtime. %5 |
| 0xbe0000d1 | 11 | %4: Cannot create the process for package %1 because an error was encountered while resuming the thread. %5 |
| 0xbe0000d2 | 11 | Created Desktop AppX container %3 for package %1. |
| 0xbe0000d3 | 11 | Added process %1 to Desktop AppX container %3 for package %2. |
| 0xbe0000d4 | 11 | %1: Cannot add process %2 to Desktop AppX container %4 for package %3 because an error was encountered. |
| 0xbe0000d5 | 11 | %1: Cannot create the Desktop AppX container for package %2 because an error was encountered creating the job. |
| 0xbe0000d6 | 11 | %1: Cannot create the Desktop AppX container for package %2 because an error was encountered creating the description. |
| 0xbe0000d7 | 11 | %1: Cannot create the Desktop AppX container for package %2 because an error was encountered converting the job. |
| 0xbe0000d8 | 11 | %1: Cannot create the Desktop AppX container for package %2 because an error was encountered configuring the runtime. |
| 0xbe0000d9 | 11 | Destroyed Desktop AppX container %2 for package %1. |
| 0xbe0000da | 11 | Cannot destroy Desktop AppX container %2 for package %1. |
| 0xbe0000db | 11 | PSMFlags for Desktop AppX process %1 with applicationID %2 is %3. |
| 0xbe0000dc | 11 | Cannot start the process %2 because the executable was not found the package %1. |
| 0xbe0000dd | 11 | GetClientInformationFailureFromTokenForSxs failed with error %1 with applicationID %2. State:%3 . |
| 0xbf000001 | 11 | Error while deleting file: %1. Error Code: %2 |
| 0xbf000002 | 11 | Error while deleting directory: %1. Error Code: %2 |
| 0xbf000003 | 11 | Error while allocating memory |
| 0xbf000004 | 11 | ApiSet Function: %1 returned with Error Code: %2 |
| 0xbf000005 | 11 | Low-level data store access error. Function: %1 returned with Error Code: %2 |
| 0xbf000006 | 11 | Cleanup of temporary state has been skipped due to low disk usage. |
| 0xbf000007 | 11 | Cleanup of temporary state has completed. |
| 0xbf000008 | 11 | Cleanup of temporary state was unable to enumerate the user profiles. Object: %1, Error Code: %2. |
| 0xbf000009 | 11 | Cleanup of temporary state has aborted unexpectedly. |
| 0xbf00000e | 11 | Need to update state locations of package %1 for user %2 because the schema is not found. Error Code: %3 |
| 0xbf00000f | 11 | Need to update state locations of package %1 for user %2 because the package is not found. Error Code: %3 |
| 0xbf000010 | 11 | Need to update state locations of package %1 for user %2 because the package full name has changed. Error Code: %3 |
| 0xbf000011 | 11 | Need to update state locations of package %1 for user %2 because the schema version has changed. Error Code: %3 |
| 0xbf000012 | 11 | Succeeded to fix state locations for package %1. |
| 0xbf000013 | 11 | Failure to fix state locations for package %1. Error Code: %2 |
| 0xd4000011 | 11 | Fan speed reporting is unsupported |
| 0xdc000008 | 11 | disabled due to hardware constraints |
| 0xdc000009 | 11 | disabled due to VBS anti-rollback policy is missing |
| 0xdc00000a | 11 | enabled due to VBS registry configuration |
| 0xdc00000b | 11 | enabled due to HyperV |
| 0xdc00000c | 11 | enabled due to VBS locked configuration |
| 0xdc00000d | 11 | enabled due to Code Integrity policy |
| 0xdc00000e | 11 | enabled due to Velocity |
| 0xdc00000f | 11 | enabled due to Hardware constraints |
| 0xdc000010 | 11 | BL_LOG_INFO_NONE: Info none |
| 0xdc000011 | 11 | BL_LOG_INFO_BLI_IO_INITED: IO initialized in boot library initialization. |
| 0xdc000012 | 11 | BL_LOG_INFO_BLI_FINISHED: Finished in boot library initialization. |
| 0xdc000013 | 11 | BL_LOG_INFO_BM_BL_INITED: The boot library has been initialized for bootmgr. |
| 0xdc000014 | 11 | BL_LOG_INFO_BM_GET_BOOT_SEQ: Getting boot sequence in bootmgr. |
| 0xdc000015 | 11 | BL_LOG_INFO_BM_LAUNCH_ENTRY: Launching boot entry in bootmgr. |
| 0xdc000016 | 11 | BL_LOG_INFO_BM_URI_UDP_REDIRECT: Attempting to redirect URI device to UDP device in bootmgr. |
| 0xdc000017 | 11 | BL_LOG_INFO_BM_BL_DESTROYED: The boot library about to be destroyed for bootmgr. |
| 0xdc000018 | 11 | BL_LOG_INFO_BM_RESTART: The bootmgr is about to be restarted. |
| 0xdc000019 | 11 | BL_LOG_INFO_WDS_BL_INITED: The boot library has been initialized for wdsmgr. |
| 0xdc00001a | 11 | BL_LOG_INFO_WDS_BL_DESTROYED: The boot library about to be destroyed for wdsmgr. |
| 0xdc00001b | 11 | BL_LOG_INFO_OSL_PREPARE_ENTERED: Reached prepare target within osloader. |
| 0xdc00001c | 11 | BL_LOG_INFO_OSL_OPEN_DEVICE: Preparing to open OS device in osloader. |
| 0xdc00001d | 11 | BL_LOG_INFO_OSL_LOAD_HYPERV: Loaded hypervisor if enabled. |
| 0xdc00001e | 11 | BL_LOG_INFO_OSL_LOAD_MODULES: Preparing to load OS modules within osloader. |
| 0xdc00001f | 11 | BL_LOG_INFO_OSL_KERNEL_SETUP: Setting up kernel within osloader. |
| 0xdc000020 | 11 | BL_LOG_INFO_OSL_PRELOAD_HYPERV: Preloaded hypervisor if enabled. |
| 0xdc000021 | 11 | BL_LOG_INFO_OSL_BOOT_CANCELLED: Boot was cancelled. |
| 0xdc000022 | 11 | BL_LOG_INFO_OSL_VSM_HIBERFILE_REPLAY_PROTECTION_PROVISION: TPM provisioned for the Hiberfile replay protection |
| 0xdc000023 | 11 | BL_LOG_INFO_TCB_LAUNCH_HYPERV: Preparing to launch hyper-v. |
| 0xdc000024 | 11 | BL_LOG_ERROR: Generic Error |
| 0xdc000025 | 11 | BL_LOG_ERROR_BLI_NET_INIT: BlNetInitialize failed in BL initialization. |
| 0xdc000026 | 11 | BL_LOG_ERROR_BLI_UTL_INIT: BlUtlInitialize failed in BL initialization. |
| 0xdc000027 | 11 | BL_LOG_ERROR_BLI_SEC_BOOT_INIT: BlSecureBootInitialize failed in BL initialization. |
| 0xdc000028 | 11 | BL_LOG_ERROR_BLI_PDATA_INIT: BlpPdInitialize failed in BL initialization. |
| 0xdc000029 | 11 | BL_LOG_ERROR_BLI_RES_INIT: BlpResourceInitialize failed in BL initialization. |
| 0xdc00002a | 11 | BL_LOG_ERROR_BLI_SEC_LAUNCH_INIT: BlpTcbLaunchInitialize failed in BL initialization. |
| 0xdc00002b | 11 | ERROR_BLI_CIPOLICY_BOOT_INIT: BlpSIPolicyInitialize failed in BL initialization. |
| 0xdc00002c | 11 | BL_LOG_ERROR_BLI_REFS_VOLUME_MOUNT: ReFS volume mount failed. |
| 0xdc00002d | 11 | BL_LOG_ERROR_BM_INIT_MACH_POL: BmSecureBootInitializeMachinePolicy failed in bootmgr. |
| 0xdc00002e | 11 | BL_LOG_ERROR_BM_FW_REG_SYSINT: BmFwRegisterSystemIntegrityPolicies failed in bootmgr. |
| 0xdc00002f | 11 | BL_LOG_ERROR_BM_RES_FIND_HTML: BlResourceFindHtml failed to find BOOTMGR.XSL in bootmgr. |
| 0xdc000030 | 11 | BL_LOG_ERROR_BM_XMI_INIT: BlXmiInitialize failed in bootmgr. |
| 0xdc000031 | 11 | BL_LOG_ERROR_BM_OPEN_DATA_STORE: BmOpenDataStore failed in bootmgr. |
| 0xdc000032 | 11 | BL_LOG_ERROR_BM_SELF_INT_CHK: BmpSelfIntegrityCheck failed in bootmgr. |
| 0xdc000033 | 11 | BL_LOG_ERROR_BM_FW_REG_REV_LIST: BmFwRegisterRevocationList failed in bootmgr. |
| 0xdc000034 | 11 | BL_LOG_ERROR_BM_RESUME_HIBER: BmResumeFromHibernate failed in bootmgr. |
| 0xdc000035 | 11 | BL_LOG_ERROR_BM_PURGE_OPT_START_SEQ: BL_ERROR_BM_PURGE_OPT_START_SEQ failed in bootmgr. |
| 0xdc000036 | 11 | BL_LOG_ERROR_BM_PURGE_OPT_BOOT_SEQ: BmPurgeOption failed for BCDE_BOOTMGR_TYPE_BOOT_SEQUENCE in bootmgr. |
| 0xdc000037 | 11 | BL_LOG_ERROR_BM_REOPEN_DATA_STORE: BmOpenDataStore failed on reopen in bootmgr. |
| 0xdc000038 | 11 | BL_LOG_ERROR_BM_UPDATE_APP_OPTS: BmpUpdateApplicationOptions failed in bootmgr. |
| 0xdc000039 | 11 | BL_LOG_ERROR_BM_LAUNCH_BOOT_ENTRY: BmpLaunchBootEntry failed in bootmgr. |
| 0xdc00003a | 11 | BL_LOG_ERROR_BM_CREATE_DEVICES: BmpCreateDevices failed in bootmgr. |
| 0xdc00003b | 11 | BL_LOG_ERROR_BM_LAUNCH_FLIGHT_BM: BmFwLaunchFlightedBootmgr failed in bootmgr. |
| 0xdc00003c | 11 | BL_LOG_ERROR_BM_FE_BOOTAPP_LD: Fatal error: failure to load boot app in bootmgr. |
| 0xdc00003d | 11 | BL_LOG_ERROR_BM_FE_CONFIG_DATA: Fatal error: failure attempting to read boot config file in bootmgr. |
| 0xdc00003e | 11 | BL_LOG_ERROR_BM_FE_NO_VALID_OS_ENTRY: Fatal error: no valid os entires found in bootmgr. |
| 0xdc00003f | 11 | BL_LOG_ERROR_BM_FE_NO_VALID_PXE_ENTRY: Fatal error: no valid entries found from PXE server in bootmgr. |
| 0xdc000040 | 11 | BL_LOG_ERROR_BM_FE_FAILURE_STATUS: Fatal error: failure status in bootmgr. |
| 0xdc000041 | 11 | BL_LOG_ERROR_BM_FE_BOOT_DEVICE: Fatal error: boot device inaccessible in bootmgr. |
| 0xdc000042 | 11 | BL_LOG_ERROR_BM_FE_RAMDISK_MEM: Fatal error: ramdisk device creation had insufficient memory in bootmgr. |
| 0xdc000043 | 11 | BL_LOG_ERROR_BM_FE_INVALID_BCD_STORE: Fatal error: BCD is invalid in bootmgr. |
| 0xdc000044 | 11 | BL_LOG_ERROR_BM_FE_INVALID_BCD_ENTRY: Fatal error: Invalid BCD entry in bootmgr. |
| 0xdc000045 | 11 | BL_LOG_ERROR_BM_FE_NO_SECUREBOOT_POL: Fatal error: Default Secure Boot policy not found in bootmgr. |
| 0xdc000046 | 11 | BL_LOG_ERROR_BM_FE_NO_PAE_SUPPORT: Fatal error: CPU does not support PAE in bootmgr. |
| 0xdc000047 | 11 | BL_LOG_ERROR_BM_FE_UNSEAL_NOT_POS: Fatal error: Cannot unseal sensitive data in bootmgr. |
| 0xdc000048 | 11 | BL_LOG_ERROR_BM_FE_GENERIC: Fatal error: Generic failure in bootmgr. |
| 0xdc000049 | 11 | BL_LOG_ERROR_BM_FAILED_URI_UDP_REDIRECT: Failed to redirect URI device to UDP device in bootmgr. |
| 0xdc00004a | 11 | BL_LOG_ERROR_BM_FAILED_SVN_CHECK: Bootmgr SVN check failed. |
| 0xdc00004b | 11 | BL_LOG_ERROR_BM_FAILED_CHAINLOAD_SVN_CHECK: SVN check failed while chainloading bootmgr. |
| 0xdc00004c | 11 | BL_LOG_ERROR_BM_PURGE_OPT_DISABLE_TRUSTED_WIM_BOOT: BmPurgeOption failed for BCDE_OSLOADER_TYPE_DISABLE_TRUSTED_WIM_BOOT in bootmgr. |
| 0xdc00004d | 11 | BL_LOG_ERROR_OSL_REM_INTERN_APP_OPTS: OslpRemoveInternalApplicationOptions failed in osloader. |
| 0xdc00004e | 11 | BL_LOG_ERROR_OSL_GET_APP_OPT_DEVICE: BlGetApplicationOptionDevice failed for BCDE_OSLOADER_TYPE_OS_DEVICE in osloader. |
| 0xdc00004f | 11 | BL_LOG_ERROR_OSL_GET_SYSTEM_ROOT: Failed to get SystemRoot in osloader. |
| 0xdc000050 | 11 | BL_LOG_ERROR_OSL_FORCED_FAIL: OslpCheckForcedFailure failed implying a forced failure in osloader. |
| 0xdc000051 | 11 | BL_LOG_ERROR_OSL_DISABLE_VGA: BlAppendApplicationOptionBoolean for BCDE_OSLOADER_TYPE_DISABLE_VGA_MODE failed in osloader. |
| 0xdc000052 | 11 | BL_LOG_ERROR_OSL_OPEN_OS_DEVICE: BlDeviceOpen failed for os device in osloader. |
| 0xdc000053 | 11 | BL_LOG_ERROR_OSL_LOAD_SYS_HIVE: OslpLoadSystemHive failed in osloader. |
| 0xdc000054 | 11 | BL_LOG_ERROR_OSL_CREATE_OS_LD_OPTS: AhCreateLoadOptionsString failed in osloader. |
| 0xdc000055 | 11 | BL_LOG_ERROR_OSL_DISPLAY_INIT: OslDisplayInitialize failed in osloader. |
| 0xdc000056 | 11 | BL_LOG_ERROR_OSL_PROCESS_SI_POLICY: OslpProcessSIPolicy failed in osloader. |
| 0xdc000057 | 11 | BL_LOG_ERROR_OSL_DISP_ADV_OPT: OslDisplayAdvancedOptionsProcess failed in osloader. |
| 0xdc000058 | 11 | BL_LOG_ERROR_OSL_ARCH_HV_SETUP: OslArchHypervisorSetup failed in osloader. |
| 0xdc000059 | 11 | BL_LOG_ERROR_OSL_ARCH_HYPERCALL_SETUP: OslArchHypercallSetup failed in osloader. |
| 0xdc00005a | 11 | BL_LOG_ERROR_OSL_INIT_RESUME_CONTEXT: OslInitializeResumeContext failed in osloader. |
| 0xdc00005b | 11 | BL_LOG_ERROR_OSL_INIT_LDR_BLOCK: OslInitializeLoaderBlock failed in osloader. |
| 0xdc00005c | 11 | BL_LOG_ERROR_OSL_PROC_INIT_MACH_CONFIG: OslpProcessInitialMachineConfiguration failed in osloader. |
| 0xdc00005d | 11 | BL_LOG_ERROR_OSL_ENUM_DISKS: OslEnumerateDisks failed for the loader block in osloader. |
| 0xdc00005e | 11 | BL_LOG_ERROR_OSL_REINIT_SYS_HIVE: OslpReinitializeSystemHive failed in osloader. |
| 0xdc00005f | 11 | BL_LOG_ERROR_OSL_INIT_CODE_INT: OslInitializeCodeIntegrity failed in osloader. |
| 0xdc000060 | 11 | BL_LOG_ERROR_OSL_INIT_CODE_INT_LD_BLOCK: OslBuildCodeIntegrityLoaderBlock failed in osloader. |
| 0xdc000061 | 11 | BL_LOG_ERROR_OSL_SECURE_BOOT_VARS: OslFwProtectSecureBootVariables failed in osloader. |
| 0xdc000062 | 11 | BL_LOG_ERROR_OSL_LD_MODULES: OslpLoadAllModules failed in osloader. |
| 0xdc000063 | 11 | BL_LOG_ERROR_OSL_LD_FW_DRIVERS: OslFwLoadFirmwareDrivers failed in osloader. |
| 0xdc000064 | 11 | BL_LOG_ERROR_OSL_VSM_CHK_ENCRYPT_KEY: BlVsmCheckSystemPolicy failed for master sncrupt key provisioning in osloader. |
| 0xdc000065 | 11 | BL_LOG_ERROR_OSL_VSM_PHASE_0: Fatal VSM Phase 0 initializatin failure in osloader. |
| 0xdc000066 | 11 | BL_LOG_ERROR_OSL_SET_SEIL_SIGN_POL: OslSetSeILSigningPolicy failed in osloader. |
| 0xdc000067 | 11 | BL_LOG_ERROR_OSL_CMS_PROV_IDK: BlVsmCheckSystemPolicy failed during VSM Idendity key work in osloader. |
| 0xdc000068 | 11 | BL_LOG_ERROR_OSL_ARCH_KERNEL_SETUP_0: OslArchKernelSetup failed for 0 in osloader. |
| 0xdc000069 | 11 | BL_LOG_ERROR_OSL_FW_KERNEL_SETUP: OslFwKernelSetup failed for 0 in osloader. |
| 0xdc00006a | 11 | BL_LOG_ERROR_OSL_PROC_EV_STORE: OslpProcessEVStore failed in osloader. |
| 0xdc00006b | 11 | BL_LOG_ERROR_OSL_COPY_BOOT_OPTS: BlCopyBootOptions failed in osloader. |
| 0xdc00006c | 11 | BL_LOG_ERROR_OSL_FVE_SEC_BOOT_REST_ONE: BlFveSecureBootRestrictToOne failed in osloader. |
| 0xdc00006d | 11 | BL_LOG_ERROR_OSL_NET_UNDI_CLOSE: BlNetUndiClose failed in osloader. |
| 0xdc00006e | 11 | BL_LOG_ERROR_OSL_PROC_APP_PDATA: OslProcessApplicationPersistentData failed in osloader. |
| 0xdc00006f | 11 | BL_LOG_ERROR_OSL_BLD_MEM_CACHE_REQ_LIST: OslFwBuildMemoryCachingRequirementsList failed in osloader. |
| 0xdc000070 | 11 | BL_LOG_ERROR_OSL_BLD_RT_MEM_MAP: OslFwBuildRuntimeMemoryMap failed in osloader. |
| 0xdc000071 | 11 | BL_LOG_ERROR_OSL_VSM_SETUP_1: OslVsmSetup failed for 1 in osloader. |
| 0xdc000072 | 11 | BL_LOG_ERROR_OSL_BLD_KERNEL_MEM_MAP: BlTraceBuildKernelMemoryMapStop failed in osloader. |
| 0xdc000073 | 11 | BL_LOG_ERROR_OSL_ARCH_KERNEL_SETUP_1: OslArchKernelSetup failed for 1 in osloader. |
| 0xdc000074 | 11 | BL_LOG_ERROR_OSL_SET_VSM_POL_SYS_HIVE: OslSetVsmPolicy failed in osloader. |
| 0xdc000075 | 11 | BL_LOG_ERROR_OSL_ENUM_ENCLAVE_PAGES: OslEnumerateEnclavePageRegions failed in osloader. |
| 0xdc000076 | 11 | BL_LOG_ERROR_OSL_GATHER_ENTROPY: OslGatherEntropy failed in osloader. |
| 0xdc000077 | 11 | BL_LOG_ERROR_OSL_VSM_SETUP_0: OslVsmSetup failed for 0 in osloader. |
| 0xdc000078 | 11 | BL_LOG_ERROR_OSL_VSM_CANNOT_BE_DISABLED_BY_KSR: VSM must not be disabled through KSR |
| 0xdc000079 | 11 | BL_LOG_ERROR_OSL_VSM_PHASE0_ALLOCATE_PAGES_FAILED |
| 0xdc00007a | 11 | BL_LOG_ERROR_OSL_VSM_PHASE0_LOAD_MODULES_FAILED |
| 0xdc00007b | 11 | BL_LOG_ERROR_OSL_VSM_PHASE0_LOAD_CIDATA_FAILED |
| 0xdc00007c | 11 | BL_LOG_ERROR_OSL_VSM_PHASE0_COPY_VSM_KEYS_FAILED |
| 0xdc00007d | 11 | BL_LOG_ERROR_OSL_VSM_PHASE0_COPY_ACPI_TABLES_FAILED |
| 0xdc00007e | 11 | BL_LOG_ERROR_OSL_VSM_PHASE0_ARCH_SETUP_FAILED |
| 0xdc00007f | 11 | BL_LOG_ERROR_OSL_VSM_PHASE0_BUILD_PAGE_TABLES_FAILED |
| 0xdc000080 | 11 | BL_LOG_ERROR_OSL_BUILD_BSD_LOCATION_FAILED: OslpBuildBsdLogLocation failed in osloader. |
| 0xdc000081 | 11 | BL_LOG_ERROR_OSL_GET_APP_OPT_DEVICE_OSDATA: BlGetApplicationOptionDevice failed for BCDE_OSLOADER_TYPE_OS_DATA_DEVICE in osloader. |
| 0xdc000082 | 11 | BL_LOG_ERROR_OSL_OPEN_OSDATA_DEVICE: BlDeviceOpen failed for osdata device in osloader. |
| 0xdc000083 | 11 | BL_LOG_ERROR_OSL_ENUMERATE_PERSISTENT_MEMORY: OslEnumeratePersistentMemory failed in osloader. |
| 0xdc000084 | 11 | BL_LOG_ERROR_OSL_HVCI_CANNOT_BE_ENABLED_BY_KSR: HVCI must not be enabled through KSR |
| 0xdc000085 | 11 | BL_LOG_ERROR_OSL_PROCESS_PRESERVED_MEMORY: Error while processing preserved memory. |
| 0xdc000086 | 11 | BL_LOG_ERROR_OSL_LOAD_DEVICES_HIVE: OslpLoadDevicesHive failed in osloader. |
| 0xdc000087 | 11 | BL_LOG_ERROR_OSL_LOAD_OSBOOT_HIVE: OslpLoadOsBootHive failed in osloader. |
| 0xdc000088 | 11 | BL_LOG_ERROR_OSL_LOAD_DRIVER_STORES: OslpLoadDriverStoreNodes failed in osloader. |
| 0xdc000089 | 11 | BL_LOG_ERROR_OSL_CMS_PROV_HBK: BlVsmCheckSystemPolicy failed during VSM Hibernation key work in osloader. |
| 0xdc00008a | 11 | BL_LOG_ERROR_OSL_ALLOC_LDR_BLOCK: OslAllocateLoaderBlock failed in osloader. |
| 0xdc00008b | 11 | BL_LOG_ERROR_OSL_ARCH_TCB_LAUNCH_0: OslTcbLaunch(0) failed in osloader. |
| 0xdc00008c | 11 | BL_LOG_ERROR_OSL_HVCI_CANNOT_BE_DISABLED_BY_KSR: HVCI must not be disabled through KSR |
| 0xdc00008d | 11 | BL_LOG_ERROR_OSL_GET_APP_OPT_DEVICE_BSP: BlGetApplicationOptionDevice failed for BCDE_OSLOADER_TYPE_BSP_DEVICE in osloader. |
| 0xdc00008e | 11 | BL_LOG_ERROR_OSL_OPEN_BSP_DEVICE: BlDeviceOpen failed for bsp device in osloader. |
| 0xdc00008f | 11 | BL_LOG_ERROR_OSL_FVE_UNLOCK_DEVICE_OSDATA: Failed to unlock osdata device in osloader. |
| 0xdc000090 | 11 | BL_LOG_ERROR_OSL_FVE_UNLOCK_DEVICE_BSP: Failed to unlock bsp device in osloader. |
| 0xdc000091 | 11 | BL_LOG_ERROR_OSL_FVE_UNLOCK_DEVICE_COMPOSITE: Failed to unlock composite device in osloader. |
| 0xdc000092 | 11 | BL_LOG_ERROR_OSL_PROCESS_PRM_FIRMWARE: Failed to parse PRM firmware table. |
| 0xdc000093 | 11 | BL_LOG_ERROR_OSL_LOAD_PRM_UPDATES: Failed to load PRM updates. |
| 0xdc000094 | 11 | ERROR_OSL_HOT_PATCH_FAILURE: Failed apply hot patches. |
| 0xdc000095 | 11 | BL_LOG_ERROR_OSL_SET_CIMFS_FAILURE: Failed to store CIMFS information. |
| 0xdc000096 | 11 | BL_LOG_ERROR_OSL_SET_COMPOSITEFS_FAILURE: Failed to store Compositefs information. |
| 0xdc000097 | 11 | BL_LOG_ERROR_OSL_TPM_SHUTDOWN: BlTpmShutdown failed in osloader. |
| 0xdc000098 | 11 | BL_LOG_ERROR_OSL_LOAD_DUMP_STACK: Failed to load dump stack. |
| 0xdc000099 | 11 | BL_LOG_ERROR_OSL_INIT_FUNC_OVERRIDE_CAPABILITIES: Failed to initialize function override capabilities. |
| 0xdc00009a | 11 | BL_LOG_ERROR_OSL_LOAD_MICROCODE_UPDATE: OslLoadMicrocodeUpdateDll failed in osloader. |
| 0xdc00009b | 11 | BL_LOG_ERROR_OSL_PRE_MICROCODE_UPDATE: OslPreMicrocodeUpdateControls failed in osloader. |
| 0xdc00009c | 11 | BL_LOG_ERROR_OSL_EXTRACT_MICROCODE_RECORD: OslpExtractMicrocodeRecord failed in osloader. |
| 0xdc00009d | 11 | BL_LOG_ERROR_OSL_PRELOAD_HYPERV: Failed to preload hypervisor. |
| 0xdc00009e | 11 | BL_LOG_ERROR_OSL_LOAD_HYPERV: Failed to load hypervisor. |
| 0xdc00009f | 11 | BL_LOG_ERROR_OSL_LOAD_HVLOADER: Failed to load hvloader. |
| 0xdc0000a0 | 11 | BL_LOG_ERROR_OSL_VSM_PHASE0_VBS_POLICY_NOT_PRESENT |
| 0xdc0000a1 | 11 | BL_LOG_ERROR_KSR_KSEG0: InitializeRebootAddressRange failed in SK extension. |
| 0xdc0000a2 | 11 | BL_LOG_ERROR_KSR_OUT_OF_MEMORY: Memory allocation failed in SK KSR extension. |
| 0xdc0000a3 | 11 | BL_LOG_ERROR_KSR_IMAGE_VALIDATION: Image validation failed in SK KSR extension. |
| 0xdc0000a4 | 11 | BL_LOG_ERROR_KSR_IMAGE_RELOCATION: Image relocation failed in SK KSR extension. |
| 0xdc0000a5 | 11 | BL_LOG_ERROR_KSR_BIND_IMPORT: Failed to bind imports to image in SK KSR extension. |
| 0xdc0000a6 | 11 | BL_LOG_ERROR_KSR_LOADER_ENTRY_POINT: SK loader entry point returned failure. |
| 0xdc0000a7 | 11 | BL_LOG_ERROR_KSR_RESERVE_EFI_RUNTIME: SK loader failed to reserve EFI runtime VA range. |
| 0xdc0000a8 | 11 | BL_LOG_ERROR_KSR_APPLY_FUNCTION_OVERRIDE: SK loader failed to apply function override fixups to osloader. |
| 0xdc0000a9 | 11 | BL_LOG_ERROR_TCB_SI_POLICY_CHECK: Failed to validate and measure SI policy. |
| 0xdc0000aa | 11 | BL_LOG_ERROR_TCB_LOAD_TCBLOADER: Failed to load tcbloader.dll. |
| 0xdc0000ab | 11 | BL_LOG_ERROR_TCB_LOAD: Failed to perform load action. |
| 0xdc0000ac | 11 | BL_LOG_ERROR_TCB_RESUME: Failed to perform resume action. |
| 0xdc0000ad | 11 | BL_LOG_ERROR_TCB_INVALID_ATTRIBUTES: Invalid tcblaunch application attributes. |
| 0xdc0000ae | 11 | BL_LOG_ERROR_TCB_REGISTER_EVENT_HANDLER: Failed to register launch notificaiton handler. |
| 0xdc0000af | 11 | BL_LOG_ERROR_TCB_OPEN_DEVICE: Failed to open application device. |
| 0xdc0000b0 | 11 | BL_LOG_ERROR_TCB_GET_DEVICE: Failed to query application device. |
| 0xdc0000b1 | 11 | BL_LOG_ERROR_GET_SYSTEM_ROOT: Failed to get SystemRoot value. |
| 0xdc0000b2 | 11 | BL_LOG_ERROR_OSL_PROCESS_BOOTSTAT_DATA: Failed to process bootstat data. |
| 0xdc0000b3 | 11 | BL_LOG_ERROR_OSL_VIRT_SETUP_0: Failed to perform virtual setup phase 0. |
| 0xdc0000b4 | 11 | BL_LOG_ERROR_OSL_VIRT_SETUP_1: Failed to perform virtual setup phase 1. |
| 0xdc0000b5 | 11 | BL_LOG_ERROR_OSL_PRELOAD_SI_POLICY: Failed to preload SI policies from OS volume. |
| 0xdc0000b6 | 11 | BL_LOG_ERROR_OSL_ARCH_TCB_LAUNCH_1: OslTcbLaunch(1) failed in osloader. |
| 0xdc0000b7 | 11 | ERROR_TCB_PLATORM_INIT: Failed to initialize TCB platform. |
| 0xdc0000b8 | 11 | BL_LOG_ERROR_OSL_INITIALIZE_FEATURE_CONFIGURATION: OslInitializeFeatureConfiguration failed in osloader. |
| 0xdc0000b9 | 11 | BL_LOG_ERROR_OSL_PROCESS_BOT_BCD: OslpProcessBootBcd failed in osloader. |
| 0xdc0000ba | 11 | BL_LOG_ERROR_RES_OPEN_HIBERFILE: Failed to open the hiberfile. |
| 0xdc0000bb | 11 | BL_LOG_ERROR_RES_INIT_DISPLAY: Failed to initialize display. |
| 0xdc0000bc | 11 | BL_LOG_ERROR_RES_INVALID_PAGEFILE: Page file is invalide for hibernate resume. |
| 0xdc0000bd | 11 | BL_LOG_ERROR_RES_HW_CHANGE: Hardware or firmware settings have changes since hibernate. |
| 0xdc0000be | 11 | BL_LOG_ERROR_RES_INVALID_HIBERFILE: Hiberfile is invalid. |
| 0xdc0000bf | 11 | BL_LOG_ERROR_RES_GET_CONTEXT_FAILED: Failed to get the resume context. |
| 0xdc0000c0 | 11 | BL_LOG_ERROR_RES_INVALID_HBBOOT_MEM_MAP: The memory map has changed since associated cold boot. |
| 0xdc0000c1 | 11 | BL_LOG_ERROR_RES_FIRMWARE_PHASE_0: Failed phase 0 of firmware setup for resume. |
| 0xdc0000c2 | 11 | BL_LOG_ERROR_RES_USB_HANDOFF: Failed setup for legacy usb handoff. |
| 0xdc0000c3 | 11 | BL_LOG_ERROR_RES_SMBIOS: Failed to get SMBIOS data. |
| 0xdc0000c4 | 11 | BL_LOG_ERROR_RES_TCB_ALLOCATE: Failed to allocate space for TCB resume. |
| 0xdc0000c5 | 11 | BL_LOG_ERROR_RES_TCB_PREPARE: Failed to prepare TCB data. |
| 0xdc0000c6 | 11 | BL_LOG_ERROR_RES_INIT_PREALLOCATION: Failed to initialize the preallocation. |
| 0xdc0000c7 | 11 | BL_LOG_ERROR_RES_INIT_TRANSITION_SPACE: Failed to intialize transition space. |
| 0xdc0000c8 | 11 | BL_LOG_ERROR_RES_INIT_PAGE_ALLOCATOR: Failed to initialize the free page allocator. |
| 0xdc0000c9 | 11 | BL_LOG_ERROR_RES_RELOC_PROC_CONTEXT: Failed to relocate the processor context page. |
| 0xdc0000ca | 11 | BL_LOG_ERROR_RES_LOAD_SECURE_DATA: Failed to load secure data from the hiberfile. |
| 0xdc0000cb | 11 | BL_LOG_ERROR_RES_RESTORE_IMAGE: Failed to restore image from the hiberfile. |
| 0xdc0000cc | 11 | BL_LOG_ERROR_RES_SECURE_DECRYPT_0: Failed phase 0 of secure data decryption. |
| 0xdc0000cd | 11 | BL_LOG_ERROR_RES_FVE_RESTRICT: Failed to restrict bitlocker to resuming OS. |
| 0xdc0000ce | 11 | BL_LOG_ERROR_RES_TCB_PREP_DATA: Failed to prepare data for TCB resume. |
| 0xdc0000cf | 11 | BL_LOG_ERROR_RES_SET_BGFX_OPTION: Failed to set BGFX option to preallocate progress frames. |
| 0xdc0000d0 | 11 | BL_LOG_ERROR_RES_CHECK_FILE_ARCH: Failed to verify hiberfile processor architecture. |
| 0xdc0000d1 | 11 | BL_LOG_ERROR_RES_GET_FADT_TBL: Failed to check the revision through FADT table. |
| 0xdc0000d2 | 11 | BL_LOG_ERROR_RES_MAP_FADT_TBL: Failed to check hardware configuration through FACS table. |
| 0xdc0000d3 | 11 | BL_LOG_ERROR_RES_HW_SIGNATURE_MISMATCH: Failed to resume due to hardware configuration changed. |
| 0xdc0000d4 | 11 | BL_LOG_ERROR_RES_SECURE_BOOT_MISMATCH: Failed to resume due to the state of secure boot. |
| 0xdc0000d5 | 11 | BL_LOG_ERROR_RES_PAGE_LEVEL_CHANGED: Failed to resume due to paging levels change. |
| 0xdc0000d6 | 11 | BL_LOG_ERROR_RES_ABANDON_HIBERNATION: Failed to resume due to user cancellation. |
| 0xdc0000d7 | 11 | BL_LOG_ERROR_RES_ALLOC_PAGE_PFN_ARRAY: Failed to allocate page for context parameters. |
| 0xdc0000d8 | 11 | BL_LOG_ERROR_RES_MAP_PAGE_PFN_ARRAY: Failed to map pages to transition space. |
| 0xdc0000d9 | 11 | BL_LOG_ERROR_RES_ALLOC_LIB_PAGES: Failed to allocate page for vresume library. |
| 0xdc0000da | 11 | BL_LOG_ERROR_RES_MMAP_RESUME_HEADER: Resume cancelled due to keystroke of the user. |
| 0xdc0000db | 11 | BL_LOG_ERROR_RES_BITLOCKER_MMAP_KEY_RING: Failed to memory map KeyRing. |
| 0xdc0000dc | 11 | BL_LOG_ERROR_RES_BITLOCKER_ALLOC_PFN: Failed to allocate free pages as temporary storage. |
| 0xdc0000dd | 11 | BL_LOG_ERROR_RES_BITLOCKER_MMAP_FREE_KEY_ADDR: Failed to memory map free keys. |
| 0xdc0000de | 11 | BL_LOG_ERROR_RES_IMAGE_ALLOC_SCRATCH_REGION: Failed to allocate memory for scratch region. |
| 0xdc0000df | 11 | BL_LOG_ERROR_RES_IMAGE_MAP_SCRATCH_REGION: Failed to memory map the scratch region. |
| 0xdc0000e0 | 11 | BL_LOG_ERROR_RES_IMAGE_RANGE_TBL_INVALID_READING: Failed to read hiber file. |
| 0xdc0000e1 | 11 | BL_LOG_ERROR_RES_IMAGE_RANGE_TBL_INVALID_HEADER: Failed to resume due to bad hiber table header. |
| 0xdc0000e2 | 11 | BL_LOG_ERROR_RES_IMAGE_RANGE_ARRAY_READING: Failed to read the range array. |
| 0xdc0000e3 | 11 | BL_LOG_ERROR_RES_IMAGE_ADD_DECOMPRESSION_PAGE: Failed to add page to decompression block. |
| 0xdc0000e4 | 11 | BL_LOG_ERROR_RES_IMAGE_PROCESS_DECOMPRESSION_PAGE: Failed to process the decompression block. |
| 0xdc0000e5 | 11 | BL_LOG_ERROR_RES_IMAGE_UNMAP_SCRATCH_REGION: Failed to unmap the scratch region. |
| 0xdc0000e6 | 11 | BL_LOG_ERROR_RES_IMAGE_FREE_SCRATCH_REGION: Failed to free scratch region. |
| 0xdc0000e7 | 11 | ERROR_RES_GET_HIBERFILE_DEVICE: Failed to get hiberfile device. |
| 0xdc0000e8 | 11 | ERROR_RES_GET_HIBERFILE_PATH: Failed to get hiberfile path. |
| 0xdc0000e9 | 11 | ERROR_RES_READ_HIBERFILE_HEADER: Failed to read hiberfile header. |
| 0xdc0000ea | 11 | ERROR_RES_EFI_GET_MEM_MAP: Failed to get memory map. |
| 0xdc0000eb | 11 | ERROR_RES_FW_MEM_MAP_CHANGE: Firmware runtime regions are changed. |
| 0xdc0000ec | 11 | ERROR_RES_EXIT_BOOT_SERVICE: Failed to terminate firmware boot services. |
| 0xdc0000ed | 11 | BL_LOG_ERROR_RES_TPM_SHUTDOWN: Failed to shutdown TPM to resuming OS. |
| 0xdc0000ee | 11 | ERROR_RES_RESUME_CONTEXT_PHASE_0: Failed to copy firmware resume context to OS. |
| 0xdc0000ef | 11 | ERROR_RES_RESUME_CONTEXT_PHASE_1: Failed to copy firmware resume context to OS. |
| 0xdc0000f0 | 11 | BL_LOG_ERROR_IO_SPACE_ALLOCATION_FAILURE: Failed to apply Io Space configuration. |
| 0xdc0000f1 | 11 | ERROR_RES_ALLOCATE_LOG_PAGE: Failed to allocate pages for boot log. |
| 0xdc0000f2 | 11 | None |
| 0xdc0000f3 | 11 | Processor is not supported. |
| 0xdc0000f4 | 11 | VMX is not supported. |
| 0xdc0000f5 | 11 | SMX is not supported. |
| 0xdc0000f6 | 11 | TXT is disabled by the BIOS in MSR_FEATURE_CONTROL. |
| 0xdc0000f7 | 11 | Required GETSEC[CAPABILITIES] are not available. |
| 0xdc0000f8 | 11 | TPM 2.0 is not available. |
| 0xdc0000f9 | 11 | Memory Attributes Table (MAT) not available. |
| 0xdc0000fa | 11 | No SINIT ACM module type found at the SINIT base address. |
| 0xdc0000fb | 11 | The ACM UUID does not match well known value. |
| 0xdc0000fc | 11 | The ACM client/server flags do not match the BIOS data. |
| 0xdc0000fd | 11 | The ACM debug flag does not match platform. |
| 0xdc0000fe | 11 | The ACM does not support the chipset. |
| 0xdc0000ff | 11 | The ACM does not support the processor. |
| 0xdc000100 | 11 | A more up to date ACM is available on the system. |
| 0xdc000101 | 11 | No compatible ACM found on the system. |
| 0xdc000102 | 11 | The system does not support DMA remapping in the DMAR table. |
| 0xdc000103 | 11 | TPM does not meet provisioning requirements. |
| 0xdc000104 | 11 | System does not meet required configuration to validate SMM. |
| 0xdc000105 | 11 | A VMX failure was encountered. |
| 0xdc000106 | 11 | Call to retrieve SMM information failed. |
| 0xdc000107 | 11 | SMM has access to OS memory regions. |
| 0xdc000108 | 11 | SMM signature is missing or corrupt. |
| 0xdc000109 | 11 | SMM signature check failed. |
| 0xdc00010a | 11 | SMM has access to a MSR that is not allowed by policy level. |
| 0xdc00010b | 11 | SMM has access to an IO port that is not allowed by policy level. |
| 0xdc00010c | 11 | SMM has access to IOMMU structures. |
| 0xdc00010d | 11 | ACM layout corruption. |
| 0xdc00010e | 11 | SKINIT instruction not supported by platform. |
| 0xdc00010f | 11 | The required platform module was not found. |
| 0xdc000110 | 11 | The platform module is invalid. |
| 0xdc000111 | 11 | The platform module failed to initialize. |
| 0xdc000112 | 11 | The platform does not have required capabilities or features. |
| 0xdc000113 | 11 | SMM has access to CPU state save. |
| 0xdc000114 | 11 | SMM has access to a restricted platform range. |
| 0xdc000115 | 11 | Not started at EL2. |
| 0xdc000116 | 11 | The platform firmware does not support SMCCC. |
| 0xdc000117 | 11 | Failed to query the platform for its DRTM version. |
| 0xdc000118 | 11 | The DRTM version provided by this platform is not supported. |
| 0xdc000119 | 11 | Failed to query the platform's DRTM capabilities or features. |
| 0xdc00011a | 11 | The platform's DRTM implementation is not supported by this version of Windows. |
| 0xdc00011b | 11 | The platform's firmware does not properly implement DRTM. |
| 0xdc00011c | 11 | The hash algorithm in use is not supported by this version of Windows. |
| 0xdc00011d | 11 | The PCR schema in use is not supported by this version of Windows. |
| 0xdc00011e | 11 | The DMA protection feature is not supported. |
| 0xdc00011f | 11 | Not running on the correct processor core for DRTM. |
| 0xdc000120 | 11 | The platform module returned a fatal error from the previous boot. |
| 0xdc000121 | 11 | The ACM on the system has been revoked. |
| 0xdc000122 | 11 | Failed to read the SVN from the AUX NV index. |
| 0xdc000123 | 11 | None |
| 0xdc000124 | 11 | Using 2k PPAM manifest. |
| 0xdc000125 | 11 | Using PPAM 3k manifest |
| 0xdc000126 | 11 | PPAM 3k manifest system table missing. |
| 0xdc000127 | 11 | None. |
| 0xdc000128 | 11 | Failed to reserve scratch VA. |
| 0xdc000129 | 11 | Failed to get connection parameters. |
| 0xdc00012a | 11 | Debugging blocked by BitLocker. |
| 0xdc00012b | 11 | Failed to initialize debug device descriptor. |
| 0xdc00012c | 11 | Failed to setup debugging device. |
| 0xdc00012d | 11 | Failed to initialize debug transport. |
| 0xdc00012e | 11 | Failed to setup debug traps. |
| 0xdc00012f | 11 | Failed to load debugger transport module. |
| 0xdc000130 | 11 | Failed to allocate scratch buffer. |
| 0xdc000131 | 11 | Failed to get debugger transport extension name. |
| 0xdc000132 | 11 | Failed to establish connection with isolated hypervisor. |
| 0xdc000133 | 11 | Pluton-Windows firmware upgrade not supported for this CPUID. |
| 0xdc000134 | 11 | Failed to load Pluton firmware package. |
| 0xdc000135 | 11 | Pluton firmware package is invalid. |
| 0xdc000136 | 11 | Pluton firmware binary not found. |
| 0xdc000137 | 11 | Failed to apply firmware. |
| 0xdc000138 | 11 | truncatememory |
| 0xdc000139 | 11 | avoidlowmemory |
| 0xdc00013a | 11 | testsigning |
| 0xdc00013b | 11 | nointegritychecks |
| 0xdc00013c | 11 | undefined |
| 0xdc00013d | 11 | Undefined |
| 0xdc00013e | 11 | Available |
| 0xdc00013f | 11 | Applied |
| 0xdc000140 | 11 | Rejected |
| 0xdc000141 | 11 | NotFound |
| 0xdc000142 | 11 | Low |
| 0xdc000143 | 11 | High |
| 0xdc000144 | 11 | Base |
| 0xdc000145 | 11 | End |
| 0xdd000001 | 11 | applied through registry |
| 0xdd000002 | 11 | applied through compatibility database |
| 0xdd000003 | 11 | applied through registry |
| 0xdd000004 | 11 | applied through compatibility database |
| 0xf2000002 | 11 | None |
| 0xf2000003 | 11 | HSP Shadow Stacks in compatibility mode |
| 0xf2000004 | 11 | HSP Shadow Stacks in strict mode |
| 0xf2000005 | 11 | HSP Shadow Stacks in compatibility mode (audit mode) |
| 0xf2000006 | 11 | HSP Shadow Stacks in strict mode (audit mode) |
| 1721 entries | ||