Error 0xc00d36c4 "This File Isn't Playable" on Windows

You double-click a video, the Movies & TV app opens (Windows 11 calls it Media Player now), and instead of your footage you get "This file isn't playable" with 0xc00d36c4 in small print underneath. The wording makes it sound like the file is damaged. Usually it isn't.

What the code actually means

Movies & TV, the newer Media Player app, and Groove all sit on Media Foundation, the playback framework built into Windows. When Media Foundation fails to open a stream, it reports 0xc00d36c4 without saying why. "I have no decoder for this codec" and "this file is damaged" both produce the same code, and that ambiguity is why the advice about this error is so contradictory online.

In practice the causes rank roughly like this:

1. Missing codec, almost always HEVC. By far the most common.
2. A container Windows doesn't handle well (some MKVs, old AVIs, unusual MOV variants).
3. Actual corruption, typically from an interrupted transfer or an interrupted recording.

The HEVC case (start here)

Windows has not shipped an HEVC (H.265) decoder by default since 2017. Meanwhile most recent phones record HEVC out of the box: iPhones in High Efficiency mode, many Android flagships, GoPro's higher-quality modes, DJI drones. Copy one of those files to a Windows PC and 0xc00d36c4 is the standard greeting.

Microsoft sells the missing piece as "HEVC Video Extensions" in the Microsoft Store, currently $0.99. Some PCs come with it preinstalled by the manufacturer, which is why the same file can play on one machine and fail on another.

Before spending anything, open the file in VLC. VLC carries its own decoders and ignores whatever Windows has installed. If VLC plays the file, the file is healthy. Buy the extension, or just keep watching in VLC, and stop worrying about corruption.

When it's really corruption

If VLC refuses the file too, the picture changes. Damage from these sources shows up under 0xc00d36c4 all the time:

• A copy from an SD card or phone that got interrupted (a pulled cable, a reader that disconnected, a card error mid-transfer).
• A recording the camera or phone never finished because the battery died or the app crashed.
• A download that stopped early but kept the .mp4 name.

Signs pointing to a damaged file rather than a codec gap:

• VLC fails as well, often with "moov atom not found" in its message log.
• Properties show a plausible size but the duration reads 0:00.
• Other videos from the same phone or camera play fine on the same PC.
• The file is noticeably smaller than its siblings from the same shoot.

Why a chopped file dies instantly

MP4 and MOV files keep their index (the moov atom) separate from the actual frames (the mdat atom). Cameras and phones typically write the index when the recording stops cleanly. Interrupt the recording, or chop the tail off during a transfer, and you get frames without a map. A player reads the index first, finds nothing, and gives up on the spot. That's why the failure is total and immediate rather than a video that plays partway and stops.

The practical consequence is that the frames are usually still in the file. Playback fails because the map is missing, not because the footage is gone.

How our recovery handles these files

• The index is rebuilt from the stream itself. No reference clip needed; codec parameters are read from the frames.
• H.264 and HEVC both handled, which covers essentially every file that triggers this error on consumer hardware.
• Audio comes back too. AAC (phones, drones, action cams) and PCM are reconstructed alongside the video.
• Proof before payment. You get a free 5-second preview of the recovered footage first. If the preview is wrong, you pay nothing.

What you do

1. Upload the file. Free.
2. About a minute later, watch the free 5-second preview.
3. Pay from $5 only if the preview shows your footage.

Files sit on EU servers and are auto-deleted after 48 hours.

FAQ

Is the $0.99 HEVC Video Extensions purchase legitimate? Yes, it's a Microsoft product in the official Store. Check that you actually need it first: if VLC plays your file, the extension will make Movies & TV play it too. If VLC can't play it, the extension won't change anything.

Why do only the videos from my phone show 0xc00d36c4? Because your phone records HEVC and your downloads are mostly H.264. Windows decodes H.264 natively and HEVC only with the paid extension. That split is the classic signature of the codec case, not corruption.

I installed a codec pack and the error is still there. Codec packs target older playback frameworks and don't always register decoders where Media Foundation looks. Test in VLC before concluding anything about the file. If VLC also fails, no codec pack will help, because the container is damaged.

The same file plays on my old laptop but not my new PC. The old machine probably has HEVC support preinstalled by its manufacturer, or a codec pack from years ago. That's still a support gap on the new machine, not a broken file.

Is my file safe if I upload it? It's uploaded over HTTPS to EU servers, auto-deleted after 48 hours, and never shared or used for anything else. Privacy policy.

Related

• This file is not supported
• moov atom not found
• Recover corrupted HEVC files
• Black screen when playing video
• How our recovery engine works

Upload your file →