When you see this error
You're in the middle of editing a podcast in Audacity, or maybe you fired up an old VoIP app, and bam — 'NS_E_WAVE_OPEN (0XC00D006D) — Error opening wave device, the device might be in use.' The app just sits there, no sound, no progress. Had a client last month whose entire Skype for Business setup died with this after a Teams update. The trigger is almost always one app holding a lock on the audio hardware, or a corrupted audio driver that won't release the device.
Root cause in plain English
Windows audio devices don't like sharing. When one app opens a wave device (like your mic or speakers), it can lock it exclusively. The next app that tries to open it gets this error. It's not a hardware issue — the device is fine. It's a software handshake problem. Common culprits: DAWs, video conferencing tools, or old games that don't properly close the device when done.
Fix it in 4 steps
Step 1: Kill the app that's holding the lock
Press Ctrl+Shift+Esc to open Task Manager. Look under the Processes tab for any audio-hungry programs: your DAW, Zoom, Teams, Discord, or even a browser tab playing media. Right-click and End task. Then try your app again. This fixes it about 70% of the time. If you don't see obvious offenders, check under 'Background processes' — sometimes a lingering process from an app you closed an hour ago is still squatting on the device.
Step 2: Restart the Windows Audio service
If killing apps didn't work, the audio service itself might be stuck. Hit Windows+R, type services.msc, and press Enter. Find 'Windows Audio' in the list. Right-click it and select Restart. Do the same for 'Windows Audio Endpoint Builder'. This flushes all audio device handles. I've seen this clear the error after a driver update left the service in a weird state.
Step 3: Check for exclusive mode conflicts
Some apps grab the device in exclusive mode and don't let go. Right-click the speaker icon in the system tray, select 'Sounds', go to the Playback tab, double-click your default device, and switch to the Advanced tab. Under 'Exclusive Mode', uncheck both 'Allow applications to take exclusive control of this device' and 'Give exclusive mode applications priority'. Hit Apply. Repeat this for the Recording tab if the error involves a mic. This prevents any one app from hogging the hardware.
Step 4: Reset the audio device driver
If steps 1-3 fail, the driver might need a kick. Open Device Manager (right-click Start > Device Manager). Expand 'Sound, video and game controllers'. Right-click your audio device (usually Realtek or High Definition Audio) and select 'Disable device'. Wait 10 seconds, then right-click and 'Enable device'. This reloads the driver without a reboot. For stubborn cases, uninstall the driver completely, then restart Windows — it'll reinstall the default driver automatically.
What to check if it still fails
If you're still seeing 0XC00D006D, you're dealing with something deeper. First, check if you have any third-party audio management software (like Dolby Atmos, Nahimic, or Realtek Audio Console) that might be locking the device. Uninstall them temporarily. Second, run the Windows Audio troubleshooter: Settings > System > Troubleshoot > Other troubleshooters > Audio. Third, if you're on a laptop, check if the built-in mic or speakers are physically disabled by a function key — some Lenovo and Dell models have a hardware mute that throws this error. Last resort: a clean boot. Run msconfig, select 'Selective startup' and uncheck 'Load startup items', reboot, and test. If it works, enable startups one by one to find the conflict.
I had a case last week where a Logitech webcam driver was fighting with the onboard audio for the wave device. Uninstalling the webcam's audio component fixed it. Look for anything that adds a virtual audio device — those are usually the troublemakers.