What's your go to fix when a laptop refuses to wake from sleep

[NinaVrina]

Every OS seems to have its own version of this problem eventually. Drop whatever combination of driver updates, power settings or plain old restarts has actually solved it for you, ideally with the OS and rough laptop age included.

[FairDos]

I agree with the driver angle, although I would put the firmware and dock situation slightly higher if this is a laptop that normally lives on a desk. USB-C docks, external monitors, Ethernet adapters and even certain USB devices can complicate resume badly. As a test, disconnect everything except the charger and see whether the laptop wakes reliably. If it suddenly behaves, reconnect things one at a time rather than blaming the laptop immediately.

Network adapters are another odd one. In Device Manager, checking the adapter's power-management options can reveal whether Windows is allowing it to wake the computer or power it down during sleep. I would not blindly disable every wake option, though. If you rely on wake-on-LAN or similar features, that can create a new problem while apparently fixing the old one.

There is also a useful distinction between failing to wake and waking without bringing the display back. Caps Lock or Num Lock responding to the keyboard can be a crude but handy test. If the indicator changes, the machine may be alive and the display path is what has failed. That points me towards the GPU driver, external display configuration, lid sensor or dock rather than the power button.

My general rule is to reproduce it with the simplest possible setup, record exactly what happened, then change one variable at a time. Sleep problems are particularly good at producing folklore fixes because the same symptom can have several completely different causes. If someone tells you one magic registry setting fixes every laptop, keep one eyebrow raised.

[Woven Sarah]

For me the quickest trick is pressing the power button once, then giving it a surprisingly long moment. Some laptops look completely dead when the display has failed to resume, but the system is actually awake. Plugging in an external monitor is a useful sanity check if you have one. If the external display works, you are probably chasing a graphics or panel wake-up issue rather than a completely frozen machine.

After that, I tend to check what sleep mode the laptop is actually using. Windows machines can behave quite differently depending on whether they support Modern Standby or the older S3 sleep state. Two laptops with identical-looking power settings can therefore have very different failure modes. That caught me out once because I was applying advice intended for S3 to a machine that simply did not use it.

For a repeat offender, I would run powercfg /sleepstudy on supported Windows systems and look for devices or drivers keeping the machine active. It can turn the vague complaint of "it won't wake" into something much more useful, such as a network adapter or driver repeatedly changing power state. On Linux, checking journal logs around the suspend and resume timestamps gives you a similar direction to investigate.

And yes, sometimes the fix really is rebooting. There is a point where spending forty minutes diagnosing a ten-second reboot becomes its own form of technical debt.

[BrayWyatt_WCW]

A full restart is still my first move, mainly because it tells you whether you have a sleep problem or a machine that has decided it is now a decorative paperweight. If the keyboard and mouse do nothing, I usually hold the power button for a few seconds and boot fresh, then check Event Viewer afterwards rather than immediately changing ten settings at once.

If it happens repeatedly, graphics drivers are high on my list. Windows sleep and modern standby seem to have a complicated relationship with GPU drivers, especially after an update. I have had a laptop that would wake perfectly until the display driver changed, then suddenly it needed a hard reboot every other day.

Another useful test is to disable Fast Startup temporarily and see whether the behaviour changes. It is not a universal fix, but it can help separate a power-state problem from something happening during a normal boot. For persistent cases, I would also check whether the BIOS has a newer firmware version and whether the manufacturer has a chipset or power-management driver available.

One thing I would avoid is randomly changing every power setting you can find. That makes troubleshooting much harder because you no longer know which change actually mattered. Change one thing, test it for a while, then move on. Less exciting than throwing registry tweaks at it, but considerably easier to undo