Fix JPEG Error 0XC00D1039: No Image Found

0XC00D1039 means Windows Photo Viewer can't decode that JPEG. The file is either corrupt, mislabeled, or missing its image data. Here's how to fix it.

Quick answer

Error 0XC00D1039 means the file is either corrupt, renamed from another format (like HEIC to JPG), or missing its image data entirely. The real fix is to repair the file with a hex editor or convert it using a tool that actually decodes the format, not just renames it.

Why this error pops up

Windows Photo Viewer and the Photos app expect a JPEG to start with the magic bytes FF D8 FF and end with FF D9. When those markers are missing or the internal structure is broken, the decoder throws 0XC00D1039. This usually happens in three scenarios: a download got interrupted halfway, someone renamed a .heic or .webp file to .jpg without converting it, or the file was recovered from a failing drive and the header got zeroed out. I've seen this most often with iPhone users who AirDrop a photo, rename the extension to .jpg, and then wonder why Windows can't open it. The Photos app also triggers this if the file is stored on a network share and the read operation times out mid-stream.

Step-by-step fixes

Check the file header with a hex editor. Open the file in HxD (free, portable). The first three bytes should be FF D8 FF. If you see 00 00 00 or random garbage, the file is toast. If you see 66 74 79 70 ("ftyp"), it's actually an MP4 or HEIC file with the wrong extension.
Try opening it in a different app. Right-click the file, choose Open with, and pick Paint or IrfanView. If IrfanView opens it, the file is fine and Windows Photo Viewer is the problem — update your codecs or switch to IrfanView permanently. It handles broken JPEGs way better than the built-in viewer.
Rebuild the JPEG header. If the header is missing but the rest of the file looks like JPEG data, you can prepend the standard header. In HxD, insert these bytes at the start: FF D8 FF E0 00 10 4A 46 49 46 00 01. Save and try opening again. This works maybe 30% of the time, but it's worth a shot before you give up on the file.
Use a proper repair tool. JPEGsnoop (free) will tell you exactly where the file breaks. If it reports "no SOI marker," the header is gone. If it reports a truncated scan, the file was cut off during download. Stellar Repair for Photo is paid but actually works on truncated files — I've used it on SD card recoveries with good results.
Re-download or re-transfer the file. If this came from email or cloud storage, delete the local copy and pull it again. A 0-byte or partially downloaded file will always throw 0XC00D1039. Check the file size — a real JPEG from a phone is usually 2-5 MB. If it's 50 KB, it's incomplete.

If the main fixes don't work

Sometimes the file is genuinely unrecoverable. Before you bin it, try these:

Convert with ImageMagick. Install it, then run:
```
magick broken.jpg fixed.png
```
ImageMagick is lenient about malformed headers and will often salvage the visible portion. The output won't be perfect, but you'll at least see what the photo was.
Open it in a browser. Drag the file into Chrome or Edge. Browsers use their own decoders and sometimes render images that Windows apps reject. If it shows up, right-click and save it as a new file.
Check for alternate file streams. Right-click the file, Properties, and look for an Unblock checkbox at the bottom. Files downloaded from the internet get flagged, and that flag can cause the decoder to fail with 0XC00D1039. Unblock it and try again.
Try a different user account. If the file opens under another Windows profile, your user profile's thumbnail cache is corrupt. Delete %localappdata%\Microsoft\Windows\Explorer\thumbcache_*.db and reboot.

Prevention

Don't rename file extensions. If you have a HEIC from an iPhone, convert it properly with a tool like CopyTrans HEIC or the HEIF Image Extensions from the Microsoft Store. Also, always eject USB drives and SD cards before pulling them — interrupted writes are the number one cause of corrupt JPEGs. And if you're downloading photos from a cloud service, let the download finish completely before opening the folder. Windows will happily show you a 0-byte placeholder and then throw 0XC00D1039 when you double-click it.