What does HRESULT 0x80270254 (E_APPLICATION_NOT_REGISTERED) mean?

Status / error code:

Category:

Constant name:

Source:

Facility:

Operating System:

Description:

No installed app registration supports the requested activation contract.

Previous	Next
E_FULL_ADMIN_NOT_SUPPORTED	E_MULTIPLE_EXTENSIONS_FOR_APPLICATION

E_APPLICATION_NOT_REGISTERED

The requested app or activation contract is not registered

E_APPLICATION_NOT_REGISTERED is HRESULT 0x80270254 (signed decimal -2144927148, unsigned decimal 2150040148). Its failure severity is set, facility is 39 (FACILITY_SHELL), and code field is 0x0254. AllStat records: “This app does not support the contract specified or is not installed.”

Two distinct resolution failures share this code

The activation broker could not find a usable registration for the identity and contract in the request. The package may be absent or not registered for the current user, or the package may exist while its manifest does not declare the requested launch, file, or protocol extension. IApplicationActivationManager exposes separate methods for generic launch, file, and protocol contracts, so recording which method failed is essential.

An AppUserModelID is more specific than a package display name. It identifies an application entry within a package. A correctly installed package can still fail if the caller supplies a stale or malformed AppUserModelID, references the wrong application ID after an upgrade, or asks that application to handle a contract it never declared.

Typical causes

The package is provisioned for the machine but not registered in the affected user profile.
The app was removed, partially updated, or left with inconsistent registration after profile migration.
The caller persisted an obsolete AppUserModelID across a package or manifest change.
ActivateForFile or ActivateForProtocol targets an app that lacks the corresponding manifest extension.
Deployment completed for another user, architecture, or package identity but not for the current activation context.
Registry or package-repository permissions were changed and the shell can no longer resolve registration correctly.

Evidence to collect

Exact AppUserModelID, activation method, file verb or protocol URI, caller user SID, and session ID.
Package full name, family name, version, architecture, install location, and registration state for the affected user.
The installed package manifest’s Application IDs and extension declarations.
AppX deployment logs and Immersive-Shell activation events from the same timestamp.
Whether generic launch succeeds while file/protocol activation fails, which points to contract registration rather than installation.

Diagnostic sequence

Resolve the supplied AppUserModelID back to the expected package and application entry.
Confirm that the package is registered for the actual user, not merely installed for another profile or provisioned for future users.
Read the deployed manifest and verify the requested extension category, executable, entry point, and supported file types or protocols.
Compare package version and identity with the caller’s cached configuration or shortcut.
Use supported repair or re-registration procedures only after identifying a missing or damaged registration; preserve deployment logs before changing state.

Retry and recovery

An identical retry cannot create a missing registration. Retry after installing/registering the correct package, updating the AppUserModelID, or selecting an app that declares the requested contract. If deployment is in progress, wait for its transaction to finish and re-query package state instead of racing the repository.

Difference from neighboring activation HRESULT

E_MULTIPLE_EXTENSIONS_FOR_APPLICATION means resolution found too many matching declarations inside the app. E_MULTIPLE_PACKAGES_FOR_FAMILY means family resolution found an unsupported package multiplicity. E_APPLICATION_ACTIVATION_EXEC_FAILURE means identity resolution advanced farther and startup then failed.

Practical example

A desktop design tool stores an AppUserModelID and later calls ActivateForProtocol. The package is installed, but the updated manifest moved the protocol declaration to another application entry. Windows returns E_APPLICATION_NOT_REGISTERED. Updating the stored identity to the application that actually owns the protocol fixes activation; reinstalling the unchanged package alone does not.

Official Microsoft references

Looking for a different code? Search another status or error code.