JPEG 0XC00D103E Error: Unsupported SOF Marker Fix

What 0XC00D103E Actually Means

I know this error is infuriating. You double-click a photo, Windows Media Player opens instead of Photos, and you get smacked with 0XC00D103E and a mouthful of jargon: NS_E_WMP_JPG_SOF_UNSUPPORTED. The file isn't corrupt. Your PC isn't broken. WMP just found a JPEG Start-Of-Frame (SOF) marker it refuses to handle.

Every JPEG starts with byte markers that tell the decoder what kind of compression it's looking at. SOF0 is baseline. SOF1 is extended sequential. SOF2 is progressive. WMP happily reads SOF0 and SOF1. The moment it hits something like SOF2, SOF3, SOF9, or a weird embedded profile from a scanner or phone app, it throws this exact code and quits.

This trips people up because the same JPEG opens fine in Chrome, Photoshop, or even Windows Photos. That's the tell — if another app shows the image without complaint, your file is fine and WMP is the picky one.

Cause 1: Progressive (SOF2) JPEG — The Most Common Trigger

Nine times out of ten, the file was saved as progressive JPEG. Adobe Photoshop, Lightroom, GIMP, and most web export tools default to progressive because it makes files smaller and loads nicer on slow connections. Great for the web. Useless to WMP.

You'll see this constantly with photos downloaded from WordPress sites, stock photo sites, or anything that went through an image optimizer like ImageOptim, Squoosh, or TinyPNG. Those tools love progressive encoding.

The fix: re-save as baseline

Fastest route is Photoshop or GIMP. In Photoshop: File > Export > Export As, pick JPEG, then uncheck Progressive. Save. WMP will now open it.

Got a folder full of them? Use ImageMagick from a command prompt. Install it, then:

magick mogrify -interlace none *.jpg

That strips progressive encoding and rewrites each file as baseline in place. Two seconds for a hundred images. If you don't want to touch the originals, copy them to a scratch folder first.

On a Mac with sips already installed (any modern macOS):

sips -s format jpeg --setProperty formatOptions normal input.jpg --out output.jpg

Do this and 0XC00D103E disappears.

Cause 2: CMYK or 12-bit Color Space JPEGs

Second most common. Print shops, scanners, and old design pipelines save JPEGs in CMYK color instead of RGB. A CMYK JPEG uses a different SOF structure — typically SOF0 with 4 components, or occasionally a variant WMP won't touch. WMP is built for consumer media. CMYK isn't consumer media.

Same story with 12-bit or 16-bit JPEGs from high-end scanners or scientific imaging gear. WMP expects 8-bit RGB. It sees the metadata, decides it's not worth the effort, and bails with 0XC00D103E.

The fix: convert to 8-bit sRGB

In Photoshop: Image > Mode > RGB Color, then Image > Mode > 8 Bits/Channel. Export as JPEG with progressive off. Done.

In GIMP: Image > Mode > RGB and Image > Precision > 8-bit integer.

Batch converting with ImageMagick:

magick mogrify -colorspace sRGB -depth 8 *.jpg

If you're on Linux and don't have ImageMagick, install it with sudo apt install imagemagick on Debian/Ubuntu or sudo dnf install ImageMagick on Fedora.

Cause 3: Corrupt or Truncated SOF Marker

Less common but nastier. Sometimes the JPEG's SOF marker itself is damaged — a half-finished download, a drive that dropped a write, or a transfer over a flaky USB cable that ate a few bytes. The file might still render in browsers because they're forgiving and skip garbage. WMP isn't forgiving. It hits a malformed SOF header and returns NS_E_WMP_JPG_SOF_UNSUPPORTED.

The giveaway: the same file fails in Photos, Paint, and WMP, but opens fine in Chrome or Firefox. Or the file size looks suspiciously small for the resolution.

The fix: repair or re-download

If the file came from an email or download, re-download it. Seriously. Don't spend an hour repairing what took five seconds to fetch again.

If it's irreplaceable — old family scans, a client's photo shoot — try a repair tool. JPEGsnoop (free, Windows) will show you the exact SOF marker and whether the header is damaged. For actual repair, jpegtran from the libjpeg-turbo package can sometimes rebuild a broken header:

jpegtran -copy none -optimize broken.jpg > fixed.jpg

If that fails, Stellar Repair for Photo or JPEG Recovery Pro are the paid tools that actually work on severely damaged files. I've seen Stellar pull usable images out of JPEGs that every free tool gave up on. Worth the $40 if the photo matters.

One more thing: if your drive is throwing this error on multiple files it opened fine last month, run chkdsk /f and check the drive's SMART status. Random SOF corruption is an early sign of a failing disk.

Stop WMP From Opening Photos at All

Honestly? The cleanest fix is to stop letting Windows Media Player be your default image viewer. It was never designed for photos and this error is only one of about a dozen ways it'll annoy you.

Set the default properly:

1. Press Win + I to open Settings.
2. Go to Apps > Default apps.
3. Scroll to Windows Photo Viewer (or install IrfanView or ImageGlass — both are far better than Photos).
4. Click it, then set .jpg and .jpeg to that app.

On Windows 11, the Photos app handles progressive and CMYK JPEGs without blinking. If you actually want to use WMP for a slideshow, convert the files first using the ImageMagick commands above.

Quick Reference

Start with the progressive-JPEG check. It fixes the majority of 0XC00D103E reports in under a minute, and once you've converted the offending file you'll never see this error again from it.