| Previous | Next |
| ERROR_APPCONTAINER_REQUIRED | ERROR_INVALID_PACKAGE_SID_LENGTH |
ERROR_NOT_SUPPORTED_IN_APPCONTAINER
The API is incompatible with the caller’s sandboxed context
ERROR_NOT_SUPPORTED_IN_APPCONTAINER indicates that the current AppContainer process called functionality Windows does not expose within that isolation boundary. This is stronger than a missing capability: some operations are categorically unavailable because they manipulate global machine state, unrestricted processes, services, or resources that cannot be safely brokered.
Confirm the API support statement for packaged desktop and AppContainer callers. Move privileged work to an approved broker, full-trust companion, service, or deployment-time manifest extension when the platform provides one. Adding broad capabilities does not make a fundamentally unsupported API available, and disabling the sandbox changes the application security model rather than fixing the call.
What to inspect
- Read the API’s AppContainer and package-identity support notes.
- Use a documented broker or full-trust component for privileged work.
- Do not confuse unsupported context with a user-consent denial.
References
- Microsoft: WinRT APIs unsupported for some desktop contexts
- Microsoft: AppContainer resource isolation
- Microsoft: capability limits and trust levels
Looking for a different code? Search another status or error code.