ShadowPlay silent after a headset swap: the audio device it latched onto
By Daniel Brooks Published 11 min read
On this page (9 sections)
- The short version
- ShadowPlay records the output device it picked at startup, not the one playing now
- How to confirm which output device ShadowPlay is currently bound to
- Why the old headset stays selected even after Windows default changes
- The order that works: default device, then restart capture, then test
- Desktop capture versus game capture changes which audio gets recorded
- Test in one short clip before recording anything long
- What to reset if the new headset still does not appear in the list
- Questions people still ask
In short: The fix depends on which output device ShadowPlay captured at startup. It latched onto your old headset while that headset was the Windows default, so it keeps recording a device that no longer plays game audio. Set the new headset as default, then re-select it in ShadowPlay's audio settings, restart the capture, and test with a short clip.
Part of our guide on checking drivers for lag
The recorder picked your old headset the moment capture started, and it never checks again.
| Fix time | about 2 minutes |
|---|---|
| First step | set new headset as Windows default |
| Second step | restart ShadowPlay capture |
| Test clip length | 10 seconds |
| Settings location | GeForce Experience, Recording tab |
| Device check | old headset still listed is the symptom |
The short version
- ShadowPlay binds its recording output when it starts, so a device swap mid-session goes unnoticed
- Set the new headset as the Windows default first, then restart the capture, not the other way round
- Open the ShadowPlay audio settings and confirm the output shows your new headset by name, not the old one
- Test with a 10-second instant replay clip before recording anything long
- If the new headset never appears in the list, re-pair or re-plug it, then restart GeForce Experience
ShadowPlay records the output device it picked at startup, not the one playing now
Say you finish a late session on your wired headset, unplug it, and next evening you sit down with a new Bluetooth set. Windows switches over fine, game audio plays through the new cans, you hit record, and the clip comes back with gameplay footage but no sound. Nothing feels broken because nothing sounds broken.
That's the stale latch. When ShadowPlay started its capture, it sampled the audio output that was default at that moment and bound its recorder to it. The recorder does not follow the Windows default around. It keeps pointing at whatever device it caught, even after that device stops playing anything.
This matters because it reframes the problem. Your audio stack is almost certainly fine, since you can hear the game. What's wrong is a single selection: the recorder is aimed at a device that no longer carries game audio. Fixing it is a matter of re-aiming, not repairing.
| Symptom | What it points to | Fix direction |
|---|---|---|
| Clip has game footage, no game audio | Recorder latched to old or silent device | Re-select output in ShadowPlay settings |
| Mic recorded but game audio missing | Mic input fine, output latch stale | Re-select recording output only |
| No devices listed at all | Capture service or driver issue | Restart GeForce Experience, check drivers |
| Audio in file but very quiet | Wrong device or volume mix issue | Check device volume and app mixer |
How to confirm which output device ShadowPlay is currently bound to
Picture checking the list and seeing your old headset's name still sitting in the recording output field. That one glance ends the mystery, so do it before touching anything else. Guessing leads to changing three things at once and not knowing which one worked. If that sounds like your situation, read up on xbox controller troubleshooting next.
Open GeForce Experience and click the gear icon, then look under the recording or capture settings. ShadowPlay exposes the audio devices it records separately from what Windows plays. The field will name a specific device, and that name is the truth of what's in your clips.
Cross-check it against Windows. Right-click the speaker icon in the taskbar, open sound settings, and look at both the output list and the default device. If ShadowPlay's field names a headset that isn't the default, or one you've unplugged entirely, you've found the cause.
One trap worth knowing: a Bluetooth headset you switched off still shows in Windows' list for a while, greyed out. A greyed or disconnected device can look like a valid selection. Treat any name that isn't the device currently playing sound as the wrong pick. The other half of this decision is android built-in screen recording.
- GeForce Experience: gear icon, then recording or capture settings, then audio output field
- Windows sound settings: right-click the speaker icon, compare the default device to the name ShadowPlay shows
- Device Manager: confirm the new headset appears without warning icons before blaming ShadowPlay
Why the old headset stays selected even after Windows default changes
The instinct is that changing the Windows default should fix everything downstream. It doesn't, and the reason is simple. ShadowPlay made its choice at the moment capture started, when your old headset was still the default. Nothing tells it that the default later moved.
Most capture tools behave this way, and it's partly deliberate. Binding to a specific device means a mid-game default change doesn't drop the recording or grab the wrong stream. The trade-off is that the recorder trusts the selection it made, and only you can update it.
There's a second layer with Bluetooth headsets. Windows treats a Bluetooth device that disconnects as removed and falls back to speakers, but ShadowPlay's stored selection can still reference the disconnected entry. When you reconnect, the name matches the stale selection, so nothing prompts you to look twice. That's why the bug feels random when it's actually consistent. If that sounds like your situation, read up on cloud gaming lag causes next.
The practical takeaway: never assume the recorder followed the switch. Default change plus capture restart plus re-selection is the complete move, and skipping the re-selection is what leaves clips silent.
The order that works: default device, then restart capture, then test
Order matters more than any individual step, because a capture restart samples whatever is default at that moment. Do it before fixing the default and you've just re-latched the problem. Here's the sequence that avoids that.
Work through it in this exact order: For the detail, see our notes on v-sync on but still tearing at 144hz.
- Set your new headset as the Windows default output: right-click the speaker icon, open sound settings, and pick the headset under output.
- If ShadowPlay is mid-capture, stop it completely. Turning the overlay off and on, or toggling the instant replay function, forces a fresh start.
- Open the ShadowPlay recording settings and select your new headset by name in the audio output field. Don't leave it on any previous custom pick.
- Restart the game, or at minimum restart the capture, so the recorder samples the corrected setup.
- Record or save a short instant replay clip and play it back before any long session.
Desktop capture versus game capture changes which audio gets recorded
If your clips are still silent after the re-selection, look at what mode you're capturing in. Game capture records the application's audio stream, while desktop capture records everything Windows is playing. The same stale-device logic applies to each, but the failure looks different.
In game capture mode, ShadowPlay hooks the game itself, so the audio it records follows the game's output device, not a manual pick. If the game is still sending audio to the old headset, you'll hear nothing in the clip even though your re-selection was correct. Check the game's own audio output in Windows' per-app sound settings, found under advanced sound options.
Desktop capture mode is more forgiving and also more dangerous. It records system-wide audio, so any device playing sound lands in the file, including music and notifications. If you switched to desktop capture as a workaround and now hear background noise, that's why. If that sounds like your situation, read up on how to block inappropriate games on kids pc next.
A rule of thumb worth keeping: if the game plays it and you can hear it, game capture should record it. When it doesn't, the mismatch is between the game's output device and your ears, not between ShadowPlay and the world.
| Capture mode | What audio it records | When it fails |
|---|---|---|
| Game capture | The game's own audio stream | Game outputs to a device your ears don't use |
| Desktop capture | Everything Windows plays | Background apps and notifications leak in |
| Separate mic track | Your microphone only | Game audio missing if output latch is stale |
Voice chat and party audio in the same clip
Discord and similar apps pick their own output device independently of Windows. If your friends are audible to you but missing from clips, that app is likely still pointed at the old headset. Open the app's audio settings and set both input and output to the new headset. Then restart the app so its voice processing rebinds.
Test in one short clip before recording anything long
The cheapest insurance here is the instant replay function. Play the game for ten seconds, make a sound you can hear clearly, hit the replay hotkey, and play the saved clip back. That loop takes under a minute and tells you whether the latch is fixed. If that sounds like your situation, read up on steam remote play lag issues next.
Use a sound you can distinguish. A menu blip or a gunshot works; ambient wind doesn't, because a silent clip of wind looks identical to a muted one. Watch for both halves: game audio present, and your mic present if you use one. Instant replay saves to your temporary cache, so a bad test costs you no disk space worth caring about.
If the replay clip has audio, record a two-minute manual clip as a second check, because instant replay and manual recording occasionally behave differently with device switching. Once both pass, you're safe to record a session. Skip this step and the price is a whole evening of silent footage, which no one can recover.
What to reset if the new headset still does not appear in the list
Sometimes the new headset never shows up as an option at all, and then no amount of re-selection helps. Start at the physical layer. Unplug and re-plug a wired headset, or power the Bluetooth set off and on and re-pair it, and watch Windows' output list while you do. If the device appears and disappears, the connection is the problem.
Next, restart the software layer. Quit GeForce Experience entirely from the system tray and relaunch it, so its capture service rebuilds its device list. If it still shows nothing, a full reboot clears driver-level device handles that no app can release on its own. In stubborn cases, uninstalling the headset in Device Manager and letting Windows rediscover it resets the driver's association.
Bluetooth adds one more wrinkle: Windows sometimes leaves a disconnected headset registered under the same name twice, once stale and once live. If you see duplicate names, pick the entry that shows as connected and has a volume slider that responds. A stale duplicate is exactly the kind of entry a stale latch grabs.
If none of that works and every other app hears audio fine, check that your graphics driver and GeForce Experience are current, because the capture layer depends on both. I'd stop short of reinstalling audio drivers first; the vast majority of these cases end at the re-pair or reboot stage.
Treat a silent ShadowPlay clip after a headset swap as a stale device selection, not broken audio, and the fix takes about two minutes.
Questions people still ask
Does unplugging my headset while recording break the clip?
The video usually survives, but the audio can drop or go silent for the rest of the clip because the recorded device vanished mid-capture. If you must swap mid-session, stop the recording first, redo the default-plus-restart sequence, then record again.
Why does ShadowPlay record my mic fine but not the game?
The microphone and game audio are captured as separate streams with separate device selections. Your mic input was re-detected correctly, but the recording output is still latched to the old headset. Re-selecting the audio output field fixes exactly this split.
Should I set the headset as default or pick it manually in ShadowPlay?
Do both, in that order. Set it as the Windows default first so game audio actually plays through it, then select it in ShadowPlay's recording settings. Picking it manually without fixing the default records a device nobody is playing through.
Does this happen with Discord or Spotify too?
Any app that lets you choose an audio device can hold a stale selection, including Discord, Spotify and OBS. Discord is the usual offender for voice chat, so if friends are audible to you but missing from clips, check Discord's output device first.
Can I stop this from happening every time I swap headsets?
Not completely, because the capture binds at startup by design. The habit that works is a ten-second instant replay test after any device change. If the replay clip has sound, your session is safe to record.
Is there a way to record both speakers and headset audio at once?
Desktop capture mode records whatever Windows plays system-wide, so it can catch multiple outputs, but it also catches notifications and background apps. If you need clean game audio plus mic, game capture with a separate mic track is the better setup.