How to Fix Mac Wi-Fi Dropping After Sleep on macOS Tahoe (2026 Guide)

Why Does Mac Wi-Fi Drop After Sleep? (The Real Cause in 2026)

If your Mac reconnects to Wi-Fi just fine most of the time but loses its connection every time it wakes from sleep, you are not imagining things — and the problem is not your router. On macOS Tahoe, Apple redesigned the Power Nap subsystem to allow deeper sleep states on Apple Silicon Macs. A side effect is that the Wi-Fi interface (en0) can enter a fully suspended state during sleep. When the lid opens or the machine wakes, macOS sometimes fails to bring en0 back online cleanly, leaving the system in an odd limbo: the menu bar shows Wi-Fi as connected, but no packets flow.

Three specific macOS Tahoe changes make this worse than previous releases:

• Deeper sleep (S0ix / Low-Power Mode): Apple Silicon Macs in macOS Tahoe use CPU idle states that park the Wi-Fi co-processor more aggressively than before.
• Rotating Private Wi-Fi Addresses: When the MAC address rotates at wake, some routers reject the re-association until a new DHCP lease is negotiated — a process macOS does not always trigger automatically.
• iCloud Private Relay and Limit IP Address Tracking: These privacy features add an extra network handshake layer at wake, and if the iCloud handshake times out, the whole interface stalls.

Understanding the root cause means you can target the right fix instead of running through a generic checklist. The fixes below go from quickest to most thorough.

Quick Checklist Before You Start Troubleshooting

• macOS version: Apple menu > About This Mac. Note the exact Tahoe build number.
• Affected network: does the drop happen on all Wi-Fi networks or only one SSID?
• Consistent or intermittent: does it fail after every wake, or only after longer sleeps?
• Other devices on the same network: are they also dropping, or only your Mac?

If the drop happens only on one network, jump to Fix 3 (Private Wi-Fi Address) and Fix 4 (IP Tracking). If it happens on every network, start with Fix 1.

Fix 1: Disable Wake for Network Access Power Nap Setting

Power Nap lets your Mac accept incoming network requests while asleep — useful for file sharing and remote login, but it can confuse the Wi-Fi driver at wake when the interface was half-active the whole time.

1. Open System Settings > Battery (MacBook) or Energy Saver (desktop).
2. Click Options.
3. Set Wake for network access to Never.
4. If you see a separate Enable Power Nap toggle, turn it off.

Restart your Mac after making this change, then let it sleep for a few minutes and wake it. Many users report this single change eliminates the drop entirely on MacBook Air M2, M3, and M4 models.

Fix 2: Renew DHCP Lease and Flush DNS Cache After Wake

When your Mac wakes and fails to get a valid IP address, the Wi-Fi connection appears active in the menu bar but nothing loads. Forcing a fresh DHCP lease resolves this immediately.

GUI method (no Terminal required)

1. Go to System Settings > Network > Wi-Fi.
2. Click Details next to your connected network.
3. Select the TCP/IP tab.
4. Click Renew DHCP Lease.

Terminal method

Open Terminal (Applications > Utilities > Terminal) and run:

sudo ipconfig set en0 DHCP
sudo dscacheutil -flushcache
sudo killall -HUP mDNSResponder

The first command forces a fresh DHCP negotiation. The next two commands flush the DNS resolver cache and restart the mDNS daemon, clearing stale name-resolution entries from before sleep.

Fix 3: Set Private Wi-Fi Address to Fixed (Not Rotating)

macOS Tahoe defaults to Rotating private Wi-Fi addresses on networks with weak security. Every time the MAC address rotates — which can happen at wake — your router sees a new device and may not immediately assign an IP. Switching to Fixed keeps the same private MAC address for that network.

1. Open System Settings > Network > Wi-Fi.
2. Click Details next to your network name.
3. Under Private Wi-Fi Address, change Rotating to Fixed.
4. Click OK and reconnect.

This is especially effective if the sleep/wake drops happen only on your home or office network but not on others.

Fix 4: Disable Limit IP Address Tracking and iCloud Private Relay

Two iCloud privacy features can stall the post-wake reconnection sequence:

• Limit IP Address Tracking — routes traffic through Apple relay servers and adds latency at wake when the relay handshake must be re-established.
• iCloud Private Relay — encrypts DNS queries via a second-hop relay; if that relay is slow at the moment your Mac wakes, DNS times out and the connection appears broken.

To disable per-network IP tracking: go to System Settings > Network > Wi-Fi > Details, then turn off Limit IP Address Tracking.

To disable iCloud Private Relay: go to System Settings > your Apple Account > iCloud > Private Relay and toggle it off.

If this resolves the issue, you can re-enable Private Relay and only leave Limit IP Address Tracking off on your primary network.

Fix 5: Reset the Wi-Fi Interface via Terminal (ifconfig Restart)

This is the fastest fix for an already-broken connection — useful if you are sitting at your Mac right now with no Wi-Fi after a wake. It manually cycles the en0 interface the way macOS should do automatically:

