You close the lid at 80% and open it the next morning at 61%. The laptop was warm in your bag, and the battery graph shows a steady decline all night. It was supposed to be asleep — Modern Standby is advertised as sipping power — yet something kept it half-awake for hours.

On ARM laptops, including every Snapdragon Copilot+ PC, sleep is Modern Standby (S0 low-power idle): the machine stays lightly connected so it can wake instantly, sync mail, and run background tasks. That design is efficient only when every device and app cooperates. One misbehaving USB device, Wi-Fi driver, or background app can hold the system in a high-power “active” phase all night — and Windows records exactly who did it.

This guide shows you how to generate a SleepStudy report, read it like a technician, identify the top battery offenders, and fix them in order — from settings changes to driver updates to hardware isolation.

Why this happens

  • A device refusing to enter low power: Wi-Fi, Bluetooth, or a USB peripheral that will not idle keeps the SoC in an active phase; SleepStudy names these offenders precisely.
  • Background apps with unrestricted activity: Mail sync, cloud backup, or a misbehaving Store app can run maintenance tasks all night instead of in short bursts.
  • Outdated Wi-Fi or chipset drivers: The network adapter is the most common SleepStudy offender on ARM laptops — an old driver fails to enter its D3 low-power state.
  • Wake timers firing repeatedly: Scheduled tasks and app wake timers pull the machine out of its deepest idle phase over and over, each wake costing battery.
  • USB devices preventing idle: Docks, external drives, and even some mice keep the USB controller awake; unplugging them often transforms the report overnight.
  • Windows Update or Store maintenance running in sleep: Legitimate maintenance scheduled during idle can consume far more battery than expected on a machine that never truly sleeps.

How to fix it

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

Fix 1: Generate and read your SleepStudy report

Everything starts with the report. One command produces an HTML file that shows every sleep session of the last three days with per-device battery attribution — the closest thing to an X-ray of your overnight drain.

  1. Open an elevated Command Prompt (right-click Start > Terminal (Admin)) and run powercfg /sleepstudy — Windows saves the report and prints its path.
  2. Open the HTML file in your browser and look at the top summary: each session shows duration, battery drain percentage, and a color-coded state.
  3. Click into the worst session (highest drain) and read the Top Offenders section — it lists devices, apps, and drivers by percentage of battery consumed.
  4. Note the exact offender names (e.g., “WiFi Driver,” a USB device name, or an app) — you will act on these in the fixes below.
  5. Also check the Battery Drain chart: a flat-ish low line is healthy; long high plateaus mean the machine was stuck in an active phase instead of idling. If the pattern resembles unexplained battery drain after the screen locks , background capture or sync activity is a prime suspect.

Fix 2: Silence the top-offending app or background task

When SleepStudy names a specific app — a mail client, cloud sync tool, or Store app — restricting its background activity usually fixes the drain without uninstalling anything.

  1. Go to Settings > Apps > Installed apps, find the offending app, open its Advanced options.
  2. Under Background apps permissions, set it to Never (or Power optimized at minimum).
  3. In Settings > System > Power & battery > Battery usage, check the app’s background vs. active usage to confirm it was the culprit.
  4. For scheduled tasks, open Task Scheduler, find tasks belonging to the offender, and disable their wake permissions on the Conditions tab (“Wake the computer to run this task”).
  5. Generate a fresh SleepStudy the next morning (powercfg /sleepstudy again) and confirm the offender dropped off the list.

Fix 3: Update or reset the Wi-Fi driver (the most common offender)

On Snapdragon laptops, the Wi-Fi adapter is the most frequent SleepStudy offender — an old driver fails to enter its low-power state and holds the whole SoC awake.

  1. In your SleepStudy report, confirm the offender mentions Wi-Fi, WLAN, or the network adapter name.
  2. Open Device Manager > Network adapters, right-click your Wi-Fi adapter, and choose Update driver > Search automatically — then also check your maker’s support page for a newer package.
  3. Download the latest Wi-Fi driver from Dell , HP , or Lenovo support for your exact model — OEM-validated wireless drivers matter more on ARM than on x86.
  4. In the adapter’s Properties > Power Management tab, make sure “Allow the computer to turn off this device to save power” is checked.
  5. In Device Manager > Network adapters > adapter Properties > Advanced, look for power-save or WoWLAN settings and set them to maximum power saving if the drain persists.
  6. Re-run SleepStudy after a night’s sleep — a fixed Wi-Fi driver typically moves from top offender to near zero.

