-
×InformationNeed Windows 11 help?Check documents on compatibility, FAQs, upgrade information and available fixes.
Windows 11 Support Center. -
-
×InformationNeed Windows 11 help?Check documents on compatibility, FAQs, upgrade information and available fixes.
Windows 11 Support Center. -
- HP Community
- Archived Topics
- Unanswered Topics - Notebook
- Strange sleep/hibernate behaviour

Create an account on the HP Community to personalize your profile and ask a question

10-15-2020 01:07 AM
Hi,
I've just bought a Zbook Studio G7, and I'm having issues when I try to put the system to sleep using the 'sleep' key on a Logitech MX Keys bluetooth keyboard. I'm running Windows 10 Pro version 2004. All drivers are up to date.
When I press the sleep key on the keyboard, the system hibernates, instead of going to sleep. If I choose sleep from the start menu it sleeps as expected. I've tried disabling hibernate completely using 'powercfg.exe /hibernate off'. If I then press the sleep key, nothing happens. No sleep or hibernate. Turn hibernate back on, and it's back to how it was before.
I also tried creating a desktop sleep shortcut with the following command'C:\Windows\System32\rundll32.exe powrprof.dll,SetSuspendState 0.1.0'. This behaves in the same way as the sleep key and triggers hibernate. With hibernate disabled, this shortcut does nothing.
I've tried the keyboard on another laptop (Lenovo P50), and it goes to sleep as expected. This laptop is also running Win 10 version 2004. I assume this proves the keyboard is working correctly.
I've checked all the power plan settings, and everything is configured to sleep (power button, closing lid, after timeout etc). All sleep settings are identical to the Lenovo laptop. I don't know if it's relevant, but the Zbook doesn't have any settings for Hybrid sleep like the Lenovo, although it's set to off on the Lenovo. I also have considerably more things available to configure on the Lenovo. I assume HP have limited the power options here.
I don't know if this is an HP problem or Windows problem, and would appreciate any suggestions of how to diagnose further.
Thanks,
Ian.
