Unfortunately, WoW doesn’t dynamically detect or switch to a new default audio device mid-session, even when toggling it in Windows.
WoW stubbornly clings to the output device it started with, even if you’ve told it to use “System Default.” The fact that /run Sound_GameSystem_RestartSoundSystem() works, shows they already have the functionality—they’re just not calling it automatically when the system output changes.
In theory, it wouldn’t take much for Blizzard to implement something like:
if GetCVar(“Sound_OutputDriverIndex”) == -1 then
C_Timer.After(1, function()
Sound_GameSystem_RestartSoundSystem()
end)
end
That would allow users relying on system-default routing to change outputs dynamically. If a setting claims to follow the system’s default output, then it should follow it—even when it changes during runtime. That’s just standard behavior in modern software, especially games and apps with live audio switching. For a subscription-based MMO in 2025, this sort of functionality is expected, not a luxury.
It’s not like this is a niche scenario either—tons of players use USB headsets, docks, stream controllers, or devices like BEACN Mix, GoXLR, etc. And when a game refuses to update its audio routing unless it’s restarted (or a hidden macro is triggered), that’s a frustrating, unpolished experience.
If this was a free indie game from 2012? Maybe. But for a $15/month Blizzard product? Yeah—they should absolutely fix it.