09-20-2019 01:38 PM
So this one is a real puzzler. We have a dozen or so X1 Carbon Gen6 (and a couple of Gen5 machines) that for some reason do not have the "sleep" option in the start menu. I went through all the normal troubleshooting for such a situation (checked Control Panel for the tick box that allows it, checked group policy as well).
We also updated the BIOS to the latest and greatest (regardless that there wasn't any relesase notes that mention Modern Standby or Sleep). We also reset to factory defaults (much to our techs' chagrin as they had to do bitlocker recovery) - but same result.
I checked that "Connected Standby" was also still enabled in Registry (HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Power "CSEnabled")
However, everytime we run powercfg /a - we get this:
Standby (S0 Low Power Idle)
The system firmware does not support this standby state.
And "Sleep" isn't even an option in the control panel settings area and GPO for Show sleep in the power options menu has no effect.
The tougher factor is that these machines had the setting previously before being re-built with same OS via SCCM (Win 10 1803) - and the hardware didn't change.
Anyone else seen their S0 sleep states become unavailable even with updated BIOS/drivers?
09-20-2019 05:04 PM
09-23-2019 08:00 AM
Thanks for the reply, however when doing this step the option for "Sleep" isn't present on the screen and even the drop down for "When I close the Lid" is blank. I'm also thinking this is a larger thing since we also have a Desktop with the same issue (P330 ThinkStation).
09-23-2019 11:07 AM
09-24-2019 08:19 AM
Thanks again for the assistance.
Sadly this did not make a difference.
I do think it might be a GPO however, as I unjoined some of the machiens from the domain and after reboot, the sleep option came back.
Going to have to do a line by line compare since something must have changed to cause it to hide the sleep option despite it being enabled everywhere else.
09-24-2019 01:47 PM
Spoke too soon! The result I got when removing GPO was actually that S3 got re-enabled (we disable as part of MBAM/Bitlocker policies) but the S0 is still in a 'disabled' state.
Any other thoughts?
09-24-2019 02:01 PM
09-24-2019 02:34 PM
We're on the same wavelength it seems. I had just downloaded the Win10 1903 USB creation tool and am installing now on one of the impacted machines.
I'll see how it goes with that and report back.
This test would also rule out SCCM (if it fails) since it'd be a completely isolated machine from our infrastructure (not AD joined etc).