9 Ways to Fix a Windows 11 or 10 PC That Won’t Sleep

“Windows won’t go to sleep automatically” is frustrating when manual sleep works but the configured timeout does nothing. The cause is usually an active power request, wake timer, driver, peripheral, or media-sharing service.

Fix #1: Check the sleep timeout

Start by confirming that Windows is actually configured to sleep. A power-plan change or laptop vendor utility can alter this setting.

1. Open Start > Power > Sleep to confirm that manual sleep works.

2. In Windows 11, open Settings > System > Power & battery.
3. Expand Screen, sleep, & hibernate timeouts.
4. Set Make my device sleep after to a short interval, such as five minutes, for testing.

5. In Windows 10, open Settings > System > Power & sleep instead.
6. Check both the battery and plugged-in sleep settings if you’re using a laptop.

Leave the computer idle without playing audio or video. It should enter sleep after the selected interval.

Fix #2: Find active power requests

The powercfg /requests command is the fastest check because it identifies the process, service, or driver blocking sleep. Check this before changing several unrelated settings.

1. Right-click Start and select Terminal (Admin) or Windows PowerShell (Admin).
2. Select Yes when User Account Control appears.
3. Run:

powercfg /requests

4. Review the results under DISPLAY, SYSTEM, AWAYMODE, EXECUTION, PERFBOOST, and ACTIVELOCKSCREEN. Each entry names its caller type, such as [PROCESS], [SERVICE], or [DRIVER].

If every category says None, continue to Fix #3. If an app, service, or driver appears, close or update that item and run the command again. Windows should sleep once the request disappears.

Fix #3: Generate an energy report

The energy report checks power settings and drivers for 60 seconds. It’s especially useful when /requests returns None but automatic sleep still fails.

1. Close any apps you don’t need during the test.
2. Open Terminal (Admin).
3. Run the original energy diagnostic command:

powercfg.exe /energy

4. Wait until Windows displays the number of errors and warnings.

5. Run this command to copy the report somewhere easier to open:

copy %SystemRoot%\System32\energy-report.html "%USERPROFILE%\Desktop\energy-report.html"

6. Open energy-report.html from your desktop.
7. Check Errors for devices or drivers preventing sleep.

An error about a USB device, network driver, or active system request gives you a specific target. Warnings about short display timeouts during the test don’t necessarily explain the sleep failure.

Fix #4: Disconnect peripherals

A USB dock, external drive, printer, Bluetooth adapter, controller, or media device can hold the computer awake. Testing without them is quick and often works.

1. Shut down the computer.
2. Disconnect every nonessential USB device and dock.
3. Leave only the keyboard, mouse, and display connected.
4. Start Windows.
5. Wait for the configured sleep timeout.

If sleep works, reconnect one device at a time and repeat the test. The last device connected before the problem returns is the likely cause; update its driver or leave it disconnected when unused.

Fix #5: Adjust wake timers and media settings

Advanced Power Options contains two settings worth checking: wake timers and media sharing.

1. Press Windows + R.
2. Type control.exe powercfg.cpl and press Enter.
3. Select Change plan settings beside the active power plan.
4. Select Change advanced power settings.

5. Expand Sleep > Allow wake timers.
6. Choose Important Wake Timers Only, or choose Disable temporarily for testing.
7. Expand Multimedia settings > When sharing media.
8. Select Allow the computer to sleep.

9. Select Apply > OK.
10. Restart the computer and test automatic sleep.

I’d avoid disabling all wake timers permanently, though. Important maintenance tasks can depend on them.

Fix #6: Check media sharing and network activity

Media streaming or an active network share can create a SYSTEM request, sometimes associated with srvnet. HomeGroup isn’t part of current Windows versions, so focus on media sharing and active file connections.

1. Open Control Panel.
2. Select Network and Internet > Network and Sharing Center.
3. Select Change advanced sharing settings.

4. Find the media-streaming controls. Their placement can vary by Windows version.
5. Open Choose media streaming options if it appears.

6. Block devices or turn off media streaming if you don’t use it.

7. Restart Windows.
8. Run powercfg /requests again.

