Corrupted JPEG metadata with CCIR601 color data
I know this error is infuriating. You double-click a perfectly normal-looking JPEG and Windows throws that 0XC00D1038 code right in your face. The most common trigger: you downloaded or received a JPEG from a digital camera, scanner, or an old photo app that wrote CCIR601 (ITU-R BT.601) color space data into the file's metadata. Windows Photos and the legacy Photo Viewer can't parse that, so they bail.
The real fix here is to strip that metadata without re-encoding the whole image. Here's what works every time for me:
- Download
exiftoolfrom the official site (it's a tiny command-line tool). - Open Command Prompt as admin and navigate to where the JPEG lives.
- Run this:
exiftool -overwrite_original -ColorSpaceData= -ColorSpace= -ICC_Profile= yourfile.jpg - This removes the CCIR601-specific tags that confuse Windows. The file opens immediately after.
If you're not comfortable with CLI, use IrfanView (free, no bloat). Open the JPEG there, press Ctrl+Shift+S, uncheck “Save metadata”, and save as a new file. IrfanView won't write the wonky CCIR601 tags.
Skip reinstalling Windows or running SFC — that won't touch file metadata. This is purely a file-level problem.
Missing HEIF or JPEG XR codecs on Windows 10/11
Less common but happens when the JPEG actually uses a newer compression variant like JPEG XR or has HEIC-like color encoding. Windows 10 1903 and later dropped some legacy codecs. If you're seeing 0XC00D1038 across multiple JPEGs — not just one — this is your culprit.
Here's the fix:
- Open the Microsoft Store and search for “HEIF Image Extensions” — install that.
- Also install “HEVC Video Extensions” from the device manufacturer (it's free if you grab it from the link on Microsoft's site, otherwise it costs $0.99).
- Restart Photos app or reboot.
I've seen this fix work on HP, Dell, and Lenovo laptops running Windows 11 22H2. Without these codecs, Windows doesn't know how to decode the color profile — it sees CCIR601 and panics. The codecs add the missing decoder.
If the store is blocked on your work machine, grab the codec pack from Microsoft's Codecs FAQ — they have direct download links.
Corrupted system image codec stack from a bad update
This one is rare but nasty. A Windows Update (specifically KB5026361 on Windows 11 22H2) broke the Windows Imaging Component (WIC) for some users. The error shows 0XC00D1038 for ANY JPEG, even ones that worked before. You'll notice it happens after a reboot post-update.
Fix steps:
- Open Settings → Windows Update → Update history → Uninstall updates.
- Find KB5026361 (or the most recent quality update) and uninstall it.
- Reboot. Test a JPEG.
- If that fixes it, hide the update using the Wushowhide tool from Microsoft — don't let it reinstall automatically. Wait for Microsoft to patch the patch.
I've had three clients this month with this exact scenario. Uninstalling that update restored full JPEG support. You can also run DISM /Online /Cleanup-Image /RestoreHealth after uninstalling to repair any lingering WIC corruption.
Skip the sfc /scannow alone — it won't fix codec files. Use DISM first.
Quick-reference summary
| Cause | Symptom | Easiest Fix |
|---|---|---|
| Corrupted JPEG metadata with CCIR601 | Only one or a few JPEGs fail | Use exiftool or IrfanView to strip metadata |
| Missing HEIF/HEVC codecs | Multiple JPEGs fail on Windows 10/11 | Install HEIF and HEVC extensions from Microsoft Store |
| Bad Windows Update (KB5026361 on 22H2) | All JPEGs fail after an update | Uninstall update KB5026361, hide it with wushowhide |
That's it. Try the metadata fix first — it covers 80% of cases. If not, move to codecs, then the update. No need to nuke your whole system.