What does HRESULT 0x80000019 (E_ASYNC_OPERATION_NOT_STARTED) mean?

 
Previous Next
E_ILLEGAL_DELEGATE_ASSIGNMENT E_APPLICATION_EXITING

E_ASYNC_OPERATION_NOT_STARTED

Asynchronous operation was not started correctly

E_ASYNC_OPERATION_NOT_STARTED is HRESULT 2147483673 (0x80000019) from winerror.h. AllStat describes it as “An async operation was not properly started.” In the Windows Runtime metadata, object lifetime, asynchronous operation, activation, and apartment model, the code identifies a specific failure boundary and should not be replaced by a generic COM exception.

Telemetry should preserve this result as a separate outcome rather than merging it with unrelated COM or WinRT failures.

Decisive interpretation boundary

Before choosing recovery, verify that the creation path, start call, operation ID, status transitions, and completion handler registration are all present in the expected order. That boundary prevents this result from being misclassified as corruption, network failure, or a reason for an unsafe automatic retry.

Also confirm that all observed objects, tokens, buffers, proxies, metadata files, or ACLs belong to the current operation generation and were not retained from an earlier attempt.

Where it is encountered

  • This result can be returned during C++/WinRT, WRL,.NET projections, or native WinRT ABI calls. Record the interface, method, component version, thread, apartment, process, and correlation ID.
  • This result can be returned during runtime-class activation, WinMD reflection, asynchronous objects, observable state, or view lifecycle.
  • It can be returned during cross-thread and cross-apartment handoff between UI, ASTA, STA, MTA, broker, and background work.

The immediate focus for this HRESULT is an async object that is queried, awaited, cancelled, or completed without the required start transition or producer initialization. Keep it attached to that operation; the same numeric severity outside the owning API does not supply enough context.

Correct handling and recovery

Start the operation through the documented API, propagate start failures, and do not expose the object to consumers before its state machine is active.

An unchanged retry loop for this HRESULT can duplicate effects, deepen reentrancy, or hide an invalid lifetime transition.

Difference from nearby HRESULTs

It means no valid async execution began; E_PENDING means an operation did begin but its result is not ready.

The distinction around it should be represented explicitly in control flow and operational dashboards.

Lifetime, retry, and cleanup rules

After it, determine whether the current object, interface pointer, call context, token, stream, metadata reader, asynchronous operation, or access-control instance remains valid. Release only resources owned by the failing attempt, cancel callbacks through their documented mechanism, and avoid double close, double commit, repeated activation, or replay of a non-idempotent remote method.

The retry policy for this HRESULT should state the trigger, maximum attempts, cancellation owner, and reconciliation step for effects that may have completed elsewhere.

Developer and administrator guidance

When it crosses native, managed, scripting, RPC, or WinRT projection boundaries, preserve the unsigned 32-bit HRESULT. Unit tests for this HRESULT should assert the code-specific postcondition and resource ownership, not merely that an exception was thrown.

After it, avoid broad permission grants or system-wide resets unless code-specific evidence proves a global configuration problem. Define who owns retry, cancellation, cleanup, policy changes, package repair, and user-facing messaging for this HRESULT.

Practical scenario

A wrapper creates an async object but returns it before invoking the producer callback. The implementation starts production first and adds a test for immediate cancellation.

A regression test should reproduce it, assert the raw HRESULT and all relevant outputs, then correct only the decisive condition and verify the intended success or neighboring failure result.

References

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