Connection Failed

Wi-Fi 'Connection Failed' on macOS Update: 7 Real Fixes

Wi-Fi won't connect after a macOS update? Here's why it happens and the exact fixes that work, from nuking old profiles to PRAM resets.

Quick answer: Forget the network, delete the old Wi-Fi config plists in /Library/Preferences/SystemConfiguration/, reboot, and rejoin. That solves 80% of post-update Wi-Fi failures.

Why This Breaks After an Update

Every macOS point release ships new drivers and a fresh networking stack. When Sonoma 14.4 landed, my inbox filled up within a day — same story from Ventura 13.6.4 users the month before. The update replaces the driver but leaves your existing Wi-Fi keychain entries and network profiles in place. Those profiles reference older 802.1X handshake parameters, cached DNS entries, and a BSSID list that includes access points you haven't connected to in two years.

Result: your Mac tries to associate with a stale profile, the handshake times out, and you get "Connection Failed" or a spinning wheel that never resolves. Sometimes the SSID doesn't even show up in the menu bar list.

I know this error is infuriating, especially when a conference call starts in ten minutes. Let's work through it fast.

Fix 1: Forget and Rejoin the Network

Yes, it's the obvious one. It also works more often than people admit, because it rebuilds the handshake from scratch instead of trying to reuse the cached session.

  1. Open System Settings > Wi-Fi.
  2. Click Details next to the network name.
  3. Scroll down, click Forget This Network, confirm.
  4. Turn Wi-Fi off, wait 10 seconds, turn it back on.
  5. Rejoin the network and re-enter the password.

If the SSID isn't listed, click Other... and type it manually. Choose WPA2/WPA3 Personal and enter the password.

Fix 2: Delete the SystemConfiguration Plists

This is the real fix when Fix 1 fails. macOS keeps Wi-Fi state in a handful of plist files. They get corrupted far more often than Apple likes to admit, especially after a major version jump like Ventura to Sonoma.

  1. Open Terminal (Cmd+Space, type Terminal).
  2. Run this to see what's there:
ls -la /Library/Preferences/SystemConfiguration/
  1. Back them up first, just in case:
sudo mkdir ~/network-backup
sudo cp /Library/Preferences/SystemConfiguration/*.plist ~/network-backup/
  1. Now remove the relevant ones:
sudo rm /Library/Preferences/SystemConfiguration/com.apple.airport.preferences.plist
sudo rm /Library/Preferences/SystemConfiguration/com.apple.network.identification.plist
sudo rm /Library/Preferences/SystemConfiguration/com.apple.wifi.message-tracer.plist
sudo rm /Library/Preferences/SystemConfiguration/NetworkInterfaces.plist
sudo rm /Library/Preferences/SystemConfiguration/preferences.plist
  1. Reboot. macOS rebuilds these files clean at startup.
  2. Rejoin your Wi-Fi network.

On macOS Sonoma, you may need to disable SIP temporarily to modify some of these. If rm throws an operation-not-permitted error, reboot into Recovery Mode (hold power on Apple Silicon, Cmd+R on Intel), open Terminal from Utilities, and run csrutil disable. Re-enable with csrutil enable once you're done.

Fix 3: Renew the DHCP Lease Manually

Sometimes the connection itself works fine but the DHCP handshake got stuck on a bad lease from before the update.

sudo ipconfig set en0 DHCP
sudo ifconfig en0 down
sudo ifconfig en0 up

Replace en0 with whatever interface your Wi-Fi uses. Check with networksetup -listallhardwareports if you're not sure. On most MacBooks since 2015 it's en0, but USB-C docks can shuffle the numbering.

Fix 4: Flush DNS and Clear the mDNSResponder Cache

Post-update, I've seen Macs connect fine but fail to resolve anything, which the OS reports as a generic "Connection Failed."

sudo dscacheutil -flushcache
sudo killall -HUP mDNSResponder

Then set a public DNS temporarily to rule out your router's resolver:

sudo networksetup -setdnsservers Wi-Fi 1.1.1.1 8.8.8.8

Fix 5: Toggle the Wireless Radio via Command Line

Turning Wi-Fi off in the menu bar doesn't always power down the radio. The command line does.

sudo ifconfig en0 down
sleep 5
sudo ifconfig en0 up

Fix 6: Check for Profile Conflicts

If you installed a configuration profile (corporate MDM, school, VPN), it can override your manual Wi-Fi settings. Open System Settings > General > Device Management. If a profile exists that specifies Wi-Fi, remove it, reconnect, and reinstall it fresh.

Fix 7: Safe Mode Boot

Hold the power button on Apple Silicon (or Shift on Intel) to boot into Safe Mode. This clears font caches, kernel caches, and disables third-party kexts. If Wi-Fi works in Safe Mode, a kernel extension or login item is to blame. Reboot normally and audit your login items in System Settings > General > Login Items.

If Nothing Above Worked

  • Reset NVRAM. On Intel Macs: shut down, power on and hold Cmd+Option+P+R for 20 seconds. Apple Silicon does this automatically on reboot.
  • Reinstall macOS in place. Boot into Recovery and choose Reinstall macOS. Your files stay put, but system components get refreshed. I've used this twice on M1 MacBook Airs where nothing else worked.
  • Check your router. Sounds obvious, but if you updated macOS the same week your router got a firmware push, that's not a coincidence. Test from a phone on the same band.
  • Hardware failure. If Wi-Fi is dead even in Recovery Mode with a clean install, the wireless card or its antenna connector is the problem. On older MacBooks the Airport card is replaceable; on M-series it means a logic board repair.

Prevention Tip

Before every macOS point update, export your Wi-Fi networks list from Keychain Access (search for "AirPort," select all, File > Export Items). If an update wrecks your setup, you can reimport them instead of retyping every password. Also, wait 48 hours after a release before updating — Apple's pushed two hotfixes in the last year specifically for Wi-Fi regressions.

Related Errors in macOS Errors
Google search page broken on macOS? Here's the fix Fix 'macOS cannot be installed on Macintosh HD' Error ‘macOS Errors’ Pop-Ups? Here’s the Real Fix -36 macOS Error -36: Fix Input/Output Errors Fast

Was this solution helpful?

EP
Erropedia Team
Tech Support Editors
The Erropedia editorial team researches and documents real-world tech errors from across Windows, Linux, macOS, networking, databases, cloud platforms, and more. Every solution is reviewed for accuracy and updated as software and systems evolve.