What does HRESULT 0x001B0007 (WER_S_REPORT_ASYNC) mean?

 
Previous Next
WER_S_DISABLED_ARCHIVE WER_S_IGNORE_ASSERT_INSTANCE

WER_S_REPORT_ASYNC

WER report submission continues asynchronously

WER_S_REPORT_ASYNC is HRESULT 1769479 (0x001B0007) from winerror.h. AllStat describes it as “Reporting was successfully spun off as an asynchronous operation.” In the Windows Error Reporting collection, queue, upload, archive, assertion, or debugging workflow, the value reports a nonfailure state that must not be collapsed into plain S_OK.

The status must be preserved until its code-specific output and next action have been processed.

Where the status is encountered

  • WerReportSubmit and WER store processing; capture the exact API, object, and phase because the same numeric success severity does not define the state by itself.
  • Crash, hang, assertion, and application-failure reporting;
  • Enterprise policy controlling WER queue, archive, upload, debugger, and throttling;

Keep this result attached to the operation that returned it. Interpreting it outside that API contract can turn a normal continuation or partial result into an incorrect retry or false completion.

What must be true before accepting it

Verify that the report handle, registered files, and process state remain valid until asynchronous ownership is complete. That proof prevents usable partial state from being confused with full completion.

Also confirm that returned outputs belong to the current operation generation and were not inherited from an earlier attempt.

Correct handling and recovery

Do not free report resources prematurely. Track WER completion through the supported store or callback workflow and prevent duplicate submissions.

Retry after it only when a recorded input, capability, resource, policy, or state has changed.

Difference from nearby results

Queued is a durable deferred report; asynchronous means the submit operation was spun off and completion is not yet final.

The distinction around it should be visible in control flow, telemetry classification, and user messaging.

Practical scenario

A service submits a large report asynchronously during shutdown. It transfers ownership correctly and records the report ID before exiting.

References

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