| Previous | Next |
| NS_E_WMP_JPG_SOF_UNSUPPORTED | NS_E_WMP_FAILED_TO_OPEN_IMAGE |
NS_E_WMP_JPG_UNKNOWN_MARKER
Where the Player stopped
The symbolic result NS_E_WMP_JPG_UNKNOWN_MARKER narrows 0xC00D103F to the JPEG unknown marker condition: the JPEG marker stream contains a marker the decoder cannot classify at its current position. Keep the JPEG unknown marker boundary visible when a later dialog reduces it to a general media error.
An additional test is to record the marker byte, offset and preceding segment length to distinguish corruption from unsupported extension data; that evidence is more useful than reinstalling the Player or changing several unrelated settings at once.
What succeeds before this failure
Representative case: A bad segment length causes image data to be interpreted as a new JPEG marker.
State worth preserving
Capture state before Player cleanup:
- What to verify: record the marker byte, offset and preceding segment length to distinguish corruption from unsupported extension data.
- Artifact: format header fields, dimensions, bit depth and color model.
- State: first invalid marker/chunk and its byte offset.
- Object identity: decoder-supported coding mode versus the file’s declared mode.
- Underlying evidence: standalone decode result outside the skin package using the same bytes.
- Correlation: archive member name, byte length, hash and file signature.
Reproduce without destroying evidence
- Preserve
0xC00D103F, the ErrorItem context and the object instance involved in the failing operation. - Confirm the failure directly: record the marker byte, offset and preceding segment length to distinguish corruption from unsupported extension data.
- After you repair the segment structure or re-export from an intact source, recreate the owning WMP object and verify that the corrected generation completes.
Related HRESULTs with different meanings
| Result | Different condition |
|---|---|
NS_E_WMP_JPG_SOF_UNSUPPORTED | The JPEG frame marker selects an unsupported coding process |
NS_E_WMP_JPG_UNEXPECTED_ENDOFFILE | The JPEG byte stream ends before the decoder reaches the markers needed to finish the image |
NS_E_WMP_JPG_IMAGE_TOO_BIG | The JPEG dimensions exceed the decoder’s accepted image-size boundary |
Recovery at the right layer
Change the responsible precondition rather than masking the symptom: repair the segment structure or re-export from an intact source.
- 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.
Technical references
- Skin files and image resources — API or format context.
- ITU-T T.81 JPEG specification — documentation for this result.
- JPEG standards overview — normative or platform material relevant to this result.
Looking for a different code? Search another status or error code.