What does HRESULT 0x800401D3 (CLIPBRD_E_BAD_DATA) mean?

Status / error code:

Category:

Constant name:

Source:

Facility:

Operating System:

Description:

Clipboard data for the requested format is malformed or inconsistent.

Previous	Next
CLIPBRD_E_CANT_SET	CLIPBRD_E_CANT_CLOSE

CLIPBRD_E_BAD_DATA

Data on clipboard is invalid

Windows defines CLIPBRD_E_BAD_DATA as 2147746259 (0x800401D3; signed value -2147221037). AllStat’s description is “Data on clipboard is invalid”. The code marks a specific failure: Clipboard data for the requested format is malformed or inconsistent. The relevant operation is retrieving, converting, or exposing data already present on the clipboard.

The high bit in 0x800401D3 is set, so this is a failure rather than a success or informational result. Its facility field is 4 (FACILITY_ITF) and its low 16-bit code is 467 (0x01D3). Those bit fields classify the value, but they do not identify the failing object by themselves; the native method, object identity, and first producer of this result remain essential.

Where it is raised

Understanding this result requires this subsystem context: The Win32 clipboard is a short ownership transaction with format-specific handle semantics. Logging only a final HRESULT loses whether the failure happened while opening, emptying, publishing, or later consuming data.

Associate this result with one exact operation in OpenClipboard, EmptyClipboard, SetClipboardData, format-specific handle rules, delayed rendering, and clipboard ownership.
Confirm that this result came from retrieving, converting, or exposing data already present on the clipboard, rather than from cleanup or a wrapper that ran afterward.
Preserve any IErrorInfo, underlying Win32 result, provider message, or callback failure that preceded it; the HRESULT alone should not erase a more specific cause.

Telemetry checklist

A useful incident records the clipboard opener HWND, owner HWND, sequence number, format ID and name, handle type, allocation flags, delayed-rendering choice, last-error value, and thread or message-loop state. Also retain the application and component build, architecture, process and thread IDs, COM apartment, operation correlation ID, elapsed time, and the first state-changing event before the failure. When logging it, redact content and credentials while preserving types, lengths, hashes, opaque identities, and lifecycle generations needed to reproduce its contract.

record format, handle size/type, clipboard sequence number, and producer window when available.
validate data before parsing and cap all lengths and dimensions.
copy required bytes while the clipboard is open, then parse the private copy.

Why it is specific

It can result when the producer publishes bytes that do not satisfy the declared format.
It can result when delayed rendering returns an invalid or incomplete handle.
It can result when a consumer trusts missing terminators, lengths, structure versions, or bitmap dimensions.

Investigation order

Capture it at the first native return before a wrapper maps it to a generic exception.
Identify the exact object, method, and lifecycle phase involved in retrieving, converting, or exposing data already present on the clipboard.
Reproduce it with one controlled input or state change, and verify that the correction changes the decisive evidence rather than merely hiding the result.

Safe handling

Correction. for it, reject the malformed format, try a different advertised format, and report the producing application or integration path. Retry boundary. Retry only after the clipboard sequence changes or another format is chosen; rereading identical malformed data is deterministic. Before repeating the operation, close the clipboard on every path, determine whether EmptyClipboard changed ownership, and never free a handle successfully transferred to the system.

Practical scenario

A producer advertises CF_UNICODETEXT without a terminating wide null; the consumer rejects that format and uses a valid HTML format from the same clipboard transaction. This isolates it within Win32 clipboard ownership and data publication and provides a regression test for the stated correction.

Difference from related HRESULTs

CLIPBRD_E_CANT_SET means publication failed; it means data is available but invalid for its claimed format. Keep those outcomes separate in exception mappings, telemetry dimensions, user messages, and automated retry policy.

Developer and administrator guidance

Serialize the open-empty-publish-close transaction, use the documented handle type for each format, and retain delayed-rendering ownership until WM_RENDERFORMAT handling completes. Regression coverage for it should include clipboard contention, owner-window destruction, invalid handle types, delayed rendering, empty data, multiple formats, and failure after ownership has changed.

Operational repair for it must target the evidence-backed owner: identify the process holding or publishing the clipboard and reproduce without clipboard managers or remote-session redirection before changing system configuration. Retain before-and-after traces for it so the change can be attributed and reversed.

References

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