If the media or network request is gone, wait for the sleep timeout. The computer should now sleep normally.

Fix #7: Update or roll back problem drivers

Graphics, chipset, network, and audio drivers are common sleep offenders. Start with any device named by /requests, the energy report, or Event Viewer.

1. Right-click Start and select Device Manager.
2. Expand the relevant device category.
3. Right-click the device and select Properties.

4. Open the Driver tab.
5. Select Update Driver > Search automatically for drivers.
6. Install the GPU, chipset, or network package from the computer or component manufacturer’s support page if Windows doesn’t find a newer driver.
7. If the problem began immediately after a driver update, return to the Driver tab and select Roll Back Driver.
8. Restart the computer.

For a network adapter, also inspect its power controls:

1. Return to the adapter’s Properties dialog.
2. Open Power Management if the tab is available.

3. Select Allow the computer to turn off this device to save power.
4. Clear Allow this device to wake the computer temporarily.

5. Select OK and test sleep.

Some adapters place similar controls under Advanced, with labels such as Wake on Magic Packet or Power Saving Mode. The exact options depend on the adapter and driver.

Fix #8: Identify wake timers and recent wake events

A computer that sleeps and immediately wakes has a different problem from one that never enters sleep. Two powercfg commands can separate those cases.

1. Open Terminal (Admin).
2. Run:

powercfg /waketimers

3. Note any task scheduled to wake the computer.
4. Run:

powercfg /lastwake

5. Check the reported device or wake source.

If a network adapter appears, use the Power Management settings in Fix #7. If a scheduled task appears, open Task Scheduler, find that task, and clear Wake the computer to run this task under Conditions when the wake isn’t needed.

Fix #9: Test a clean boot

A clean boot disables third-party services and startup apps without removing them. Use it when the hardware tests pass but an unnamed background program still blocks sleep.

1. Press Windows + R.
2. Type msconfig and press Enter.
3. Open the Services tab.
4. Select Hide all Microsoft services.
5. Select Disable all.
6. Open the Startup tab.
7. Select Open Task Manager.
8. Disable each enabled startup item.
9. Restart Windows and test automatic sleep.

If sleep actually works in a clean boot, re-enable a few services and startup items at a time. Restart after each group until the blocker returns.

After testing, open msconfig, select Normal startup, and restart. Windows should load your regular services again.

Check Event Viewer and recent updates

If the fixes above don’t identify the cause, Event Viewer can expose a driver or kernel power error recorded when sleep failed.

1. Right-click Start and select Event Viewer.
2. Open Windows Logs > System.
3. Select Filter Current Log.
4. Check Critical, Warning, and Error.
5. Review events recorded around the failed sleep attempt.

Look for a device, driver, or service name repeated at the same time as each failure. Update or roll back that component.

If sleep stopped immediately after a Windows update, open Settings > Windows Update > Update history > Uninstall updates. Remove only the newest update tied to the problem, then restart and test.

Override an SRVNET request only as a last resort

Use this only when powercfg /requests repeatedly names srvnet and you’ve confirmed that no required file transfer or media stream is active. The override lets Windows sleep despite that driver’s system request.

1. Open Terminal (Admin).
2. Run:

powercfg /requestsoverride DRIVER srvnet System

3. Wait for the configured sleep timeout.

To remove the override, run:

powercfg /requestsoverride DRIVER srvnet

I’d skip this step unless srvnet appears consistently. Overriding a legitimate request can interrupt an active network transfer when the computer sleeps.

When the fixes don’t work

Install the latest BIOS or firmware package from your computer manufacturer’s support page, especially if the energy report says a sleep state isn’t supported. A desktop or laptop that freezes, restarts, or loses devices while resuming needs hardware-specific support rather than another Windows setting.

Conclusion

Fix #2, checking powercfg /requests, is the most useful check because it usually names the blocker instead of making you guess. Keep the companion commands handy if sleep problems return; repeated crashes or missing hardware after resume point to a deeper driver, firmware, or hardware fault. Microsoft’s guide to power settings in Windows 11 covers the timeout options in more detail, and our older guide to fixing a Windows 10 PC that won’t sleep has extra checks for that version.