Fix Windows Laptop Speakers Not Working: Complete 2026 Guide

Most laptop speaker faults end up being a routing problem rather than a broken speaker. Windows can send sound to a headset that is no longer connected, a monitor with no speakers, or an app that chose its own output, all while the laptop speakers sit idle and healthy. This guide shows how to fix Windows laptop speakers not working by tracing where the sound is actually going, before anyone opens the case or orders a replacement part.

The first clue is usually the volume mixer. If the meter moves while nothing is heard, sound is playing somewhere you are not listening. If the meter stays flat, the app or the driver is the problem. Either answer points at a different fix, and both answers take less than a minute to find.

What Usually Causes This

Before the steps, it helps to know that this fault rarely has a single cause, and the table below separates the likely causes by the sign you actually see, so you can start at the row that matches your situation rather than at the top of a generic list. Working out how to fix Windows laptop speakers not working starts with that match, because the right first step depends on the symptom in front of you.

Likely cause	Sign you will see	First check
Wrong output device	Sound plays through headphones only	Select the laptop speakers as output
Muted or low volume	No sound with no error	Check volume and mute in two places
App specific mute	Sound fails in one app only	Check the Volume mixer
Audio service stopped	No device listed at all	Restart the Windows Audio service
Driver fault	Speakers missing after an update	Update or reinstall the audio driver
Speaker hardware fault	No sound after all software steps	Book a service check

Note what changed before the fault began, what still works, and what you have already tried, because those three facts turn a frustrating afternoon into a short sequence of tests. A short note on those points, written before you start, also makes any later conversation with support far shorter, since you can describe what you have ruled out instead of repeating the symptom.

Before You Check the Output

Read the whole guide once before changing anything, because the order matters, and a step skipped early often returns as a larger problem later. Where a price or a feature is given, check it on the vendor page before you commit, since pricing and features change, and the right choice depends on your situation and your existing setup.

When you approach fix Windows laptop speakers not working, keep a simple log of each test and its result, even a few lines on paper. Change one thing, test, and note the result before moving on, because changing three things at once and seeing an improvement leaves you unsure which change helped, and the fault returns when the unhelpful changes are undone.

Back up anything important before the later steps, even if you do not expect to reach them. A backup made while the device still works is worth far more than a backup attempted after a destructive step, and it removes the fear that keeps people from taking a legitimate last resort step. Check that the backup completed, rather than assuming it did, since a backup that never finished offers no protection at all.

Windows laptop speakers visual tied to the Before You Check the Output section of this guide

How to fix Windows laptop speakers not working in the Right Order

Working through fix Windows laptop speakers not working in this order keeps the least disruptive tests first, so a simple settings fault is found before anyone considers a reinstall, a replacement, or a repair booking, and each step below ends with what a success looks like, so you know when to stop.

