XPost: alt.comp.os.windows-11   
   From: winstonmvp@gmail.com   
      
   Maria Sophia wrote on 1/25/2026 1:40 PM:   
      
   > Hi Frank,   
   >   
   > Thanks for requesting me to clarify my situation with this particular   
   > machine with respect to whether hibernation is possible if desired.   
   >   
   > Here is my "powercfg -a" output:   
   > Runbox > cmd {ctrl+shft+rtn} > UAC > Yes   
   > C:\> powercfg -a      The following sleep states are available on this   
   > system:   
   >        Standby (S1 S3)   
   >   
   >       The following sleep states are not available on this system:   
   >        Standby (S2)   
   >       The system firmware does not support this standby state.   
   >   
   >       Hibernate   
   >        Hibernation has not been enabled.   
   >   
   >       Standby (S0 Low Power Idle)   
   >        The system firmware does not support this standby state.   
   >   
   >       Hybrid Sleep   
   >        Hibernation is not available.   
   >   
   >       Fast Startup   
   >        Hibernation is not available.   
   >   
   > At first, I interpreted that to mean Hibernation is not possible, but in   
   > reality, after deeper inspection, that hibernation line is ambiguous unless   
   > I test further, because Windows uses that same wording at different times.   
   > A. Hibernate exists but is disabled because hiberfil.sys is missing   
   > B. Hibernate does not exist because the firmware does not expose S4   
      
   Not really ambiguous.   
     - for the device it shows:   
     Hiberatation is not enabled => it's not turned on   
     Fast Startup/Hibernation not available => Fast Startup, which requires   
   Hibernation, will not be possible because Hibernation is not available   
   for the device.   
      
   Thus, because of space or device constraints and until resolved,   
   hibernation can't be turned on, nor can Fast Startup.   
      
   >   
   > To know for sure, at an admin prompt, I tried to turn it on:   
   > C:\> powercfg /hibernate on   
   >       Hibernation failed with the following error:      There is not   
   > enough space on the disk.   
   >       The following items are preventing hibernation on this system.   
   >       The system could not create the hibernation file.      The   
   specific   
   > error code is 0xc000007f.   
   >   
   > So, as you kindly had suggested, hibernate does exist on my machine.   
   > Windows attempted to enable it, and the firmware did not block it.   
   >   
      
   > Since I have 16GB of RAM, about 16 GB of free space is required for a full   
   > hibernation file, whereas a fast-startup reduced hibernation file might   
   > only require about 40% of my RAM (or 6.4GB free space on the C: drive).   
      
   Not always true.   
      The hibernation file, when enabled on this device with 24 GB RAM and   
   ~123 GB free space(on a 256 SSD) is ~4.7 GB without Fast Startup being   
   enabled.  My Surface device running Win10 Pro with 8 GB RAM, 128 SSD(~65   
   GB free space) with Hibernation enabled and Fast Start not enabled has a   
   4.4 GB hiberation file.   
      
   >   
   > But when I tried to run reduced hibernation just now, I got an error:   
   > C:\> powercfg /hibernate /type reduced   
   >       A device attached to the system is not functioning.   
   > This is not the same as the earlier disk-full error.   
   > This is a device-level failure.   
   >   
   > The most logical reason might be a driver or device reports that it cannot   
   > enter S4 such as an older storage controller or other device that blocks S4   
   > but looking it up shows that it could be a GPU driver that does not support   
   > hibernation or a BIOS ACPI table that is incomplete, or something else.   
   >   
   > Testing which devices can be configured for wake we find a half dozen:   
   > C:\> powercfg -devicequery wake_programmable   
   >       HID-compliant consumer control device (001)   
   >       HID Keyboard Device (001)   
   >       HID-compliant mouse   
   >       HID-compliant system controller   
   >       Realtek PCIe GbE Family Controller   
   >       HID-compliant consumer control device (004)   
   >   
   > Testing what devices are allowed to wake the system, we find 3 of them:   
   > C:\> powercfg -devicequery wake_armed   
   >       HID Keyboard Device (001)   
   >       HID-compliant mouse   
   >       Realtek PCIe GbE Family Controller   
   >   
   > One by one I could disable each of those devices, and then re-try reduced   
   > hibernation, but this doesn't change that the system is unstable with it.   
   >   
   > Personally, my use model fits me just fine where I shut down the system,   
   > and separately I power down my astoundingly huge but old monitor each   
   > night. In the morning, I power up the computer and go make myself a coffee.   
   >   
   > While it works for me, the point of this thread was to survey what works   
   > for other people, where our combined city/highway mileage may vary   
   > depending on what works best with our particular system components.   
   >   
   > I'm not going to dig further (because I don't want hibernation anyway),   
   > but I do thank you for asking me to dig deeper to confirm it does exist.   
      
      
   --   
   ...w¡ñ§±¤ñ   
      
   --- SoupGate-Win32 v1.05   
    * Origin: you cannot sedate... all the things you hate (1:229/2)