| Previous | Next |
| WER_S_IGNORE_ASSERT_INSTANCE | WER_S_ASSERT_CONTINUE |
WER_S_IGNORE_ALL_ASSERTS
WER handled the assertion and added it to a permanent ignore list
WER_S_IGNORE_ALL_ASSERTS is HRESULT 1769481 (0x001B0009) from winerror.h. The documented description is “The assertion was handled and added to a permanent ignore list.” 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.
This result is actionable completion information and may require waiting, reconciliation, fallback, or user disclosure.
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 broad ignore decision is authorized and scoped to the correct assertion identity and application version. The caller should reject a path where outputs and state do not match the recorded condition.
Correct handling and recovery
Record the ignore rule, provide a way to remove it, and avoid hiding unrelated assertion sites that share a generic message.
Continuation after it within the documented state machine is different from restarting the entire operation.
Difference from nearby results
The instance-only variant resumes once; this status changes handling for future matching assertions.
Practical scenario
A developer suppresses a noisy assertion fingerprint for one build. The tool stores the exact module and line signature and expires the rule on upgrade.
References
Looking for a different code? Search another status or error code.