Check volume and mute in two places. Raise the system volume, check the speaker icon for a mute symbol, and check the physical mute key or function key on the laptop. A system mute and an app mute are separate, and either one silences the speakers while the other looks normal. Test with a known audio file after each change, so the result is unambiguous. If this step restores normal behaviour, stop here and note what worked, because continuing past a working fix only adds risk.
Select the correct output device. Open Settings, System, Sound, and check the Output device list. Select the built in speakers by name, not a monitor, a headset, or a Bluetooth device that may have taken over output. Windows often switches output when a new device connects, so a device that worked yesterday can be routed elsewhere today. If this step restores normal behaviour, stop here and note what worked, because continuing past a working fix only adds risk.
Test with a second app and a second file. Play audio in a browser, a media player, and a system sound, and note which ones fail. Sound that fails in one app only points at that app and its own volume or output setting, while sound that fails everywhere points at the system. This test prevents a driver reinstall for an app level mute. If this step restores normal behaviour, stop here and note what worked, because continuing past a working fix only adds risk.
Open the Volume mixer. Right click the speaker icon and open Volume mixer, then check each app volume and mute state. An app can sit muted in the mixer while the system volume looks healthy, and browsers in particular can be muted per tab or per site. Raise any muted app and test that app again before moving on. If this step restores normal behaviour, stop here and note what worked, because continuing past a working fix only adds risk.
Restart the laptop. Restart Windows fully rather than using sleep or hibernate, since a restart reloads the audio stack and clears a stuck audio session. Test the speakers immediately after restart, before connecting headphones or Bluetooth devices, so a new device cannot seize output before the test. If this step restores normal behaviour, stop here and note what worked, because continuing past a working fix only adds risk.
Run the audio troubleshooter. Open Settings, System, Troubleshoot, Other troubleshooters, and run the Audio troubleshooter, following its prompts. The troubleshooter checks output selection, driver state, and service state in one pass, and it can fix a misconfigured device without manual steps. Note what it reports, even if it claims no fault, since that narrows the remaining causes. At this stage of fix Windows laptop speakers not working, a success here is especially valuable, because it proves the fault sat in the middle of the sequence rather than at either end. If this step restores normal behaviour, stop here and note what worked, because continuing past a working fix only adds risk.
Restart the Windows Audio service. Press Windows and R, type services.msc, and press Enter. Find Windows Audio, right click it, and choose Restart, then check that its startup type is Automatic. Also restart Windows Audio Endpoint Builder if it is listed. A stopped audio service silences every app at once, and a restart restores it without touching drivers. If this step restores normal behaviour, stop here and note what worked, because continuing past a working fix only adds risk.
Update the audio driver. Open Device Manager, expand Sound, video and game controllers, right click the audio device, and choose Update driver, then Search automatically. If Windows finds nothing, check the laptop maker support site for an audio driver for your exact model. Install, restart, and test before trying any other driver change. If this step restores normal behaviour, stop here and note what worked, because continuing past a working fix only adds risk.
Roll back or reinstall the driver. If sound failed after a driver update, open Device Manager, open the audio device Properties, and use Roll Back Driver on the Driver tab if it is available. Otherwise uninstall the device, restart, and let Windows reinstall it. Test after the reinstall before installing a maker driver, so you know which driver state actually works. If this step restores normal behaviour, stop here and note what worked, because continuing past a working fix only adds risk.
Check BIOS and hardware mute settings. Check the laptop maker utility or BIOS for an audio or speaker setting, and check any hardware mute switch on the laptop edge. Some laptops carry a physical audio switch that overrides every software setting, and a BIOS update can reset audio options. Change only the audio setting, and note the original value before changing it. If this step restores normal behaviour, stop here and note what worked, because continuing past a working fix only adds risk.
Test with headphones as a comparison. Plug in wired headphones and test the same audio file. Sound through headphones with silence from speakers points at the speakers or their connection, while silence through both points at the system. This comparison is the evidence a technician will ask for, so record it before seeking help. If this step restores normal behaviour, stop here and note what worked, because continuing past a working fix only adds risk.
Stop and book service for a hardware pattern. Stop when speakers stay silent after output selection, service restart, driver reinstall, and a headphone comparison that proves the system produces sound. Further driver changes cannot repair a failed speaker or a loose internal connection. Take your notes on output selection and headphone results for the service check. If this step restores normal behaviour, stop here and note what worked, because continuing past a working fix only adds risk.

Windows laptop speakers visual tied to the How to fix Windows laptop speakers not working in the Right Order section of this guide

Details People Often Miss

Speaker faults hide behind output routing more than any other cause. Windows can send sound to a monitor, a headset, or a Bluetooth device without any warning, and the speakers then look dead while the system works perfectly. Checking the output device first is not a trivial step, it is the step that resolves a large share of reported speaker faults. This distinction shapes how you should approach fix Windows laptop speakers not working.

Mute also hides in more than one place. System mute, app mute in the Volume mixer, browser tab mute, and a physical mute key can each silence sound independently, and fixing one while another stays muted leaves the fault apparently unchanged. Checking all four before touching drivers prevents a driver reinstall for a mute that was never a driver fault.

Driver faults usually follow a clear trigger, such as a Windows update, a maker driver update, or a new audio device. A speaker fault with no trigger points more at output selection or mute, while a fault that began the day after an update points at the driver. Matching the fault to its trigger saves time, because it tells you whether to roll back, update, or leave drivers alone.

The checks that matter most, in brief, are the first five steps of the sequence, and they deserve a second pass if the fault survives them.

Check volume and mute in two places
Select the correct output device
Test with a second app and a second file
Open the Volume mixer
Restart the laptop

Microsoft publishes Windows sound and troubleshooter guidance through its official support pages, and the Settings paths in this guide follow those pages. See Microsoft Support for the current sound troubleshooting steps for your Windows version.

Testing one change at a time is the habit that separates a quick repair from a long afternoon of guessing. Change a single setting, run the same test you ran at the start, and write down the result before you touch anything else. When a later step appears to work, that note tells you whether the improvement came from the latest change or from an earlier one that only needed time to take effect. Support teams ask for the same log, so the habit pays twice.

