| Previous | Next |
| ERROR_PACKAGES_REPUTATION_CHECK_TIMEDOUT | APPMODEL_ERROR_PACKAGE_RUNTIME_CORRUPT |
APPMODEL_ERROR_NO_PACKAGE
A package-identity API was called by an unpackaged process
APPMODEL_ERROR_NO_PACKAGE means the current process is not associated with a package identity. Traditional unpackaged Win32 processes can run normally but do not have a package full name, family name, package graph, or manifest identity for APIs that require those concepts.
Confirm the actual activation and deployment model. Package the application, use packaging with external location, or choose an API supported for unpackaged desktop applications. Do not infer identity from the executable being stored near an MSIX or from a package installed for another process. Query the current process at runtime and handle the no-package result as an expected branch when supporting both models.
What to inspect
- Query identity in the process that makes the failing call.
- Distinguish unpackaged, sparse/external-location, and fully packaged apps.
- Guard APIs that explicitly require package identity.
References
- Microsoft: Package APIs in packaged and unpackaged processes
- Microsoft: APIs that require package identity
- Microsoft: packaged versus unpackaged Windows apps
Looking for a different code? Search another status or error code.