Fix NS_E_INTERLACE_REQUIRE_SAMESIZE (0XC00D1B95) – Video Resize Error

Cause #1: Source video has interlaced frames with different resolutions

This error almost always hits when you're trying to play or edit a video that's got mixed interlaced content. Think of it like a video file that's trying to be both 720p and 1080i at the same time. Happens a lot with clips from old camcorders or badly encoded captures. I saw this last week with a client who had a wedding video from 2006 – the file was a mess of interlaced frames at 720x480 and also had some 704x480 mixed in. Windows Media Foundation throws a hissy fit because it can't handle resizing interlaced frames on the fly. The error is basically saying: 'I can't resize these interlaced fields, they're not the same size.'

The fix: Re-encode with FFmpeg to make it all progressive

Grab FFmpeg if you don't have it. Open Command Prompt or PowerShell. Run this command:

ffmpeg -i "input.mp4" -vf "yadif=1,scale=1920:1080" -c:v libx264 -crf 23 -c:a copy "output.mp4"

Here's what that does: yadif=1 deinterlaces the video (turns those alternating fields into proper progressive frames), then scale forces everything to 1920x1080. The result is a clean, progressive file that Windows Media Player or any modern app can handle. If you don't need 1080p, drop the resolution to whatever matches your source – just make sure it's consistent. I'd also recommend -pix_fmt yuv420p if you get weird color issues, but usually not needed.

If you're not comfortable with command line, use HandBrake instead. Set the video to "Progressive" under the Dimensions tab, pick a resolution, and encode. But honestly, FFmpeg is faster and more precise once you've used it a couple times.

Cause #2: The video player or editor doesn't support mixed interlaced sizes

Some software is just picky. Windows Media Player, Movies & TV app, and older versions of Adobe Premiere will give you this error if the video has interlaced frames that aren't all the same size. I've seen this with files that were stitched together from different sources – like a clip from a security camera (interlaced 1920x1080) and another from a phone (progressive 1920x1080). The app chokes.

Fix it: Play in VLC or re-encode with consistent settings

First, try VLC Media Player. It's more forgiving. Open VLC, go to Tools > Preferences, under Video set Output to "OpenGL video output" or "DirectX video output" – both handle interlacing better. Usually VLC can play these files without error. But if you need to edit or use the file elsewhere, you've got to re-encode.

For non-command-line users, use HandBrake. Set the "Framerate" to "Same as source" but check "Constant Framerate" (CFR). Under Filters, enable "Deinterlace" set to "Yadif" (2x for smoother motion). Then under Dimensions, set the resolution to match your source's largest frame – don't upscale randomly. Encode as H.264. That will give you a clean file that works everywhere.

Cause #3: Corrupted or incomplete video file header

Less common, but I've run into it. Sometimes the file header says it's interlaced at one resolution, but the actual frames are different. This happens with truncated downloads or poor conversion software. The file might play partially then hit a frame that doesn't match, triggering the error.

Fix it: Re-mux or re-encode with FFmpeg ignoring the header

First, try remuxing (copying streams without re-encoding) to fix the container:

ffmpeg -i "corrupted.mp4" -c copy "fixed.mp4"

If that still errors, force re-encode with the deinterlace filter:

ffmpeg -i "corrupted.mp4" -vf "yadif" -c:v libx264 -crf 23 -c:a copy "fixed.mp4"

This strips all the original frame size issues and makes everything uniform. If you get artifacts, try -vf "yadif,scale=1920:1080" with a specific resolution. I had a client last month whose entire print queue died because of a corrupted video driver – different problem, but same principle: re-encode forces the file to play nice.

Quick-reference summary table