What does HRESULT 0x001B0000 (WER_S_REPORT_DEBUG) mean?

 
Previous Next
MF_S_CLOCK_STOPPED WER_S_REPORT_UPLOADED

WER_S_REPORT_DEBUG

WER attached or invoked a debugger

WER_S_REPORT_DEBUG is HRESULT 1769472 (0x001B0000) from winerror.h. AllStat describes it as “Debugger was attached.” 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.

A cleared severity bit does not make the return equivalent to ordinary completion; the postcondition remains specific.

What must be true before accepting it

Verify that the debugger attachment is intentional and report ownership is transferred according to the chosen debugging policy. The boundary determines whether the caller continues, waits, falls back, or ends the operation.

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

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.

Correct handling and recovery

Pause ordinary upload handling, record the debugger outcome, and continue or terminate the faulting process only through the documented WER decision path.

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

Practical scenario

A test build crashes with just-in-time debugging enabled. WER launches the debugger and the harness records that no normal upload was expected.

Difference from nearby results

WER_S_REPORT_UPLOADED means data was submitted; this status says interactive debugging handled the event instead.

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

References

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