Fix 4: Disconnect USB devices and docks overnight

Docks and peripherals are the second great offender class. Isolate them with one clean test night, then deal with the specific culprit.

  1. Check the SleepStudy top offenders for anything USB-related (hub, dock, external drive).
  2. Tonight, unplug everything except the charger before closing the lid — no dock, no dongles, no external drives.
  3. Compare the next morning’s battery level and the new SleepStudy: if the drain collapses, reintroduce devices one per night to find the culprit.
  4. For the offending device, check for firmware updates from its maker, or replace it — some older docks simply never idle correctly on ARM USB controllers.
  5. If you must keep a dock connected, disable USB selective suspend exceptions by setting the USB root hubs’ Power Management to allow the computer to turn them off. The same isolate-one-variable discipline fixes game storage stutter issues on ARM and works just as well for power.

Fix 5: Tame wake timers and overnight maintenance

Even with devices behaving, wake timers can pull the machine out of deep idle dozens of times a night. Each wake is short, but the cumulative cost shows clearly in the SleepStudy timeline as repeated spikes.

  1. Run powercfg /waketimers in an elevated Command Prompt to list every timer that can wake the machine — note which apps own them.
  2. Open Settings > System > Power & battery and expand Battery saver — turn it on at a higher threshold (e.g., 40%) so background activity is throttled during long idle.
  3. In Task Scheduler, open the worst offenders’ tasks (UpdateOrchestrator, Store, app updaters) and uncheck “Wake the computer to run this task” on the Conditions tab.
  4. Go to Settings > Windows Update > Advanced options and set Active hours generously so update maintenance does not run at 3 AM in your bag.
  5. Re-run SleepStudy after two nights — the session timeline should show long uninterrupted idle phases instead of sawtooth wake spikes.

Fix 6: Update the chipset platform and BIOS

When no single offender dominates, the platform firmware itself is suspect — the SoC’s power-management firmware decides how deep idle goes, and vendors fix these behaviors in BIOS updates.

  1. Check Microsoft’s Windows support pages for any documented Modern Standby fixes for your Windows build.
  2. Install every pending Windows Update, then download the latest chipset/platform driver package and BIOS from your maker’s support page.
  3. Update the BIOS on AC power with all USB devices disconnected — interrupted firmware writes are not recoverable by this guide.
  4. After the update, run one clean overnight test: full charge, lid closed, nothing plugged in except the charger.
  5. Compare the new SleepStudy against the old one — platform updates typically cut system-wide idle drain dramatically. If drain persists across firmware versions, the battery itself may be degraded, and the same systematic elimination used for app crashes on ARM applies: the hardware, not the software, is the last variable.

Closing

SleepStudy turns “my laptop drains overnight” from a mystery into a named offender — generate the report, fix the top entry (usually Wi-Fi, a USB device, or a background app), and re-measure. On ARM laptops there is no S3 fallback, so the discipline of reading the report and silencing offenders is the entire game.

Frequently asked questions

What is a SleepStudy report?
SleepStudy is a Windows diagnostic that records exactly what your laptop did during each sleep session — which devices stayed awake, how much battery each consumed, and how long the session lasted. It is generated with a single powercfg command and opens as an HTML report in your browser.
How much battery drain in sleep is normal on an ARM laptop?
A healthy Modern Standby session on a Snapdragon laptop drains roughly 1-3% over 8 hours. If your SleepStudy shows 5% or more overnight, or the top offenders list names a device or app consuming double digits, something is misbehaving and worth fixing.
Does SleepStudy work on Copilot+ PCs?
Yes. SleepStudy works on every Windows 11 machine that uses Modern Standby, including all Copilot+ PCs and Windows on ARM laptops. It does not require admin tools beyond an elevated Command Prompt to generate.
Can I just disable Modern Standby to stop the drain?
On ARM laptops you generally cannot — Modern Standby (S0 low-power idle) is the only sleep state these machines support; there is no S3 to fall back to. The correct fix is finding and silencing the offender in the SleepStudy report, which this guide walks through.