Windows / Modules / wininit.exe

wininit.exe

Associated Error Codes

Below lists error codes and symbolic names found for this module.

CodeFound inDescription
0xb8.11011Custom dynamic link libraries are being loaded for every application. The system administrator should review the list of libraries to ensure they are related to trusted applications. Please visit http://support.microsoft.com/kb/197571 for more information.
0xc8.11011LSASS.exe was started as a protected process with level: %1.
0xd1011Credential Guard was started and will protect LSA credentials.
0xe10Credential Guard configuration: %1, %2
0xf10Credential Guard is configured but the secure kernel is not running; continuing without Credential Guard.
0x1010LsaIso.exe, the host process for Credential Guard and Key Guard, failed to launch: %1
0x111011Error reading Credential Guard (LsaIso.exe) UEFI configuration: %1
0x1210Key Guard was started and will protect VSM-isolated keys.
0x1000003878.11011Classic
0x3000000078.11011Info
0x3000000178.11011Start
0x3000000278.11011Stop
0x400003e978.11011%1
0x500000021011Error
0x5000000378.11011Warning
0x5000000478.11011Information
0x80000bbb78.11011Windows start-up process has failed to start the remote shutdown server.
0x80000bbc78.11011Windows start-up process has failed to synchronize with the local security subsystem during setup.
0x9000000178.11011Microsoft-Windows-Wininit
0x9000000278.11011System
0xc00003f778.11011A critical system process, %1, failed with status code %2. The machine must now be restarted.
0xc0000bba78.11011Windows start-up process has unexpectedly terminated.
0xc0000bbd78.11011Windows start-up process has failed to terminate system processes.
0xe11Credential Guard configuration: Registry Configuration: %1 Test Configuration: %2 Auto Enablement: %3
0xf11Credential Guard and/or VBS Key Isolation are configured but the secure kernel is not running; continuing without them.
0x1011LsaIso.exe, the host process for Credential Guard and VBS Key Isolation, failed to launch: %1
0x1211VBS Key Isolation was started and will protect VSM-isolated keys.
0x1311Virtualization Based Security new timer creation status HRESULT: %1 New latch timer needed: %2 New latch timer waiting for system update completion: %3 Previous latch timer exists but disabled by registry: %4 Policy file exists: %5
0x1411Virtualization Based Security master key timer start status Win32Error: %1 Start time: %2 Grace period: %3 Due time: %4 Policy version: %5
0x1511Virtualization Based Security previous timer resume status HRESULT: %1 Previous timer present: %2 Start time: %3 Grace period: %4 Policy version: %5 Attempted recovery increment succeeded: %6 Previous timer invalid: %7 Unlatched policy file exists: %8
0x1611Virtualization Based Security latch policy status HRESULT: %1 TPM counter value: %2 Expected TPM counter value: %3 Policy version: %4 Incremented: %5
0x1711Boot App Anti-Rollback: Initialize Completed with status: HRESULT: %1 New timer needed: %2 New timer waiting for system update completion: %3 Previous latch timer exists but disabled by registry: %4
0x1811Boot App Anti-Rollback: Timer start completed with status: Win32Error: %1 Start time: %2 Grace period: %3 Due time: %4
0x1911Boot App Anti-Rollback: Previous timer resumed with status: HRESULT: %1 Previous timer present: %2 Start time: %3 Grace period: %4 Attempted recovery enforcement succeeded: %5
0x1a11Boot App Anti-Rollback: Boot.stl Enforcement completed with status: HRESULT: %1 Boot Stl Enforced Successfully: %2 WNF Published with result: %3
0x6411Hybrid shutdown has been overridden by a disk check request. The system will perform a full shutdown instead.
0xc0000bbe11Windows shudown failed with error code %1 in phase: %2.
0xb7Custom dynamic link libraries are being loaded for every application. The system administrator should review the list of libraries to ensure they are related to trusted applications.
38 entries