How to Fix Sound Not Working Windows: A 9-Step Checklist From Connections to Drivers

Fix sound not working in Windows by checking hardware connections first, then confirming the correct playback device is set, then restarting the audio services and driver — most silent PCs are resolved at the third step. The exact order matters because Windows 10 and Windows 11 hide different switches, and many users waste an hour reinstalling drivers when the real fault is a muted output or an unplugged cable. Work through the nine steps below in sequence rather than jumping to the end.

The steps assume you can still hear nothing anywhere — system sounds, music, video calls. If only one app is silent, jump to the per-app volume mixer section. If the sound icon in the taskbar shows a crossed-out red circle, the audio service has stopped and the service-restart step is your fastest fix.

Step 1: Confirm the Physical Connection and Speaker Power First

Before touching a single Windows setting, prove the fault isn't outside the computer. A large share of "no sound" reports end at a detached cable or a speaker switched to the wrong input. Ten seconds on this saves an hour of driver surgery.

1: Unplug and reseat the 3.5 mm jack or USB audio cable at both the speaker and the PC. 2: Confirm the speaker or headset is powered on and its volume knob is past zero. 3: If your monitor has built-in speakers over HDMI or DisplayPort, check the monitor's own input source and volume menu. 4: Try a second pair of headphones or another speaker on the same jack. 5: If a front-panel jack is silent but the rear one works, suspect the front-panel header cable inside the case.

A quick rule: if plugging in headphones produces the static pop in your ears, Windows is sending current and the OS is likely fine — the output device or its driver is the suspect. If there's no pop at all, treat the jack, cable, and speaker as the fault until proven otherwise. Laptops with a single combo jack need a TRRS headset; a four-pole plug misaligned in a three-pole socket will often play through one channel only or not at all.

Step 2: Set the Correct Playback Device in Sound Settings

Windows happily routes audio to a device you can't hear — a disconnected Bluetooth headset, a virtual cable, or a monitor that reports a speaker it doesn't have. Setting the default output explicitly clears this class of fault.

On Windows 11, open Settings, then System, then Sound. The output list sits at the top; pick the device you want and click the arrow or check mark to set it as default. On Windows 10, open Settings, then System, then Sound, and use the "Choose your output device" dropdown. The legacy Control Panel applet at mmsys.cpl gives you a fuller picture: it names every render endpoint, including disabled HIDMI outputs.

If the device you expect doesn't appear at all, right-click in the Playback tab and tick "Show Disabled Devices" and "Show Disconnected Devices." A disabled Realtek or USB endpoint is a common silent cause, especially after a Windows feature update. Select the endpoint, click "Set Default," then "Properties" and test the levels slider to confirm the meter moves when you play audio — a live meter with no sound means cable or speaker; a dead meter means the OS or driver.

Step 3: Restart the Windows Audio Services and Driver

The Windows audio stack runs through three services — Windows Audio, Windows Audio Endpoint Builder, and, on some systems, the Human Interface Device service for headset controls. If Windows Audio crashes, the taskbar speaker icon gets the red crossed circle and no endpoint can produce sound.

Press Win+R, type services.msc, and press Enter. Find Windows Audio, right-click, and choose Restart. If Restart is greyed out, open Start and choose Restart. Repeat for Windows Audio Endpoint Builder, then play a test sound. For a faster reset, open Device Manager, expand "Sound, video and game controllers," right-click your primary audio device, and choose Disable device; wait five seconds, then Enable device.

On Windows 11, the quickest equivalent is Settings > System > Sound > Troubleshoot, which restarts the endpoint and probes for a configured device. According to Microsoft's support documentation, restarting the Windows Audio service is the recommended first software step when the speaker icon shows a red X. If the service stops again within a minute, a third-party app or a corrupt registry key is killing it — check the Applications log in Event Viewer for a stop entry tied to a specific process.

Step 4: Clear the Mute and Volume Traps in Windows 11 and 10

A muted endpoint, a zero app slider, or a communications ducking rule on Windows 10 and 11 account for plenty of "no sound" tickets. Windows has three separate volume layers and the one that's wrong is rarely the one you checked.

