| Previous | Next |
| E_MONITOR_RESOLUTION_TOO_LOW | E_UAC_DISABLED |
E_ELEVATED_ACTIVATION_NOT_SUPPORTED
Packaged app activation was requested from an elevated context
E_ELEVATED_ACTIVATION_NOT_SUPPORTED is HRESULT 0x80270251 (signed decimal -2144927151, unsigned decimal 2150040145). Its failure bit is set, the facility is 39 (FACILITY_SHELL), and the code field is 0x0251. AllStat preserves the SDK message: “This app can't be activated from an elevated context.”
The security boundary represented by the HRESULT
The shell activation pipeline rejected the caller’s elevated token before performing a normal packaged-app launch. This often appears in administrative tools, elevated command shells, installers, test harnesses, or debuggers that call IApplicationActivationManager while running “as administrator.” The result describes the caller’s integrity context; it does not mean the target package itself needs more privilege.
Packaged app activation is intentionally different from calling CreateProcess for an ordinary desktop executable. The activation manager resolves an AppUserModelID and dispatches a launch, file, or protocol contract in the current interactive session. Passing that request through an elevated process can cross a security boundary the shell refuses to use.
Common cause branches
- An automation runner or support utility was launched elevated even though its app-launch action did not require elevation.
- A desktop product performs both administrative configuration and user-facing activation in one high-integrity process.
- A debugger or certification tool inherits an elevated token from an administrator shell.
- A scheduled task uses “run with highest privileges” and then tries to open a packaged UI application.
- A broker design omitted a medium-integrity per-user process for shell-facing operations.
How to prove the cause
- Record the caller PID, user SID, session ID, token elevation type, integrity level, and whether UAC virtualization is relevant.
- Capture the AppUserModelID and activation contract without logging user document contents passed to file or protocol activation.
- Repeat the same call from a non-elevated process in the same interactive session.
- Verify whether administrative work truly has to occur in the process that performs activation.
- Check the Immersive-Shell activation event to confirm that no later package-start failure replaced this HRESULT.
Correct architecture
Separate privileged configuration from user-session activation. A high-integrity service or helper can finish the administrative operation, then signal a normal per-user process that invokes the shell activation API. Validate the IPC request, bind it to the intended user/session, and pass only the minimum launch data. Do not solve the problem by lowering the entire application’s security posture or by attempting to duplicate an elevated token into the packaged app.
Retry policy
Retrying from the same elevated token will return the same result. A retry is safe after execution has moved to a non-elevated process in the intended user’s interactive session. If no such session exists, queue or report the user-facing action rather than launching UI from a service session.
Nearby errors that mean something else
E_UAC_DISABLED says the system-wide UAC prerequisite is disabled. E_FULL_ADMIN_NOT_SUPPORTED identifies the built-in Administrator context. E_APPLICATION_ACTIVATION_EXEC_FAILURE indicates that activation passed earlier policy checks but the app still did not start. These branches require different evidence and should not be collapsed into “access denied.”
Practical scenario
An elevated maintenance console completes a repair and calls ActivateApplication to open the repaired Store app. The call returns E_ELEVATED_ACTIVATION_NOT_SUPPORTED. The durable fix is to send a signed request to the console’s medium-integrity companion process and let that process activate the AppUserModelID.
Official Microsoft references
- Microsoft: COM error codes for security and setup
- Microsoft: IApplicationActivationManager interface
- Microsoft: ActivateApplication method
- Microsoft: User Account Control settings and configuration
- Microsoft: Windows app deployment and launch tests
Looking for a different code? Search another status or error code.