| Previous | Next |
| CO_E_ERRORINDLL | CO_E_OBJNOTREG |
CO_E_WRONGOSFORAPP
Meaning
Windows documents CO_E_WRONGOSFORAPP as “Wrong OS or OS version for application”. In practical terms, it is returned when COM activation selects an application binary whose operating-system requirements are incompatible with the current Windows environment.
Where the failure belongs
This result belongs to COM activation and object lifetime. COM activation is a sequence rather than one registry lookup: identifier resolution, class registration, module or process start, class-factory publication, marshaling, and object lifetime can fail independently. The relevant condition is that COM activation selects an application binary whose operating-system requirements are incompatible with the current Windows environment.
Diagnostic sequence
- Confirm that the observed path matches this condition: COM activation selects an application binary whose operating-system requirements are incompatible with the current Windows environment.
Likely causes
- Possible cause 1: the server targets a newer Windows version or unavailable platform component.
- Possible cause 2: an obsolete binary expects a removed subsystem or unsupported execution model.
- Possible cause 3: deployment selected the wrong build for the host edition or architecture.
Evidence to collect
- Capture 1: the executable headers, subsystem version, manifest and supportedOS declarations.
- Capture 2: the current Windows build, edition, architecture and compatibility settings.
- Capture 3: installer selection logs showing why this server binary was deployed.
Correct handling and retry
- Corrective action 1: install a server build supported on the current Windows version.
- Corrective action 2: correct package targeting so incompatible binaries are never registered for this host.
- Corrective action 3: remove unsupported compatibility shims that obscure the real deployment requirement.
Retry guidance. Retry only after installing a compatible application build or moving the workload to a supported system. When retrying, avoid launch duplicate servers, reuse stale proxies or repeat an activation whose side effects are unknown.
Practical scenario
A package registers its Windows 11-only local server on an older servicing baseline; deploying the vendor-supported legacy build prevents it.
Developer and operational guidance
Difference from nearby HRESULTs
CO_E_DLLNOTFOUND concerns locating a module; it concerns whether the located application can run on the current operating system.
Official Microsoft references
Looking for a different code? Search another status or error code.