What does HRESULT 0xC00D1031 (NS_E_WMP_BMP_COMPRESSION_UNSUPPORTED) mean?

 
Previous Next
NS_E_WMP_BMP_BITMAP_NOT_CREATED NS_E_WMP_BMP_INVALID_FORMAT

NS_E_WMP_BMP_COMPRESSION_UNSUPPORTED

What this HRESULT means

The symbolic result NS_E_WMP_BMP_COMPRESSION_UNSUPPORTED narrows 0xC00D1031 to the BMP compression unsupported condition: the BMP header selects a compression mode unsupported by the WMP skin decoder. Keep the BMP compression unsupported boundary visible when a later dialog reduces it to a general media error.

An additional test is to record biCompression, bit count, masks and DIB header size; that evidence is more useful than reinstalling the Player or changing several unrelated settings at once.

What succeeds before this failure

Representative case: A valid BMP uses a compression variant that the legacy skin image path does not implement.

State worth preserving

Capture state before Player cleanup:

  • What to verify: record biCompression, bit count, masks and DIB header size.
  • Artifact: first invalid marker/chunk and its byte offset.
  • State: decoder-supported coding mode versus the file’s declared mode.
  • Object identity: standalone decode result outside the skin package using the same bytes.
  • Underlying evidence: archive member name, byte length, hash and file signature.
  • Correlation: format header fields, dimensions, bit depth and color model.

Reproduce without destroying evidence

  1. Preserve 0xC00D1031, the ErrorItem context and the object instance involved in the failing operation.
  2. Confirm the failure directly: record biCompression, bit count, masks and DIB header size.
  3. After you re-encode as an uncompressed or otherwise supported BMP/PNG resource, recreate the owning WMP object and verify that the corrected generation completes.

Related HRESULTs with different meanings

ResultDifferent condition
NS_E_WMP_BMP_BITMAP_NOT_CREATEDThe image parsed far enough to request a Windows bitmap but bitmap allocation or creation failed
NS_E_WMP_BMP_INVALID_FORMATThe BMP header or pixel-layout fields are internally inconsistent
NS_E_WMP_BMP_TOPDOWN_DIB_UNSUPPORTEDThe BMP is a top-down DIB representation unsupported by this WMP path

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

Change the responsible precondition rather than masking the symptom: re-encode as an uncompressed or otherwise supported BMP/PNG resource.

  • 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

Keep one fixture that reproduces 0xC00D1031 and one corrected fixture that changes only the identified precondition.

Technical references


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