0XC00D1BDC

NS_E_INVALID_INTERLACE_COMPAT (0XC00D1BDC) Fix

Windows Errors Intermediate 👁 2 views 📅 May 29, 2026

Windows Media Player 7 refuses videos with interlacing flags it can't handle. Real fix: re-encode without interlacing or use a modern player.

Quick answer

Drop the video into VLC or MPC-HC, or re-encode it with FFmpeg using -vf bwdif to remove interlacing. WMP7 just can't handle certain interlaced formats.

What's actually happening here

Windows Media Player 7 is old. Really old—shipped with Windows 2000 and early XP. Back then, video interlacing was a mess. The error 0XC00D1BDC with message NS_E_INVALID_INTERLACE_COMPAT means WMP7 found a video flag that says "I'm interlaced" but in a way its decoder doesn't support. Specifically, it's the INTERLACE_COMPAT property in the Windows Media format—a flag that tells the player how to handle interlaced frames. WMP7 only understands a subset of those flags. If your video was encoded with a newer tool (like Windows Media Encoder 9 or a third-party tool) that set a flag WMP7 doesn't know, you get this error. The video itself might play fine in anything else.

The trigger: you're probably trying to play an old .wmv or .asf file encoded with a later version of the Windows Media SDK, or someone used a custom profile. I've seen this on Win2K machines with archived conference recordings.

Fix steps

  1. Try a modern player first. VLC or MPC-HC will ignore the interlacing flag and just deinterlace on the fly. Download VLC from videolan.org. Open the file. If it plays, you're done. This is the real fix—don't fight old software.
  2. If you must use WMP7, re-encode the video. Use FFmpeg:
    ffmpeg -i input.wmv -vf bwdif -c:v wmv2 -c:a wmav2 output.wmv
    The bwdif filter removes interlacing completely. wmv2 is a codec WMP7 understands; use wmv1 if that fails. This strips the problematic flag.
  3. Check your FFmpeg version. Old builds might not support bwdif. Use ffmpeg -version; anything 4.0+ works. If you can't update, use -vf yadif instead—older but same idea.
  4. Test the re-encoded file. Open it in WMP7. If you still get the error, the new file might have the same flag. Re-run FFmpeg with -top 0 to force field order: ffmpeg -i input.wmv -vf bwdif -top 0 -c:v wmv2 output.wmv. That tells the encoder to mark the video as progressive (no interlacing).

Alternative fixes if the main one fails

  • Use Windows Media Encoder 9 (the old one). It writes flags WMP7 understands. Convert using WME9's GUI: load the file, set output to "Windows Media Video 9" with no interlacing. This is tedious but authentic.
  • Strip metadata with ASFChop. From the Windows Media SDK (old, but findable), asfchop -i input.wmv -o output.wmv sometimes rewrites headers cleanly. Doesn't always work, but worth a shot if re-encoding is too heavy.
  • Patch the registry. Not recommended, but you can make WMP7 skip the interlacing check entirely. Add a DWORD at HKEY_CURRENT_USER\Software\Microsoft\MediaPlayer\Player\Settings\EnableInterlaceCheck set to 0. This disables the check and may cause visual artifacts (combing) but the video will play.

Prevention tip

Don't use WMP7 for anything modern. If you're archiving old video for long-term use, always encode progressive (no interlacing). In FFmpeg, that means using -vf bwdif at encode time. If you must keep interlacing for broadcast or CRT displays, use a container like MP4 with H.264—those players don't have this problem. For WMV files specifically, stick to profiles created by Windows Media Encoder 9 or later, and test playback on your target player before distributing.

Key takeaway: This error isn't about a broken file. It's about a flag WMP7 can't read. Changing the flag—either by switching players or re-encoding—is the only reliable path.

Was this solution helpful?