When this error shows up
You're working on a Dell Latitude or HP EliteBook running Windows 10 22H2 or Windows 11 23H2. Everything's fine for 10-15 minutes, then the Wi-Fi icon turns into a globe with a red X. It reconnects after 30 seconds, but keeps happening. Or you close the laptop lid, open it an hour later, and it won't connect until you restart the adapter. The culprit here is almost always power management or a bad driver.
Root cause in plain English
Windows is too aggressive with power saving. By default, your Wi-Fi adapter is told to go into low-power mode the second it thinks you're not using it. That's fine for battery life, but it breaks the connection when the adapter wakes up and forgets how to talk to your router. Another common cause: Intel and Realtek drivers from 2020-2022 have a bug where they don't handle access point handoffs properly. If you have a mesh network or multiple APs, the adapter gets confused and drops.
Fix it in 4 steps
Step 1: Kill power saving on the adapter
This is the single most effective fix. I've done this on hundreds of machines. Here's how:
- Right-click the Start button and select Device Manager.
- Expand Network adapters.
- Find your Wi-Fi adapter — usually something like
Intel(R) Wi-Fi 6 AX201 160MHzorRealtek RTL8822CE. - Right-click it, choose Properties.
- Go to the Power Management tab.
- Uncheck "Allow the computer to turn off this device to save power."
- Click OK.
Do this for your Ethernet adapter too if you use it. Both are guilty.
Step 2: Update or roll back the driver
Don't bother with Windows Update drivers — they're often months old. Go straight to the manufacturer:
- Intel: Download the latest driver from Intel Driver & Support Assistant.
- Realtek: Get it from your laptop vendor's support page. Realtek's own site is a mess.
If you're already on the latest driver and the problem started after an update, roll it back. In Device Manager, right-click the adapter > Properties > Driver tab > Roll Back Driver. This happens a lot with Intel's 22.150.0 driver — it had a known memory leak that crashed the connection after an hour.
Step 3: Disable Bluetooth (yes, really)
On many laptops, the Wi-Fi and Bluetooth share the same physical chip (Intel's CNVi or Realtek's combo). They interfere with each other. If you don't need Bluetooth, turn it off in Device Manager or via the physical switch (Fn key). I've seen this fix Wi-Fi drops on Dell XPS 13 and Lenovo ThinkPad X1 Carbon models.
Step 4: Reset the network stack
If power saving and drivers didn't fix it, the network stack itself is corrupted. Open an admin Command Prompt (cmd as administrator) and run these commands one at a time:
netsh winsock reset
netsh int ip reset
ipconfig /release
ipconfig /renew
ipconfig /flushdns
Then restart the machine. This clears any stale DHCP leases and corrupt socket entries. You'll lose any static IP settings, so note those down first.
Still failing? Check these three things
1. Your router is the problem
Log into your router and turn off "Band Steering" or "Smart Connect." This feature forces the router to bounce your device between 2.4GHz and 5GHz based on signal strength. Most Windows adapters hate this. Set them to separate SSIDs (e.g., Home_2.4 and Home_5) and connect to the 5GHz one only.
2. Channel congestion
Use a Wi-Fi analyzer app on your phone. If you see 10+ networks on the same channel, your adapter is fighting for airtime. Change your router's channel to 1, 6, or 11 (for 2.4GHz). For 5GHz, use channel 36 or 149 — both are less crowded.
3. IPv6 issue
Some ISPs have broken IPv6 implementations. Disable it on your adapter: Network Connections > right-click Wi-Fi > Properties > uncheck Internet Protocol Version 6 (TCP/IPv6). I've seen this fix persistent drops on Comcast and BT Home Hub routers.
If none of that works, you've got a hardware issue — a failing Wi-Fi card or a loose antenna cable inside the laptop. At that point, replace the card (costs about $20) or take it to a repair shop. Don't waste time with software fixes on a dying adapter.