Most Windows Bluetooth faults come down to a service that stopped, a driver that updated badly, or a device that paired halfway and now refuses to finish the job. The symptom is always the same, a device that will not connect, but the cause hides in a different layer each time. This guide shows how to fix Windows bluetooth not working by checking those layers from the outside in, starting with the service that must be running before any driver or pairing step can possibly succeed.
Bluetooth on Windows is a stack, and a stack fails at its weakest layer. The service layer, the driver layer, and the pairing layer each leave their own evidence, and the order of the checks matters, because fixing the pairing while the service is stopped changes nothing and teaches you nothing. Working from the bottom up keeps every test meaningful.
Reading the Symptom Before You Change Anything
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 bluetooth 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 |
|---|---|---|
| Bluetooth off or airplane mode | No Bluetooth toggle at all | Check Settings and airplane mode |
| Bluetooth Support Service stopped | Devices will not appear | Restart the service and set Automatic |
| Driver fault | Adapter missing after an update | Update or reinstall the driver |
| Device not in pairing mode | One device never appears | Put the device in pairing mode |
| Interference or range | Pairing drops or stutters | Move closer and remove obstacles |
| Hardware fault | Adapter missing after all 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 Remove the Device
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 bluetooth 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.
How to fix Windows bluetooth not working in the Right Order
Working through fix Windows bluetooth 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 the Bluetooth toggle and airplane mode.** Open Settings, Bluetooth and devices, and confirm Bluetooth is on, then check that airplane mode is off. Airplane mode disables Bluetooth on many laptops, and a quick settings toggle can leave Bluetooth off without any warning. Toggle Bluetooth off and on again once, then check whether devices appear. 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, since a restart reloads the Bluetooth stack and clears a stuck adapter state. Test Bluetooth immediately after restart, before connecting other wireless devices, so the first result reflects a clean state rather than a crowded radio environment. If this step restores normal behaviour, stop here and note what worked, because continuing past a working fix only adds risk.
- **Run the Bluetooth troubleshooter.** Open Settings, System, Troubleshoot, Other troubleshooters, and run the Bluetooth troubleshooter, following its prompts. The troubleshooter checks adapter state, service state, and driver problems in one pass. Note what it reports, even when it claims no fault, since that narrows the remaining causes. If this step restores normal behaviour, stop here and note what worked, because continuing past a working fix only adds risk.
- **Restart the Bluetooth Support Service.** Press Windows and R, type services.msc, and press Enter. Find Bluetooth Support Service, right click it, and choose Restart, then open Properties and set Startup type to Automatic. A stopped service leaves Bluetooth present but unable to discover or connect, 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.
- **Check Device Manager for the adapter.** Open Device Manager and expand Bluetooth, checking whether an adapter is listed and whether any entry shows a warning symbol. A missing adapter points at a driver or hardware fault, while a listed adapter with a warning points at a driver conflict. Note the adapter name, since a maker driver search needs the exact model. If this step restores normal behaviour, stop here and note what worked, because continuing past a working fix only adds risk.
- **Update the Bluetooth driver.** In Device Manager, right click the Bluetooth adapter and choose Update driver, then Search automatically. If Windows finds nothing, check the laptop or adapter maker support site for a driver for your exact model. Install, restart, and test pairing before changing other settings. At this stage of fix Windows bluetooth 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.
- **Uninstall and reinstall the driver.** In Device Manager, right click the adapter and choose Uninstall device, then restart and let Windows reinstall it. If a driver update caused the fault, use Roll Back Driver on the Driver tab instead, where available. Test after the reinstall before installing a maker driver, so you know which driver state works. If this step restores normal behaviour, stop here and note what worked, because continuing past a working fix only adds risk.
- **Remove the device and pair again.** Open Settings, Bluetooth and devices, Devices, and remove the problem device, then put the device into pairing mode and add it again. A stale pairing entry can block a fresh connection even when both sides look ready. Pair close to the laptop, with the device fully charged, and watch for a pairing code prompt. 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 Bluetooth device.** Try a second headset, mouse, or speaker. If the second device pairs and works, the fault sits in the first device, while failure with every device points at the laptop. This test prevents a driver reinstall for a single device fault, and it also proves whether the laptop radio works at all. If this step restores normal behaviour, stop here and note what worked, because continuing past a working fix only adds risk.
- **Check for interference and range.** Move the device within a metre of the laptop, away from USB 3 hubs, microwaves, and crowded wireless environments, and test again. Bluetooth shares radio spectrum with Wi-Fi and USB 3 devices, and interference can block discovery or drop a connection that works fine at close range. A fault that vanishes at close range is an environment fault. If this step restores normal behaviour, stop here and note what worked, because continuing past a working fix only adds risk.
- **Check Windows Update and BIOS updates.** Open Settings, Windows Update, and install any available update, then check the laptop maker site for a BIOS or chipset update if Bluetooth failed after a major Windows update. Chipset and BIOS updates can restore an adapter that a Windows update left unrecognised. Install one update at a time and test after each. 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 missing adapter.** Stop when Device Manager shows no Bluetooth adapter after a driver reinstall, a service restart, and a Windows update, or when Bluetooth fails on every device after all steps. Further driver changes cannot repair a failed radio or a loose internal connection. Take your notes on adapter state and service state 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.
The Checks Most Guides Skip
Bluetooth faults split into two families that need different repairs, and the Device Manager view separates them. A missing adapter is a driver or hardware problem, while a present adapter that cannot pair is a service, pairing, or device problem. Owners who skip that check often reinstall drivers for a pairing fault, or re-pair devices endlessly for a missing adapter. This distinction shapes how you should approach fix Windows bluetooth not working.
Pairing entries go stale in ways that look like hardware failure. A device that paired months ago can hold an old key that no longer matches, and Windows can hold a matching stale entry on its side. Removing the device on both sides and pairing fresh clears both entries at once, which is why a clean re-pair belongs in the sequence rather than at the end.
Interference is easy to dismiss and hard to prove without a close range test. A headset that stutters across a room but works beside the laptop is not faulty, it is fighting a crowded radio environment. Moving closer for the test costs nothing and prevents a replacement for an environment fault.
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 the Bluetooth toggle and airplane mode
- Restart the laptop
- Run the Bluetooth troubleshooter
- Restart the Bluetooth Support Service
- Check Device Manager for the adapter
Microsoft publishes Windows Bluetooth troubleshooting guidance through its official support pages, and the Settings paths in this guide follow those pages. See Microsoft Support for the current Bluetooth 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.
Monitor the fix for a full week of normal use before declaring it permanent, since some faults return only under specific conditions such as heat, low battery, weak signal, or heavy load. Keep the log going through that week, noting any recurrence and its conditions, because a recurrence pattern is itself diagnostic evidence. A fix that survives a normal week has earned your confidence, while a fix that fails in that week still has a fresh trail to follow.
Ways People Accidentally Prolong This Fault
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 the service and the toggle, which replaces working software for a settings fault.
- Pairing repeatedly without removing the stale entry, which repeats the same failed handshake.
- Testing only one Bluetooth device, which leaves a device fault disguised as a laptop fault.
- Downloading drivers from untrusted sites, which risks malware and wrong drivers for the model.
- Ignoring airplane mode, which disables Bluetooth silently on many laptops.
Avoiding those errors keeps fix Windows bluetooth 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.
Signs That Point to a Repair
Book a service check when Device Manager shows no Bluetooth adapter after a driver reinstall and a Windows update, or when every device fails to pair after a service restart and a clean re-pair. Take notes on adapter presence, service state, and the second device test. Stop if Bluetooth failure appears alongside other hardware faults, such as dead Wi-Fi or USB ports, since that pattern points at internal hardware.
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.
Keeping This Fault From Coming Back
Keep Windows and drivers updated through Windows Update or the laptop maker site, remove old Bluetooth pairings you no longer use, and check the Bluetooth toggle after any major update. Pair new devices close to the laptop first, then move to normal range. A short check of adapter presence and service state after each major update catches Bluetooth 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.
More Reading on Stratilyze
More Reading on Stratilyze. If this guide helped, the related guides on this site cover the neighbouring faults that often appear alongside this one, including Fix Bluetooth Not Turning On Phone, Fix Bluetooth Earbuds Keeps Disconnecting and Fix Bluetooth Speaker Not Connecting Laptop. Reading the closest match first usually saves a second round of troubleshooting, because a fault in one feature often shares a cause with a fault in another. Keep this guide open while you check the related one, and compare the symptom tables before changing any setting, since the right fix depends on matching your exact symptom rather than the closest headline.
The Longer Route When Short Fixes Fail
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.
The Closing Checks That Catch a Partial Fix
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 bluetooth 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.
Finishing With a Working Setup
Work through fix Windows bluetooth 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.
