Your volume is not working because the signal chain is broken somewhere between the app and the speaker, and Windows or macOS is usually routing audio to a different output device, a muted per-app mixer, or a failed driver. The fix starts by checking the output device selected in the system tray or menu bar, then confirming the app's own volume slider, then the physical mute switch on laptops and headsets.
That sequence matters more than any single setting. Audio on a modern computer passes through four or five independent volume layers, and each one can zero out the signal while every other layer looks fine. A laptop at 80 percent system volume with a muted browser tab plays nothing, and the user sees a working volume slider.
This explainer walks the full chain: the digital mix, the driver handoff, the hardware switch, and the Bluetooth codec negotiation. It also covers why one app is silent while another works, when a driver reset helps, and what typically cannot be fixed by software.
The Four-Stage Audio Signal Chain
Every sound on a computer crosses four stages before it reaches your ear. The application generates samples. The operating system mixes those samples with other apps and applies the master and per-app volume. The audio driver receives the mixed stream and passes it to the hardware. The hardware converts digital samples to analog voltage and drives the speaker or headphone.
A failure at any stage produces the same symptom: silence. That is why volume problems feel confusing. The slider you see in the tray reflects the operating system mixer, which is only stage two. A muted app, a broken driver, or a failed speaker each bypasses that slider's authority.
The mix stage is where most problems hide. Windows and macOS both keep separate volume values per application. Windows stores these in the volume mixer, and macOS ties some apps to their own slider inside the app. When an app like Chrome or Zoom updates, it can reset its session volume to zero without touching the system master.
Below the mixer sits the audio endpoint, a virtual device object the driver creates. Windows assigns each endpoint its own volume curve. A corrupted endpoint can show a slider at 100 percent while the driver outputs silence, because the slider is a UI element that writes to the endpoint, not a measurement of actual output.
The driver stage is the most failure-prone in older machines. Realtek, Intel, and AMD audio drivers occasionally fail to reinitialize after a Windows update or a sleep cycle. The device manager may show no error while the driver streams zeros.
Plain language: the volume slider is a request, not a receipt. It tells the computer what you want, not what the speaker is doing.
How Loudness, Headroom, and Codecs Interact
Digital audio carries amplitude as sample values, and that amplitude has a ceiling. A 16-bit sample tops out at 0 dBFS, the loudest value the format can represent. Above that, samples clip. Windows applies a volume curve that reduces amplitude below full scale, so a slider at 50 percent is not half the perceived loudness. The curve compresses and shifts depending on the driver and the device.
Bluetooth adds a second layer. When you connect Bluetooth headphones, the codec negotiates a bitrate and the operating system hands volume control to the headset in many cases. The absolute volume setting, common on Android and increasingly on Windows, means the phone or PC tells the headset to set its own internal volume. If the headset firmware ignores that command, the slider moves but the loudness does not.
USB and HDMI outputs behave differently again. HDMI audio relies on the display's own volume and mute state. A monitor with a built-in speaker can be muted on the monitor itself while the PC reports active audio. USB headsets often expose hardware volume as a separate HID control, and that control can sit at zero independently of the system slider.
The perceived loudness scale is not linear. A jump from 30 to 60 percent system volume sounds larger than a jump from 60 to 90, because loudness perception roughly follows a power law. This explains why small slider adjustments near the top feel ineffective and why users sometimes think volume has stopped working when the real problem is a compressed curve.
Quantified Context: Numbers That Explain the Symptom
Silence has thresholds. Digital silence is not zero amplitude; it is anything below the noise floor of the output path. A typical laptop speaker produces audible output above roughly 30 to 40 dB SPL in a quiet room, and the DAC noise floor sits near -90 dBFS. That leaves a wide window where the signal exists but is inaudible.
The Windows volume mixer persists per-app values across reboots. A reset to zero on a single app is common after a crash, and the master stays untouched. Because the taskbar slider reflects only the master, the user sees full volume and hears nothing from that app.
Bluetooth absolute volume has a known failure mode. When the setting is enabled and the headset firmware mishandles the command, the headset stays at a fixed low internal level. Disabling absolute volume in Windows developer settings or in the headset app often restores control.
Driver timeouts are another measurable failure. The Windows audio service, Audiosrv, restarts automatically after a fault, usually within seconds. A loop of restarts appears in Event Viewer as repeated service start events, and audio cuts in and out on a rhythm. One restart is normal; a repeating pattern points to a driver or endpoint fault, not a user setting.
Headset impedance matters for wired gear. High-impedance headphones above roughly 100 ohms on a weak onboard jack can sound faint but not silent. That is a gain limitation, not a volume bug.
Why One App Is Silent While Others Work
Per-app mixing is the single most common cause of selective silence. Each audio session in Windows gets its own volume node. When an app updates or crashes, that node can persist in a muted state. Restarting the app usually resets it, but sometimes the session survives and keeps the mute.
Browser tabs are a common culprit. Chrome and Edge let each tab carry its own mute state, and a muted tab shows a small speaker icon on the tab itself. The operating system mixer may show the browser at full volume because the tab-level mute sits upstream.
Communication apps add automatic ducking. Zoom, Teams, and Discord reduce other audio when a call starts. That is intentional behavior, not a failure, but it makes music or video sound faint during a meeting. The setting is usually labeled as a volume reduction or ducking option.
Exclusive-mode audio can lock a device. Some apps request exclusive control of the output device and block others. If the app holding the device hangs, every other app goes silent until the holder releases the endpoint or the process is killed.
Streaming apps with their own volume inside the player, such as some web players and desktop clients, can sit at zero even when the system and mixer are correct. That third slider is the one users most often miss.
Misconceptions That Waste Repair Time
The first misconception is that a full slider means full volume. It does not. The slider is a control input, and the actual output depends on the endpoint, the app session, and the hardware. Treating the slider as a measurement leads to reinstalling drivers that were never broken.
The second is that driver reinstalling fixes everything. Driver resets help when the endpoint object is corrupt or the driver failed to initialize. They do nothing for a muted browser tab, a hardware mute switch, or an HDMI display that is muted on its own menu. A large share of "audio driver" fixes that appear to work are actually endpoint resets triggered by the reinstall.
The third is that a silent speaker means dead hardware. Most built-in laptop speakers that go silent are muted by a keyboard function key, a firmware switch, or an output routing change. The speaker hardware fails far less often than the settings layer does.
The fourth is that Bluetooth disconnection means pairing failure. When Bluetooth audio goes silent but the device still shows connected, the usual cause is codec or absolute-volume negotiation, not lost pairing. Re-pairing wastes time and can make the headset forget its volume state.
The counterintuitive detail is this: on many laptops, the headphone jack and the internal speakers share one amplifier. Plugging in a headphone with a damaged plug can leave the jack sensor stuck, so the laptop keeps routing audio to a jack that has nothing connected. The speakers go silent while the system reports headphones. Cleaning or exercising the jack often restores speaker output without any software change.
Comparison: Which Output Path Fails How
| Output type | Typical failure mode | Software-fixable | First check |
|---|---|---|---|
| Built-in laptop speakers | Function-key mute, jack sensor stuck | Usually yes | Keyboard mute key and jack |
| Wired headphone jack | Impedance too high, plug damage, sensor stuck | Partially | Cable seating and impedance |
| USB headset | Hardware HID volume at zero, driver conflict | Yes | Hardware volume wheel and device manager |
| HDMI or DisplayPort monitor | Monitor mute or its own volume at zero | Yes | Monitor menu buttons |
| Bluetooth headphones | Absolute volume mismatch, codec downgrade | Yes | Headset app and OS absolute-volume setting |
| Virtual audio device | Wrong default device selected, app bound to it | Yes | Default device in sound settings |
| External DAC or interface | USB power fault, sample-rate mismatch | Sometimes | Cable, port, and sample-rate setting |
The table shows why a single fix never covers every case. Each path carries its own failure signature, and the symptoms look identical to the user.
Timeline: A Typical Silent-Audio Troubleshooting Session
| Step | What you do | Expected time | What it isolates |
|---|---|---|---|
| 1 | Check the output device selected in the tray or menu bar | 1 minute | Wrong default device |
| 2 | Check per-app mixer and the app's own slider | 2 minutes | Muted session or app-level zero |
| 3 | Check keyboard mute keys and hardware switches | 1 minute | Physical mute state |
| 4 | Test with a different app and a different output | 3 minutes | App-specific versus system-wide |
| 5 | Restart the Windows audio service or coreaudiod | 2 minutes | Service or driver hang |
| 6 | Reinstall or roll back the audio driver | 5 to 15 minutes | Endpoint corruption |
| 7 | Test hardware with another computer or cable | 5 minutes | Failed speaker, jack, or cable |
Most silent-audio cases resolve in steps 1 through 3. That is three to five minutes of checking, and it explains why technicians ask about the taskbar device before opening device manager. The longer steps matter only when the quick checks come back clean.
Practical Actions, With Thresholds
Work down the chain, not up. Start at the application, then the system mixer, then the endpoint, then the hardware.
Confirm the selected output device. In Windows, open Settings, then System, then Sound, and check the output dropdown. In macOS, open Control Center and the Sound pane. If the device listed is not the one you expect, that is your fault point. Open the per-app mixer. In Windows, right-click the taskbar speaker icon and open Volume mixer. Check every app at or near 0. In macOS, check each app's own volume slider, because the system mixer does not expose per-app levels. Check the app's internal slider. Look inside the player, the call app, or the browser tab. A tab speaker icon with a slash means that tab is muted regardless of system volume. Exercise the physical controls. Press the mute function key once, watch the on-screen indicator, then press it again. On headsets, turn the hardware volume wheel through its full range and back. Reseat the connection. Unplug and replug the headphone or USB cable. On laptops, plug a known-good headphone into the jack and pull it out to clear a stuck sensor. Restart the audio service. In Windows, open Services and restart Windows Audio. On macOS, run sudo killall coreaudiod in Terminal, which restarts the core audio daemon. Roll back a suspect driver. In Windows, open Device Manager, right-click the audio device, then Properties, then Driver, then Roll Back Driver. Use this only after a recent update changed behavior. Test with a second output. Route audio to a different device, such as Bluetooth or HDMI. If the second device works, the fault is in the first path, not the software.
Stop and reassess when two different output devices both fail across two different apps. At that point the problem is system-wide, and the service restart or driver step is justified. If only one device fails across all apps, the fault is in that device or its cable.
If the machine is a managed work computer, check whether corporate policy has disabled or redirected audio devices. Group policy can hide endpoints, and no amount of local troubleshooting overrides it.
Limitations: What Software Cannot Fix
Software fixes stop at the boundary of the hardware. A blown speaker, a cracked solder joint on the headphone jack, or a damaged USB port will not respond to driver resets. Testing the device on a second computer is the cleanest way to separate hardware from configuration, and it takes about five minutes.
Some failures live in firmware you cannot reach. Monitor firmware can hold a stale mute state until the display is power-cycled for 30 seconds or more. Headset firmware sometimes ships with absolute-volume bugs that only a vendor update resolves.
Sample-rate mismatches cause crackle or pitch problems rather than silence, but a mismatched rate between the app and the endpoint can also produce no output at all on some interfaces. Setting both to 48 kHz resolves most of these.
Corrupted user profiles occasionally keep audio settings stuck across reboots. Creating a fresh test account and checking audio there isolates a profile-level fault from a hardware one.
Finally, virtualization adds a layer that local fixes cannot touch. Virtual machines and remote desktop sessions have their own audio redirection settings, and the host and guest must both allow the route.
The general rule: work the chain in order, isolate with a second device and a second app, and stop chasing software once hardware testing reproduces the silence.