A short note made before you start will save time later, especially if the fault returns or if someone else has to finish the job. Record what changed just before the fault appeared, which tests you have already run, and what each test showed. A fault that began after an update, a new accessory, or a move points in a different direction from a fault that appeared out of nowhere, and that single detail often narrows the search more than any single setting.

Do not judge a fix by the first few seconds after you apply it. Some settings need a restart, some connections need a fresh pairing attempt, and some apps need a full close before a change takes effect. Run the same real world test you used at the start, such as opening the feature, making a test call, or playing a short clip, and give the result a full minute before you declare the step a failure and move on.

If the same fault has appeared before, look for the pattern rather than treating each occurrence as new. A fault that returns after every update, every long trip, or every period of heavy use usually has a trigger that the ordered steps can expose. Fixing the trigger, such as a worn cable, a full storage, or an app that hogs resources, prevents the next occurrence far better than repeating the same quick fix.

Keep the accessories you use for testing in a known good state. A spare cable, a charged spare remote battery, or a second pair of earbuds turns a vague suspicion into a clear answer in under a minute. When the fault follows the accessory to another device, the accessory is the problem. When the fault stays with the original device, the device or its settings deserve the attention.

Before any step that erases data or resets settings, confirm where your important content lives. Photos, messages, and documents that sync to a cloud account usually return after a reinstall, while local downloads and unsaved work may not. A quick backup takes a few minutes and turns a last resort step from a risk into a routine procedure.

When a fault may end in a warranty claim, preserve evidence as you go rather than reconstructing it later. Keep dated notes, keep the original accessory that failed, and avoid opening a sealed device, since an opened device can complicate a claim even when the fault is genuine. A repair centre that receives a clear timeline and untouched hardware can usually decide faster than one that receives only a description.

After any system or app update, retest the feature that previously failed, even if the update notes do not mention it. Updates change drivers, permissions, and background behaviour in ways that release notes rarely capture fully, and a fault that an update quietly fixed can return with the next update just as quietly. A two minute retest after each update turns that uncertainty into a known result.

A second device is the cheapest diagnostic tool you can own for this kind of fault, because it answers the device versus environment question in a single test. Borrow a second phone, headset, remote, or monitor for ten minutes, and run the same test on both. When the fault follows the accessory, replace the accessory. When it stays with the original device, focus the repair there and stop buying accessories.

Windows laptop speakers visual tied to the Details People Often Miss section of this guide

Mistakes That Make It Worse

The following errors do not cause the original fault, but they regularly turn a short repair into a long one, and they are worth naming before you start.

Reinstalling drivers before checking output selection, which replaces working software for a routing fault.
Testing only one app, which leaves an app mute disguised as a system fault.
Changing several audio settings at once, which makes it impossible to tell which change helped.
Downloading drivers from untrusted sites, which risks malware and wrong drivers for the model.
Ignoring the headphone comparison, which is the test that separates system faults from speaker faults.

Avoiding those errors keeps fix Windows laptop speakers not working short and calm, because every wasted reset or repeated test adds frustration without adding evidence, and a calm repair is a faster repair.

Windows laptop speakers visual tied to the Mistakes That Make It Worse section of this guide

When to Stop and Get Help

Book a service check when speakers stay silent after output selection, service restart, and driver reinstall, while headphones produce sound normally, or when the speakers crackle, distort, or cut out at all volumes. Take notes on output device, mixer state, and headphone results. Stop if the laptop shows other hardware faults alongside the speaker failure, such as a dead keyboard or a swollen battery.

Take your notes with you when you seek help, including which tests passed and which failed, and the exact conditions where the fault appears. Support moves faster with ruled out causes than with a repeated symptom description, and a clear log often leads to a faster repair or a correct replacement part on the first visit.

Windows laptop speakers visual tied to the When to Stop and Get Help section of this guide

How to Prevent a Repeat

Check the output device after connecting any new monitor, headset, or dock, and review the Volume mixer after installing a new media app. Keep audio drivers updated through Windows Update or the laptop maker site, and avoid third party driver tools. A short check of output, volume, and mixer state after each Windows update catches speaker faults early.

A ten minute monthly check of updates, storage, cables, and permissions catches most problems while they are still small, and it builds a baseline so a future change stands out immediately. Prevention is not extra work on top of the repair, it is the same discipline applied before the fault appears, and it pays for itself the first time it saves a repeat repair.

Windows laptop speakers visual tied to the How to Prevent a Repeat section of this guide

