What does HRESULT 0x001B000C (WER_S_REPORT_UPLOADED_CAB) mean?

 
Previous Next
WER_S_THROTTLED ERROR_FLT_IO_COMPLETE

WER_S_REPORT_UPLOADED_CAB

WER report and CAB payload were uploaded

WER_S_REPORT_UPLOADED_CAB is HRESULT 1769484 (0x001B000C) from winerror.h. AllStat describes it as “Report was uploaded with cab.” 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 WER_S_REPORT_UPLOADED_CAB status must be preserved until its code-specific output and next action have been processed.

Where the status is encountered

  • WER_S_REPORT_UPLOADED_CAB can appear during 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.
  • WER_S_REPORT_UPLOADED_CAB can appear during crash, hang, assertion, and application-failure reporting; capture the exact API, object, and phase because the same numeric success severity does not define the state by itself.
  • WER_S_REPORT_UPLOADED_CAB can appear during enterprise policy controlling WER queue, archive, upload, debugger, and throttling; capture the exact API, object, and phase because the same numeric success severity does not define the state by itself.

Keep WER_S_REPORT_UPLOADED_CAB attached to the operation that returned it. Interpreting WER_S_REPORT_UPLOADED_CAB 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 CAB contains the intended attachments and no sensitive file was included outside consent or policy. For WER_S_REPORT_UPLOADED_CAB, that proof prevents usable partial state from being confused with full completion.

For WER_S_REPORT_UPLOADED_CAB, also confirm that returned outputs belong to the current operation generation and were not inherited from an earlier attempt.

Evidence and telemetry

  • Preserve report ID for WER_S_REPORT_UPLOADED_CAB.
  • Preserve CAB hash and size for WER_S_REPORT_UPLOADED_CAB.
  • Preserve attachment manifest for WER_S_REPORT_UPLOADED_CAB.
  • Preserve consent and policy for WER_S_REPORT_UPLOADED_CAB.
  • Preserve submission result for WER_S_REPORT_UPLOADED_CAB.

For WER_S_REPORT_UPLOADED_CAB, also record UTC time, process and thread IDs, component version, operation generation, and a correlation ID. Keep sensitive WER_S_REPORT_UPLOADED_CAB content out of logs; use lengths, hashes, GUIDs, and policy-safe metadata where possible.

Diagnostic sequence

  • Capture raw 0x001B000C and WER_S_REPORT_UPLOADED_CAB before exceptions, signed formatting, or a generic success wrapper removes the symbolic value.
  • Identify the interface, method, callback, service, driver, or broker that returned WER_S_REPORT_UPLOADED_CAB, including component version, process, thread, and correlation ID.
  • Prove the decisive condition for WER_S_REPORT_UPLOADED_CAB: the CAB contains the intended attachments and no sensitive file was included outside consent or policy.
  • For WER_S_REPORT_UPLOADED_CAB, inspect every output, count, object handle, callback, queue entry, media item, report, transaction, topology element, or signaling response the call produced.
  • Compare state immediately before and after WER_S_REPORT_UPLOADED_CAB and verify that ownership, lifetime, persistence, and user-visible effects match the status.
  • Reproduce WER_S_REPORT_UPLOADED_CAB with the smallest input, then change only the suspected cause and confirm that the return value or postcondition changes as predicted.

Correct handling and recovery

Finalize submission, retain the report ID and attachment manifest hash, and remove temporary packaging artifacts.

Do not use an unchanged tight retry loop for WER_S_REPORT_UPLOADED_CAB; it can duplicate effects or conceal a terminal state.

Difference from nearby results

WER_S_REPORT_UPLOADED confirms report upload; this status specifically confirms upload with the CAB package.

Precise classification of WER_S_REPORT_UPLOADED_CAB selects the correct wait, stop, retry, cleanup, or disclosure path.

Practical scenario

A hang report includes a minidump and logs in a CAB. After upload, the app deletes its staging directory and records the manifest.

A regression test should reproduce WER_S_REPORT_UPLOADED_CAB, assert all relevant outputs and state, then change only the decisive condition and verify ordinary completion or the expected neighboring result.

Developer and administrator guidance

Branch on WER_S_REPORT_UPLOADED_CAB before the ordinary SUCCEEDED(hr) path whenever output validity or the next method differs. Keep 0x001B000C, the WER_S_REPORT_UPLOADED_CAB method, component build, and correlation ID in telemetry.

Administrators handling WER_S_REPORT_UPLOADED_CAB should change only the producing component or policy identified by the captured evidence. Document who owns continuation, cancellation, cleanup, fallback, and user messaging for WER_S_REPORT_UPLOADED_CAB.

References

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