sudo ifconfig en0 down
sleep 5
sudo ifconfig en0 up

For a more thorough reset that also flushes ARP and routing tables:

sudo ifconfig en0 down
sudo route flush
sudo ifconfig en0 up
sudo dscacheutil -flushcache
sudo killall -HUP mDNSResponder

You will be prompted for your administrator password. Wi-Fi will disappear for a few seconds and return. This does not persist across reboots, but if it reliably fixes the drop each time, it confirms the interface-suspension root cause and points you toward fixes 1 through 4 for a permanent solution.

Fix 6: Delete Stale Wi-Fi Preferences and Keychain Entries

macOS stores Wi-Fi configuration in property list files. Over time — especially after a major version upgrade to Tahoe — these files can contain conflicting entries that cause unpredictable reconnection failures.

Delete Wi-Fi preference files

sudo rm /Library/Preferences/SystemConfiguration/com.apple.wifi.plist
sudo rm /Library/Preferences/SystemConfiguration/com.apple.network.identification.plist
sudo rm /Library/Preferences/SystemConfiguration/NetworkInterfaces.plist
sudo rm /Library/Preferences/SystemConfiguration/preferences.plist

Restart your Mac after running these commands. macOS will recreate them with clean defaults.

Remove stale Keychain Wi-Fi passwords

1. Open Keychain Access (search in Spotlight).
2. In the search box, type your Wi-Fi network name.
3. Delete the entry, then reconnect to the network and re-enter your password.

This is particularly effective if the Mac sometimes connects at wake on the second or third attempt — a sign it is finding and discarding stale credentials before succeeding.

Fix 7: Update to the Latest macOS Tahoe Point Release

Apple has acknowledged Wi-Fi stability regressions in early Tahoe releases and has shipped targeted fixes in point updates. Always ensure you are on the latest build before assuming a hardware problem.

1. Go to Apple menu > System Settings > General > Software Update.
2. Install any pending macOS Tahoe updates.
3. On Intel Macs, reset NVRAM after updating: shut down, hold Shift+Control+Option+Power for 10 seconds, release, then power on. (Not needed on Apple Silicon.)

Point releases such as macOS Tahoe 26.1 and 26.2 have each included Wi-Fi driver patches. Staying current is the lowest-effort long-term fix.

When to Contact Apple Support or Get Expert Help

If you have worked through all seven fixes and the Wi-Fi still drops after every sleep cycle, the issue may be hardware-related — specifically the Wi-Fi/Bluetooth combo chip or the antenna cable on MacBooks. Signs that point to hardware:

• Wi-Fi signal strength is consistently low even when the Mac is next to the router.
• Bluetooth also drops at the same moment as Wi-Fi (they share the same chip).
• The Mac shows no en0 interface after wake: run ifconfig | grep en0 — if no output appears, the interface is not being registered by the OS.
• Apple Diagnostics (hold D at startup) reports a Wi-Fi hardware failure code (WFH).

At that point, book an appointment at an Apple Authorised Service Provider or reach out for professional desktop support. Our certified macOS technicians can remotely diagnose the exact failure mode, guide you through advanced diagnostic commands, and advise whether a component repair is warranted — same day, no appointment queue.

Frequently Asked Questions

Q: Why does my Mac show Wi-Fi connected after waking but pages still will not load?

A: This is the classic symptom of a stale IP address or a suspended en0 interface. The Wi-Fi association survives sleep but the IP lease expires. Run sudo ipconfig set en0 DHCP in Terminal or use Renew DHCP Lease in Network settings to get a fresh address immediately.

Q: Does the ifconfig en0 down/up command work on Apple Silicon Macs?

A: Yes. The command works on M1, M2, M3, and M4 MacBooks and Mac minis running macOS Tahoe. The interface name remains en0 for the built-in Wi-Fi adapter on all Apple Silicon models. You will need to enter your sudo password.

Q: Will disabling Power Nap affect Time Machine backups or Find My Mac?

A: Time Machine will still back up whenever the Mac is awake and connected. Disabling Wake for Network Access only prevents the Mac from waking itself in response to an incoming network request. Find My Mac continues to work via the Bluetooth Low Energy beacon, which operates independently of the Wi-Fi interface.

Q: I deleted the Wi-Fi preference files but my saved networks are gone. How do I get them back?

A: Deleting the preference files removes the list of known networks. You will need to rejoin each network manually and re-enter its password. The passwords stored in iCloud Keychain may be offered automatically when you rejoin. There is no recovery for locally-stored network lists once the plist is deleted.

Q: How do I know if my Mac Wi-Fi problem is hardware and not software?

A: Run ifconfig | grep en0 in Terminal immediately after a failed wake. If there is no en0 listed, the OS is not detecting the Wi-Fi hardware — that points to a hardware fault. Also boot into Apple Diagnostics by holding D at startup; a WFH error code confirms a hardware-level failure that software fixes will not resolve.