| Previous | Next |
| E_MULTIPLE_PACKAGES_FOR_FAMILY | E_APPLICATION_ACTIVATION_TIMED_OUT |
E_APPLICATION_MANAGER_NOT_RUNNING
The app-management component required by activation is unavailable
E_APPLICATION_MANAGER_NOT_RUNNING is HRESULT 0x80270257 (signed decimal -2144927145, unsigned decimal 2150040151). It has failure severity, FACILITY_SHELL facility 39, and code field 0x0257. AllStat records the SDK message: “The app manager is required to activate applications, but is not running.”
Public contract boundary
The symbolic description identifies required app-management infrastructure, but the public HRESULT contract does not name one universally restartable Windows service or authorize callers to manipulate internal processes. The owner can vary with Windows generation and activation path. Diagnose the platform state through supported logs and service-health mechanisms rather than guessing a process name from the phrase “app manager.”
The failure occurs before the target app can be treated as successfully launched. It is broader than an app executable crash and narrower than a missing package: Windows knows it needs the management layer but cannot use it in the current environment.
Likely condition branches
- The interactive shell or packaged-app infrastructure has not finished starting after sign-in.
- A required system component crashed, is shutting down, or is blocked during servicing.
- The request originates from an unsupported session, recovery environment, or stripped-down image.
- Security policy, service hardening, or permission changes prevent normal app-management startup.
- System files or registrations used by modern app infrastructure are damaged.
Evidence to collect before recovery
- Windows build, boot time, sign-in time, session type, shell state, and whether the failure affects every packaged app.
- Immersive-Shell, AppModel-Runtime, AppX deployment, service-control, and application crash events around the same timestamp.
- Pending reboot/servicing state and recent cumulative update, image customization, or security-policy changes.
- Caller identity, session ID, AppUserModelID, activation method, and exact HRESULT.
- Whether activation succeeds after a clean sign-out/sign-in or reboot without package modification.
Diagnostic sequence
- Test another known packaged app in the same user session to establish platform-wide versus package-specific scope.
- Inspect event chronology for an infrastructure crash, startup timeout, service termination, or servicing lock.
- Verify that the request is made from an interactive supported Windows session rather than session 0 or a recovery shell.
- Complete pending servicing and restart the machine when required by system state.
- If the condition persists across users and packages, validate Windows component health before re-registering individual apps.
Retry and recovery
A short bounded retry can be reasonable immediately after user sign-in if logs show infrastructure still starting. Persistent retries are inappropriate when the manager has crashed or the OS is in an unsupported state. Reboot or component repair is justified only by collected system evidence, not by the symbolic name alone.
What this code does not prove
It does not establish that the target package is absent, that its license expired, or that its executable returned an error. It also does not identify a third-party “application manager.” The term belongs to the Windows activation infrastructure.
Practical scenario
An enterprise image finishes an update and an autostart agent immediately tries to activate a packaged dashboard during first sign-in. The shell management layer has not reached a usable state, so activation returns E_APPLICATION_MANAGER_NOT_RUNNING. A bounded post-sign-in retry succeeds. Reinstalling the dashboard would have added risk without addressing readiness.
Official Microsoft references
- Microsoft: COM error codes for security and setup
- Microsoft: packaged-app activation manager
- Microsoft: activation event-log diagnostics
- Microsoft: Store apps fail to start and activation events
- Microsoft: package deployment and query troubleshooting
Looking for a different code? Search another status or error code.