IntactFile

"This item was encoded in a format that's not supported" (0xc00d5212)

Windows raises 0xc00d5212 for two very different reasons: either your player is missing a codec for a perfectly healthy file, or the file itself is damaged. The fix depends entirely on which — so the first job is to tell them apart.

Your file never leaves your device — repair runs in your browser. 0 bytes uploaded.

Your data is the big block — usually intact. What breaks is the small index. Repair rebuilds it.

Drop a file here or browseTap to choose a file

ZIP · Office · PDF · video · JPG · PNG · RAR/7z · SQLite — repaired right here in your browser. Nothing is uploaded

0 bytes uploadedFree: 3 repairs/day — up to 500 MB video, 100 MB docs & archives, 50 MB photos. Free download. Single repair €5.90. No account required.

Fix it now

  1. Drop the file
  2. Repair runs locally
  3. Download the result

You try to open a video in Windows Media Player or the Movies & TV app and get: "Can't play. This item was encoded in a format that's not supported. 0xc00d5212." This is a playback error, not a diagnosis — it means Windows couldn't decode what it found inside the container (AVI, MKV, MOV or MP4). There are two root causes with two different fixes: a missing/mismatched codec (the file is fine), or an actually corrupt file (the file needs repair). This page helps you tell which, and — when it's genuine damage — rebuilds the container in your browser with nothing uploaded.

Cause 1: a codec gap (the file is fine)

A video file is a container (the .mp4, .mkv, .avi or .mov wrapper) holding streams encoded with a specific codec. Windows only decodes the codecs it ships with. Feed it something it doesn't have — a legacy MPEG-4 / DivX / Xvid stream in an AVI, an older MOV codec like ProRes or Cinepak, or HEVC/H.265 without the HEVC Video Extension installed — and it throws 0xc00d5212 even though the file is perfectly intact.

The tell: the same file plays fine in VLC (which bundles its own decoders) or on another device. If it does, you have a codec gap, not damage — install the right codec/extension or just use VLC, and you're done. Nothing needs repairing, and no repair tool (this one included) can add a codec to your system. Only rule this out first so you don't try to "fix" a healthy file.

Cause 2: a corrupt or damaged file (repair it)

If the video also fails in VLC, opens to audio-only, shows 0:00 length, or won't open at all, the file itself is likely damaged. Common origins: an interrupted or incomplete download, a camera or app that was cut off before it finalized the file (leaving an MP4/MOV with valid frames but no moov index), a truncated transfer, or bad sectors on the source drive. Here the container's map of the streams is broken, so Windows can't even work out what to decode — and reports the same 0xc00d5212.

This is the case a rebuild fixes. Drop the file above and the tool inspects the container in your browser: it locates the surviving video and audio data and reconstructs the index (the sample tables and offsets) a player needs, producing a file that opens again. It works on MP4 and QuickTime MOV, which share the same underlying atom structure. Converting the file to MP4 in a healthy player is another route when the file isn't corrupt — but if it won't open anywhere, a container rebuild is what's needed first.

What this can and can't fix

Can fix

  • A damaged MP4/MOV that fails everywhere (including VLC) because its index is broken or missing
  • A file left unfinalized by a camera or app that was cut off before writing the moov
  • Truncated or partially-downloaded video, salvaging the frames that arrived
  • Container damage: wrong offsets, bad timestamps, zero-length duration

Can't fix

  • A healthy file that only fails because Windows lacks the codec (install the codec / use VLC — nothing to repair)
  • Adding a missing codec or HEVC extension to your Windows install (that's not a file repair)
  • The part of a truncated download that never arrived
  • Files that read as 0 bytes or mostly zeros

If a repair fails, we tell you why (missing data versus broken structure), and you are never charged for a failed repair.

FAQ

How do I know if 0xc00d5212 is a codec problem or a broken file?

Open the same file in VLC. If it plays, the file is fine and you just need the right codec (or keep using VLC). If VLC also fails, opens audio-only, or won't load it, the file is likely corrupt and a container rebuild is the fix.

The file plays in VLC but not in Windows Media Player. Should I repair it?

No — that's a codec gap, not damage. Installing the matching codec/extension (for example the HEVC Video Extension for H.265) or simply using VLC solves it. Repairing a healthy file achieves nothing.

It won't play anywhere and I can't re-download it. Can you help?

Yes. If the file is genuinely damaged, the tool rebuilds the MP4 or MOV container around the surviving video and audio so it opens again — all inside your browser.

Do I have to upload the video to fix it?

No. The file is read from your disk and rebuilt in your browser tab; nothing is transmitted. You can confirm 0 bytes leave your machine in the browser's Network tab.

Related: Fix error 0xc00d36c4 · Repair MP4 (any source) · Repair a video file