PC won't go to sleep

TenFour

TenFour

New member
Ever since upgrading to 10, every time I come back to my PC the next day, it is awake again. I assume this is because Windows Update has restarted it overnight (I've turned off "Allow wake timers" in the advanced power settings), and it's not automatically going to sleep.

I've set the screen to turn off in one minute, and I've set Sleep to start after one minute. Neither ever happens.

If I do powercfg -requests, it says none for everything. What else could it be?
 
TenFour said:
Ever since upgrading to 10, every time I come back to my PC the next day, it is awake again. I assume this is because Windows Update has restarted it overnight (I've turned off "Allow wake timers" in the advanced power settings), and it's not automatically going to sleep.

I've set the screen to turn off in one minute, and I've set Sleep to start after one minute. Neither ever happens.

If I do powercfg -requests, it says none for everything. What else could it be?
Click to expand...


Is Cortana running in the background "Hey Cortana Shut down PC"
 
Cortana doesn't run in the background unless you enable "hey Contana". The mic device will show up in the power requests.

I suggest you make a new user account to test the timer settings.
 
OK, I tried creating a new account. It still won't sleep when logged into the other account.

I have Cortana turned off.

EDIT: Ok, now something has appeared in powercfg requests:

SYSTEM:
[DRIVER] \FileSystem\srvnet
An active remote client has recently sent requests to this machine.

I read somewhere that I could disable this with this command, but it didn't work:

powercfg -requestsoverride DRIVER \FileSystem\srvnet system
 
Last edited:
You're doing it wrong.:bleh: I had this problem on windows 8.1 before I think it has something to do with homegroup sharing. Try stopping HomeGroup Provider in services. If HomeGroup Listener is running then stop that too. Check the power request after. If it's still listed then try the cmd below

powercfg -requestsoverride DRIVER srvnet system
Click to expand...
If successful you should that process listed under [DRIVER] after using:
powercfg -requestsoverride
Click to expand...
To undo the override simply input the override command without system at the end.
 
Last edited:
I solved my problem. Was my Xbox 360 controller. With it plugged in, no sleep, no monitors turning off, and no screen saver.

Unplug it, and all works as it should. The original suggestion was someone had the problem with a logitech Pro. They suggest if you don't have a controller (joystick, gamepad, etc) plugged in, then look at the other Hid usb devices.


good luck.
 
0091/2 said:
You're doing it wrong.:bleh: I had this problem on windows 8.1 before I think it has something to do with homegroup sharing. Try stopping HomeGroup Provider in services. If HomeGroup Listener is running then stop that too. Check the power request after. If it's still listed then try the cmd below


If successful you should that process listed under [DRIVER] after using:

To undo the override simply input the override command without system at the end.
Click to expand...
This is what I tried. Despite having override on srvnet, it is still making requests occasionally. But right now, nothing. And it still won't sleep.

Capture_zpscodsi7lv.png


I have also tried disabling my Bluetooth and network adapters in devices and that doesn't help.
 
Last edited:
OK, I got it!

I unplugged all USB devices and it went to sleep, so then I tried plugging them in one by one.

It turned out to be an old DualShock-to-USB adapter I got from Radio Shack 10 years ago. I don't use it much so I'll just keep it unplugged.

I don't know why it wasn't showing up in powercfg requests.

Thank you all so much for the advice!
 
TenFour said:
OK, I got it!

I unplugged all USB devices and it went to sleep, so then I tried plugging them in one by one.

It turned out to be an old DualShock-to-USB adapter I got from Radio Shack 10 years ago. I don't use it much so I'll just keep it unplugged.

I don't know why it wasn't showing up in powercfg requests.

Thank you all so much for the advice!
Click to expand...


Great!

Pretty funny, yet concerning if something so simple as 1 piece of hardware plugged into a USB port causes such a problem. Even more concerning is when it is a piece of hardware and drivers made by Microsoft as in my case. If they can't get it right with their own hardware/drivers for their own OS, how the hell can anyone else be expected to get it right. Thank god that their are smarted people out there then Microsoft drones.
 
I was going to suggest (for future reference) that perhaps wake-on-lan was set on your ethernet/wifi adapter. I've had issues with it before, and every new Windows update switches the options back.
 
We are, what, basically 1 month after Win10 release?

I'm pretty sure that a USB driver waking a computer is not so high priority on the old MS radar...

Also can't you just go to Device Manager-> Device -> Properties -> Power Management and untick the "Allow this device to wake the computer" box? If there isn't a box there you might look in the BIOS and change the allowed wake events there. If it is available....

I had it happen to my dad's computer. His was waking with the nic. Did the old 'powercfg lastwake' and found the driver.

'powercfg -devicequery wake_armed' gives you a list of things that can wake your computer. Then you just take that list and turn off the things that you don't want waking the computer.
 
Last edited:
andino said:
We are, what, basically 1 month after Win10 release?

I'm pretty sure that a USB driver waking a computer is not so high priority on the old MS radar...

Also can't you just go to Device Manager-> Device -> Properties -> Power Management and untick the "Allow this device to wake the computer" box? If there isn't a box there you might look in the BIOS and change the allowed wake events there. If it is available....

I had it happen to my dad's computer. His was waking with the nic. Did the old 'powercfg lastwake' and found the driver.

'powercfg -devicequery wake_armed' gives you a list of things that can wake your computer. Then you just take that list and turn off the things that you don't want waking the computer.
Click to expand...


Pretty short sighted opinion don't you think, considering the vast amount of USB devices in use now days, and the majority of all input devices on nearly all computers?

It's not about a usb device waking the computer, it is about usb devices breaking sleep, screen saver, monitor standby, etc. never allowing them to sleep much less using them to wake the pc. (can't wake something that never goes to sleep) yes, I get that it is all part of the same system, but this is a bug that has been around since the release of 8.1. And as in my case, we are talking about xbox 360 controller, a common device that is used by millions.

Controllers and such that are pretty much never used to wake a device and keeping a machine from even entering sleep, or allowing the screensaver to come on is a huge bug and or flaw. What next, will your flash drive break it?

USB devices breaking sleep functions is a huge, and should never be on the low priority list.

You also have to remember, that to you, your solution is simple, but your solution to 99% of the computer users of the world is talking to them in a language that they have never heard before. Your own example proves that. What if your dad did not have you around to fix the problem? A problem that should never be present to start with.

It would be like getting a brand new car, plugging in your Ipod, and the lights never turning off afterwards... would that be a low priority problem?
 
I had this problem when leaving my DS4 controller plugged in. I agree its stupid, a game controller or any other USB device should not stop the PC from going to sleep.
 
So actually, it's not fixed. I only got the monitor to turn off on its own. The computer still won't sleep.
 
You must log in or register to reply here.
Back
Top