NS_E_VIDCAPDRVINUSE (0XC00D1B6E): Stream Already Active

Cause #1: Another app has the camera open

What's actually happening here is simple: Windows only lets one application grab a video capture device at a time. If you're seeing 0XC00D1B6E, something else already opened your webcam or capture card and hasn't let go.

The usual suspects are Skype, Zoom, Discord, OBS, or even a browser tab using WebRTC. I've also seen Windows Camera app linger in the background after you thought you closed it. The fix is quick:

1. Press Ctrl+Shift+Esc to open Task Manager.
2. Look under the Processes tab for anything using your camera — apps like Camera.exe, SkypeApp.exe, Zoom.exe, or obs64.exe.
3. Right-click each and select End task.

If you can't spot the culprit, switch to the Details tab, look for CameraFrameServer.exe or WindowsCamera.exe, and kill them both. Then try your app again. Nine times out of ten, that's it.

One edge case: some modern webcams have built-in privacy shutters. If the shutter is closed, Windows might report the device as busy. Open the shutter physically, then retry.

Cause #2: The camera driver didn't release the stream

The reason step 1 doesn't always work is that some drivers (especially cheap USB cameras or capture cards) don't properly signal the release to Windows when an app crashes. The device appears free in Task Manager, but the driver still thinks there's a stream active.

Here's the real fix:

• Unplug the USB camera or capture device. Wait 10 seconds. Plug it back in.
• If it's a built-in laptop camera, open Device Manager (devmgmt.msc). Expand Cameras or Imaging devices. Right-click your camera and select Disable device. Wait 5 seconds, then Enable device.

This forces the driver to reinitialize and clear that stuck stream state. I've had to do this with Elgato Cam Link and Logitech C920 on Windows 10 and 11 after OBS crashed mid-stream.

Cause #3: Privacy settings blocking the device

Less common, but I've seen it. Windows 10 and 11 have per-app camera permissions. If an app was denied permission previously, or if you changed privacy settings while the device was active, Windows can sometimes lock the stream with this error.

Check it:

1. Go to Settings > Privacy & security > Camera.
2. Make sure Camera access is On.
3. Scroll down and ensure your specific app (e.g., OBS, Zoom, Discord) has permission toggled On.

If everything looks fine, toggle Camera access off, wait 5 seconds, then back on. That resets the device state.

This bug is rarer on Windows 11 23H2+, but I still see it on older 22H2 builds. If you're there, consider updating Windows.

Quick-reference summary

If none of that works, reboot the machine. It's boring but effective — it clears all driver locks. I've never seen this error survive a full restart.