| Previous | Next |
| E_ASYNC_OPERATION_NOT_STARTED | E_APPLICATION_VIEW_EXITING |
E_APPLICATION_EXITING
Application is exiting and cannot service the request
E_APPLICATION_EXITING is HRESULT 2147483674 (0x8000001A) from winerror.h. The documented description is “The application is exiting and cannot service this request.” The relevant context is the Windows Runtime metadata, object lifetime, asynchronous operation, activation, and apartment model.
What to verify
Verify that the shutdown initiator and point of no return are known, and the rejected operation has not partially committed durable state. Validate this condition using the owning API state, not an inferred UI symptom.
Where it is encountered
- C++/WinRT, WRL, .NET projections, or native WinRT ABI calls.
- Runtime-class activation, WinMD reflection, asynchronous objects, observable state, or view lifecycle.
- Cross-thread and cross-apartment handoff between UI, ASTA, STA, MTA, broker, and background work.
The immediate focus is a process-wide shutdown phase in which new work is rejected because services, dispatchers, package state, or runtime infrastructure are being torn down.
Correct handling and recovery
Stop accepting new requests, cancel or drain existing work according to policy, and persist only shutdown-safe state. A retry requires a new process instance.
Reconcile partial output and server-side effects before attempting the operation again.
Difference from nearby HRESULTs
It is process-wide; E_APPLICATION_VIEW_EXITING may affect only one view while the application remains alive.
Developer and administrator guidance
Change the smallest component, identity, ACL, package, or threading boundary that the evidence identifies, then reproduce the same operation.
Practical scenario
A background broker receives a save request after app shutdown begins. It records that the request was rejected before mutation and lets the next launch reconcile the draft.
References
Looking for a different code? Search another status or error code.