I get the impression this is something that people were seeing a couple of years ago, but was believed to be no longer an issue? Unfortunately, it is apparently still around.
My new laptop running Windows 11 reliably either fully powers down in sleep, or hard reboots coming out of sleep, or something along those lines. The behavior is that I lift the lid to start using it, nothing lights up, I press the power button, and the full POST / boot sequence kicks off.
It isn’t shutting down due to low battery - this is happening while it’s plugged in to AC power. The “Power mode” setting is still in its factory-default “Balanced” state, and the “Screen and sleep” settings are also at their defaults.
The default “Screen and sleep” setting for “When plugged in, put my device to sleep after…” setting is 5 minutes - I’ll experiment with turning that off entirely, to see if that helps, but of course that shouldn’t matter…
Framework Laptop 12th Gen Intel Core (brand new)
Windows 11 22H2 (OS Build 22621.1105)
2 and 3 - ha, you presume that I know what you’re talking about
By “event manager” do you mean the Event Viewer? In the “System” logs section I do see things like an Error from EventLog that says simply “The previous system shutdown at 9:09:39 AM on 2/13/2023 was unexpected”. The only log entry around that time is apparently just like a bajillion others all the time, an “Information” level note that process c:…\WUDFHost.exe reset policy scheme from [hashmess] to [same hashmess].
It never occurred to me that Framework would ship me a brand new unhealthy drive; I didn’t even know that “checking NVME health” was even a thing…
Yep, that sounds like the same issue. For the record, turning off the “When plugged in, put my device to sleep after…” behavior in Windows did not fix the issue; it’s still happening. I might try some of the lower-level interventions described in that thread.
According to that thread, it appears to be a combination of hardware misbehavior (Intel chipset / power management) and the way Windows 11 uses it.
@Christopher_Tate What version of the graphics driver are you on currently? This issue reappeared for me recently (after applying various fixes mentioned in the other thread) and it hasn’t happened since I updated the graphics drivers.
For the record, the approach described here in that other thread for setting a registry entry to disable S0 sleep did not fix this shutdown/hard reboot problem for me.
@Tinkererer_Belle if I’m reading the Device Manager properly, the Intel Xe Graphics driver currently on the laptop is version 30.0.101.1314, dated 2/22/2022. Windows Update says there is no more recent driver release available.
@Tinkererer_Belle alas, using Intel’s driver assistant to bring everything to the latest rev still doesn’t help the powering-off issue. If it sits for a day or two, lid down and on AC power, then when I raise the lid the indicator light around the power button is dark, the fingerprint sensor doesn’t read, and pushing the power button clearly kicks off a full power-on sequence from POST.
Thank you for posting this tip. I’ve changed my settings to see if I can reproduce as other solutions have not worked. Sometimes I go for one or two weeks without a shutdown, but then it comes back, always at seemingly random intervals, sometimes twice in a day.
May I ask how long you have gone since making changes on your system without a reboot?
i had same issues. and i was able to finally resolve it by turning off ‘automatically restart’ in ‘system properties’ > ‘advanced’ > ‘startup and recovery’ > ‘setting’
This issue sounds like the behavior of S0, which is a sleep state. Why this hasn’t really been mentioned in this thread yet is weird.
Basically in Windows battery drain under S0 is high. S0 on Windows works in such a way that when 5% of your battery is drained it will AUTOMATICALLY hibernate. For people not aware of this functionality it will show a laptop that should be sleeping as posting as if you were cold booting. Couple this with the unusually high power drain during S0 sleep and it is confusing.
However, switching your laptop to S3 in Windows, and ensuring that the hibernate after time in advanced power settings is disabled will allow you to suspend until the battery dies.
What haha is talking about with disabling fast startup (which is something I recommend everyone disable, but for different reasons) has nothing to do with this issue.
Thanks for your input and agree @haha’s latest fix is unrelated. The behavior is exactly the same as pressing the power button for 10 seconds and forcing a power-off shutdown.
Do you have a suggestion other than switching to S3 (doesn’t appear possible on this Gen 12 board, see end of post)?
Note the shutdown happens randomly while the laptop is connected to AC power. Occasionally it is left overnight unplugged and correctly has entered hibernation (power button not lit) and comes back to its previous state as expected when powered back on, although I’ve now disabled fast startup as you recommend.
P.S. I tried the previous @haha fix related to preventing the SSD from sleeping, and that greatly reduce the frequency of the problem but did not provide a fix. Took your advice and disabled fast startup as well as automatic restart as I don’t need either but agree they are unrelated.
C:\>powercfg /a
The following sleep states are available on this system:
Standby (S0 Low Power Idle) Network Connected
Hibernate
Fast Startup
The following sleep states are not available on this system:
Standby (S1)
The system firmware does not support this standby state.
This standby state is disabled when S0 low power idle is supported.
Standby (S2)
The system firmware does not support this standby state.
This standby state is disabled when S0 low power idle is supported.
Standby (S3)
This standby state is disabled when S0 low power idle is supported.
You will need to add a registry entry item to suppress S0 and allow Windows to use S3. I have a 12th gen mainboard as well, and S3 works on it. It is just not the default option Windows wants to use.
These are instructions to do that. Please note that while S3 seems to work for me, Framework engineers have stated that S3 is not officially supported.
Set CsEnabled to 0 to disable Connected Standby (S0).
Reboot the system.
You could also look into setting S0 to network disconnected which makes it so that updates and other such nonsense can’t happen while the computer is supposed to be sleeping. This doesn’t mean, however, that the computer wont semi wake to perform OS maintenance. You can disable this but it is outside of the scope of what we are talking about here.
Thanks for this info, but I think I’ll stick with S0 since S3 isn’t officially supported. Hibernation is working correctly for me the couple of times I’ve been on battery and it has kicked in, and I don’t mind the shorter battery life on S0 as I am most often plugged in while sleeping.
The specific problem I have is an apparent power disconnect at random times while sleeping. All running apps shut down and Edge looses all tabs (although has a Restore button that brings them back). This is identical behavior to holding the power button down for 10+ seconds to get a forced power-off, then pressing the power button again to reboot. Example error from Reliability Monitor when this happens is: "Windows was not properly shut down" / "The previous system shutdown at 4:50:45 AM on 4/25/2025 was unexpected."
I was confused by the email notification I got on this thread which showed a Zongyong_Zou (not @haha) who previously suggested “i resolved this issued by setting “Never” for hard disk / turn off hard disk after” setting, but this account / comment I initially replied to has been removed. Oddly that suggestion is the only suggestion from several threads that provided an apparent improvement in the behavior by significantly lengthening the time between shutdowns during sleep. Unfortunately it isn’t a complete fix (and of course also contributes to the power drain during S0).
On another thread someone suggested disabling the fingerprint reader, and I had tried disabling and removing the driver in Device Manager without any improvement, but in looking in BIOS for a setting to disable network during SO (not found), I noticed that I could disable the fingerprint hardware, so have done that now.
I’ll report back to this thread if I go several months without a power-off shutdown during S0 sleep with the fingerprint hardware disabled in BIOS.
Honestly, you shouldn’t have to disable anything. Your fingerprint sensor is fully compatible with Windows. If you are having issues where the machine is just turning off while it is supposed to be suspending, and you are up to date on Window updates, then I think you should contact support. You may have a hardware defect or failure.
