The short version
- 01Record the full startup message and any executable or DLL named in the error.
- 02Confirm the affected application's version and the recent installation or dependency change.
- 03Use the application's available Repair option through Windows before a fresh installation.
- 04Reinstall through the original software publisher's installation route if repair is unavailable or fails.
- 05As the developer, match the process architecture to every in-process DLL dependency.
- 06Give the publisher the named module, architecture and repair result if the same failure remains.
Raw message
0xc000007b — STATUS_INVALID_IMAGE_FORMAT
Likely causes
- An executable or DLL is not a valid image for the attempted Windows load.
- An incompatible process/dependency architecture is a possible branch to investigate, not a universal diagnosis.
Keep the module named by the Bad Image message
Microsoft's NTSTATUS table maps 0xc000007b to STATUS_INVALID_IMAGE_FORMAT. The message describes an image not designed for Windows or containing an error, and points to original installation media or vendor support. Our first record is the complete message and any named module; the code alone does not identify which dependency is faulty.
Restore the application's installation through its publisher
Windows offers Repair for some apps under Installed apps > Advanced options, or Repair/Change under Control Panel > Programs and Features. Use the available repair route. If reinstalling is needed, Microsoft's Bad Image message directs you to the original installation package; our recommendation is to preserve application data before replacing the installation.
Developers: verify each in-process dependency's architecture
Microsoft documents that a 64-bit process cannot load a 32-bit DLL and a 32-bit process cannot load a 64-bit DLL. Check the executable and its native dependencies together. This is an architecture compatibility check, not proof that every 0xc000007b is caused by a 32/64-bit mismatch.
Sources and review notes
Checked on . The code meaning is from Microsoft's NTSTATUS specification; generic repair and architecture context are separately sourced. Retaining module names, preserving app data and choosing a compatibility branch are editorial guidance. This does not prescribe a universal runtime download or a DLL replacement from an unrelated website. Glitchary is independent of Microsoft.