| Previous | Next |
| STATUS_INVALID_ACE_CONDITION | STATUS_NOTIFICATION_GUID_ALREADY_DEFINED |
STATUS_IMAGE_SUBSYSTEM_NOT_PRESENT
The image requires a missing execution subsystem
PE images declare a subsystem such as Windows GUI, Windows console, native, EFI, or another defined environment. The subsystem value influences startup conventions and required platform support. This status means the loader recognized the image but cannot provide the subsystem named in its optional header.
The failure is not corrected by adding a missing DLL when the execution environment itself is absent. It can indicate a legacy subsystem removed from modern Windows, a firmware-targeted image launched as an application, a native system component used incorrectly, or a corrupt subsystem field.
What to inspect
- Read the Optional Header Subsystem and subsystem version fields with a PE-aware inspection tool.
- Confirm that the file was built for the intended target environment rather than firmware, native startup, or a retired subsystem.
- Compare linker /SUBSYSTEM settings and post-link transformations against the released artifact.
- Do not patch the subsystem value without rebuilding; startup ABI, imports, and entry-point expectations can also differ.
References
- Microsoft Open Specifications: NTSTATUS values
- Microsoft: PE and COFF format
- LLVM: llvm-readobj COFF inspection
- Wine source: PE module loader
Looking for a different code? Search another status or error code.