4 ms·

Is this perhaps an issue with BIOS settings, such as wake on LAN or something else? When Windows hibernates, it turns the PC off. You need to investigate what i

Is this perhaps an issue with BIOS settings, such as wake on LAN or something else? When Windows hibernates, it turns the PC off. You need to investigate what is turning it back on, and I don’t think that’s Windows.

vladvasiliu 4y ago
That particular PC dual-boots windows and Linux. When the PC is either fully off or hibernates under Linux, it never ever turns on on its own. Wake on LAN and bios timers are all disabled. I've already complained about this on some other thread, and a poster talked about some kind of timer that windows activates. I think there's some merit to that because it always turns on at night, I don't remember it turning on during the day. I never went looking for details, since this is only a gaming PC, so it's not that much of a hassle to just turn it off. I'm not confident that an update won't reverse the change.
- LeoNatan25 4y ago
  In that case, you can most likely find it in the event viewer.
  - vladvasiliu 4y ago
    I don't doubt that. But the point is that this is an extremely terrible implementation of whatever it is they are trying to achieve. I've jumped through the obvious hoops of disabling sleep and automatic update installs. If I put my PC to sleep, I want it to stay asleep, I don't want the OS to second-guess me, especially if it's unable to plan for its own configuration that may prevent it from doing what it's doing. To me, this just reeks of a half-assed attempt at copying apple's "power nap" feature. "Yah, let met check your mail while the pc sleeps (who the hell cares?!) or apply random updates". Except that on macOS, you can disable this with an obvious checkbox in an obvious place. Having to sift through event viewer (which for some reason is unbearably slow even on an 8-core Xeon with an NVMe drive) and going spelunking in the registry looking for undocumented settings is so user hostile.
    - LeoNatan25 4y ago
      Sleep has been terrible on Windows for many, many years. Typically, when setting up a PC, in order for it to sleep consistently until _I_ wake it, I have to go into device manager, go over each USB device, and disable it waking the PC. That is a terrible experience that nobody should do. Not sure whether this behavior is due to bad drivers or a bad Windows implementation, and frankly I don’t care. I’ve never seen what you are describing with hibernation, because it just shuts off the PC. But I have little to none experience with Windows 11.
- jakopo87 4y ago
  I think it's the wake timer[0] settings in the energy options. [0]https://www.softwareok.com/?page=Windows/10/Power-Options/11 https://www.softwareok.com/?page=Windows/10/Power-Options/11
mvandermeulen 4y ago
Is it possible that it is resuming from standby prior to hibernation which is causing this?
- vladvasiliu 4y ago
  I don't think so. It's an older PC without the new "s2idle" thing. It's either classic S3 sleep or hibernation. It also doesn't do the Linux kind of "sleep + hibernate" (don't know if that's a thing under windows) because the LED doesn't blink (it blinks for s3) and even if I turn it back on right away, it will go through the whole BIOS POST thing, bootloader, etc. The MB has an internal LED showing its state and it shows the same thing as a full shut down.

vladvasiliu 4y ago

That particular PC dual-boots windows and Linux. When the PC is either fully off or hibernates under Linux, it never ever turns on on its own. Wake on LAN and bios timers are all disabled. I've already complained about this on some other thread, and a poster talked about some kind of timer that windows activates. I think there's some merit to that because it always turns on at night, I don't remember it turning on during the day. I never went looking for details, since this is only a gaming PC, so it's not that much of a hassle to just turn it off. I'm not confident that an update won't reverse the change.

LeoNatan25 4y ago
In that case, you can most likely find it in the event viewer.
- vladvasiliu 4y ago
  I don't doubt that. But the point is that this is an extremely terrible implementation of whatever it is they are trying to achieve. I've jumped through the obvious hoops of disabling sleep and automatic update installs. If I put my PC to sleep, I want it to stay asleep, I don't want the OS to second-guess me, especially if it's unable to plan for its own configuration that may prevent it from doing what it's doing. To me, this just reeks of a half-assed attempt at copying apple's "power nap" feature. "Yah, let met check your mail while the pc sleeps (who the hell cares?!) or apply random updates". Except that on macOS, you can disable this with an obvious checkbox in an obvious place. Having to sift through event viewer (which for some reason is unbearably slow even on an 8-core Xeon with an NVMe drive) and going spelunking in the registry looking for undocumented settings is so user hostile.
  - LeoNatan25 4y ago
    Sleep has been terrible on Windows for many, many years. Typically, when setting up a PC, in order for it to sleep consistently until _I_ wake it, I have to go into device manager, go over each USB device, and disable it waking the PC. That is a terrible experience that nobody should do. Not sure whether this behavior is due to bad drivers or a bad Windows implementation, and frankly I don’t care. I’ve never seen what you are describing with hibernation, because it just shuts off the PC. But I have little to none experience with Windows 11.
jakopo87 4y ago
I think it's the wake timer[0] settings in the energy options. [0]https://www.softwareok.com/?page=Windows/10/Power-Options/11 https://www.softwareok.com/?page=Windows/10/Power-Options/11

mvandermeulen 4y ago

Is it possible that it is resuming from standby prior to hibernation which is causing this?

vladvasiliu 4y ago
I don't think so. It's an older PC without the new "s2idle" thing. It's either classic S3 sleep or hibernation. It also doesn't do the Linux kind of "sleep + hibernate" (don't know if that's a thing under windows) because the LED doesn't blink (it blinks for s3) and even if I turn it back on right away, it will go through the whole BIOS POST thing, bootloader, etc. The MB has an internal LED showing its state and it shows the same thing as a full shut down.