Windows 10: Black screen every Thursday, PC quit sleeping this past week.

Please follow my instructions on Disabling Windows Driver Updates. Earlier posting. You don't need to be getting the latest and greatest and in a number of instances this causes people a lot of grief.

 

Came home tonight and the sleep situation was the same. Previously, when it went to sleep, it showed 6 watts on the UPS meter. Since this started, it shows about 60 watts, with the monitor off, but apparently the PC remaining on.

 

So with all USB devices unplugged, your keyboard / mouse and USB dongle set to do not wake computer you came home and found your computer awake? Did you run powercfg command to see if same gremlin?

 

I need to get back into your previous ideas, just haven't had time for all that, and have never set a PC back and am nervous about that - about whether it could disrupt programs installed since then.

No, the powercfg /requests is showing nothing.

 

I think command was powercfg /lastwake

To id gremlin or in your case gremlins issuing the wake up.

Hear you. How many programs have you install since December 6th? Sometimes you just got to pull the band aid off.

 

Well the first issue is why it hasnt been going to sleep, since that update a couple of weeks ago. Because there are no requests, I'm wondering if Microsoft programmed something to ignore sleep and keep it awake all the time.

Perhaps I mis-spoke on the wake up. At times, Ive been finding the monitor screen on when I come in, which goes off after 10 minutes.

The PC hasnt slept though.

 

Your powercfg /requests is telling us that nothing is prevent from going to sleep at the time of request.

Have you restore your power plan to defaults.

You may also wish to run powercfg /waketimers
to see if any devices are armed to wake.

Your machine did go to sleep at least once as you ran powercfg /lastwake and you got the message about hub. Force it to sleep and if it awakens see what woke it up. If Microsoft programed something to prevent sleep the Internet would be buzzing.

Try restoring your power plan to defaults, reboot and when you are finished tonight force it to sleep.

 

Ok, I've been busy, but I set the power plan to defaults today, rebooted, then forced sleep. What did it do? Right in front of me, it goes to sleep, I hear the PC click, the wattage on the UPS meter goes low, THEN I hear the drive spinning up again and the screen comes back on!

So I just ran powercfg and got:

 

Here's what you want to see on the Power Management tab for the corresponding device. If you have multiple USB root hubs, make sure this applies to ALL of them.
HTH,
--Ed--

 

Thanks Ed. @EdTtittel

IN my opinion these should all be centralized in Advance Power Mgmt settings under some new heading.

MamaBear as we could be hunting these for a long time, lets head back to powercfg and type

powercfg devicequery wake_armed

and

powercfg devicequery wake_programmable

Windows will then report, to each query, all other items with this ability and we can address as required.

 

Ok, just did a bunch of them and switched them to not allow, like you show, then forced sleep and it did the same thing - shut down and immediately woke back up. Arghh... STILL showing usb root hub as the culprit. WTF???

 

Ok, I just entered both of those, but am not sure how to read the results now. Will try the forced sleep now...

 

Could you print screen prints of results. Basically it should pretty much be blank. You said you shut off a bunch previously, you said you shut of wake timers, you followed Ed's suggestion and shut off more. Would be interesting to see what else Windows says is okay to wake it.

 

This is interesting. The host controller may be on the motherboard itself? I checked this and found that the driver hasnt updated since 2006. Is this PC THAT old? It was refurbed when I bought it, but I don't recall the year.

 

The controller is indeed on MB. Lots of old drivers are still in use. You could try updating driver but make a restore point before you do this.