NS_E_UNSUPPORTED_ENCODER_DEVICE (0XC00D1B87) – Fix Webcam & Capture Card Errors

1. Corrupted or Missing Media Foundation Codecs

This is the #1 cause. I've seen this on at least a dozen machines running Windows 10 20H2 through 22H2. The error pops up when an app like OBS, Discord, or the built-in Camera app tries to access a webcam or capture card and Windows Media Foundation can't find the codec it needs.

Had a client last month whose entire print queue died because of this—turns out a Windows Update (KB5025239) hosed the Media Foundation components. The fix is simple:

1. Open PowerShell as admin (right-click Start, choose Windows PowerShell Admin).
2. Run this command: DISM /Online /Cleanup-Image /RestoreHealth
3. Let it finish—might take 10-15 minutes.
4. Then run: sfc /scannow
5. Restart your PC.

That rebuilds the system file cache and re-registers the codecs. Usually works. If not, also run this in PowerShell: regsvr32 /s /n /i:U shell32.dll and regsvr32 /s /n /i:U wmp.dll. This re-registers Windows Media Player codecs which Media Foundation depends on.

2. Outdated or Wrong Webcam Driver

Another common one. Windows Update sometimes pushes a generic driver that doesn't have the proper encoder support. I've seen this with Logitech C920 cameras and Elgato Cam Link capture cards. The device shows up in Device Manager but produces this error when you try to use it.

Here's the fix:

1. Right-click Start > Device Manager.
2. Expand Cameras or Sound, video and game controllers.
3. Find your webcam or capture card. Right-click > Properties > Driver tab.
4. If it says Microsoft driver or a generic one, click Update Driver > Browse my computer for drivers > Let me pick from a list.
5. Choose the manufacturer's driver from the list (if available). If not, uninstall the device (check Delete driver software) and reboot.
6. After reboot, go to the manufacturer's website and grab the latest driver. For Logitech, use Logitech G Hub. For Elgato, use the installer from their site—never rely on Windows Update for these.

One thing I've learned: the generic Microsoft USB Video Class driver doesn't support hardware encoding on most devices. You need the OEM driver.

3. Capture Card Not Getting Enough Power or Bandwidth

This one bites people with USB 3.0 capture cards like the Elgato HD60 S or the AVerMedia Live Gamer. If you plug it into a USB 2.0 port or a USB hub that's sharing bandwidth with other devices, the encoder can't initialize. The error code is the same: 0XC00D1B87.

Fix:

1. Plug the capture card directly into a motherboard USB 3.0 or 3.1 port—never a front-panel port or a hub. I've seen people use the USB port on their monitor; that's a USB 2.0 hub, no good.
2. Check the cable. If it's a USB-C device, try a different cable—preferably the one that came with it. Cables matter.
3. If you're on a desktop, use a USB 3.0 port on the back. Laptops? Use the USB port on the side that has the SS (SuperSpeed) icon.
4. Disconnect any other high-bandwidth USB devices (external hard drives, VR headsets) and try again.

Had a client who was convinced his Elgato was dead. I moved it from a USB hub to a direct port and it worked instantly. He felt stupid but was happy.

Quick-Reference Summary Table

If none of these work, you might be dealing with a hardware failure—try the device on another PC. But 90% of the time, it's one of these three. I've fixed this error on everything from a $20 USB webcam to a $300 capture card. You're probably fine.