These steps use two Microsoft pages: the Windows keyboard shortcuts list and the powercfg command-line reference. Neither page is tied to one Windows build, so the steps are written for Windows 11 in general. This site has no lab and has not run them on Windows 11 26H2, the current release. I did not find a single Microsoft support article for this exact problem, which is why the order below is ours and the individual commands are Microsoft's.
First, know which problem you have. A PC that never comes back at all is different from one whose screen stays black while the fans and lights say it is running. The first check below is for the second case. The rest are for a PC that sleeps badly in either direction.
Check 1: wake the screen with the shortcut
If the PC seems to be running but the screen is black, press the Windows logo key, Ctrl, Shift and B together. Microsoft's shortcuts page lists it for Windows 11 as "Wake up the device when the screen is blank or black". You may hear a short beep or see the screen flicker. Before that, press a key on the built-in keyboard once, and open the lid if it is closed. If an external monitor or dock is attached, unplug it and test with the built-in screen alone. This check only helps when Windows resumed and the display did not.
Check 2: see what is stopping sleep
Right-click Start, choose Terminal (Admin) or Command Prompt (Admin), and run powercfg /requests. Microsoft describes it as listing the application and driver power requests that prevent the computer from turning off the display or entering sleep. If a program or driver is named under a heading, that is what is holding the PC awake, and closing or updating that program is the fix. Do not use powercfg /requestsoverride to silence a request unless you know what the named item does.
Check 3: see what woke it
If the PC wakes when you did not want it to, run powercfg /lastwake after an unwanted wake. Microsoft describes it as reporting what woke the system from the last sleep transition. Then run powercfg /devicequery wake_armed, which lists the devices currently allowed to wake the PC from any sleep state. If a mouse or network adapter you do not need for waking appears, powercfg /devicedisablewake followed by the device name in quotes turns that off. powercfg /waketimers lists scheduled wake timers.
Check 4: the sleep timers
Go to Start > Settings > System > Power & battery > Screen, sleep, & hibernate timeouts. There are two dropdowns: "Turn my screen off after" and "Make my device sleep after", each with a battery and a plugged-in value. Microsoft's power settings page documents the path. Community answers on Microsoft's Q&A site report that Energy saver can override these timers and put the PC to sleep sooner than set, but that is not in Microsoft's own page, so treat it as a lead and not a rule.
Check 5: the report
In the same administrator window, run powercfg /systemsleepdiagnostics /output system-sleep-diagnostics.html. Microsoft says it needs an elevated prompt and produces an HTML file covering the last three days, showing the intervals when you were not present and whether the system went to sleep. The file lands in the folder the prompt is open in. It will not name a cause for you; it shows when sleep failed, which you can match against an update, a driver install or a new device.
If the option is not there
powercfg says a command is not recognized or is denied. Open the prompt as administrator; the report command requires it.
The shortcut does nothing. Then Windows may not have resumed, and the display is not the problem. Hold the power button until the PC turns off and start it again. Make a note of whether it happens after an update or a driver change.
The sleep timers are missing or greyed out. On a PC managed by an employer or school, an administrator may control them. Microsoft's page does not say more about that.
powercfg /requests shows nothing under any heading. Then no program or driver is blocking sleep, and the cause is elsewhere: a display driver, the PC maker's firmware or the hardware.
What these checks do not fix
They cover settings and diagnostics, not a driver or firmware fault. If the black screen started after a graphics driver update, the PC maker's support page for your exact model is the place to look for a driver, and Device Manager's driver properties may offer a rollback when an earlier driver is still stored. A PC that fails to wake on every attempt, whatever you change, points to firmware or hardware, and that is a question for the manufacturer. Microsoft's pages do not promise a fix for any of these, and neither does this one.
If the PC wakes but the network does not come back, the Wi-Fi walkthrough covers the adapter power setting. For a headset that drops after waking, the Bluetooth walkthrough has the Energy Saver and Device Manager steps. And if the PC is slow once it is up, finding what holds the disk at 100 percent is the next check.
Last updated October 9, 2026