Close the lid, open it later, and… molasses. The login screen takes forever, the network won’t connect, apps hang for minutes. But restart the laptop and everything’s snappy. That gap — slow after sleep, fine after restart — is the signature of resume problems, and it has a best-first fix order that resolves most cases quickly.

This guide is the prioritized path: the fixes ranked by how often they work, so you try the winners first. Driver power management and standby mode top the list; the deeper tweaks follow. If you want the full diagnostic deep-dive instead, see slow after sleep troubleshooting ; for general sluggishness, speeding up a slow Windows 11 laptop covers the rest.

Start at Fix 1 — it alone resolves roughly half of all slow-resume complaints.

Why this happens

  • Drivers resuming badly: Network, GPU, and USB drivers that don’t reinitialize cleanly leave the system stumbling for minutes after wake.
  • Modern Standby churn: S0 standby keeps background activity alive during sleep, creating more state to untangle on wake.
  • Fast Startup compounding resume issues: Hybrid shutdown plus sleep states interact badly on some hardware, corrupting the resume path.
  • USB devices failing to re-enumerate: Docks, hubs, and peripherals that don’t wake properly stall the whole resume sequence.
  • Network reconnection delays: Wi-Fi adapters with bad power management take minutes to reconnect, and apps waiting on network hang meanwhile.
  • Memory pressure after long sleep: Compressed memory and standby lists built up over days make the first minutes after wake feel loaded.
  • Windows Update pending operations: Updates staged during sleep finalize on wake, competing with your return to work.

How to fix it

Work through these in order — diagnose first, then act.

Fix 1: Update GPU and network drivers first

The single highest-yield fix — resume bugs live in drivers more than anywhere else.

  1. Update your GPU driver from the manufacturer: NVIDIA NVIDIA’s driver download page , AMD AMD’s driver download page , or Intel’s driver detection tool.
  2. Update Wi-Fi and chipset drivers from your laptop manufacturer’s support page.
  3. Do a clean GPU driver install to clear corrupted driver state.
  4. Test sleep/wake three times — resume bugs are intermittent, so one good wake isn’t proof.

Fix 2: Disable Fast Startup

Fast Startup’s hybrid state interacts badly with sleep resume on many laptops.

  1. Open Control Panel, Power Options, Choose what the power buttons do.
  2. Click Change settings that are currently unavailable and uncheck Turn on fast startup.
  3. Shut down fully (not restart) once to clear the hybrid state.
  4. Test sleep/wake cycles — this fixes a large share of remaining cases.

Fix 3: Switch from Modern Standby to classic sleep or hibernate

If S0 standby is the problem, sidestep it entirely.

  1. Check your standby mode: run powercfg /a in Command Prompt — if Standby (S0) is listed and S3 isn’t, you’re on Modern Standby.
  2. Some BIOS setups offer a sleep-mode toggle; check yours.
  3. Alternatively, set the power button and lid-close to Hibernate instead of Sleep.
  4. Hibernate wakes cleanly because it reinitializes everything — slower to wake, but reliably fast after.

Fix 4: Fix USB selective suspend and devices

USB power management is a notorious resume-staller.

  1. In Power Options advanced settings, set USB selective suspend to Disabled.
  2. In Device Manager, find USB Root Hubs, Properties, Power Management — uncheck Allow the computer to turn off this device.
  3. Test wakes with docks and hubs disconnected to isolate a bad peripheral.
  4. Update dock/hub firmware if the manufacturer offers it.

Fix 5: Tune network adapter power management

Wi-Fi adapters that sleep too deeply cause the ‘wake but no network for minutes’ pattern.

  1. In Device Manager, find your Wi-Fi adapter, Properties, Power Management.
  2. Uncheck Allow the computer to turn off this device to save power — test whether wakes improve.
  3. In the Advanced tab, look for power-saving or roaming aggressiveness settings and set them moderate.
  4. If it helps, keep it off; the battery cost is small.

Fix 6: Clear the cobwebs: memory and updates

Long uptimes accumulate cruft that punishes resumes.

  1. Restart at least weekly — sleep is not a substitute for restarts.
  2. Install pending Windows updates so they stop staging work during sleep.
  3. Check Task Manager’s Startup apps and trim aggressively — see disabling startup programs .
  4. Microsoft’s sleep guidance: Microsoft’s Windows support site .

Fix 7: Reset power plans to defaults

Corrupted or over-tweaked power schemes cause exotic resume bugs.

  1. Open an admin Command Prompt and run powercfg -restoredefaultschemes.
  2. Re-select Balanced and reapply only the tweaks you need.
  3. Test sleep/wake before re-adding customizations.
  4. If a specific tweak reintroduces the slowness, you’ve found a trigger to avoid.

Fix 8: Disable wake timers and sleep-time background work

A laptop that never truly sleeps wakes up groggy. Wake timers and background tasks fragment standby, leaving the system in a half-awake state that resumes slowly.

  1. Open Power Options, advanced settings, expand Sleep, then Allow wake timers — set to Disable on both battery and plugged in.
  2. In Task Scheduler, browse common wakers (UpdateOrchestrator, Media Center tasks) and uncheck Wake the computer to run this task where you don’t need it.
  3. In Settings, Apps, disable background running for apps that don’t need it — fewer apps active during standby means cleaner sleep.
  4. Run powercfg /waketimers to audit what’s still allowed to wake the PC, and powercfg /sleepstudy after a few nights to verify sessions are clean.
  5. Fewer interruptions during sleep means the laptop actually rests — and wakes like it did.

Closing

Slow-after-sleep is a resume problem, and resume problems are driver and standby-mode problems — which is why the best-first order starts with GPU/network drivers, Fast Startup, and standby mode. Most laptops are fixed by the first three steps. If yours isn’t, hibernate is an honorable fallback: slightly slower to wake, but consistently fast once awake, which is the tradeoff that actually matters.

Frequently asked questions

Why is my laptop slow specifically after sleep but fine after restart?
Sleep preserves your session in RAM while powering down components; wake-up has to reinitialize drivers, reconnect network, and restore device states. If any driver resumes badly — common with network, GPU, and USB drivers — the system stumbles for minutes until things settle. A restart avoids this entirely by initializing everything cleanly, which is why restarts feel fine while resumes don’t.
Is Modern Standby (S0) worse than classic sleep (S3)?
It can be. Modern Standby keeps the system semi-awake for updates and notifications, which means more background activity during ‘sleep’ and more to untangle on wake. Many users report snappier wakes after switching to classic S3 sleep or hibernate. The tradeoff: S0 wakes instantly to notifications; S3 sleeps deeper and wakes cleaner. For a laptop that’s slow after wake, S3 or hibernate usually wins.
How long should wake-from-sleep take?
A healthy wake takes 2-5 seconds to the login screen and another 5-15 seconds for network and apps to become responsive. If you’re waiting over a minute, or the system is sluggish for several minutes after waking, that’s abnormal. Consistent 3+ minute recoveries point to a driver or standby-mode problem worth fixing.
Will disabling sleep and using hibernate instead fix it?
Often yes, and it’s a legitimate strategy. Hibernate writes RAM to disk and fully powers off — waking is a clean re-initialization, avoiding the driver-resume bugs that plague sleep. The cost: slower wake (15-30 seconds) and disk space for hiberfil.sys. If sleep resumes are broken and driver fixes fail, hibernate is the pragmatic best way.