Start your 3-day free trial
Sign up to experience all premium features at no cost.
*Available only to new users. Each user is limited to one trial.


Wi-Fi dropping while a laptop sleeps is usually expected, because the system can power down the wireless adapter to save energy; the real problem is when Wi-Fi keeps disconnecting after sleep and does not come back cleanly on wake. The useful clue is that transition: the laptop worked before sleep and the problem appeared after wake. The Wi-Fi control may have disappeared, the computer may have left the network, the local link may still exist without internet access, or only one application may be stale.
Use one controlled sleep-and-wake cycle before changing settings. Note the exact network name, whether the laptop was on battery or connected to power, whether a dock or Ethernet adapter was attached, and what the Wi-Fi status showed immediately after wake. Save work first; repeated sleep cycles can interrupt downloads, calls, or unsaved browser sessions.
Key Takeaways
- Separate a missing Wi-Fi control, a disconnected network, a connected-without-internet state, and an app-only failure.
- Compare another device on the same network and the same laptop on another network before resetting anything.
- Toggle Wi-Fi or Airplane Mode and reconnect normally before forgetting the network.
- Use the platform branch that matches the observed state; do not apply every power or driver change at once.
- Keep network reset, driver removal, and broad power-policy changes for the end because they remove settings or hide the evidence.
The device and app troubleshooting guide explains the wider device-versus-network comparison. This guide stays focused on the sleep-to-wake boundary.
Sleep keeps your session in memory while cutting power to most hardware, and the Wi-Fi adapter is one of the devices Windows can switch off. The adapter's Power Management tab in Device Manager can show Allow the computer to turn off this device to save power, and Microsoft lists clearing that box as a step when Wi-Fi keeps dropping.[1] A lost connection while the lid is closed is therefore not a fault on its own.
It becomes a fault when the adapter, the saved network, or internet access does not return shortly after wake, or when the connection drops again while the laptop is awake. That is the case the rest of this guide diagnoses, one wake cycle and one variable at a time.
Wake the laptop once and wait long enough for the desktop, clock, and network indicator to settle. Then record which of these states you actually have:
| Observed state | First question |
|---|---|
| Wi-Fi control or adapter is missing | Did the wireless hardware or driver resume at all? |
| Wi-Fi is on, but the saved network is disconnected | Is the network visible, and can you reconnect normally? |
| Network says connected, but there is no internet | Do other apps, websites, and devices have upstream access? |
| One app fails while a simple website works | Is the app session or service stale rather than Wi-Fi? |
| Connection returns and drops again | Does it happen only on battery, through a dock, or on one network? |
Do not call every state “Wi-Fi disconnected.” A missing adapter needs a different path from an app that failed to refresh. If the network name is absent from the available list, use the Wi-Fi network not showing up guide. If Windows or macOS remains joined but cannot reach the internet, use the linked platform guide after completing the comparison below.
Repeat the sleep-and-wake cycle only once if you need confirmation. Change one condition, such as disconnecting the dock or connecting the charger, and record the result. Several uncontrolled repetitions make it difficult to tell whether the change, elapsed time, or the router restored the connection.
Run a small comparison matrix while the failure is present:
Microsoft recommends trying the same Wi-Fi network on another device; if that device connects, the affected computer becomes the more likely source.[1] Apple similarly includes a different network as a useful comparison before escalating to the internet provider or administrator.[2]
Interpret the results narrowly. If every device loses internet, investigate the router, access point, captive portal, or provider. If the laptop fails on every network only after waking, focus on its resume path. If it fails only on one SSID, keep the router's band, authentication, address assignment, and enterprise policy in scope. If only a docked wake fails, the dock, Ethernet preference, display link, or power transition may be involved.
On a managed work or school laptop, record whether the network uses certificates, a login portal, device management, or an organization profile. Do not remove those settings. A policy may intentionally control Wi-Fi, sleep, or network access, and the administrator needs the comparison evidence.
Start with reversible actions. Open the operating system's network control and turn Wi-Fi off, wait briefly, then turn it on. If that does not restore the adapter or network list, turn Airplane Mode on and back off. Ubuntu's official wake-without-wireless guide recommends this order and then a restart if the radio still does not recover.[3]
Select the known network and reconnect normally. Confirm that the network name is the expected one; do not join a similarly named public network. If the device reports connected, open a simple site and a second app. If only the original app fails, close and reopen that app or refresh its session instead of changing network configuration.
Restart the laptop once after saving work if the control remains missing or the session remains stale. Do not begin by rebooting the router when other devices are working, because that interrupts everyone and removes a useful comparison. Restart the router only when multiple devices show the same fault or the network owner has evidence that the access point is stuck.
Do not disable the firewall or security software as a generic test. Do not permanently disable all sleep or power saving to make the symptom disappear. Those changes enlarge the security or battery cost and do not identify which resume component failed.
Open Network & internet settings and confirm Wi-Fi exists, is on, and shows the expected status. If the basic toggle and reconnect did not work, run the Network troubleshooter in the Get Help app on Windows 11. Microsoft places forgetting the network, adapter-driver work, and network reset after simpler checks; network reset removes adapters and returns their settings to defaults.[1]
If the adapter disappears or repeatedly fails after wake, install normal Windows updates and the laptop manufacturer's approved wireless or chipset update for the exact model. Do not use a random driver-download utility. If you consider removing the adapter driver, first obtain the official installer and another way to access it, because the computer may not reconnect automatically.
Microsoft's Wi-Fi troubleshooting includes clearing Allow the computer to turn off this device to save power on the Wi-Fi adapter's Power Management tab in Device Manager.[1] Treat it as a narrow diagnostic variable, not a permanent blanket change. Record the original value, change only the Wi-Fi adapter, test one sleep-and-wake cycle, and restore it if the result does not change. If you also adjust the wireless adapter's power saving mode, change only that adapter setting rather than switching every power plan to maximum performance permanently.
Confirm that the Mac rejoined the expected network. Restarting macOS can renew the address assigned when joining Wi-Fi, and Apple recommends checking date and time, updating macOS from a working network, using Wi-Fi Recommendations or Wireless Diagnostics, and comparing another network.[2]
If the Mac is connected but has no internet, follow the Mac connected-without-internet guide. Do not delete network preference files or remove organization profiles as an early step. Save any Wireless Diagnostics report and the time of the failed wake for support.
Open the Wi-Fi panel, switch Wi-Fi off and on, then toggle Airplane Mode if needed. If the connection still does not return, restart and use a wired connection, if available, to install official system updates. Ubuntu notes that some wireless drivers do not fully support particular power-saving features, which can prevent the radio from turning on correctly after resume.[3]
If Wi-Fi also fails after a cold start, the issue is no longer limited to resume; use the Ubuntu Wi-Fi troubleshooting guide. Avoid copying an old kernel command, module option, or power-management script from an unrelated adapter model.
Forget one saved network only when it is visible but the stored relationship appears stale and you have the correct password, certificate, proxy details, and recovery path. Enterprise Wi-Fi may require an administrator-provided identity or certificate; do not remove it casually.
Update the operating system and use the laptop or adapter manufacturer's official driver for the exact model. Keep the charger connected when required and avoid interrupting firmware updates. A newer package is not automatically the correct package.
Use network reset last. On Windows it removes installed network adapters and their settings, may require network software to be set up again, and can change known connections to a public profile.[1] Before proceeding, record saved network, proxy, virtual-switch, and organization requirements. A reset is not justified when the evidence points to one app, one provider outage, or one access point.
If the adapter vanishes after every wake across networks despite supported updates, collect the exact model, operating-system version, driver version, power state, dock state, and timestamps. That evidence is more useful to the manufacturer than repeated resets.
Classify the post-wake symptom before treating it as one generic Wi-Fi failure. Compare another device, another network, power state, and dock state; then use Wi-Fi or Airplane Mode toggles and a normal reconnect. Follow the Windows, macOS, or Ubuntu branch that matches the state. Forget the network, change a supported adapter power option, update a driver, or reset networking only after simpler comparisons, with the original settings and recovery path recorded.
The wireless radio, driver, saved network session, address lease, dock path, or power transition may not resume correctly. Compare another network and one undocked wake before changing settings.
The operating system may not currently detect or enable the wireless adapter. Restart once, install official updates, and collect the adapter status if it keeps disappearing.
The local wireless link may be active while address assignment, DNS, the router, a portal, or the upstream provider is not. Compare another device and another app.
No. Toggle Wi-Fi and reconnect normally first. Forget the network only when you have its password and any certificate or managed configuration needed to restore it.
No. If the exact adapter and manufacturer support a power-management test, record the original value and test one narrow change. Do not disable every power-saving policy permanently.
Yes. A dock can alter power, Ethernet preference, USB devices, or display state. Test one sleep-and-wake cycle with the dock and nonessential peripherals disconnected.
Only when multiple devices fail or the router shows a problem. If other devices work, keep the router running so it remains a useful comparison.
Provide the laptop and adapter model, system and driver versions, network type, battery or charger state, dock state, exact post-wake status, timestamps, and results on another device and network. AethoVPN cannot keep a sleeping laptop's Wi‑Fi adapter awake or repair its post-wake driver state; confirm plain connectivity before checking VPN reconnection.
Sources checked 4 October 2026.
This article provides general troubleshooting information. Follow the current platform, device-manufacturer, network-owner, and organization instructions for the exact equipment involved.
Sign up to experience all premium features at no cost.
*Available only to new users. Each user is limited to one trial.





