Quick Fix (30 seconds) — Close Everything Using Your Mic
I know this error is infuriating. You’re in the middle of a call or recording, and suddenly nothing works. The error 0XC00D1B61 (NS_E_AUDIODEVICE_BUSY) means another program has grabbed your microphone and won’t let go. Windows only lets one app use a capture device in exclusive mode at a time.
- Close every app that might be using your mic. That means Skype, Discord, Zoom, Teams, OBS, Audacity, web browsers with open tabs that requested mic access—everything.
- Open Task Manager (Ctrl+Shift+Esc). Look for any lingering processes in the Processes tab that show a microphone icon next to them. End those tasks.
- Try your recording or call again.
If that works, you’re done. The culprit was a background process that didn’t release the device. But if it doesn’t, read on—this is just the first step.
Moderate Fix (5 minutes) — Disable Exclusive Mode
This tripped me up the first time too. Exclusive mode lets apps take full control of your audio device. That’s great for low-latency recording, but it causes this exact error when two apps fight for the mic. Disabling it prevents the lock.
- Right-click the speaker icon in your system tray (bottom-right of the screen) and select Sounds.
- Go to the Recording tab. Find your active microphone (the one with a green checkmark), right-click it, and choose Properties.
- Switch to the Advanced tab.
- Uncheck both boxes under Exclusive Mode: Allow applications to take exclusive control of this device and Give exclusive mode applications priority.
- Click Apply then OK.
- Reboot your system—yes, even if you think you don’t need to. This clears any cached locks.
This fix works for 80% of the cases I’ve seen, especially on Windows 10 and 11. I’ve watched it save a live streamer’s setup in under a minute.
Advanced Fix (15+ minutes) — Identify and Kill the Blocking Process
If disabling exclusive mode doesn’t help, something is stubbornly holding onto your mic. Let’s find it with the Windows Audio troubleshooting tool or a command-line trick.
Step 1: Use the built-in troubleshooter
- Go to Settings > System > Troubleshoot > Other troubleshooters (Windows 11) or Additional troubleshooters (Windows 10).
- Run Recording Audio troubleshooter. It’ll scan for issues and might tell you which app is locking the device.
Step 2: Kill the audio device driver stack from Command Prompt
This is a nuclear option—skip it unless you’re comfortable with command line. It forces the audio driver to release everything.
net stop audiosrvThen restart the service:
net start audiosrvThis might cause a temporary pop from your speakers. If the error returns immediately, run this to see which processes are holding handles:
handle64 -a -p audiodg.exeYou’ll need the Sysinternals Handle tool for that. The output will show you process IDs (PIDs). Note the PID of any suspicious process (like a browser helper or a recording app). Then use Task Manager to end that process by PID.
Step 3: Update or reinstall audio drivers
Outdated drivers can cause this error to keep coming back. Go to Device Manager (Win+X > Device Manager), expand Audio inputs and outputs, right-click your microphone, choose Update driver > Search automatically for drivers. If that finds nothing, go to your motherboard or laptop manufacturer’s website and download the latest audio driver manually.
If all else fails, a clean driver reinstall can help. Uninstall the device in Device Manager, check Delete the driver software for this device, reboot, and let Windows reinstall it fresh.
One more thing: I’ve seen this error pop up when a web browser tab keeps the mic open after you close it. Chrome and Edge both do this. Check the browser’s site permissions and revoke microphone access for any site you’re not actively using.
That’s the full battle plan. Skip what doesn’t apply, stop when your mic works again. And if you’re still stuck, drop a comment with your specific setup—microphone model, Windows version, and what you were doing when the error hit. I read every one.