Why Won't My MacBook Connect to Wi-Fi? Common Causes and How to Fix Them
Few things are more frustrating than a MacBook that refuses to connect to Wi-Fi — especially when every other device on the same network works fine. The good news is that most Wi-Fi connection failures have identifiable causes, and many can be resolved without any specialist knowledge. The less straightforward news is that the right fix depends heavily on where the problem actually lives.
What's Actually Happening When a MacBook Can't Connect
When your MacBook fails to join a Wi-Fi network, it's usually a breakdown at one of several layers: the network adapter on the MacBook itself, the router or access point, the macOS software stack, or the network credentials and configuration stored on the device.
MacBooks use a Wi-Fi chip managed by macOS through a system called Network Framework. When you click a network name, macOS authenticates with the router using stored credentials, requests an IP address via DHCP, and establishes a working connection. A failure at any one of these steps produces the same symptom — no connection — but requires a different fix.
The Most Common Reasons a MacBook Won't Connect to Wi-Fi
1. The Router Is the Actual Problem
Before assuming your MacBook is at fault, check whether other devices — phones, tablets, other laptops — can connect to the same network. If they can't either, the issue is almost certainly the router or modem, not the MacBook. A simple router restart (unplug for 30 seconds, plug back in) resolves a surprisingly large number of connection failures.
2. Incorrect or Outdated Network Password
macOS stores Wi-Fi passwords in its Keychain — a secure credential store. If the router's password was recently changed, macOS may be attempting to reconnect with the old one silently failing. Go to System Settings → Wi-Fi, click the network name, choose Forget This Network, then reconnect and enter the current password manually.
3. IP Address Conflicts or DHCP Failures
Every device on a network needs a unique IP address. When a MacBook connects, it requests one from the router's DHCP server. If that request fails — due to a full DHCP pool, a glitchy router, or a corrupted network configuration on the Mac — the MacBook may show as connected but have no actual internet access, or refuse to connect at all.
You can attempt to renew the DHCP lease manually: go to System Settings → Wi-Fi → Details (next to your network) → TCP/IP → Renew DHCP Lease.
4. Corrupted Network Preferences or Plist Files
macOS stores network configuration in preference files. These can become corrupted after updates, crashes, or incomplete installations. Symptoms often include the Wi-Fi menu appearing greyed out, networks not showing up, or constant disconnections.
Removing and recreating the network service in System Settings → Network sometimes resolves this. In more persistent cases, deleting the relevant .plist files from /Library/Preferences/SystemConfiguration/ and restarting can clear corrupted state — though this resets all network configuration, so it's worth trying simpler steps first.
5. macOS Software Issues
Wi-Fi problems frequently appear after major macOS updates. Apple's network stack changes between versions, and occasionally a new release introduces driver-level bugs or conflicts with third-party security software like VPNs or firewalls. 🔧
Checking for supplemental updates in System Settings → General → Software Update is worth doing before deeper troubleshooting. Conversely, if problems started immediately after an update, rolling back or waiting for a patch release is sometimes the most practical path.
6. Wi-Fi Hardware: The Network Interface Card (NIC)
MacBooks contain a wireless NIC — in modern models, this is integrated into the logic board. Physical damage, manufacturing defects, or in rare cases heat-related failure can cause the adapter to stop functioning correctly. If Wi-Fi doesn't appear as an option at all in System Settings, or if the Wi-Fi: No hardware installed message appears, a hardware fault may be involved.
Running Apple Diagnostics (hold D during startup on Intel Macs, or hold the power button until options appear on Apple Silicon) can surface hardware-related error codes that point to Wi-Fi adapter issues.
7. Interference and Signal Environment
Connection problems aren't always about the Mac or the router — they're sometimes about the radio environment between them. Wi-Fi operates on 2.4 GHz and 5 GHz bands. The 2.4 GHz band has longer range but is shared with microwaves, Bluetooth, and neighbouring networks. The 5 GHz band is faster and less congested but doesn't penetrate walls as effectively.
If the MacBook connects but drops frequently, or struggles in specific locations, band congestion or signal strength may be the issue rather than any device fault.
Variables That Determine Which Fix Actually Works
| Factor | Why It Matters |
|---|---|
| macOS version | Network stack behavior varies; some bugs are version-specific |
| MacBook model/year | Older Wi-Fi chips have different capabilities and known issues |
| Router make and model | Some routers have compatibility quirks with Apple devices |
| Network security type | WPA2 vs WPA3 compatibility varies across macOS versions |
| Third-party software | VPNs, firewalls, and antivirus tools can intercept network traffic |
| Physical environment | Distance, walls, and interference affect wireless stability |
A Sensible Troubleshooting Order
- Restart the router and the MacBook
- Forget the network and reconnect with the correct password
- Renew the DHCP lease
- Disable VPN or firewall software temporarily to test
- Create a new Network Location in System Settings → Network
- Check for macOS updates (or review recent update history)
- Run Apple Diagnostics to rule out hardware 🖥️
Where Individual Situations Diverge
A MacBook that won't connect after a macOS Sonoma update on a WPA3-only router is a completely different problem from an older MacBook Air that drops connection sporadically near a busy apartment building's 2.4 GHz network. Both present as "won't connect to Wi-Fi" — but the causes, and therefore the fixes, have almost nothing in common.
The same is true when corporate network environments, captive portals (like hotel or café Wi-Fi), or managed device policies are involved — each introduces its own layer of variables. 📶
Understanding the layers where Wi-Fi connections can fail is the foundation — but the specific cause in any individual case depends on the exact combination of hardware, software version, network configuration, and environment involved.