NS_E_TOO_MANY_DEVICECONTROL (0XC00D1B96) – Only One Plug-In Controls This Device
You see this when two apps try to grab control of the same device. Usually a webcam or mic being hogged by a second app.
When This Error Shows Up
You're trying to use your webcam for a Zoom call, or your mic for a Discord chat, and instead of video you get a pop-up saying NS_E_TOO_MANY_DEVICECONTROL with the code 0XC00D1B96. The exact message reads: "Only one device control plug-in can control a device." I've seen this most often with Logitech C920 webcams and Blue Yeti mics on Windows 10 and 11. The trigger is almost always the same: you had one app using the device, then opened a second app that also tried to grab exclusive control.
What's Actually Happening
Windows Media Foundation only allows one app to take exclusive control of a device at a time. Think of it like a single lock on a door — only one key fits at a time. If App A has the lock (say, OBS Studio in preview mode), and App B tries to get it (maybe your webcam software), Media Foundation throws this error instead of just sharing the device. Some apps are polite and request shared mode, but others demand exclusive access. That's when you get the plug-in conflict.
How to Fix It
Step 1: Kill the App Hogging the Device
Open Task Manager (Ctrl+Shift+Esc). Look under the Apps section or Background processes for anything that might be using your camera or mic. Common culprits: OBS, Zoom, Microsoft Teams, Discord, Skype, your webcam's own software (Logitech Capture, Camera Settings), or any video conferencing tool you forgot to close. End each task you suspect. Then try your app again.
Step 2: Check Background Camera Access
On Windows 10 and 11, apps can run in the background and still hold the device. Hit Start and type "Camera privacy settings." Click it. Under "Let apps access your camera," make sure it's on, but also scroll down and turn off camera access for any app you don't need. Then restart your PC. Had a client last month whose print queue died because of this — actually, it was a Teams leftover process that kept his webcam locked.
Step 3: Restart the Windows Camera Frame Server
If killing apps doesn't free it, the service itself might be stuck. Open Command Prompt as admin (right-click Start, select Terminal Admin). Run:
net stop WpnService
net start WpnServiceOr just restart the Windows Camera Frame Server service in services.msc. That often flushes a stuck exclusive lock.
Step 4: Disable Exclusive Mode in Device Properties
Right-click the speaker icon in the taskbar, select Sounds. Go to the Recording tab. Right-click your mic (or camera in Device Manager for webcams) and choose Properties. Click the Advanced tab. Uncheck "Allow applications to take exclusive control of this device." Click Apply. This forces apps to share instead of fighting for exclusive access. Works best for microphones. For webcams, you might not see that option — skip to the next step.
Step 5: Update or Roll Back the Driver
Open Device Manager. Find your camera or mic under Cameras or Sound, video and game controllers. Right-click it, choose Properties, Driver tab. Try "Update driver" first. If it's already up to date or the error persists, click "Roll Back Driver" if available. I've seen a bad driver update on a Logitech Brio break device control — rolling back to the manufacturer's original driver fixed it instantly.
Still Getting the Error?
If none of that works, the app you're using might be buggy. Try a different app to see if the error repeats. If it doesn't, uninstall and reinstall the problematic app. Also check for third-party antivirus that blocks camera access — Bitdefender and Norton have caused this before. Disable any camera/mic blocker in your security software temporarily to test. Last resort: system restore to a point before the error started.
Was this solution helpful?