Error 0xc10100be "This file isn't playable": how to fix it on Windows
By the FixMP4 engineering team · · 7 min read
Error 0xc10100be appears in the Windows Media Player app (and the older Movies & TV app) with the message "This file isn't playable. That might be because the file type is unsupported, the file extension is incorrect, or the file is corrupt." The three possibilities in that sentence are a good checklist. In practice the codec is the most common culprit, a wrong extension comes second, and real corruption third. This guide shows how to tell them apart in a few minutes and what to do for each one.
Step 1: try the file in VLC
Before changing anything on your system, install VLC media player (free, from videolan.org) and open the file with it. VLC ships with its own decoders and ignores file extensions, so it is the quickest test available:
- VLC plays it normally: the file is fine. Windows is missing a decoder or is confused by the extension. Continue with steps 2 and 3, or simply keep using VLC.
- VLC plays it with glitches or stops early: the file is partly damaged. Skip to step 4.
- VLC shows nothing, or the time bar stays at 00:00: the file is probably structurally broken. Skip to step 4.
Step 2: find the real format with MediaInfo
MediaInfo is a small free tool that reads a file's headers and reports what is really inside. Open the file in it and switch to the Text or Tree view. Look at three lines:
- Format in the General section: MPEG-4, QuickTime, Matroska, AVI, MPEG-TS, WebM and so on.
- Format in the Video section: AVC (H.264), HEVC (H.265), AV1, VP9, MPEG-4 Visual, MPEG-2.
- Format in the Audio section: AAC, AC-3, E-AC-3, DTS, FLAC, PCM.
Write these down; the fix depends on them.
Step 3a: the extension does not match the content
Download managers, screen recorders and messaging apps sometimes save a file with the wrong ending. A Matroska file named clip.mp4, or an MPEG transport stream named video.mov, will trip the Windows app because it picks a parser based on the extension and then finds data it does not expect.
If MediaInfo's General format disagrees with the extension, make a copy of the file and rename the copy:
| General format in MediaInfo | Extension to use |
|---|---|
| MPEG-4 | .mp4 (or .m4a for audio only) |
| QuickTime | .mov |
| Matroska | .mkv |
| WebM | .webm |
| MPEG-TS | .ts |
| AVI | .avi |
Turn on "File name extensions" in File Explorer's View menu first, otherwise you may end up with a name like clip.mkv.mp4.
Step 3b: the codec is not supported
Windows includes decoders for H.264 and AAC, but several common formats need an extra component:
- HEVC / H.265 (iPhones, many Android phones, drones, action cameras): install HEVC Video Extensions from the Microsoft Store. It is a paid extension for most users; some PCs came with it preinstalled. More detail is in our guide to repairing and playing HEVC video.
- AV1: install the free AV1 Video Extension from the Store.
- VP9 and WebM: the VP9 Video Extensions and Web Media Extensions packages cover these.
- MPEG-2 and DVD rips: Microsoft offers an MPEG-2 Video Extension in the Store; VLC handles MPEG-2 for free.
- Older formats such as DivX, Xvid in AVI, RealMedia or WMV variants from old cameras: the modern Media Player app does not handle all of them; use VLC or convert the file.
When the clip has to open in the Windows app itself (on a meeting-room laptop, a kiosk or a relative's PC), re-encode a duplicate with HandBrake's "Fast 1080p30" preset. It produces the most widely supported combination: an MP4 holding H.264 picture and AAC sound.
Step 4: when the file itself is damaged
If VLC also fails, the third possibility in the error message is the likely one. Damaged videos tend to fall into recognisable groups:
- Recording interrupted: a phone or camera lost power, the app crashed, or a screen recorder was killed. The video frames were written, but the index at the end of the file (the moov atom in MP4 and MOV) never was. The file size looks right but no player can read it.
- Copy interrupted: a transfer from a phone, card or cloud stopped early. The end of the file is missing. Compare the size with the original if you still have it.
- Storage damage: a failing SD card or drive returned bad sectors. Parts of the file contain zeros or unrelated data.
The first two cases are the most recoverable. If the original source still exists (phone, card, cloud), copy it again before trying anything else; a fresh copy often solves an interrupted transfer completely.
If the file you have is the only copy, open the FixMP4 repair tool. It inspects the file locally in your browser, tells you whether the index is missing, and rebuilds it from the video and audio data that is still there. For recordings from phones and cameras, adding a short healthy clip shot with the same device and settings gives the tool the codec details it needs. A free preview of your own repaired footage plays before you decide to buy the export, so you can confirm the recovery worked.
FixMP4 handles H.264 and HEVC video with AAC audio in MP4, MOV and M4A files. For AVI, MKV or professional codecs, a different tool is the better choice.
Related Windows errors
Windows media apps use several codes for overlapping problems, and the fix often carries over:
- 0xc00d36c4 is the classic "can't play" code for unsupported or corrupted files.
- 0xc00d5212 points specifically at a missing codec.
- 0x80004005 is an unspecified error that can hide either.
- 0xc1010103 appears in the Photos app and older Movies & TV builds.
System-wide remedies, like resetting the media apps or installing a newer graphics driver, are gathered in our Windows MP4 playback guide.
Quick checklist
- Test in VLC to separate a Windows problem from a file problem.
- Read the real container and codec with MediaInfo.
- Rename a copy if the extension is wrong.
- Install the matching codec extension, or convert to H.264 and AAC.
- If nothing plays the file, copy it again from the source, then repair the index.
Following this order means you never spend money on a codec when the extension was the problem, and never reach for repair software when the file was healthy all along.
A similar message with the code 0xc00d1199 usually points to a missing decoder for older formats such as AVI or FLV; see error 0xc00d1199.
Frequently asked questions
What does error 0xc10100be mean?
It is the Windows media apps' way of saying they gave up on the file. The full message names three suspects: a file type the app does not support, an extension that does not match the real format, or a damaged file. The code itself does not tell you which one applies, so you test them in order.
Does 0xc10100be mean my video is corrupted?
Not necessarily. Most of the time the file plays fine in VLC, which proves the data is intact and the problem is a missing codec or a mislabelled extension. Only when every player rejects the file, on every computer, is damage the likely explanation.
Will renaming the file fix 0xc10100be?
Only if the extension was wrong to begin with, for example a Matroska file saved as .mp4 by a download tool. Renaming never converts the content. If you are unsure, look at the real format with MediaInfo first and rename to match what it reports.
Can I fix 0xc10100be without installing anything?
Sometimes. Opening the file in a different built-in app, such as the Photos app or a browser tab, can work for common formats. For HEVC, older codecs or a damaged index you will need VLC, a free codec extension from the Microsoft Store, or a repair tool.
Have a broken recording right now?
Diagnose it and hear or watch a free repaired preview. Nothing is uploaded.
Open the repair tool