First, click the speaker icon in the system tray and confirm the master slider is above zero and the endpoint isn't muted. Second, open Settings > System > Sound > Volume mixer and check the individual sliders for your browser or media app — a muted Spotify or browser tab is invisible in the master control. Third, check Settings > System > Sound > More sound settings, Communications tab, and set "When Windows detects communications activity" to "Do nothing" if VoIP software has been ducking all your media.

On Windows 11, the Volume mixer also exposes per-app output device routing. A video player can be pinned to a dead output while the system default is fine. If one app is silent and the rest work, the mixer is the first place to look before any driver work.

Step 5: Update, Roll Back, or Reinstall the Audio Driver

Driver faults show up as crackling, a missing device list, or a Code 10/Code 43 device status in Device Manager. Updating is the standard fix; rolling back is the fix when a fresh update broke working audio.

The Roll Back Driver button greys out when Windows has no previous driver cached, which happens after a clean install. On laptops, prefer the manufacturer's audio package over Windows Update's generic Realtek build — the OEM package often carries the amplifier tuning that a generic driver lacks.

Step 6: Run the Built-In Audio Troubleshooter and Check Device Status

Windows ships two audio troubleshooters, and the one in Settings is more capable than the legacy Control Panel version. It can re-enable a disabled endpoint, restart the service, and report a specific error code before you touch a driver.

Open Settings > System > Sound and scroll to Troubleshoot (Windows 11) or Settings > Update & Security > Troubleshoot > Additional troubleshooters > Playing Audio (Windows 10). Run it with the failing speaker already selected in the output list. The report names the endpoint checked and any service or driver it restarted; note the exact wording, because "Audio services not responding" points at the service layer while "Device is disabled" points at the endpoint.

If the troubleshooter returns "No problems detected" but sound still fails, open Device Manager and read the device status under Properties > General. A Code 10 ("This device cannot start") or a yellow triangle means the driver hasn't loaded; Code 43 is a reported hardware fault and often means a failed codec or a USB audio chip that needs a power-cycle (unplug, wait, replug). Windows 11's Device Manager also exposes "Events" on the device, logging each driver install and start attempt.

Step 7: Check HDMI, DisplayPort, and Bluetooth Routing to the Wrong Endpoint

Monitors over HDMI or DisplayPort present a speaker endpoint even when the display has no speakers. Windows may auto-switch to that endpoint when the monitor connects, so the PC is "playing" to a display that can never emit sound.

Open mmsys.cpl's Playback tab and disable endpoints you never use — right-click the monitor entry and choose Disable. That stops the auto-switch. For Bluetooth, disconnect and re-pair the headset rather than trusting the listed device; a half-connected Bluetooth audio profile commonly shows "Connected" for voice but not music. In Settings > Bluetooth & devices, remove the device, then re-add it, and confirm the output switches when the headset connects.

On a laptop docked over a single USB-C cable, both the dock's audio jack and the monitor's HDMI endpoint can claim priority. The reliable rule is to set your primary output once, then disable the other endpoints in the Playback tab so Windows can't re-route at the next wake. If you hear sound the moment you unplug the monitor, the monitor endpoint was the problem.

Step 8: Rebuild the Audio Stack When Settings Are Corrupt

When every UI check passes and the device list is still wrong, the audio registry keys or the endpoint database are corrupt. Rebuilding from a clean state usually takes ten minutes and reverses the fault.

1: Open Device Manager and uninstall every entry under "Sound, video and game controllers." 2: Restart the PC without reinstalling anything. 3: Let Windows re-detect and reinstall the default driver. 4: Install the OEM audio package from the PC maker's support page if the device shows as "High Definition Audio Device." 5: Rerun the Settings audio troubleshooter, then re-select your default output.

If the fault survives a rebuild, run the system file checker: open an elevated Command Prompt and type sfc /scannow, then DISM /Online /Cleanup-Image /RestoreHealth. Both take several minutes and repair damaged Windows component files, including the audio endpoint builder's dependencies. A corrupt user profile can also break audio routing; create a new local account and test sound there before attempting a full reset.

Step 9: When to Suspect Hardware and What to Try Before Replacing It

