What does HRESULT 0x001B0005 (WER_S_DISABLED_QUEUE) mean?

 
Previous Next
WER_S_SUSPENDED_UPLOAD WER_S_DISABLED_ARCHIVE

WER_S_DISABLED_QUEUE

WER did not queue the report because queueing is disabled

WER_S_DISABLED_QUEUE is HRESULT 1769477 (0x001B0005) from winerror.h. AllStat describes it as “Report was not queued to queueing being disabled.” 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.

Telemetry and tests should retain this result because its operational meaning differs from S_OK.

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 application knows whether upload already happened and does not assume a deferred report exists. 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.

Difference from nearby results

WER_S_REPORT_QUEUED confirms durable deferral; this status explicitly says no queue entry was created.

The neighboring result changes whether output is final, more work remains, or fallback is required.

Correct handling and recovery

Record the submission outcome and retain any application-owned diagnostics needed by policy. Do not delete the only local evidence under the assumption WER queued it.

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

Practical scenario

A policy allows immediate upload but disables local queueing. When the endpoint is unavailable, the app keeps its own sanitized failure record.

References

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