| Previous | Next |
| E_UAC_DISABLED | E_APPLICATION_NOT_REGISTERED |
E_FULL_ADMIN_NOT_SUPPORTED
The activation request is running as the built-in Administrator
E_FULL_ADMIN_NOT_SUPPORTED is HRESULT 0x80270253 (signed decimal -2144927149, unsigned decimal 2150040147). It is a failure from facility 39 (FACILITY_SHELL), code 0x0253. The SDK text states: “This app can't be activated by the Built-in Administrator.”
Account identity is the decisive fact
This HRESULT identifies the special local built-in Administrator account and its full-administrator execution model, not every user who belongs to the Administrators group. A normal administrative user operating under UAC usually has a filtered interactive token and can enter Admin Approval Mode when elevation is needed. The built-in account can be configured differently, and packaged-app activation may reject that context.
The distinction matters in support reports. Logging only “user is admin” loses the evidence needed to separate this result from E_ELEVATED_ACTIVATION_NOT_SUPPORTED or E_UAC_DISABLED.
Where the condition appears
- A recovery, manufacturing, or lab workflow signs in directly with the local account whose well-known RID is 500.
- An appliance image enables the built-in Administrator and disables Admin Approval Mode, reproducing the unsupported account context.
- A remote support procedure uses that account to validate a packaged application after repair.
- An automated desktop test is scheduled under the built-in account rather than a normal test user.
- A renamed built-in Administrator is mistaken for an ordinary local administrator because only the display name was checked.
Evidence to collect
- User SID, not merely account name; the built-in account can be renamed.
- Effective Admin Approval Mode policy for the built-in Administrator and general UAC state.
- Caller integrity level, elevation type, session ID, and whether activation came from a service or interactive desktop.
- The target AppUserModelID and whether the same package starts for a standard user or ordinary administrative user.
- Immersive-Shell events around the activation attempt.
Resolution choices
Use a normal user profile for interactive packaged applications. If administration is also required, keep privileged maintenance in a separate process or account and perform user-facing activation in the intended user’s session. In managed environments, enabling the policy that places the built-in Administrator in Admin Approval Mode may change behavior, but that security decision should follow the organization’s baseline and be tested; it is not a package repair step.
Retry policy
Repeating activation under the same account and token will not change the result. Retry after switching to a supported user context or after an approved policy change and required restart. Avoid creating a loop that repeatedly unregisters or reinstalls the app, because the account context—not package content—is the reported blocker.
Related results
E_UAC_DISABLED applies when the machine lacks the UAC prerequisite. E_ELEVATED_ACTIVATION_NOT_SUPPORTED applies to an elevated caller even when it is not the built-in account. E_APPLICATION_NOT_REGISTERED means package or contract resolution failed. Preserve the exact HRESULT because all four can present to a user as “the app did not open.”
Practical scenario
A technician enables and renames the local built-in Administrator, logs on with it, and tests a repaired Store application. Activation returns E_FULL_ADMIN_NOT_SUPPORTED, while the package opens for a newly created standard account. The correct action is to validate the app under the supported user profile, not to alter its manifest.
Official Microsoft references
Looking for a different code? Search another status or error code.