Silent GameLoop — the audio is usually playing, just not where you are listening
GameLoop's audio crosses three layers before it reaches your headphones, and the two cheapest checks catch most failures. Reinstalling the emulator catches almost none.
Sound in GameLoop travels through three layers before you hear it: the virtual audio device the emulator presents to the Android game, GameLoop's bridge from that device into a Windows audio stream, and the Windows audio stack itself. Total silence is a break at one of those three joints, and the joint nearest to Windows is by far the most likely.
That ordering matters, because the standard response to "no sound" is to reinstall the emulator — close to the least likely fix on the list.
Start with the two cheap checks
The per-application volume mixer. Windows keeps a separate volume for every application, and GameLoop can be muted there while every other program on the machine plays normally. Right-click the taskbar speaker, open Volume mixer, find the GameLoop entry with a game actually running, and confirm it is neither muted nor at the bottom of its slider.
The default playback device. With headphones, monitor speakers, desktop speakers and a Bluetooth headset all present, Windows routes to whichever endpoint is default — which is not necessarily the one on your head. Set the device you are using as both Default Device and Default Communication Device in the Playback tab, then fully exit GameLoop from the system tray and start it again. Applications latch onto an audio endpoint when they start; changing the default underneath a running emulator often does nothing until it restarts.
Between them, these two account for a large share of reported GameLoop silence.
Then the settings that break audio invisibly
Exclusive mode. In the playback device's Properties, Advanced tab, "Allow applications to take exclusive control of this device" lets one program seize the endpoint and lock everything else out. When GameLoop and a communications app both want it, one of them loses and goes quiet without an error. Unchecking both exclusive-mode boxes is the standard fix for audio that works in the launcher and disappears inside a match.
Spatial sound. Windows Sonic, Dolby Atmos and DTS insert an extra processing stage between the application and the endpoint. Turning it off for the device is worth a test, and it also removes a chunk of latency.
GameLoop's own output setting. The emulator carries its own audio configuration. If the output device there is pinned to something you are not using, Windows-side changes will not reach it.
The Windows Audio service. AudioSrv and Windows Audio Endpoint Builder can stall, and applications lose their connection with no error at all. Restarting both from services.msc frequently restores sound to a running GameLoop without relaunching it — which is also a clean way to confirm the fault was never in the emulator.
The audio driver. Windows Update has a habit of replacing a working vendor driver with a generic Microsoft one, and the symptom is exactly this: most applications fine, one silent. Check the driver date in Device Manager. If it changed recently, Roll Back Driver in the same properties window is the fastest test. Note that "Update driver" in Device Manager tends to reinstall the generic driver you are trying to escape; the vendor's own package is the one you want.
Virtual audio devices. Voicemeeter, VB-Cable, RTX Voice and voice-chat noise suppression insert virtual endpoints that can quietly capture GameLoop's output. Close them and test; if sound returns, fix the routing rather than the emulator.
What does not fix it
| Common advice | Why it misses |
|---|---|
| Reinstalling GameLoop first | Repairs the one layer least likely to be at fault, and costs the most time. Keep it last. |
| Clearing the emulator cache | Reasonable for corruption after an update. It does nothing about a muted mixer channel or a wrong default endpoint. |
| "Update driver" from Device Manager | Usually reinstalls the same generic Microsoft driver. Go to the audio hardware vendor instead. |
| Buying a new headset | Test the current one in any other application first. If it works there, the hardware is not the problem. |
| Raising every in-game slider to maximum | Worth checking that a game update did not zero them, but a slider cannot route audio to a device Windows is not using. |
A quick way to bisect the whole thing: launch a different game inside GameLoop. Sound in one game and silence in another puts the fault in that game's own audio settings or install, not in the emulator or in Windows.