| Previous | Next |
| WER_S_DISABLED_QUEUE | WER_S_REPORT_ASYNC |
WER_S_DISABLED_ARCHIVE
WER uploaded the report but did not archive it
WER_S_DISABLED_ARCHIVE is HRESULT 1769478 (0x001B0006) from winerror.h. The documented description is “Report was uploaded, but not archived due to archiving 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.
The high-level request that returned this result is complete only after the caller validates the represented condition.
What must be true before accepting it
Verify that the upload succeeded and the absence of a local archive is expected under effective policy. The boundary determines whether the caller continues, waits, falls back, or ends the operation.
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
Close submission successfully, record that no archive copy exists, and do not later search the WER archive as proof of delivery.
Do not use an unchanged tight retry loop; it can duplicate effects or conceal a terminal state.
Practical scenario
A privacy policy disables local archives while permitting upload. Support uses the report ID rather than expecting a local ReportArchive folder.
Difference from nearby results
WER_S_REPORT_UPLOADED may also leave an archive; this status adds the explicit no-archive condition.
References
Looking for a different code? Search another status or error code.