Why Is Only My Game Audio Coming Out of My Monitor? (And How to Fix It)
You're mid-session, everything sounds fine through your monitor speakers — then you realize your game audio is routing there instead of your headset or external speakers. The rest of your system audio works fine. Just the game is misbehaving. Here's why that happens and what's actually going on under the hood.
How Windows Routes Audio (The Short Version)
Windows manages audio through a system of output devices — each one assigned a role. There are two key defaults:
- Default Device — used by most apps, system sounds, browsers, music players
- Default Communications Device — used specifically for voice calls and communication apps
Most games, however, don't follow either of these automatically. Many games and game engines let you — or silently force you — to pick an audio output independently. That's where things come apart.
Why Games Behave Differently Than Other Apps
Games are built on audio engines (like FMOD, Wwise, or DirectSound) that often enumerate all available audio devices at launch and lock to whichever one was active at that moment — or whichever one is listed first in the system.
If your monitor is connected via HDMI or DisplayPort, it registers as a separate audio output device in Windows. Even if you never intended to use it for sound, Windows sees it as a valid option. If a game initializes before your headset is recognized, or if the monitor happens to be listed higher in the device priority, the game grabs it.
Other apps — your browser, Spotify, Discord — typically respect the Default Device setting more reliably. Games often don't.
Common Causes at a Glance 🎮
| Cause | Why It Happens |
|---|---|
| HDMI/DisplayPort monitor registered as audio device | These connections carry audio signals by default |
| Game set to a specific output at install time | In-game audio settings locked to monitor on first launch |
| Windows Default Device changed after game was configured | Game doesn't dynamically follow system defaults |
| Multiple audio devices with conflicting priority | Windows audio stack picks unexpectedly on launch |
| Outdated or mismatched audio drivers | Driver conflicts cause incorrect device routing |
Where to Actually Check and Fix This
1. Inside the Game's Audio Settings
This is the first place to look. Many modern games — especially PC-native titles — have an audio output selector buried in Settings > Audio or Settings > Sound. It may be labeled "Output Device," "Audio Device," or "Speaker Configuration."
If it's set to your monitor's HDMI output, switch it to your headset or speakers. This is the cleanest fix because it's game-specific and doesn't affect anything else.
2. Windows Sound Settings
If the game doesn't have its own selector, go to Windows Sound Settings (right-click the speaker icon in the taskbar > Sound settings). Under Output, make sure your preferred device is set as default.
For more control, open the Volume Mixer (available in Windows 11 via Advanced sound options, or as a classic mixer in Windows 10). Here you can see per-app volume levels — and in Windows 11, you can assign specific output devices per application, which is exactly what you need when a game is routing differently than everything else.
3. Disable the Monitor as an Audio Device
If you never want sound coming from your monitor, you can disable it entirely:
- Go to Control Panel > Sound
- Click the Playback tab
- Right-click your monitor's audio output (usually listed as the display name or "HDMI Output")
- Select Disable
This removes it from the pool of devices Windows and games can route to. 🔇
4. Check Driver State
A mismatch between your GPU drivers (which handle HDMI/DP audio) and your motherboard or USB audio drivers can cause unexpected routing behavior. If audio started misbehaving after a driver update, rolling back or reinstalling the relevant audio drivers through Device Manager is worth trying.
5. The "Set as Default" Priority Order
Windows uses device priority when no app specifies an output. If your headset isn't set as the default — or if it was plugged in after the game launched — the game may have already locked to the monitor. Restarting the game after confirming your default device often resolves this.
Why This Varies Between Setups
The same root cause plays out differently depending on:
- How your monitor is connected — HDMI and DisplayPort always register audio capability; VGA and older DVI connections don't
- Whether you use a USB headset, analog headset, or external DAC — USB and Bluetooth audio devices register differently in the Windows audio stack than 3.5mm connections
- Your version of Windows — Windows 11 introduced per-app audio device assignment natively; Windows 10 users need third-party tools like EarTrumpet for the same functionality
- The game engine involved — some engines are better behaved than others about following system defaults dynamically
- Whether you use software like Voicemeeter or virtual audio cables — these add routing layers that can interact unpredictably with games
A setup with a single USB headset and no HDMI monitor audio will almost never hit this problem. A setup with a gaming headset, HDMI monitor, and a USB DAC running on Windows 10 is practically designed to encounter it.
The Variable That Matters Most
The fix that works depends entirely on whether your game exposes its own audio output selector, which version of Windows you're on, how your devices are connected, and whether the issue is persistent or only happens at launch. Each of those factors changes which lever actually solves it — and some combinations require more than one adjustment to stick.