Windows 11 Wi-Fi Drops After Sleep: An Ordered Fix

A PC that wakes from sleep but comes back without Wi-Fi is one of the more frustrating Windows 11 faults because nothing looks broken: the machine boots, the desktop appears, and the network icon simply shows no connection. The pattern is consistent across user reports. In one Microsoft Q&A thread, a user describes Wi-Fi disconnecting and failing to reconnect automatically after locking the device and leaving it idle, requiring a manual reconnect each time ^¹. A separate thread reports that after a Windows 11 update both LAN and Wi-Fi refuse to come back from sleep, with a restart as the only reliable recovery ^². Notably, the second user says updating drivers from Intel's site and disabling power management on both adapters did not help — a useful warning that the obvious fixes are not always sufficient.

What follows is an ordered sequence, cheapest and safest first. Work through it one step at a time and test by putting the PC to sleep and waking it after each change, so you know which step actually mattered.

1. Confirm the adapter's power-saving setting. Open Device Manager, expand Network adapters, right-click the Wi-Fi adapter, open Properties, and check the Power Management tab for "Allow the computer to turn off this device to save power." This is the fix Microsoft's community answer leads with. One caveat from that same thread: a user reported the Power Management tab was no longer available on their Windows 11 system, so if you cannot find it, do not assume you have missed something — move on.

2. Update or roll back the Wi-Fi driver. Because the failure often follows an update, the driver is the prime suspect. Check the PC or motherboard maker's support page for your exact model before trying the chipset vendor's generic package; the second Q&A thread shows a user installing Intel's own drivers without success on an Asus TUF board. If you are already on the newest driver and the problem started right after it arrived, rolling back to the previous version is a legitimate test.

3. Check for a pending Windows update, and note your build. Both threads tie the fault to a recent Windows update, and in the second thread a responder's first question was the current Windows 11 version and build. Record your build number before and after any update so you can tell whether a change helped.

4. Run the built-in network troubleshooters. Windows can reset the adapter and re-acquire a DHCP lease without you touching settings. It is a low-risk step that sometimes clears a transient state left over from sleep.

5. Rebuild the network stack. If the adapter is present but the connection never returns, resetting the networking components from an elevated command prompt — releasing and renewing the IP configuration, flushing the DNS cache, and resetting Winsock and the TCP/IP stack — is the standard deeper repair. Treat this as the step after the simple ones, not the first move.

6. Use a full restart as a diagnostic, not a fix. In the second thread, restarting the computer is the only thing that reliably restores networking. That tells you the hardware is fine and the fault is in software state, but it does not tell you which component is at fault.

When a step fails, the useful move is to change one variable rather than stack fixes. If disabling power management does not work, do not also change the driver in the same session — you lose the ability to attribute the result. If the Power Management tab is missing, skip to the driver step. If a clean driver reinstall and a network reset both fail, the remaining evidence points at the Windows build itself: the second thread's user reported the problem appearing after an update and persisting through driver and power-setting changes, which is the signature of a regression rather than a misconfiguration. At that point, checking whether other users report the same build, and filing feedback through the Windows Feedback Hub, is more productive than further local tweaking. The sources do not establish a confirmed Microsoft fix or a specific affected build number, so any claim that a particular patch resolves this should be treated as unverified.

One reported workaround deserves a mention with a clear caveat. The second thread's author found that connecting the PC to a phone's mobile hotspot caused LAN and Wi-Fi to come back to life after about a minute. That is a single user report, not a tested procedure, and it is a workaround rather than a repair — but if you are stuck mid-task it costs nothing to try.

A related pattern is worth ruling out: if your machine is waking on its own rather than staying asleep, the problem may be sleep behaviour rather than the network adapter. Our guide to Windows 11 sleep mode waking instantly covers that separate failure. And if the disconnects happen while the PC is awake rather than after sleep, the ordered steps in our Bluetooth disconnection guide show the same discipline of isolating one variable at a time, even though the hardware differs.

The honest summary: the published evidence supports power management and driver state as the first places to look, and it shows that neither always works. If both fail and a restart is your only recovery, you are probably looking at a Windows update regression, and the right next step is to document your build and report it rather than keep reinstalling drivers.

Sources

1. ¹ Wi-Fi disconnects and does not reconnect automatically - Microsoft Q&A learn.microsoft.com
2. ² Windows 11: Network Lan and Wifi gone after sleep - Microsoft Q&A - Skip to main content video2.skills-academy.com