You tap the keyboard, the room stays dark, and the PC sits there like the power cable fell out. A gaming PC that refuses to wake from sleep is rarely broken hardware. Usually one link in the wake chain has been switched off: the keyboard was never given permission to wake the machine, Windows powered down its USB port, the board cut standby power, or the PC fell into hibernation instead of sleep. Work through the chain in order and you will find the broken link.
As an Amazon Associate, we earn from qualifying purchases.
Quick Answer
Start with permissions: run powercfg /devicequery wake_armed to confirm your keyboard and mouse may wake the PC, then clear the power-saving checkbox on every USB root hub in Device Manager. Disable hybrid sleep, and check the BIOS for ErP or Deep Sleep cutting USB power. If the PC wakes but the screen stays black, the fault is the display path, not the wake signal.
First, Read the Failed Wake
The symptom tells you which half of the chain is broken, so watch one failed wake before changing anything.
If the PC does nothing at all — no fans, no lights, no disk activity — the wake signal never arrived or never registered. That points at wake permissions, USB power, or BIOS standby settings, and it is the pattern this guide spends most of its time on.
If fans spin and lights come on but the screen stays black, the PC did wake. The failure is in the display path: the graphics driver did not reinitialise the output, or the monitor is on the wrong input. Test a different monitor input or cable before touching power settings.
If the PC wakes and immediately sleeps again, something is sending it back down — usually a wake timer conflict. Run powercfg /lastwake after one of these episodes; it names the device or timer responsible, which narrows the search considerably.
Step One: Give Your Keyboard and Mouse Permission to Wake
Windows decides per device whether it may wake the machine, and plenty of keyboards and mice ship with that permission off.
Open Device Manager, find your keyboard under Keyboards, open Properties, and look for the Power Management tab. Tick “Allow this device to wake the computer” and untick “Allow the computer to turn off this device to save power.” Repeat for your mouse. If the Power Management tab is missing, the device or its driver does not expose wake control — itself a clue, so try a different keyboard before going deeper.
Confirm the result from a command prompt with powercfg /devicequery wake_armed. Your keyboard and mouse should both appear in the list. If they do not, the usual cause is a hub between the device and the PC: an unpowered hub in the middle can swallow the wake signal. Plug the keyboard straight into a rear motherboard port for one test sleep before blaming anything else.
Step Two: Stop Windows Powering Down the USB Chain
Even with wake permission set, Windows can cut power to the port itself. Two settings do this.
The first is USB selective suspend, which lets Windows park individual USB devices to save power. A parked keyboard cannot send a wake signal. Find it under your active plan’s advanced power settings, in the USB settings group, and disable it for one test cycle.
The second is the root hub checkbox. In Device Manager, open every USB Root Hub and Generic USB Hub entry, and on the Power Management tab untick “Allow the computer to turn off this device to save power.” There are usually several hubs, so clear them all rather than guessing which one feeds your keyboard. Restart, sleep the machine, and try again. A large share of dead wakes end at this step.
Step Three: Hybrid Sleep, Hibernation and Fast Startup
Sometimes the PC is not sleeping at all. Hybrid sleep writes the session to disk like hibernation while keeping the memory powered, and on some boards the wake behaviour of that state is unreliable — the machine behaves like it is off because, electrically, most of it is.
Turn hybrid sleep off in the advanced power settings, under the Sleep group, and test plain sleep for a night. While you are there, check the hibernate-after timer: a PC set to hibernate after an hour of sleep will look exactly like a PC that will not wake, because waking from hibernation is a boot, and some boards handle it badly with certain keyboards.
Fast Startup shares the same hibernation file, and a stale one can produce strange power behaviour in both directions. If the failed wakes started after a Windows update, toggling Fast Startup off and restarting fully is a cheap reset of that file.
Step Four: BIOS Settings That Cut Power While the PC Sleeps
If the software side is clean, the board itself may be removing the power your wake device needs. Three BIOS or UEFI settings matter here.
ErP mode, sometimes labelled ErP Ready or Deep Sleep, exists to cut standby draw to near zero. Enabled in its strictest form, it removes power from USB ports in sleep and shutdown states — and a keyboard with no power cannot wake anything. If your board has ErP set to an S4 or S5 mode, disable it or set it to the S3-only option and test again.
Look also for a wake-from-USB or power-on-by-keyboard setting; most boards enable it by default, but a BIOS update or a loaded profile can reset it. Finally, note which sleep state your system uses: powercfg /a lists the supported states. Modern Standby behaves differently from classic S3 sleep, and several settings above apply to one and not the other.
How to Choose
Once the settings are right, the remaining variable is the physical chain between your finger and the motherboard. Choose test gear by what it removes from suspicion. A wired keyboard and mouse on rear ports remove batteries, receivers and hubs in one move. A self-powered hub removes the motherboard port’s power budget, which matters when ErP cannot be changed — on a work machine you do not control, for example. A dock is the laptop version: one powered point for the wake device and the display. Buy the test that matches the layer you could not fix in settings.
Anker 7-Port USB 3.0 Hub with 36W Power Adapter
The fix for the port-power pattern. Its own 36W adapter feeds every port independently of the motherboard, so a keyboard on this hub stays powered in sleep states where a board port goes dark. If wake works through this hub but not through the rear panel, the board’s standby power was the fault, and you can stop digging.
Specs
- Ports: 7 USB 3.0 data ports, up to 5 Gbps
- Power: 36W adapter included (12V, 3A)
- Charging: one BC 1.2 port with faster charging output
- Chipset: VIA VL812
- Cable: 6-foot USB 3.0 host cable included
HyperX Alloy Elite 2 Mechanical Gaming Keyboard
A wired keyboard is the cleanest wake source you can test with: no battery, no receiver, nothing between the key press and the controller. Its USB passthrough also lets your mouse ride the same known-good path, so one cable run tests both wake devices at once.
Specs
- Switches: HyperX Red linear mechanical
- Keycaps: ABS pudding keycaps with per-key RGB backlighting
- Extras: media bar, light bar, USB passthrough port
- Connection: wired USB
- Frame: steel alloy top plate
Logitech G502 HERO Wired Gaming Mouse
The mouse half of the known-good test. A wired mouse draws steady power and either wakes the PC or proves the wake path itself is broken, with no wireless link to wonder about. If it cannot wake the machine on a rear port with permissions set, the problem is in Windows or the BIOS.
Specs
- Sensor: Logitech HERO 25K
- Maximum sensitivity: 25,600 DPI
- Connection: wired USB
- Switches: mechanical Omron main switches
- Weight: 121 g, with five optional 3.6 g weights
Anker 341 USB-C Hub (7-in-1)
For a gaming laptop that will not wake on its dock or desk setup, this hub’s pass-through charging keeps the hub and everything on it fed from the charger instead of the laptop’s own port budget. A keyboard plugged in here stays alive through sleep states that starve a bus-powered hub.
Specs
- Model: A8346
- Charging: up to 85W pass-through Power Delivery
- Data: two USB-A ports and one USB-C port at 5 Gbps
- Card slots: SD and microSD readers
- Video: HDMI output up to 4K, driven by host Alt Mode
Plugable UD-6950PDH Docking Station
The full-desk version for a laptop or small PC that sleeps at a workstation. Its own power supply and 100W host charging take the host port out of the power question, and a wake device on the dock gets a consistent feed. The DisplayLink video path needs a driver install, so treat it as a desk setup rather than a gaming path.
Specs
- Video chip: DisplayLink DL-6950, driver installation required
- Output: two displays up to 4K at 60Hz over HDMI or DisplayPort
- Charging: 100W host charging
- Host link: USB-C or USB 3.0
Who Should Skip
Skip this guide if the power button also fails to start the PC from a full shutdown — that is a power supply, front-panel or board fault, not a wake problem. Skip it if the PC wakes perfectly and only the game you left open has crashed; that is a software resume issue, not the sleep chain. And if a laptop under warranty has never woken correctly since new, use the warranty — a faulty lid sensor or embedded controller is the vendor’s problem.
Final Verdict
A PC that will not wake from sleep is almost always a chain with one link switched off. Set wake permission on the keyboard and mouse, stop Windows powering down the root hubs, take hybrid sleep out of the picture, and check the BIOS for ErP or Deep Sleep cutting USB standby power. Test each change with a real sleep, and use a wired keyboard or a powered hub to prove which layer is guilty before replacing anything.
Frequently Asked Questions
Why does my PC wake with the power button but not the keyboard?
Because the power button bypasses the USB wake chain. The keyboard needs three things the button does not: wake permission in Device Manager, a port that stays powered during sleep, and a BIOS that has not cut USB standby power through ErP or Deep Sleep. Check them in that order.
What does powercfg /lastwake actually tell me?
It reports what caused the most recent wake — a device, a wake timer, or the power button. It is most useful when the PC wakes on its own or wakes and sleeps again, because it names the culprit instead of leaving you to guess which peripheral is misbehaving.
Is Modern Standby worse for wake problems than S3 sleep?
It behaves differently rather than simply worse. On Modern Standby systems several classic settings, including some in this guide, do not apply, and wake behaviour is managed more by drivers and firmware. Run powercfg /a to see which states your PC supports before changing settings, so you only adjust the ones your machine actually uses.
Can a hub stop my keyboard from waking the PC?
Yes. An unpowered hub can lose its own power feed during sleep, and a device behind it cannot send a wake signal the PC will ever see. A self-powered hub with its own adapter avoids the problem, and plugging the keyboard straight into a rear motherboard port is the fastest way to test whether the hub is the broken link.
Product and ASIN Reference
| Product | ASIN |
|---|---|
| Anker 7-Port USB 3.0 Hub with 36W Power Adapter | B014ZQ07NE |
| HyperX Alloy Elite 2 Mechanical Gaming Keyboard | B088KRFVBK |
| Logitech G502 HERO Wired Gaming Mouse | B07GBZ4Q68 |
| Anker 341 USB-C Hub (7-in-1) | B07ZVKTP53 |
| Plugable UD-6950PDH Docking Station | B09TQY97MJ |











