| Previous | Next |
| ERROR_TOO_MANY_LINKS | ERROR_APP_WRONG_OS |
ERROR_OLD_WIN_VERSION
The specified program requires a newer version of Windows.
ERROR_OLD_WIN_VERSION has decimal value 1150 (0x47E). It means the program cannot run because the available Windows version is older than the version required by the image, installer, loader, or application compatibility check. The code is about an OS-version requirement, not simply a missing DLL.
Where the requirement can come from
- the executable image or subsystem version is newer than the operating system supports
- an installer or bootstrapper performs an explicit minimum-version check
- a launcher selects a binary built only for a later Windows release
- application compatibility settings cause version detection to report an older target
- a component depends on platform behavior that the vendor intentionally gates by OS version
Do not infer the minimum supported release from marketing text alone. Record which executable returned 1150 and whether the decision came from the Windows loader or application code.
Diagnostic evidence
- complete Windows edition, build, architecture, servicing level, and installation type
- full path, file version, product version, architecture, and signature of the failing executable
- PE subsystem and version fields when loader compatibility is suspected
- application manifest and any compatibility-mode settings
- installer logs showing the exact minimum-version rule
Version APIs can be affected by application manifests and compatibility behavior. A program that uses deprecated version checks incorrectly can reject a supported system, so compare its decision with documented platform requirements and the executable manifest.
Resolution options
- install a vendor-supported build that targets the current Windows release
- upgrade Windows when hardware, licensing, security, and application compatibility allow it
- correct packaging that launched the wrong platform-specific binary
- remove accidental compatibility-mode settings in a controlled test
- fix an in-house version check to test required features rather than a guessed version number
Do not patch executable headers or bypass an installer check without proving compatibility. The application may rely on kernel, API, security, or driver behavior genuinely absent from the older system.
Developer guidance
Declare supported Windows versions in the application manifest and document the minimum supported build. Prefer feature detection for optional capabilities. When the product must reject an older release, log the detected build, required build, and the component that made the decision.
Build pipelines should test the oldest supported operating system. A binary can acquire a newer subsystem requirement or dependency during a toolchain update even when source code appears unchanged.
Related loader codes
ERROR_APP_WRONG_OS indicates that the file is not a suitable Windows or MS-DOS program. ERROR_BAD_EXE_FORMAT points to an invalid image format, and missing-entry-point errors identify absent APIs. Error 1150 specifically reports that Windows itself is too old for the program’s stated requirement.
Example
A deployment package contains separate binaries for Windows 10 and Windows 11, but its launcher selects the newer build on an older host. Startup returns 1150. Correcting package selection is safer than editing the binary or forcing compatibility mode, because the older host never received the intended executable.
References
- Microsoft: System Error Codes (1000–1299)
- Microsoft: PE format
- Microsoft: Targeting your application for Windows
- Microsoft: VerifyVersionInfo function
Looking for a different code? Search another status or error code.