| Previous | Next |
| WER_S_ASSERT_CONTINUE | WER_S_REPORT_UPLOADED_CAB |
WER_S_THROTTLED
WER report was throttled
WER_S_THROTTLED is HRESULT 1769483 (0x001B000B) from winerror.h. The documented description is “Report was throttled.” 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.
Accepting this result requires proving the documented state rather than checking only SUCCEEDED(hr).
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 report matches a throttling rule and application code does not defeat it with repeated resubmissions. Without the boundary check, the HRESULT can hide stale output, pending ownership, or omitted work.
Difference from nearby results
Suspension affects upload generally; throttling suppresses this report or bucket because of rate policy.
Precise classification of it selects the correct wait, stop, retry, cleanup, or disclosure path.
Correct handling and recovery
Accept throttling, retain the bucket and count locally if allowed, and wait for policy or time-window change. Investigate high-frequency causes independently.
Practical scenario
A crash loop produces hundreds of identical reports. WER throttles the bucket while monitoring still counts local occurrences for remediation.
References
Looking for a different code? Search another status or error code.