A MakeUseOf guide by Yadullah Abidi covers this problem well, and its advice matches Microsoft's own documentation. Check which sleep model your laptop uses, read the SleepStudy report Windows already keeps, fix whatever the report keeps pointing at, and switch to hibernation if standby still can't be trusted. Below is the full procedure, plus the parts of Microsoft's documentation that explain what the report is telling you.
Why a sleeping laptop can still drain its battery
Older laptops mostly used S3 sleep, which stops normal system activity but keeps memory powered. Most current Windows laptops use Modern Standby instead. It grew out of the Connected Standby model and keeps the machine in S0, the working power state. Individual components, and eventually the whole system-on-chip (SoC), drop into deep idle states.
Microsoft's hardware documentation compares this to a phone. The screen is off and no lights are on, but the PC stays connected over Wi-Fi, mobile broadband or Ethernet. It can wake the SoC for permitted work such as Windows Update scans, network activity, timers and device interrupts. Microsoft also says plainly that long standby battery life only happens when every device and piece of software in the PC takes part in power management. One component that won't go idle can spoil the whole night.
So a laptop with a black screen and a closed lid is not necessarily in its deepest power state. Abidi notes that Microsoft has documented cases where repeated activity cut the low-power stretches to less than a second.
Section summary: Modern Standby is designed to wake briefly for background work. Drain happens when those wake-ups become constant.
Step 1: Check which sleep model your laptop uses
Open Command Prompt as administrator and run:
powercfg /a
Look at the list of available sleep states. If the top of the list shows Standby (S0 Low Power Idle), you have Modern Standby. Some machines add a qualifier: if it shows Standby (S0 Low Power Idle) Network Connected or Standby (S0 Low Power Idle) Network Disconnected, then Modern Standby is supported.
If the laptop only lists traditional S3, SleepStudy is not the right primary diagnostic for that device. Owners of those machines should use other powercfg tools, such as checking wake sources and timers, rather than the steps below.
Step 2: Generate the SleepStudy report
On a Modern Standby laptop, stay in the elevated prompt and run:
powercfg /sleepstudy
According to Microsoft's documentation, the built-in powercfg.exe command-line tool creates an HTML file named Sleepstudy-report.html in the current working directory. If you're running the prompt from C:\Windows\System32, the file ends up there, which is not where you'll go looking for it. Microsoft's powercfg reference lists an /output switch, so you can specify the path and file name to store the Sleepstudy report HTML. For example:
powercfg /sleepstudy /output "%USERPROFILE%\Desktop\sleepstudy-report.html"
By default, the SleepStudy report covers the last three days of system operation. If the bad night was earlier than that, Microsoft says the /duration option takes a number of days, up to 28:
powercfg /sleepstudy /duration 7
Open the HTML file in any browser.
Step 3: Find the night in question
Beginning with Windows version 2004 on Modern Standby systems, the SleepStudy report is organized as a series of state changes -- primarily Active, Screen Off, and Sleep states. Microsoft describes Screen Off as the stretch where the system is still winding down, and Sleep as the long low-power period after that. An overnight problem usually shows up in a long Sleep row.
For each row, check these columns:
- Duration: how long the session lasted.
- Energy change: battery consumed, in milliwatt-hours and as a percentage.
- Change rate: average power draw over the session.
- % Low power state time: how much of the session the SoC spent in DRIPS (Microsoft's term for the deepest runtime idle platform state).
What the colours mean
Microsoft's thresholds for sessions of two minutes or longer:
| Session type | Red | Yellow | Green |
|---|---|---|---|
| Screen Off | Drain ≥ 1% per hour | Drain 0.33–1% per hour | Everything else |
| Sleep | DRIPS < 80% or drain ≥ 1% per hour | DRIPS 80–94% or drain 0.33–1% per hour | Everything else |
Sessions under two minutes are handled differently. Short Screen Off rows show green, and short Sleep rows show grey because there isn't enough data to judge them. A red child blocker also turns its parent session red, and Microsoft says obviously incorrect third-party blockers are shown in purple. Microsoft advises paying most attention to long sessions of several hours with sustained high drain, because those do the most damage to the battery.
For scale: Microsoft's older colour-coding notes say a drain rate of 1 percent per hour caps Modern Standby battery life at about four days. A rate under 0.333 percent per hour works out to 12 days or more. These are diagnostic thresholds, not a promise about how long your particular laptop should last.
Step 4: Check the top offenders
Click a red Sleep session to open its details. Microsoft says each Sleep session lists the five most active components. They fall into these types:
- Fx Device: a device whose driver supports the Windows power framework, usually on the SoC itself
- Activator: software keeping the system awake for background work, such as the broker infrastructure that coordinates background tasks
- Networking: network adapters and stack components
- Processor: CPU activity that no activator accounts for
- PDC Phase: time spent entering or leaving standby
- Other: anything else
A component is highlighted red if it was busy more than 10 percent of the time, and orange between 5 and 10 percent. Treat these as leads, not verdicts. Abidi notes that heavy drain sometimes appears with no obvious culprit. The report can also name a controller rather than the device connected to it, so a USB host controller entry doesn't tell you which peripheral caused the trouble.
Two other details in the report are useful:
- Exit reasons. Microsoft's list includes code 55, "Restricted Standby Battery Drain Budget Exceeded." If you see it, Windows' own drain protection stepped in.
- System information. The report records firmware and OS details because, in Microsoft's words, changes to the operating system, firmware and BIOS can have significant impact on modern standby battery life.
If you suspect the battery itself is worn out, Microsoft's Q&A guidance suggests running powercfg /batteryreport to separate standby drain from battery wear.
What Windows 11 already does to protect your battery
Microsoft has added two safeguards. They are separate mechanisms.
1. Wake-source restriction (Windows 11, version 24H2 and later). Microsoft's wake-source documentation says that when excessive drain is detected, most wake sources are turned off. You can still wake the laptop with the power button or by opening the lid.
2. Adaptive hibernate. This works from a battery budget instead of a fixed timer. Microsoft's defaults:
- StandbyBudgetPercent: 5 percent drain allowed per refresh interval
- StandbyBudgetRefreshInterval: 12 hours. If the budget runs out before the interval ends, the laptop hibernates.
- StandbyBudgetRefreshCount: 4 refreshes
- StandbyReserveTime: 1,200 seconds. This is screen-on time Windows tries to keep available for when you resume.
Microsoft says these settings apply only to Modern Standby systems and only on battery power. Windows waits through a 15-minute grace period before applying either trigger, and laptop makers can change the defaults. In practice, a machine on default settings that loses 5 percent within 12 hours should hibernate instead of draining to zero. Your manufacturer may have configured it differently.
Neither safeguard fixes the driver or device causing the drain. They only limit how much damage it does.
Step 5: Fix the cause, then test again
- Update firmware and drivers from your laptop maker, starting with any device that shows up repeatedly in bad sessions. Wi-Fi, Bluetooth, chipset and graphics drivers are common candidates.
- Look at background activity. Microsoft's wake-source documentation notes that on battery, Windows Update can still scan and do interactive downloads during standby, though installs are paused. Bluetooth audio that keeps playing during standby is not low-power.
- Repeat the overnight test and compare the new SleepStudy session with the old one.
Step 6: If standby still drains, use hibernation
Hibernation saves your session to disk and powers the laptop down. It uses far less power than sleep and resumes a little more slowly. Abidi points out that it's turned off by default on modern Windows systems. Based on long-standing Windows behaviour (this is general knowledge, not from his article), you can usually enable it like this:
- Open Control Panel > Power Options.
- Click Choose what the power buttons do.
- Click Change settings that are currently unavailable.
- Tick Hibernate under Shutdown settings, then save.
If the option is missing, run powercfg /hibernate on from an elevated prompt and check again.
Don't use registry hacks to force S3 sleep back on. Microsoft doesn't support switching power models on an existing installation, and many current laptops lack the firmware to support S3 at all. Hibernation does the same job without that risk.
The bottom line
Losing a lot of battery overnight is not normal. SleepStudy lets you work out why it's happening instead of guessing. Run powercfg /a, generate the report, look for long red Sleep sessions, and work through the top offenders, starting with firmware and driver updates. Windows 11 24H2's wake restrictions and adaptive hibernate help, but if your laptop still drains, hibernating at night costs you a few extra seconds in the morning.