| Previous | Next |
| NS_E_WMP_BMP_COMPRESSION_UNSUPPORTED | NS_E_WMP_JPG_JERR_ARITHCODING_NOTIMPL |
NS_E_WMP_BMP_INVALID_FORMAT
How to classify this WMP result
The symbolic result NS_E_WMP_BMP_INVALID_FORMAT narrows 0xC00D1032 to the BMP invalid format condition: the BMP header or pixel-layout fields are internally inconsistent. Keep the BMP invalid format boundary visible when a later dialog reduces it to a general media error.
An additional test is to record DIB size, dimensions, stride, bit count, masks and expected pixel-data offset; that evidence is more useful than reinstalling the Player or changing several unrelated settings at once.
What succeeds before this failure
Representative case: The bitmap claims dimensions or offsets that cannot fit within the file length.
State worth preserving
Capture state before Player cleanup:
- What to verify: record DIB size, dimensions, stride, bit count, masks and expected pixel-data offset.
- Artifact: decoder-supported coding mode versus the file’s declared mode.
- State: standalone decode result outside the skin package using the same bytes.
- Object identity: archive member name, byte length, hash and file signature.
- Underlying evidence: format header fields, dimensions, bit depth and color model.
- Correlation: first invalid marker/chunk and its byte offset.
Reproduce without destroying evidence
- Use this deciding observation for this condition: record DIB size, dimensions, stride, bit count, masks and expected pixel-data offset.
- Apply the smallest supported remedy for this condition: repair the malformed header or export a new BMP from the source artwork.
Related HRESULTs with different meanings
| Result | Different condition |
|---|---|
NS_E_WMP_BMP_COMPRESSION_UNSUPPORTED | The BMP header selects a compression mode unsupported by the WMP skin decoder |
NS_E_WMP_JPG_JERR_ARITHCODING_NOTIMPL | The JPEG uses arithmetic entropy coding that the WMP skin decoder does not implement |
NS_E_WMP_BMP_BITMAP_NOT_CREATED | The image parsed far enough to request a Windows bitmap but bitmap allocation or creation failed |
If this result is followed by a broader “cannot play,” “cannot load,” or “operation failed” result, preserve the earlier event. The later code can be a consequence from a wrapper, fallback item or UI layer rather than the producing failure.
Recovery at the right layer
The targeted correction for this condition is to repair the malformed header or export a new BMP from the source artwork. Keep the original failing input until the same operation succeeds after one controlled change.
- Avoid changing only the extension or MIME type while leaving the encoded bytes unchanged; it can destroy the artifact or state needed to explain this result.
- Avoid repeatedly recompressing the sole source image without retaining an original and a decoded pixel comparison; that can replace the original HRESULT with a secondary failure from another layer.
How to know the repair is real
Technical references
- Skin files and image resources — documentation for this HRESULT.
- BITMAPINFOHEADER structure — normative or platform material relevant to this HRESULT.
- Windows Media Player skins — API or format context.
Looking for a different code? Search another status or error code.