| 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. The documented description is “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;
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.
Difference from nearby results
WER_S_REPORT_QUEUED confirms durable deferral; this status explicitly says no queue entry was created.
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.
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.