| Previous | Next |
| CONVERT10_E_OLESTREAM_FMT | CONVERT10_E_STG_FMT |
CONVERT10_E_OLESTREAM_BITMAP_TO_DIB
There was an error in a Windows GDI call while converting the bitmap to a DIB
CONVERT10_E_OLESTREAM_BITMAP_TO_DIB is the failure HRESULT 2147746243 (0x800401C3, signed -2147221053) from winerror.h. The documented description is “There was an error in a Windows GDI call while converting the bitmap to a DIB”. In practical terms, a Windows GDI operation failed while converting an OLE 1 bitmap presentation to a DIB. Interpret it in the context of importing presentation data during OLE 1 to OLE 2 conversion.
Relevant contract
OLE 1/OLE 2 conversion combines callback I/O, binary parsing, structured storage, and presentation conversion. Retaining the stage and byte offset is essential because a read failure, format failure, missing stream, and GDI failure require different repairs.
- Associate this result with one exact operation in OleConvertOLESTREAMToIStorage, OleConvertIStorageToOLESTREAM, OLESTREAM callbacks, structured-storage streams, and presentation-data conversion.
- Confirm that this result came from importing presentation data during OLE 1 to OLE 2 conversion, rather than from cleanup or a wrapper that ran afterward.
Likely cause branches
- It can result when bitmap dimensions, stride, planes, or bit depth are invalid.
- It can result when GDI cannot allocate or create the required DIB resources.
- It can result when the source bitmap handle or palette is invalid or already released.
Evidence to preserve
A useful incident records the conversion direction, OLESTREAM Get or Put callback result, requested byte count, actual byte count, storage class, stream names, presentation format, bitmap or DIB metadata, and commit state.
- Capture BITMAP metadata, palette size, dimensions, and GDI last-error data.
- Validate multiplication for stride and image size before allocation.
- Test conversion of the presentation independently from object data.
Diagnostic sequence
- Identify the exact object, method, and lifecycle phase involved in importing presentation data during OLE 1 to OLE 2 conversion.
Recovery and retry
Correction. repair or omit only the corrupt presentation when the application can preserve object data and clearly records the loss; otherwise fail atomically. Retry condition. Retry after resource recovery or with valid bitmap data; repeated GDI calls on the same invalid handle are unsafe. Before repeating the operation, record stream positions and byte counts, release temporary GDI objects, and discard or roll back any output storage that was only partly written.
Practical scenario
A legacy object has valid storage data but a bitmap with impossible width and stride; the migration tool quarantines the presentation instead of importing corrupted pixels.
Difference from related HRESULTs
CONVERT10_E_STG_DIB_TO_BITMAP is the reverse presentation conversion from DIB to bitmap.
Developer and administrator guidance
Make OLESTREAM callbacks report exact byte counts, validate format headers before allocating, preserve structured-storage commit boundaries, and separate bitmap from DIB ownership. Regression coverage should include short reads and writes, invalid format records, absent standard streams, truncated presentation data, large dimensions, callback errors, and failure before versus after storage commit.
Preserve the original document and reproduce with a copy; repair the producing application or converter only after the failing conversion stage and file provenance are identified.
References
Looking for a different code? Search another status or error code.