| Previous | Next |
| ERROR_WMI_SET_FAILURE | ERROR_APPCONTAINER_REQUIRED |
ERROR_NOT_APPCONTAINER
An AppContainer-only operation was called from a different security context
ERROR_NOT_APPCONTAINER indicates that the current process or token is not an AppContainer, while the API requires AppContainer identity and isolation. Package identity alone is insufficient: a packaged desktop application can run at medium integrity and therefore have a package identity without being inside an AppContainer.
Inspect the process token for a package SID, AppContainer number, capabilities, and trust level. Compare the manifest TrustLevel and activation path with the API requirements. Do not assume that converting a Win32 app to MSIX automatically places every executable in an AppContainer; packaged full-trust and AppContainer processes have different resource and broker behavior.
What to inspect
- Query the actual process token rather than inferring from install format.
- Verify the manifest trust level and selected application entry point.
- Use an API supported for medium-integrity packaged desktop apps when appropriate.
References
- Microsoft: AppContainer isolation model
- Microsoft: token PackageSid and AppContainerNumber
- Microsoft: AppContainer versus medium-integrity packaged apps
Looking for a different code? Search another status or error code.