You're sitting there, batch-converting a bunch of video clips for a client's kiosk display, and the job dies at 47% with NS_E_INVALID_VIDEO_WIDTH_ALIGN (0XC00D1BCC). Or you're pulling an old AVI into Windows Movie Maker and it just refuses to import. I've hit this more times than I can count, usually when someone hands me a file from a cheap dashcam or a phone app that records at odd resolutions like 640x480 (that one's fine actually, but 854x480? Nope). The error means the video's width isn't a multiple of the alignment requirement—usually 4 pixels, sometimes 8, depending on the encoder.
Why this happens
Video encoders like Windows Media Encoder, Expression Encoder, or even FFmpeg when using certain codecs (think WMV, VC-1, or H.264 with specific profiles) require the width to be divisible by 4, 8, or even 16. This is because compression works on blocks of pixels—macroblocks are typically 16x16, but some formats use 4x4 transforms. If the width isn't aligned, the encoder can't split the frame cleanly, so it spits out this specific error code.
The trigger is almost always a source file that was created with a non-standard resolution. I had a client last month whose security camera DVR exported footage at 704x480—that's fine, 704/4=176. But then they got a new camera that recorded at 720x480, still fine. The trouble starts with oddball stuff like 640x360? No, that's fine too. Wait, let me think. The real culprits are like 1022x574, or 1280x718. Someone's editing software resized wrong, or a screen recorder captured a window at an uneven dimension.
The alignment value isn't always the same. Windows Media Foundation expects width to be a multiple of 4 for most cases, but some codecs demand 8 or 16. The error code 0XC00D1BCC is generic “invalid width alignment” so you don't get a straight answer on what the divisor should be. You just know it's not aligned.
How to fix it
Here's the no-fuss fix that works 99% of the time: re-encode or resize the video so the width is divisible by 4. You don't need fancy software. Here's the process step by step.
Step 1: Check the actual width
First, confirm the width. Right-click the file in Windows Explorer, go to Properties > Details. Look for “Frame width” under Video. If it's not divisible by 4 (like 1022, 718, 854), that's your problem. If you're a command-line person, Fire up PowerShell and run:
Get-Item "C:\path\to\video.mp4" | % { $_ } # But that's useless. Better: use ffprobe if you have it.
ffprobe -v error -select_streams v:0 -show_entries stream=width -of csv=p=0 input.mp4If you don't have ffprobe, just use the Properties method.
Step 2: Resize and re-encode
Simplest tool: HandBrake—free, reliable, works on Windows 10/11. Install it, open the video, and under the “Dimensions” tab, change the width to the nearest even number that divides by 4. HandBrake has a “Modulus” setting—set it to 4. It'll automatically adjust the width for you. For example, if the width is 1022, bump it to 1024. That's a 2-pixel difference, nobody will notice.
If you prefer FFmpeg (my go-to for batch jobs), run this:
ffmpeg -i input.mp4 -vf "scale=trunc(iw/4)*2:trunc(ih/4)*2" -c:v libx264 -crf 23 output.mp4That command rounds the width down to the nearest even multiple of 2 (which is a multiple of 2, but we need divisible by 4? Actually, trunc(iw/4)*4 is better. Let me correct myself:
ffmpeg -i input.mp4 -vf "scale=trunc(iw/4)*4:trunc(ih/4)*4" -c:v libx264 -crf 23 output.mp4That forces both width and height to multiples of 4, which covers all alignment needs. Run that, and the error vanishes.
Step 3: If you're using Windows Media Encoder (old but still around)
Some folks still use WME 9 for legacy stuff. In WME, go to the “Source” tab, click the video, then under “Output” set the width to a multiple of 4. Or just pre-process with FFmpeg above—it's faster than fighting the old UI.
Step 4: For Windows Movie Maker or Photos app
Same deal. Re-encode the file first, then import. I've seen too many people waste an afternoon trying to force WMM to accept a weird video. Don't. Just fix the source.
Still failing? Check these
If you've resized to a multiple of 4 and still get the error, the problem might be the container or codec. Some codecs like VC-1 require width to be a multiple of 16 in certain profiles. In that case, use a modulus of 16. In FFmpeg, change the command's trunc(iw/4)*4 to trunc(iw/16)*16. HandBrake can't force modulus 16 easily, but you can manually type the width—just make sure it's divisible by 16.
Also, check if your source file has a corrupted header. Sometimes the width metadata says 1022 but the actual frames are 1024. That mismatch can confuse encoders. Run the FFmpeg command above anyway—it'll recalculate from the actual data and align properly.
If it's a network stream or a device capture, also verify the capture settings—some capture cards default to 720x480 but with a weird aspect ratio that throws off alignment. Adjust the capture resolution to standard 720x480 or 640x480.
Bottom line: this error is lazy encoder validation, and the fix is simple—make your width a multiple of 4. Do that, and you're back to work in under ten minutes.