Checking Again After the First Round Clears Nothing

A second pass is not a repeat of the first pass, it is a different kind of test. The first pass rules out the common causes in order, while the second pass looks for a cause that was masked during the first, such as a second device interfering, a setting that reverted after a restart, or a fault that only appears under load. Work the second pass slowly, and change only one variable at a time, since a second pass done hastily produces the same confusion as the first pass done at random.

During the second pass, test under the exact conditions where the fault originally appeared, with the same app, the same accessory, and the same network or location. A fault that cannot be reproduced under test conditions has not necessarily been fixed, it may simply be waiting for its trigger. If the second pass still fails, the notes from both passes together give support a far stronger starting point than either pass alone, and they often reveal a pattern that a single pass hides.

Proving the Fix Before You Put the Tools Away

Return to the first step and confirm it properly before moving on, because a step that was rushed the first time often looks like a failure when it was really an incomplete test. Give it the full time it needs, watch for the result described in the main sequence, and only then move to the next step. This habit of retesting the early steps, rather than jumping to the later and more disruptive ones, saves most of the time that troubleshooting usually wastes.

The diagnosis table at the start deserves a second look once the main steps are done, because a cause that seemed unlikely at the start can become the leading explanation once the obvious ones are ruled out. Compare what you observed with the sign described for each row, and if your observation matches a row you dismissed earlier, work that row again with fresh attention. Diagnosis improves when the table is treated as a checklist to revisit, not as an introduction to skip.

Test again the next day under normal use, not just in the moment after the fix. Some faults return when the device warms up, when a background app updates, or when the original trigger recurs, and a next day test catches those returns while the repair is still fresh in your mind. If the fault returns, note exactly what changed since the fix, since that change is the most likely trigger.

Frequently Asked Questions

Why did this problem start suddenly?

The commonest trigger is a change just before the fault, such as an update, a new accessory, a move, or a period without use. Tracing that change usually points at the cause faster than testing parts at random. Note the last change first, then work through the ordered steps, because a fault with a clear trigger often has a short fix and a fault without one needs the full sequence. Retest the exact action that failed before, not an easier one.

How long should each fix take before I move on?

Give each simple step a proper test rather than a glance, because a restart, a cable swap, or a permission change needs a minute or two to show its result, while a reinstall or a restore needs longer. If a step shows no change after a fair test, move on and note the result, because the log of failed steps is what narrows the remaining causes for the steps that follow. Retest the exact action that failed before, not an easier one.

Will clearing data or resetting settings delete my content?

Clearing a cache removes temporary files only, while clearing data or storage signs you out and removes local settings, so check where your content lives before the stronger step. Content that syncs to a cloud account usually returns after a reinstall, while local downloads and unsaved work need a backup first. Never take a destructive step on a device that holds the only copy of something important. Retest the exact action that failed before, not an easier one.

What if the fault affects only one app, one device, or one connection?

That pattern is useful evidence, because a fault tied to one app points at that app and its permissions, while a fault that follows the device points at the device itself. The ordered guide for fix Windows laptop speakers not working helps separate those two cases before you change settings everywhere, and testing with a second app, a second device, or a second connection is the fastest way to draw that line. Retest the exact action that failed before, not an easier one.

When should I contact support instead of trying more fixes?

Contact support after the ordered steps fail, or immediately if you see danger signs such as heat, swelling, liquid damage, or a burning smell, and take your notes on what you tried. Support moves faster when you can list the causes you have ruled out, and continuing to guess after that point risks making a repairable fault worse or turning a warranty claim into a dispute. Retest the exact action that failed before, not an easier one.

How do I stop this happening again?

Keep updates current, keep comfortable free storage, check cables and permissions monthly, and note any change before a fault appears, because most repeats come from the same neglected basics. A ten minute monthly check is cheaper than another afternoon of troubleshooting, and it builds a baseline that makes future changes obvious before they become faults. Retest the exact action that failed before, not an easier one.

The Takeaway Worth Keeping

Work through fix Windows laptop speakers not working in order, stop at the step that works, and keep the notes on what you tried, because that discipline turns a frustrating fault into a short sequence of tests, and it also means the next fault starts from a known baseline instead of from scratch.

Start with the first step today, test one change at a time, and let the result of each test decide the next move, because a calm ordered approach beats a fast random one, and the time saved by not repeating failed steps is time you get back for the work itself.

Windows Laptop Speakers Not Working? Fixes in Order (Output, Driver, Services)