Windows 10: Power Button Sleep Stops Working Until Restart in Windows 10

I upgraded to Windows 10 from 7. Since the update I've run into an issue where, after I've been using my computer for a while and have done a few sleep/wake cycles, I won't be able to put my computer to sleep with the physical power button. It wakes up just fine with the power button. Restarting my computer temporarily resolves the issue.

:)

 

Power Button Sleep Stops Working Until Restart in Windows 10

Thank you for your response. I tried the troubleshooter and the only thing it found was that my sleep and display sleep were too long (they were set to never) so it set them back to a shorter time.

I believe I've narrowed down to issue to when I wake up the computer with the power button, then it won't go to sleep again with the power button. I was mistaken about needing to restart Windows to get the power button to work with sleep again. If I use
the start menu power to sleep because the physical power button isn't putting my computer to sleep, then wake it up with the keyboard, I can then sleep the computer with the power button again.

 

Power Button Sleep Stops Working Until Restart in Windows 10

Hi,

Welcome and thank you for posting your query in Microsoft Community.

As per your issue, I would suggest you to run Power troubleshooter ad check if it helps or not.
The Power Troubleshooter is an automated tool which checks the hardware connected to the computer for any known issues and provides the details on how to fix them. Follow these steps to run the troubleshooter.

• Press “Windows Logo” + “W” keys from the keyboard.
• Type “Troubleshooting” in the search bar and press “Enter”.
• In the “Troubleshooting” window, click on “View All” on the left pane.
• Click on “Power”.
• Click on “Advanced” and then click on “Run as Administrator”.
• Click “Next” and follow the on-screen instructions to complete the troubleshooting process.

If this doesn't helps, try making the changes to default and then again make changes to check if the issue occurs or not.

Hope this information helps. Please post us if you need any further assistance with Windows.

Thank you.

 

I have the same issue. I posted previously, but it looks like It got removed, but had no explanation. Probably because I mentioned some software that might not be legit.
I'm still looking into it, but haven't found anything yet.

 

I installed my Windows 7 from an official ISO, so I don't think that's related. I may have just noticed a new symptom, though. I tried to wake my computer this morning using the keyboard. The num lock light on the keyboard came on, but the computer did not wake until I hit the power button.

 

I've tried numerous things. I rebooted, and then pressed power button, it's all okay, I've played a couple games, gone to go to bed, and it's screwed up again. I literally have nothing, and can't find anything with a proper solution!

 

I'm also getting this.

Legit Windows 7 Home install from late 2012 until last week. Power button always put the computer to sleep no problem.

I ran the Windows 10 upgrade, then did a clean format and install. The power button refused to do anything when I tried to sleep it yesterday, so I rebooted and it seemed to work so I chalked it up to a one off. Then it did the same thing again this morning. It seems to sleep okay from the start menu, but this is very annoying.

 

Anyone? :[

I tried powering down the whole system instead of sleeping, then powering back on, leaving it for 24h and the power button DID put it to sleep after all that, so it appears it can do one sleep/resume before it stops working. No idea what would cause this and I don't really want to try BIOS updating for something that appears to be exclusively a problem with Windows.

 

It seems the upgrade from Windows 7 isn't related. I did a clean install from an ISO I made with the Windows Media Creation Tool, and the issue is still there. I submitted the bug using the Windows Feedback app built in to Windows 10. If those of you with the same issue want to upvote it, you can find it by searching the feedback app for "physical power button on my computer" with the quotes.

 

Thanks for updating. Hibernate seems to work consistently, though it crashes video drivers.

I tried disabling deep sleep (suspend to memory), and I think it worked, though it doesn't turn the fans off, which defeats some of the point. I also get the following error in the event viewer resuming from deep sleep (the one I can do only once per reboot):

Kernel Power

The system firmware has changed the processor's memory type range registers (MTRRs) across a sleep state transition (S4). This can result in reduced resume performance.Event ID: 137.

 

I'm not getting any events with ID 137. The only two kernel-power source events I'm seeing are when it goes to sleep and mentions the cause is power button or lid, and then the wake event which says "Firmware S3 times. ResumeCount: 1, FullResume: 967, AverageResume: 967".

 

I believe I've narrowed down to issue to when I wake up the computer with the power button, then it won't go to sleep again with the power button. I was mistaken about needing to restart Windows to get the power button to work with sleep again. If I use the start menu power to sleep because the physical power button isn't putting my computer to sleep, then wake it up with the keyboard, I can then sleep the computer with the power button again.

Can anyone confirm their computer is behaving the same way?

 

Yes, Mine is Identical.

I still haven't found anything remotly pointing to the problem. Me and 3 other of my techie friends looked at it, and they literally couldn't figure it out.
It's just one of those things I guess but I reckon a re-install of the OS will solve the issue.

 

I don't believe reinstalling Windows will fix the issue. I did a clean install and my computer still has the issue. I think this is an issue Microsoft will have to fix.

 

Interesting.
I've seen some users state to disable the "allow device to wake up computer" for a few devices, IE network card and stuff, and they seem to think that there is some form of "Interrupt" happening and stopping it from doing so.
I'll perform some tests.