You updated your graphics driver, your motherboard’s chipset drivers, or maybe Windows Update pushed an audio driver overnight, and now your USB headset is completely silent. The headset shows up in Windows, sometimes it even appears as the default device, but no matter what you play—YouTube, Spotify, a game—you get nothing. In some cases the device shows a red X in Sound settings, or it appears and disappears in Device Manager every few seconds. Other times you get sound fine until you launch a specific app, or the microphone works but the headphones don’t.
The good news: this is almost never a dead headset. When sound vanishes immediately after a driver change, the cause is nearly always software—a driver conflict, a default device switch, an audio service that failed to restart, or an enhancement feature that doesn’t get along with the new driver. Work through the fixes below in order, because the first three solve the majority of cases in under five minutes. Only escalate to driver rollbacks and registry cleanup if the quick fixes don’t pan out.
Likely Causes
| Cause | How to confirm | Fix difficulty |
|---|---|---|
| Wrong default playback device after driver update | Right-click the speaker icon in the taskbar, choose Sound settings, and check whether your headset is listed under Output as the selected device | Easy |
| Windows Audio services stopped or stuck after the update | Press Win+R, type services.msc, and check whether Windows Audio and Windows Audio Endpoint Builder show “Running” | Easy |
| New driver disabled or conflicts with audio enhancements | Sound settings, select the headset, Device properties, and toggle Audio enhancements off to test | Easy |
| Corrupted or incompatible driver version | Device Manager shows a yellow warning triangle on the headset, or the Device Status box reports “This device cannot start (Code 10)” | Moderate |
| Communications activity setting muting or ducking audio | Sound Control Panel, Communications tab—if “Reduce the volume by 80%” or “Mute all other sounds” is selected, calls or apps can trigger it | Easy |
| Stale USB power management or a lingering old driver instance | Device Manager, View menu, Show hidden devices—old grayed-out audio entries from the previous driver remain listed | Moderate |
Fix 1: Set the Headset as the Default Output Device
What causes it
When a new driver installs, Windows sometimes registers the headset as a “new” audio endpoint and forgets the old default. Sound then routes to a device that no longer exists, such as a disconnected monitor or the motherboard’s Realtek jack, and the headset receives nothing.
How to check
Right-click the speaker icon on the taskbar and select Sound settings. Under Output, see which device is currently selected. Then open the full list: Settings, System, Sound, and click “All sound devices” to confirm the headset actually appears there.
What to do
Go to Settings, System, Sound. Under Output, click your USB headset from the “Choose where to play sound” dropdown. Then open the legacy panel for good measure: press Win+R, type mmsys.cpl, press Enter, right-click the headset under Playback, and choose “Set as Default Device” and “Set as Default Communication Device.” Click Apply, then play any audio while the dialog is open—a green level meter should bounce next to the headset when sound flows.
How to undo it
Repeat the same steps and select your original preferred output device. This change is fully reversible with no side effects.
Fix 2: Restart the Windows Audio Services
What causes it
Driver updates require the audio stack to reload. If the Windows Audio service or its endpoint builder hangs mid-restart, the driver loads but nothing sends audio to it. This is common after a driver installs while the PC was under load.
How to check
Press Win+R, type services.msc, and press Enter. Scroll to Windows Audio and Windows Audio Endpoint Builder. If either shows a Status of blank (stopped) or “Stopping” that never finishes, this is your problem.
What to do
In services.msc, right-click Windows Audio Endpoint Builder and choose Restart. Windows will prompt to also restart dependent services—click Yes. Then right-click Windows Audio and choose Restart. Set both Startup type entries to Automatic. If a restart is refused, reboot the PC, which forces a clean reload of both services plus the driver.
How to undo it
No undo needed—restarting services is safe. If you changed a Startup type by mistake, set it back to Automatic, which is the Windows default for both.
Fix 3: Disable Audio Enhancements
What causes it
Enhancement pipelines—bass boost, virtual surround, loudness equalization—are processed by the audio driver itself. A freshly installed driver version may have broken compatibility with the enhancement module, and when Windows tries to apply it, the entire audio stream fails silently.
How to check
If sound worked before the update and died the moment it finished, enhancements are a prime suspect. You can also test quickly: play audio, then toggle the enhancement off mid-playback and listen.
What to do
Open Settings, System, Sound, click your headset under Output, then Device properties. Turn off the “Audio enhancements” toggle. For a deeper pass, press Win+R, type mmsys.cpl, double-click the headset, go to the Advanced tab, and untick “Enable audio enhancements.” Also check for vendor-specific processing apps—software like SteelSeries GG, Logitech G Hub, or Corsair iCUE often installs its own spatial or EQ layer; open the app and disable any spatial audio or surround processing, then retest.
How to undo it
Return to the same toggles and switch enhancements back on. If a specific enhancement turns out to be the culprit, leave it off but re-enable the rest individually to isolate it.
Fix 4: Check the Communications Muting Setting
What causes it
Windows can automatically duck or mute all audio when it detects “communications activity” such as a call. After a driver update, the detection logic can misfire and mute everything permanently, especially if an app holds the microphone open in the background.
How to check
Press Win+R, type mmsys.cpl, and open the Communications tab. If “Reduce the volume by 80%” or “Mute all other sounds” is selected, Windows is allowed to silence your playback automatically.
What to do
In the Communications tab, select “Do nothing” and click Apply. Then check running apps: Discord, Teams, Zoom, and browser tabs with active calls can each hold the mic. Close them one at a time while playing audio to identify the trigger.
How to undo it
Return to the same tab and pick your previous preference. “Do nothing” is a safe permanent choice for most gamers.
Fix 5: Roll Back or Reinstall the Driver
What causes it
The new driver version itself may be buggy or incompatible with your headset’s USB audio controller. This happens with both Windows-supplied generic USB Audio drivers and vendor drivers pushed through updater software.
How to check
Open Device Manager (right-click Start, choose Device Manager), expand Sound, video and game controllers, and find your headset. Right-click it, choose Properties, and read the Device Status box. A Code 10, Code 28, or Code 45 error confirms a driver problem. Check the Driver tab for the driver date—compare it to the day your sound stopped.
What to do
If the Driver tab shows a “Roll Back Driver” button that isn’t grayed out, click it, choose a reason, and let Windows restore the previous version, then reboot. If rollback is unavailable, right-click the headset in Device Manager and choose Uninstall device, tick “Attempt to remove the driver for this device” if offered, then unplug the headset, reboot, and plug it back in so Windows reinstalls a clean copy. If your headset brand offers a driver package on its support page, install that instead of relying on the generic driver.
How to undo it
Reinstall any driver version you removed via the vendor’s installer or Windows Update (Settings, Windows Update, Check for updates, then View optional updates, Driver updates). Nothing here is permanent.
Fix 6: Disable USB Selective Suspend and Power Management
What causes it
USB power-saving features can cut power to the headset port after the driver reinitializes, and a poorly written driver sometimes fails to wake the device, leaving it silent even though it enumerates fine.
How to check
If the headset’s LED goes dark after a period of idle time and never comes back, or unplugging and replugging restores sound temporarily, power management is interfering.
What to do
Open Control Panel, Power Options, click “Change plan settings” on your active plan, then “Change advanced power settings.” Expand USB settings, then USB selective suspend setting, and set it to Disabled for both On battery and Plugged in. Click Apply. Then open Device Manager, expand Universal Serial Bus controllers, and for each “USB Root Hub” and “Generic USB Hub,” open Properties, go to the Power Management tab, and untick “Allow the computer to turn off this device to save power.”
How to undo it
Repeat the same steps and re-enable selective suspend and the power-management checkboxes. Expect slightly higher idle power draw—irrelevant on a desktop.
Fix 7: Remove Stale Hidden Audio Devices
What causes it
Old driver instances from before the update can linger as hidden “ghost” devices. Windows occasionally routes audio to a ghost endpoint instead of the live one, producing total silence or random dropouts.
How to check
Open Device Manager, click View, then Show hidden devices. Expand Sound, video and game controllers and “Universal Serial Bus controllers.” Grayed-out, translucent icons of previous headset entries indicate leftovers.
What to do
With Show hidden devices enabled, right-click each grayed-out audio device that matches your headset model or old driver entries and choose Uninstall device. Leave the currently active (non-grayed) headset alone. Reboot afterward so Windows rebuilds the endpoint list cleanly.
How to undo it
Ghost devices rebuild automatically when the hardware reconnects, so no undo is needed. If you removed the live device by mistake, unplug and replug the headset.
Fix 8: Reset the Audio Stack via a Clean Boot and System Restore
What causes it
Third-party software—RGB suites, virtual audio cables, Voicemod-style voice changers, older audio APOs—can hook into the audio stack and clash with a new driver. If everything above failed, a background filter is likely corrupting audio processing.
How to check
If your installed list includes virtual audio drivers (Voicemod, VB-Audio Cable, Nahimic, Sonic Studio), suspicion is high. Confirm by testing in a clean boot.
What to do
Press Win+R, type msconfig, open the Services tab, tick “Hide all Microsoft services,” then click Disable all and reboot. Test the headset. If sound returns, re-enable services in halves until you find the offender, then update or uninstall that app. If clean boot doesn’t help, use System Restore: press Win+R, type rstrui, pick a restore point dated before the driver update, and let Windows revert. Your files stay intact; only drivers, apps, and settings roll back.
How to undo it
In msconfig, re-enable the services you disabled (or run a Normal startup on the General tab). A System Restore can be reversed by reopening rstrui and choosing “Undo System Restore.”
If Nothing Works
Test the headset on another computer or a game console. If it’s silent there too, the headset’s USB DAC or cable has likely failed coincidentally, and warranty replacement is the right move—check the manufacturer’s support page for the RMA process. If it works elsewhere, stay on the software track: uninstall the vendor’s audio software suite entirely (Settings, Apps, Installed apps), reboot, and reinstall the latest version fresh. As a last resort, run an in-place repair install of Windows via Settings, System, Recovery, “Fix problems using Windows Update,” which reinstalls Windows while keeping your files and apps. Before any of that, plug the headset into a different USB port—preferably a rear motherboard port on a desktop—and confirm the issue isn’t a single failing port, since ports and hubs fail more often than people expect heading into 2026’s USB4-heavy hardware mix.
FAQ
Why did my USB headset stop working right after a driver update?
Driver updates re-register audio endpoints and restart the audio services. If the endpoint list rebuilds incorrectly, services hang, or the new driver conflicts with audio enhancements or third-party audio apps, the headset can enumerate but receive no audio stream.
Should I use the generic Windows USB audio driver or the manufacturer’s driver?
Start with the generic driver Microsoft supplies through Windows Update—it’s the most stable baseline. If your headset has feature software (surround sound, EQ, sidetone) that only works with the vendor driver, install the vendor package after confirming basic sound works with the generic one.
Can a Windows Update break USB headset audio even if it isn’t a driver update?
Yes. Cumulative Windows updates modify the audio stack itself, and a post-update service failure can mute devices even when drivers are unchanged. Restarting the Windows Audio services (Fix 2) resolves this in most cases.
My microphone works but there’s no sound—does that change the diagnosis?
No, and it’s actually a useful clue. If the mic works, the USB connection and driver are loading correctly, which points strongly to a playback default, enhancement conflict, or communications-muting issue rather than a hardware fault. Start with Fixes 1 through 4.
