What does Windows error code 190 (ERROR_INVALID_MODULETYPE) mean?

ERROR_INVALID_MODULETYPE

What ERROR_INVALID_MODULETYPE means

ERROR_INVALID_MODULETYPE is Win32 system error code associated with the documented message: “The operating system cannot run %1.” The significant condition is that the loader recognizes the file but rejects its declared module type for the requested execution context.

Likely causes

• a DLL is launched as an executable or an executable is loaded as a library
• the image declares an OS or module class unsupported by the current subsystem
• the file extension no longer matches the binary’s real format after replacement or packaging

Troubleshooting steps

1. Inspect the image header rather than relying on the file extension
2. Confirm whether the operation is CreateProcess, LoadLibrary, or a compatibility launch
3. Restore the correct module artifact for the target architecture and subsystem

Code-specific investigation notes

Module type is encoded in the image, not reliably inferred from.EXE or.DLL. Packaging systems that rename artifacts can therefore create a plausible-looking but unloadable file.

Confirm the operation’s intent: creating a process, loading a library, registering a component, and invoking a resource-only module impose different module-type requirements.

Architecture compatibility is a separate axis. A correct module class can still fail later because of CPU or subsystem mismatch.

Difference from related errors

ERROR_BAD_EXE_FORMAT is a broader image-format failure; it indicates that the module classification itself is unsuitable.

References

• Microsoft: System error codes 0–499