Fix Discord Not Capturing Game Audio on Windows 11

You want to stream your latest indie build or a match of Counter-Strike 2 to your dev team in Discord, but your viewers are staring at smooth gameplay with total silence. Windows 11 handles audio routing differently than its predecessors, frequently failing to hook into exclusive-mode game audio when Discord runs with standard user privileges. By the end of this guide, you will reconfigure your Windows 11 audio architecture, register your game correctly within Discord's hooked process list, and stream with crisp stereo game audio.

Quick TL;DR Fix

If you are in a rush and need the stream working in the next sixty seconds, apply these three changes immediately:

1. Open Discord User Settings > Activity Settings > Registered Games and manually add your running game if it isn't listed.
2. Run Discord as Administrator by right-clicking the shortcut and selecting Run as administrator.
3. In Discord Voice & Video settings, scroll down to Audio Subsystem and switch it from Standard to Legacy (or vice versa).

If that quick combination didn't force the audio hook, the issue lies deeper in how Windows 11 isolates application audio endpoints and how Discord injects its capture DLLs. Let's fix it permanently.

The Core Culprit: Windows 11 Audio Architecture & Hooks

Windows 11 separates audio sessions by process, and newer title engines (like Unreal Engine 5 or custom DirectX 12 renderers) often use exclusive WASAPI (Windows Audio Session API) modes. When a game takes exclusive control of an audio endpoint, standard user-level applications like Discord cannot tap into that audio stream without explicit elevation or proper screen-capture hooks.

Furthermore, Discord relies on its GameActivity hook to recognize when a full-screen or borderless windowed application is active. If Windows 11 virtualization security or third-party overlays block this injection, video streams through fine, but the audio packet payload is dropped entirely.

Step 1: Elevate Discord Privileges

Discord cannot hook into elevated games (games running as Administrator) if Discord itself runs with standard user tokens.

1. Completely close Discord. Right-click the Discord tray icon in the bottom-right taskbar corner and select Quit Discord.
2. Locate your Discord shortcut (on your desktop or in the Start menu), right-click it, and select Properties.
3. Navigate to the Compatibility tab.
4. Check the box labeled Run this program as an administrator.
5. Click Apply, then OK.
6. Relaunch Discord. You may see a User Account Control (UAC) prompt; accept it.

Step 2: Configure Screen Share vs. Application Share

Windows 11 treats "Screens" and "Applications" differently when capturing audio. If you share your entire desktop screen, Discord captures the master output of your default playback device. If you share a specific application window, Discord attempts to capture only that application's specific audio stream via Windows loopback.

If you are using Application Share (sharing the game window directly):

1. Ensure your game is running in Borderles Windowed or Windowed mode. Exclusive Fullscreen mode occasionally breaks Windows 11 window-capture hooks.
2. In Discord, click the Share Your Screen button in your voice channel.
3. Switch from the Screens tab to the Applications tab.
4. Select your game explicitly. If the game window is minimized or hidden behind another window, Discord's hook may fail to initialize the audio stream. Keep the game window visible on your primary monitor while initiating the stream.

Step 3: Tweak Discord Audio Subsystems

Discord utilizes different capture backends depending on the selected subsystem. Windows 11 behaves best when Discord matches the system's default sample rates.

1. Open Discord User Settings (the gear icon near your username).
2. Scroll down to the App Settings section on the left sidebar and click Voice & Video.
3. Scroll down to the Audio Subsystem dropdown menu.
4. If it is set to Standard, change it to Experimental or Legacy.
   • Note: The Legacy subsystem bypasses several Windows 11 audio enhancements that frequently block loopback capture on Realtek and generic USB audio drivers.
5. Scroll down further to the Screen Share section and ensure Use our latest technology to capture your screen is toggled OFF. This forces Discord to use the stable, legacy capture pipeline which avoids black screens and missing audio bugs on Windows 11 build 22H2 and newer.

Verifying Windows 11 Sound Control Panel Settings

Sometimes the issue is not Discord, but Windows routing your game audio to a virtual cable or secondary output device that Discord isn't monitoring.

Check Default Communication and Playback Devices

1. Press Win + R to open the Run dialog.
2. Type mmsys.cpl and hit Enter to open the classic Sound Control Panel.
3. Under the Playback tab, verify that your primary headset or speakers are set as the Default Device and Default Communication Device.
4. Right-click your playback device, select Properties, and go to the Advanced tab.
5. Under Exclusive Mode, uncheck Allow applications to take exclusive control of this device. (Leaving this checked causes games running in exclusive mode to lock out Discord's loopback capture).
6. Click Apply and OK.

Verify Volume Mixer Routing for Discord and the Game

Windows 11 features a granular per-app volume mixer that resets or misroutes sessions after major OS updates.

1. Press Win + I to open Settings.
2. Go to System > Sound > Volume mixer.
3. Scroll down and ensure Discord is not muted and its output device points to your default physical speakers/headphones.
4. Scroll down to your game and verify the same. If a game's audio slider is tied to a disconnected virtual audio device, Discord will capture absolute silence.

If This Doesn't Work: The 3 Most Common Failure Points

If you have completed the steps above and your viewers still cannot hear your game audio, check these three stubborn Windows 11 edge cases:

• Nahimic / Sonic Studio / Realtek Audio Control Bloatware: Pre-installed motherboard audio utilities on Windows 11 inject proprietary audio effects layers that block loopback capture. Open your system tray, locate apps like Nahimic Companion or Sonic Studio, open them, and disable any "Audio Enhancements" or virtual surround sound layers.
• HDR and Variable Refresh Rate (VRR) Interference: On certain multi-monitor setups running Windows 11, enabling hardware-accelerated GPU scheduling (HAGS) alongside exclusive fullscreen game modes disrupts the DirectX hook. Disable HAGS by going to Settings > System > Display > Graphics > Default graphics settings, toggle off Hardware-accelerated GPU scheduling, and restart your PC.
• Corrupted Discord Cache: Discord holds onto old capture pipeline states in local cache directories. Close Discord completely, press Win + R, type %appdata%, delete the discord folder, and do the same for %localappdata%. Restart Discord, log back in, and test the stream.

Prevention and Alternative Streaming Workarounds

To prevent audio dropouts from recurring after future Windows 11 cumulative updates, keep your GPU drivers updated via clean installations (using DDU if necessary) and avoid running Discord inside web browsers for streaming. The native Discord desktop client has deeper API access to Windows session routing than Chrome or Edge.

If Discord's native game capture continues to fail due to stubborn anti-cheat software (such as Vanguard or Easy Anti-Cheat blocking DLL injection), bypass Discord's hook entirely by setting up an OBS Studio Virtual Camera & Audio Output, or use NVIDIA Broadcast to pipe your game audio through a virtual microphone input within Discord. This completely bypasses Windows loopback limitations and ensures stable audio delivery for every stream.