The last fork is hardware. If headphones plugged into the rear jack work but the front jack doesn't, the front-panel header cable or the jack itself is failing — a part that costs a few dollars and takes minutes to reseat. If no jack works on a desktop, a PCIe sound card or a USB audio adapter (typically a small external DAC) is the cheap workaround.

For laptops, the audio codec is soldered to the mainboard, so a dead codec means mainboard repair or an external USB adapter. Two quick tests settle it: boot a Linux live USB and play a test tone — if Linux also has no sound, the hardware is the likely fault; and check the BIOS/UEFI setup for an "HD Audio" or "Audio Controller" toggle, sometimes disabled by a technician or a Windows fast-boot glitch. A BIOS reset to default also clears a misconfigured audio controller setting.

If sound worked before a Windows feature update and failed right after, the driver layer is the prime suspect, not the codec. Check Windows Update history for the audio driver entry dated the same day, and roll it back from Device Manager before spending money on hardware. Conversely, if the device has never made sound since a repair or a case swap, check that the front-panel audio header is seated on the right pins — a common mistake after a build.

FAQ

Does a Windows reset fix sound not working?

A reset fixes sound only when the fault is in the Windows user profile or the audio registry, and that's the minority of cases. Most silent PCs are resolved at the playback-device or driver stage, so a reset wipes your apps before you've isolated the cause. Try a new local user account first — if audio works there, migrate the profile rather than resetting the PC. Only reset after the service restart, driver rollback, and sfc/DISM checks all fail.

Why is my sound not working even though the volume is up?

Volume up only proves the master slider is above zero, and Windows has three independent layers beneath it. An app slider in the Volume mixer, a muted endpoint, or a communications ducking rule can each silence output while the master reads 60%. Check the endpoint mute in mmsys.cpl first, then the per-app mixer. A dead output meter during playback points at the driver or hardware, not the volume level.

Can a monitor cause no sound on Windows?

Yes — an HDMI or DisplayPort monitor publishes a speaker endpoint whether or not it has speakers, and Windows can auto-switch to it on connection. The tell is that audio returns the moment you unplug the monitor cable. Disable that endpoint in the Playback tab to stop the auto-switch permanently. Docks compound the problem because they add a second HDMI and a headphone jack into the same routing list.

How long does an audio driver rollback take, and is it risky?

The rollback itself installs in under two minutes and is reversible by updating again. The risk isn't data loss — it's losing OEM amplifier tuning until you reinstall the manufacturer's package. If Roll Back Driver is greyed out, Windows has no cached prior driver, so you'll need the OEM download instead. Keep the downloaded installer on hand before rolling back so you can restore the working driver in one step.

What does a red X on the speaker icon mean?

The red crossed circle means the Windows Audio service has stopped, not that the speakers failed. Restart the service from services.msc or run the Settings troubleshooter, which restarts the endpoint builder too. If the X returns within a minute, check Event Viewer's Application log for the process that stopped the service — a third-party audio app or a corrupt registry key is usually behind it. A Code 10 in Device Manager is a separate driver fault with the same icon symptom.

Will a USB sound card work if the audio jack is dead?

A USB DAC or sound card bypasses the onboard codec entirely, so it works whenever the failure is the jack or the codec itself. It's the cheapest hardware test as well: plug in a $10–15 USB adapter, set it as the default output, and if sound returns, the onboard audio is confirmed faulty. A USB adapter also restores headset microphone input on laptops with a broken combo jack.

Why does sound stop after a Windows update?

Windows Update can replace an OEM audio driver with a generic one, and the generic build often lacks the amplifier tuning or the endpoint definitions your machine needs. Check Update history for the driver entry dated the same day audio failed, then roll it back in Device Manager. After restoring sound, set the device to not auto-update the driver via the OEM package's installer if it offers that option.

Does fast startup cause audio problems on Windows 10 and 11?

Fast startup keeps a hibernated kernel session, and the audio driver can resume in an inconsistent state after it. Symptoms include sound working at login and dying after the first sleep, or the endpoint disappearing from the list. Turn it off temporarily in Control Panel > Power Options > Choose what the power buttons do, then test a full shutdown and boot. If that clears the fault, a driver update or an OEM audio package is the longer-term fix.