Documentation reviewed November 16, 2026. This guide uses Microsoft documentation; it does not claim hands-on testing of these fixes.
Applies to: Surface Pro with Windows 11. SleepStudy applies to systems that support Modern Standby; check before using it. This is separate from our historical Surface Pro 4 firmware coverage.
First establish whether the Surface actually slept. A screen that turned off is not enough evidence. Compare a repeatable idle interval before making multiple changes.
1. Record a useful baseline
Save your work. Note battery percentage, time, connected accessories and how you put the device to sleep. Check the percentage and elapsed time on waking. Repeat under similar conditions with docks and unnecessary USB devices disconnected. Keep the device on a suitable surface while testing.
Compare like with like: an hour at a desk and a night in a bag are not equivalent tests. A drain rate alone does not reveal which component caused it, and there is no universal percentage threshold that proves a Surface is defective.
2. Check sleep support and recent changes
Install applicable Surface and Windows updates, then restart. Note any newly installed software or connected device. In Terminal or Command Prompt, run powercfg /a to see the available sleep states. Microsoft documents this command in its powercfg reference.
3. Use the appropriate report
On a Modern Standby system, open Command Prompt as administrator and generate a report for a known location, for example:
powercfg /sleepstudy /duration 7 /output "%USERPROFILE%\Desktop\surface-sleep.html"
Open the resulting HTML file and locate the interval you recorded. Compare time spent active, with the screen off, and asleep; examine reported activity rather than guessing from the final percentage. Microsoft’s SleepStudy documentation explains those sections. If the tool says the system is unsupported, do not treat that message as evidence of a battery failure.
4. Separate capacity from sleep activity
A battery report can provide a different view:
powercfg /batteryreport /output "%USERPROFILE%\Desktop\surface-battery.html"
Its capacity history helps distinguish reduced battery capacity from a specific overnight activity problem. Keep these reports private when sharing troubleshooting details; they can include device and usage information. Microsoft lists the roles of these tools in its power-analysis overview.
Act on one finding
If removing an accessory changes the result, repeat that comparison before replacing hardware. If a named app repeatedly appears active during the problem interval, update it and inspect its settings. Avoid forcing unsupported sleep states with registry tweaks. If the evidence remains unclear, provide the exact model, Windows version and measured interval to Surface support. Our backup checklist applies before any recovery step.
Our older Surface Pro 4 / Surface Book firmware article remains a record of that specific update, not a universal fix for newer models.
Sources
Kent Beck is an American software engineer and the creator of extreme programming, a software development methodology that eschews rigid formal specifications for a collaborative and iterative design process. Wikipedia
Knowledge Panel
