Fix NS_E_ICMQUERYFORMAT (0XC00D1B6C) Video Compressor Error

First Cause: Broken or Missing Video Codec

What's actually happening here is the video compressor you're using (like the Microsoft Video 1 or Intel IYUV codec) is corrupt or missing files. When Windows Media Encoder or VirtualDub tries to get output format info from it, the codec fails with this error. I've seen this most often on Windows 10 after a major update that replaces or breaks the old codecs.

Fix: Reinstall the Codec with K-Lite Codec Pack

Skip the old codec packs like XP Codec Pack — they're outdated and cause more issues. Instead, use K-Lite Mega Codec Pack (version 17.x or newer). Here's what to do:

1. Uninstall any current codec packs from Control Panel > Programs > Uninstall a program.
2. Download the latest K-Lite Mega Codec Pack from codecguide.com (not a mirror site).
3. Run the installer. Choose "Lots of stuff" mode — this installs the video compressors you need.
4. In the "Preferred decoders" section, set "WMV" to "Microsoft" and "AVI" to "ffdshow".
5. Finish install and reboot.

The reason step 3 works is K-Lite includes a tool called "Codec Tweak Tool" that registers the video compressor DLLs properly. Most other packs skip this step.

Second Cause: Corrupt Video File Headers

Sometimes the error isn't the codec — it's the file itself. The video compressor can't get output information because the AVI or WMV file has a damaged header. I ran into this with a 4-year-old security camera recording that got corrupted during a power failure.

Fix: Repair or Re-encode the File

Try this order — don't jump straight to advanced tools:

1. Open the file in VLC Media Player. Go to Tools > Media Information to see if basic info loads.
2. If VLC can play it (even with errors), re-encode the file using HandBrake. Set video codec to H.264 and audio to AAC. This creates a clean file.
3. If VLC can't open it, use a tool like GSpot Codec Information Appliance to check the file's FourCC code (the 4-character code that identifies the codec). A broken FourCC like "??" means the header is corrupt.
4. For corrupt AVI files, try DivFix++ (freeware). It rebuilds the AVI index. Run it, load your file, click "Rebuild Index". Save the repaired copy.

Don't bother with online repair tools — they upload your file then ask for money. Stick to offline tools.

Third Cause: 32-bit vs 64-bit Application Mismatch

This one's sneaky. The error 0XC00D1B6C happens when a 64-bit application tries to use a 32-bit video compressor filter. The video compressor runs in a separate process, and when the formats don't match, it can't return the output information. Happens a lot with Adobe Premiere Pro (64-bit) and old codecs from Windows 7.

Fix: Use 32-bit Version of Your App

If you're using a 64-bit encoding tool, switch to its 32-bit version. Here's how:

• VirtualDub: Download the 32-bit version from virtualdub.org. The 64-bit version often has codec issues.
• FFmpeg: If you use the 64-bit build, add -vcodec msmpeg4v2 to force a different compressor. Or download the 32-bit ffmpeg.exe and use that.
• Windows Media Encoder: Only 32-bit exists, so this isn't usually the problem here.

You can also install the 32-bit K-Lite codec pack instead of the 64-bit one. But I find keeping both versions works fine — just launch the 32-bit app for encoding.

Quick-Reference Summary Table

If none of this works, check the Windows Event Viewer under Windows Logs > Application for a related error from the video compressor DLL. That DLL name tells you exactly which codec failed. Then you can disable that specific codec in K-Lite's Codec Tweak Tool and use a different one.