| Previous | Next |
| STATUS_DS_AG_CANT_HAVE_UNIVERSAL_MEMBER | STATUS_INVALID_IMAGE_WIN_64 |
STATUS_INVALID_IMAGE_WIN_32
The loader received a 32-bit image in an incompatible context
This status identifies a valid-looking 32-bit Windows image where the active path expects a different bitness or image role. It can arise when a 64-bit process tries to load a 32-bit in-process DLL, when deployment selects the x86 artifact for an x64-only component, or when a low-level loader path does not support WOW translation.
WOW allows many 32-bit executables to run on 64-bit Windows, but it does not permit a 64-bit process to load a 32-bit DLL into the same address space. Cross-bitness integration requires process separation and an IPC boundary.
What to inspect
- Read both the COFF Machine field and optional-header magic for the failing image.
- Record caller process bitness and whether the image is the primary executable, DLL, driver, or data-only mapping.
- Check installer component conditions and file-system redirection for selection of an x86 path.
- Use a 32-bit helper process when the component cannot be rebuilt for the 64-bit caller.
References
- Microsoft Open Specifications: NTSTATUS values
- Microsoft: PE and COFF format
- LLVM: llvm-readobj COFF inspection
- Microsoft: LoadLibrary
Looking for a different code? Search another status or error code.