You probably cannot hear anything on your PC because Windows is sending sound to the wrong output device, or a muted or zero-volume mixer has silenced the path. Less often, the audio driver has crashed, a Bluetooth endpoint has grabbed the default, or the physical connection has failed. Check the output device, then the mixer, then the driver, in that order.
[citation:1] Microsoft Support. "Fix sound or audio problems in Windows."
The chain from a sound file to your ear has eight or more stages, and a break at any one produces total silence. That is why "no sound" is a symptom, not a diagnosis. The fastest path is to test the chain in order and stop where it breaks.
The audio path from a file to your ear
A PC plays sound by streaming a digital signal through a sequence of software and hardware stages. Each stage must pass the signal and be unmuted and powered.
On a Windows machine the sequence runs roughly like this. An application renders audio through the Windows audio engine (Audiosrv). The engine hands samples to the audio endpoint buffer, which feeds the audio driver. The driver hands data to the DAC, which converts it to an analog voltage. That voltage drives an amplifier, then a speaker or headphone driver, then the air, then your ear.
The sample rate matters at the conversion stage. Most consumer audio is 44.1 kHz or 48 kHz at 16 or 24 bits. If an app requests a format the endpoint cannot handle, the audio engine may fail to open the stream entirely, and you get silence rather than distortion. This is a common cause after a driver update resets a device to an unsupported default format.
The default-device mechanism is the most common failure. Windows routes audio to one endpoint designated as default. Plugging in headphones, a monitor with speakers, or a Bluetooth headset can change that endpoint automatically. If the new endpoint is muted, at zero volume, or disconnected but still listed, the audio goes nowhere you can hear. The app may still show meters moving, because the render stream is healthy; only the final stage is silent.
A plain-language version: Windows decides where sound goes, and if it decides wrong, everything looks fine while you hear nothing.
Quantifying silence: levels, thresholds, and what "muted" means
Audio levels are measured in decibels relative to full scale (dBFS) in the digital domain and in sound pressure level (dB SPL) in the air. A digital signal at 0 dBFS is the loudest the system can represent; lower values are quieter. Silence in the digital domain is negative infinity, but practical mute is a few tens of dB below your noise floor.
Windows mixer faders typically run from -96 dB to 0 dB. A fader at -96 dB is effectively silent for most content. The Windows volume slider maps to a curve; 0 percent mutes, and small percentages produce very low output. Some users report "no sound" when the slider is at 1 to 5 percent, because laptop speakers at that level are inaudible in a room.
There is a separate mute flag per endpoint and per application stream. Muting an app in the Volume Mixer silences only that app; muting the endpoint silences everything. Both are common. A muted endpoint shows a crossed speaker icon, but on some driver control panels the icon is not obvious.
Digitally, a healthy render stream shows non-zero peak meters. If your app's meter moves but the device meter does not, the problem is between the app and the endpoint. If the device meter moves but you hear nothing, the problem is downstream: connection, amplifier, or transducer. That single observation narrows the fault faster than any troubleshooting wizard.
One counterintuitive detail: a device can be "working" and still silent. Windows may report the device as installed and functioning while the physical jack has no speaker attached, or while the device is a virtual endpoint that routes to nothing. Device status is a software claim, not proof of audible output.
Timeline of a typical audio failure
Most no-sound situations follow a recognizable time course. Reconstructing what changed in the minutes before silence often identifies the cause faster than inspection.
| When | What often happened | Typical result |
|---|---|---|
| Minutes before | Headphones or Bluetooth device connected | Default endpoint switched silently |
| Minutes before | Windows or driver update installed | Device reset to unsupported format |
| Hours before | App muted in Volume Mixer | One app silent, system sounds fine |
| Days before | Jack or cable partially pulled | Intermittent or one-channel silence |
| Weeks before | Driver corrupted by failed update | Device disappears from list |
| Overnight | PC resumed from sleep | Endpoint failed to reinitialize |
| At boot | Audio service disabled or failing | No endpoints listed at all |
| Ongoing | Monitor speakers with no audio cable | Video works, audio never arrives |
This table is a diagnostic aid, not a causal ranking. The point is that "no sound" usually has a timestamp: identify the last change and you usually find the fault.
Edge cases that break the usual checklist
Some failures bypass every routine check because the mechanism is unusual.
Bluetooth endpoint confusion is one. A Bluetooth headset can connect in two profiles: high-quality stereo (A2DP) and low-bandwidth hands-free (HFP). Switching profiles can mute or misroute audio. The device may show connected while the active profile carries no stream. Reconnecting or removing and re-pairing the device resolves most cases.
Monitor audio is another. Many displays accept HDMI or DisplayPort audio but have no speakers, or have speakers that are disabled in the monitor menu. Windows may set the monitor as the default output because it reports an audio endpoint. The fix is selecting speakers or headphones manually.
Virtual audio devices cause silent routing. Apps like voice changers, streaming tools, and conferencing software install virtual endpoints. If a virtual endpoint becomes default, audio is captured by software you did not intend to listen through. Checking the device list for unfamiliar entries reveals this quickly.
Disabled audio services stop everything. The Windows Audio service and its endpoint builder must both run. If either is stopped, no endpoints appear, and every app reports no output device. This is rare but produces a clean, total failure that looks like hardware death.
A professional caveat: never conclude a PC has a dead sound card from symptoms alone. Endpoint, service, and driver faults mimic hardware failure. Only substitution testing, such as trying a USB audio adapter or booting a live environment, separates software from hardware.
Misconceptions about PC audio silence
Several beliefs sound reasonable and are wrong in ways that waste time.
"It must be the speakers" is the most common. In practice, the default-device and mixer faults dominate. Speakers fail less often than routing does. Test the speakers on another source before replacing them.
"If the meter moves, sound is playing" is half true. A moving meter proves a render stream exists. It does not prove the endpoint is unmuted, connected, or audible. The signal can be perfect and still terminate in a muted amplifier.
"Reinstalling Windows will fix it" is an expensive last resort. Most no-sound faults resolve at the endpoint, mixer, or driver layer within minutes. Reinstallation helps when the audio stack is corrupted beyond repair, which is uncommon.
"Volume at 100 percent means maximum loudness" ignores per-app and per-endpoint layers. The effective level is the product of the app fader, the endpoint fader, any enhancement processing, and the hardware amplifier. Any one at zero silences the rest.
A second counterintuitive point: some audio enhancements can mute output. Spatial sound, equalizer, and "loudness equalization" features occasionally fail and produce silence. Disabling enhancements is a legitimate diagnostic step, not superstition.
Practical actions, in diagnostic order
Work through these in sequence and stop when sound returns. Each step isolates one stage of the chain.
First, confirm the endpoint. Open the Windows sound settings and check which output device is selected. If an unfamiliar device, monitor, or Bluetooth headset is default, switch to speakers or headphones and test. Confirm the endpoint is not muted and its slider is above 20 percent.
Second, check the mixer. Open the Volume Mixer and verify the app producing sound is not muted and its fader is up. System sounds are a useful control: if the Windows test tone plays, the endpoint and driver are healthy and the problem is app-specific.
Third, inspect the physical connection. Reseat the jack or cable, confirm the correct port (green for line out on desktop boards), and test the headphones or speakers on another device. A partially inserted plug produces silence or one channel.
Fourth, check the audio service. Open Services and confirm Windows Audio and Windows Audio Endpoint Builder are running and set to automatic. Restart both if in doubt.
Fifth, reset the driver. In Device Manager, disable and re-enable the audio device, or uninstall it and restart so Windows reinstalls it. If the device vanished entirely, this step often restores it.
Sixth, test with a substitute. A USB audio adapter or a live Linux boot isolates hardware from software. If audio works there, the PC hardware is fine and the fault is in Windows configuration.
Red-flag warnings worth heeding:
Static, crackling, or popping before silence suggests a failing jack, cable, or amplifier, not a software fault. One channel dead points to a plug, cable, or driver channel-mapping issue, not a muted endpoint. Audio that dies only after sleep or updates indicates driver or endpoint reinitialization failure. A device that disappears from the list entirely points to a service or driver problem, not a mute. Smoke, heat, or a burning smell from the case means stop and seek service; do not keep testing.
Limits of what self-diagnosis can conclude
The checklist above resolves most everyday silence, but it cannot distinguish every fault. Driver bugs, firmware defects, and failing codecs can produce symptoms identical to configuration errors. Without substitution testing, you cannot prove a component is healthy.
Measurements have limits too. Software meters show the digital stream, not the analog output. Proving the DAC, amplifier, and speaker are working requires either a known-good substitute or measurement equipment most users lack. That is the boundary between troubleshooting and repair.
One pattern is worth remembering. Silence with moving meters is almost always downstream of the render stream: endpoint, connection, or transducer. Silence with dead meters is upstream: app, service, or driver. That single observation, made in seconds, directs you to the right half of the chain and saves the rest of the checklist.
[citation:2] Microsoft Support. "No sound in Windows."