Fix 0XC00D1BDB: Interlace Mode Not Supported by Codec

The 30-Second Fix: Switch Players

This error means Windows Media Player (or whatever Media Foundation app you're using) hit a video file with interlaced content that the codec doesn't support. I've seen this most often with old MPEG-2 captures from TV tuners or camcorder footage that was encoded as interlaced instead of progressive. The quickest way around it: don't use Windows Media Player.

Download VLC Media Player or MPC-HC. Both handle interlaced video natively without breaking a sweat. Open the file in VLC. If it looks fine, you're done. Seriously, that's it for most people. Windows Media Player has been half-baked for interlaced content since Vista. VLC won't give you this error because it uses its own decoders, not the system ones.

Still seeing the error in VLC? Then it's not a codec issue—it's the file itself. Skip to the advanced section.

The 5-Minute Fix: Change the Video Renderer in Windows Media Player

If you're stuck using Windows Media Player (maybe for DRM content or a work app), you can force it to use a different video renderer that handles interlace better. I've fixed this for a client who had a kiosk setup that only ran WMP.

1. Open Windows Media Player.
2. Press Alt to show the menu bar if it's hidden.
3. Go to Tools → Options.
4. Click the Performance tab.
5. Under Video acceleration, click Advanced.
6. In the Video Acceleration Settings window, uncheck Use high-quality mode (sometimes labeled "Use DirectX VA") and check Use Overlays if available.
7. Click OK, then OK again.
8. Try playing the file. If it works, the overlay renderer bypassed the interlace issue.

Still broken? Undo that change and try this: In the same Performance tab, slide the Video acceleration slider down one notch (from Full to some middle setting). That disables hardware decoding, forcing software decoding that often handles interlace better.

The 15-Minute Fix: Re-encode the Video to Progressive

If you need to keep the original file playing in any app, re-encode it to progressive. This is the nuclear option, but it fixes everything. Use HandBrake (free, open source).

1. Download and install HandBrake.
2. Open HandBrake and load your video file.
3. Under the Summary tab, set the output format to MP4 or MKV.
4. Go to the Video tab.
5. For Video Encoder, pick H.264 (x264) or H.265 (x265). Both work.
6. Under Framerate (FPS), choose Same as source.
7. The key setting: Under Advanced Options, check Interlace Detection and set Deinterlace to Yadif (or BWDIF for higher quality). This converts interlaced to progressive.
8. Click Start Encode. Depending on file size, it'll take 5-30 minutes.
9. Play the new file in Windows Media Player—no error.

Why this works: The original file was recorded with interlaced frames (two fields per frame). Most modern codecs expect progressive frames. Deinterlacing merges those fields into a single frame before encoding. I had a client last month whose old wedding video (DV camcorder, interlaced) wouldn't play on their new laptop. After re-encoding with HandBrake, it played everywhere.

Still Stuck? Check Your Codec Pack

If you're using a codec pack like K-Lite or Combined Community Codec Pack, it might be overriding the system decoders with one that doesn't support interlace. Uninstall the pack temporarily and see if Windows' default Microsoft decoders work. If they do, reinstall a lightweight codec pack (like LAV Filters standalone) instead—they handle interlace properly.

One more thing: Some old MPEG-2 files from broadcast TV have flags that confuse players. You can strip those flags with a tool like ffmpeg:

ffmpeg -i input.mpg -c copy -bsf:v h264_metadata=interlace=0 output.mpg

That copies the video without re-encoding but clears the interlace flag. It works maybe 50% of the time, but it's worth a shot if you're desperate.

Bottom line: This error is almost always a player or codec limitation, not a broken file. Switch players first, then try renderer settings, then re-encode. I've never seen a case where all three failed.