What does HRESULT 0x001B000A (WER_S_ASSERT_CONTINUE) mean?

 
Previous Next
WER_S_IGNORE_ALL_ASSERTS WER_S_THROTTLED

WER_S_ASSERT_CONTINUE

Assertion resumed as unhandled

WER_S_ASSERT_CONTINUE is HRESULT 1769482 (0x001B000A) from winerror.h. AllStat describes it as “The assertion was resumed as unhandled.” 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 application should branch on this result before a generic success path consumes the details.

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 it 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 caller understands that normal unhandled-assertion or crash processing may continue after this decision. Without the boundary check, the HRESULT can hide stale output, pending ownership, or omitted work.

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

Correct handling and recovery

Preserve the original assertion context and let the configured debugger, fail-fast, or report path proceed. Do not label the assertion as resolved.

Before repeating work after it, reconcile side effects and prove that the next attempt is idempotent.

Difference from nearby results

Ignore statuses consume the assertion; this status deliberately returns it to unhandled processing.

Using one generic success branch for it and its neighbor can lose output, repeat work, or misreport completion.

Practical scenario

A test harness declines to ignore an assertion. WER resumes the unhandled path and the debugger captures the original stack.

References

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