You open your Mac Bluetooth menu to pair new headphones or a wireless mouse, only to watch the searching indicator spin endlessly while your nearby devices remain completely invisible.
In my over eight years of hands-on testing with Apple hardware—from vintage Intel MacBooks to the latest M-series Apple Silicon machines—Bluetooth glitches remain among the most frustrating issues users face. Few things interrupt your workflow faster than an inquiry screen that hangs indefinitely without discovering nearby accessories.
During my diagnostic sessions across various macOS releases, I found that an infinitely spinning Bluetooth status indicator rarely points to a dead wireless card. Instead, you are almost always dealing with a locked background daemon, a corrupted preference file, or signal contention between your Wi-Fi interface and Bluetooth radio.
When macOS scans for nearby Bluetooth Low Energy (BLE) or standard Bluetooth devices, it relies on a delicate background pipeline. If a single preference file gets corrupted or a background process deadlocks, the entire discovery system freezes in an active loop.
Let us walk through the exact bench-tested steps I use in my shop to break the infinite spinning loop and restore instant Bluetooth device discovery on your Mac.
Why Mac Bluetooth Device Scanning Hangs Indefinitely
The bluetooth Daemon Deadlock
At the heart of macOS wireless discovery sits a background system service called bluetooth. This process manages radio states, handles device handshakes, and populates the discovery list in your menu bar and System Settings.
When an accessory drops connection abruptly or sends malformed telemetry packets, bluetooth can lock up while waiting for a response that never arrives. The front-end user interface keeps showing a spinning wheel because it is still waiting for the back-end service to update its device table.
Apple Wireless Direct Link (AWDL) Channel Conflicts
Your Mac uses Apple Wireless Direct Link (AWDL) to power peer-to-peer features like AirDrop, AirPlay, and Handoff. AWDL shares the same 2.4 GHz frequency bands and internal antenna assembly as your Bluetooth module.
If AirDrop gets stuck probing for nearby devices over AWDL, it creates packet collisions on the wireless chip. This contention starves the Bluetooth scanner of radio time, causing the discovery wheel to spin forever.
Corrupted Preferences and Property List Files
Every time you toggle Bluetooth, connect a peripheral, or edit settings, macOS writes temporary metadata to property list (.plist) files. If your Mac experiences a unexpected shutdown or power drop during a write cycle, these files become corrupted.
When the system tries to scan for new hardware, it hits a unreadable cache entry and pauses the discovery cycle without throwing an explicit error message.
.jpg "Fix Mac Bluetooth Available Device Spinning Forever / Step-by-step macOS Bluetooth discovery lockup repair guide.")
Step 1: Force Restart the bluetooth Background Process
Instead of rebooting your whole system, you can force macOS to terminate the hung background daemon and launch a clean instance in seconds.
Press Command + Spacebar to open Spotlight Search, type Terminal, and press Return.
Type the following command exactly as shown:
sudo pkill bluetoothPress Return.
Type your Mac administrator password when prompted and press Return. (Note: Terminal will not display characters as you type your password).
Your Bluetooth connection will drop for two seconds while the system kills the unresponsive process. The operating system instantly resurrects bluetooth with a clean memory state, which often resolves the infinite loading wheel immediately.
Step 2: Delete Corrupted Bluetooth Property List Files
If killing the background process does not clear the spinning wheel, purging the system-level configuration files removes stale or damaged pairing logs.
Open Finder from your Dock.
Click Go in the top menu bar, select Go to Folder..., or press Command + Shift + G.
Paste this exact path into the text box:
/Library/Preferences/Press Return.
Locate the file named com.apple.Bluetooth.plist.
Drag com.apple.Bluetooth.plist to the Trash (or move it to your Desktop as a temporary backup).
Shut down your Mac completely, wait 20 seconds, and turn it back on.
Upon booting, macOS reads the missing configuration file and builds a fresh, uncorrupted com.apple.Bluetooth.plist file automatically.
Step 3: Clear User ByHost Bluetooth Cache Directory
In addition to the main system preference file, individual user accounts store cached device keys inside a hidden local directory.
Open Finder, press Command + Shift + G, and enter this path:
~/Library/Preferences/ByHost/Press Return.
Look for any files starting with com.apple.Bluetooth followed by a random string of numbers and letters (for example,
com.apple.Bluetooth.XXXXXXX.plist).Select these files and move them to the Trash.
Restart your Mac.
Clearing these user-specific cache files forces the operating system to rebuild local device registries from scratch.
Step 4: Disable AirDrop and Handoff to Reduce Radio Interference
If your Bluetooth radio is overwhelmed by peer-to-peer packet traffic, temporarily pausing AirDrop allows the discovery scanner to complete its initial sweep.
Open System Settings and select General from the sidebar.
Click AirDrop & Handoff.
Change AirDrop from Everyone or Contacts Only to No One.
Toggle the switch off for Allow Handoff between this Mac and your iCloud devices.
Open System Settings > Bluetooth and check if your available devices populate instantly.
Once your desired Bluetooth device pairs successfully, you can turn AirDrop and Handoff back on without disrupting the connection.
Step 5: Unplug USB 3.0 and Thunderbolt Accessories
Unshielded USB cables and hub enclosures emit radio frequency (RF) noise directly in the 2.4 GHz spectrum. This electronic noise blinds your Mac internal Bluetooth antenna, making nearby signals impossible to decode.
Disconnect all external hard drives, USB hubs, and display adapters from your Mac ports.
Move wireless accessories closer—within 2 to 3 feet of your Mac chassis.
Open the Bluetooth settings window and monitor the device list.
If the device list populates instantly after disconnecting your peripherals, poor cable shielding is flooding your wireless antenna with RF noise. To understand more about how hardware placement impacts wireless performance, check out the official
Step 6: Reset Hardware Controller State (Apple Silicon & Intel)
When internal state registers freeze at the controller level, a full hardware power cycle clears residual standby power from the wireless module.
For Apple Silicon Macs (M1, M2, M3, M4)
Click the Apple Menu and choose Shut Down.
Close your laptop lid or disconnect your desktop power cable.
Leave the Mac completely powered down for 2 full minutes to drain the logic board capacitors.
Turn on your Mac normally.
For Intel-Based Macs (SMC Reset)
Shut down your Intel Mac.
Press and hold Control + Option + Shift on the left side of your keyboard for 7 seconds.
While holding those keys, press and hold the Power Button for an additional 7 seconds.
Release all keys, wait 5 seconds, and power on your Mac.
Frequently Asked Questions (FAQs)
Why did the Shift + Option Bluetooth Debug menu disappear in newer macOS updates?
Apple removed the old graphic debug menu in recent macOS versions to streamline background system management. Today, clearing preference files and using sudo pkill bluetooth in Terminal performs the same reset routines that the hidden debug menu used to handle.
Will deleting com.apple.Bluetooth.plist unpair my connected devices?
Yes. Deleting the primary system preference file clears your saved Bluetooth pairing database. After removing the file and restarting, you will need to re-pair your wireless accessories like keyboards, mice, and audio gear.
Can physical distance cause the discovery wheel to spin forever?
Yes. If a device is at the edge of Bluetooth range or operating on low battery power, its broadcast signal may be too weak for your Mac to resolve its identifier name. This keeps the Mac discovery engine stuck in an incomplete handshake loop.