• How to fully shutdown your machine with Shutdown

    From micky@3:633/10 to All on Thursday, January 22, 2026 18:26:57

    I suppose most of the readers of these newsgroups know that for a full
    start from scratch it's required to run Restart, instead of Shutdown
    followed by starting later. Even though I only learned this a year ago
    and even though it's a bit counter-intuitive, you all know that, right, (because if you're running with Fast Startup*** shutdown saves the
    kernel and reuses it, but Restart never uses Fast Startup and it
    rebuilds the kernel, with new values if the values have changed).

    But maybe you did not know that you can get the benefit of Restart and
    still turn your machine off if you press Shift while clicking on
    Shutdown. How about that!!

    At least that's what this guy says https://www.pdq.com/blog/restart-vs-shutdown/

    ***which I believe is the default now, and which saves time starting up,
    and everyone likes to save time. Although it doesn't save as much time
    with solid state drives as it does with spinners

    --- PyGate Linux v1.5.2
    * Origin: Dragon's Lair, PyGate NNTP<>Fido Gate (3:633/10)
  • From ...w¡ñ?±?ñ@3:633/10 to All on Friday, January 23, 2026 00:44:00
    micky wrote on 1/22/2026 4:26 PM:

    I suppose most of the readers of these newsgroups know that for a full
    start from scratch it's required to run Restart, instead of Shutdown
    followed by starting later. Even though I only learned this a year ago
    and even though it's a bit counter-intuitive, you all know that, right, (because if you're running with Fast Startup*** shutdown saves the
    kernel and reuses it, but Restart never uses Fast Startup and it
    rebuilds the kernel, with new values if the values have changed).

    But maybe you did not know that you can get the benefit of Restart and
    still turn your machine off if you press Shift while clicking on
    Shutdown. How about that!!


    If Hibernation (and by extension, Fast Startup) is disabled (e.g., via powercfg -h off), the "Shutdown" button functions as a full, traditional shutdown - clears the system state(shuts down all processes) and clears
    temp memory and powers Off. Subsequent Powering on, re-initializes the o/s
    - which, incidentally is the same results as Shift-Shutdown.
    i.e. you don't need to the keystroke combo if Hibernation is disabled.

    Restart(when Hiberation is disabled) does the exact same clearing but
    instead of shutting down, powers the device back on and re-initializes
    the o/s.


    --
    ...w­¤?ñ?¤

    --- PyGate Linux v1.5.2
    * Origin: Dragon's Lair, PyGate NNTP<>Fido Gate (3:633/10)
  • From Hank Rogers@3:633/10 to All on Friday, January 23, 2026 18:19:15
    ...w??? wrote on 1/23/2026 1:44 AM:
    micky wrote on 1/22/2026 4:26 PM:

    I suppose most of the readers of these newsgroups know that for a full
    start from scratch it's required to run Restart, instead of Shutdown
    followed by starting later.? Even though I only learned this a year ago
    and even though it's a bit counter-intuitive, you all know that, right,
    (because if you're running with Fast Startup*** shutdown saves the
    kernel and reuses it, but Restart never uses Fast Startup and it
    rebuilds the kernel, with new values if the values have changed).

    But maybe you did not know that you can get the benefit of Restart and
    still turn your machine off if you press Shift while clicking on
    Shutdown.?? How about that!!


    If Hibernation (and by extension, Fast Startup) is disabled (e.g., via powercfg -h off), the "Shutdown" button functions as a full, traditional shutdown - clears the system state(shuts down all processes) and clears
    temp memory and powers Off. Subsequent Powering on, re-initializes the o/s
    ?- which, incidentally is the same results as Shift-Shutdown.
    ?i.e. you don't need to the keystroke combo if Hibernation is disabled.

    Restart(when Hiberation is disabled) does the exact same clearing but instead of shutting down, powers the device back on and re-initializes
    the o/s.



    Exactly. And it's the best setting you can choose.





    --- PyGate Linux v1.5.2
    * Origin: Dragon's Lair, PyGate NNTP<>Fido Gate (3:633/10)
  • From Jeff Barnett@3:633/10 to All on Saturday, January 24, 2026 09:07:48
    On 1/23/2026 12:44 AM, ...w­¤?ñ?¤ wrote:
    micky wrote on 1/22/2026 4:26 PM:

    I suppose most of the readers of these newsgroups know that for a full
    start from scratch it's required to run Restart, instead of Shutdown
    followed by starting later.ÿ Even though I only learned this a year ago
    and even though it's a bit counter-intuitive, you all know that, right,
    (because if you're running with Fast Startup*** shutdown saves the
    kernel and reuses it, but Restart never uses Fast Startup and it
    rebuilds the kernel, with new values if the values have changed).

    But maybe you did not know that you can get the benefit of Restart and
    still turn your machine off if you press Shift while clicking on
    Shutdown.ÿÿ How about that!!


    If Hibernation (and by extension, Fast Startup) is disabled (e.g., via powercfg -h off), the "Shutdown" button functions as a full, traditional shutdown - clears the system state(shuts down all processes) and clears
    temp memory and powers Off. Subsequent Powering on, re-initializes the o/s
    ÿ- which, incidentally is the same results as Shift-Shutdown.
    ÿi.e. you don't need to the keystroke combo if Hibernation is disabled.

    Restart(when Hiberation is disabled) does the exact same clearing but instead of shutting down, powers the device back on and re-initializes
    the o/s.
    I have Hibernation set to never in my power profile. However, I have an
    APC UPS that will hibernate the machine in case of an extended power
    outage; in other words, the APC software is able to work around that
    setting. Does this setup change anything said in this thread so far?
    --
    Jeff Barnett



    --- PyGate Linux v1.5.5
    * Origin: Dragon's Lair, PyGate NNTP<>Fido Gate (3:633/10)
  • From ...w¡ñ?±?ñ@3:633/10 to All on Saturday, January 24, 2026 10:07:32
    Jeff Barnett wrote on 1/24/2026 9:07 AM:
    On 1/23/2026 12:44 AM, ...w­¤?ñ?¤ wrote:
    micky wrote on 1/22/2026 4:26 PM:

    I suppose most of the readers of these newsgroups know that for a full
    start from scratch it's required to run Restart, instead of Shutdown
    followed by starting later.ÿ Even though I only learned this a year ago
    and even though it's a bit counter-intuitive, you all know that, right,
    (because if you're running with Fast Startup*** shutdown saves the
    kernel and reuses it, but Restart never uses Fast Startup and it
    rebuilds the kernel, with new values if the values have changed).

    But maybe you did not know that you can get the benefit of Restart and
    still turn your machine off if you press Shift while clicking on
    Shutdown.ÿÿ How about that!!


    If Hibernation (and by extension, Fast Startup) is disabled (e.g., via
    powercfg -h off), the "Shutdown" button functions as a full,
    traditional shutdown - clears the system state(shuts down all
    processes) and clears temp memory and powers Off. Subsequent Powering
    on, re-initializes the o/s
    ÿÿ- which, incidentally is the same results as Shift-Shutdown.
    ÿÿi.e. you don't need to the keystroke combo if Hibernation is disabled.

    Restart(when Hiberation is disabled) does the exact same clearing but
    instead of shutting down, powers the device back on and re-initializes
    the o/s.
    I have Hibernation set to never in my power profile. However, I have an
    APC UPS that will hibernate the machine in case of an extended power
    outage; in other words, the APC software is able to work around that setting. Does this setup change anything said in this thread so far?

    Afaik, the UPS Hibernation feature requires enabling Windows hibernation.
    i.e. When a power outage occurs, the UPS has to communicate with
    Windows and validate Windows hibernation state(enabled/disabled), if
    enabled instruct Windows to hibernate, once done the UPS provides backup battery power for the duration of its capability.

    Lacking Windows hibernation, the UPS only provides battery power for the device(and Windows) for the duration of its backup battery capability.
    - no Windows hibernation

    --
    ...w­¤?ñ?¤

    --- PyGate Linux v1.5.5
    * Origin: Dragon's Lair, PyGate NNTP<>Fido Gate (3:633/10)
  • From Paul@3:633/10 to All on Saturday, January 24, 2026 12:48:02
    On Sat, 1/24/2026 11:07 AM, Jeff Barnett wrote:
    On 1/23/2026 12:44 AM, ...w­¤?ñ?¤ wrote:
    micky wrote on 1/22/2026 4:26 PM:

    I suppose most of the readers of these newsgroups know that for a full
    start from scratch it's required to run Restart, instead of Shutdown
    followed by starting later.ÿ Even though I only learned this a year ago
    and even though it's a bit counter-intuitive, you all know that, right,
    (because if you're running with Fast Startup*** shutdown saves the
    kernel and reuses it, but Restart never uses Fast Startup and it
    rebuilds the kernel, with new values if the values have changed).

    But maybe you did not know that you can get the benefit of Restart and
    still turn your machine off if you press Shift while clicking on
    Shutdown.ÿÿ How about that!!


    If Hibernation (and by extension, Fast Startup) is disabled (e.g., via powercfg -h off), the "Shutdown" button functions as a full, traditional shutdown - clears the system state(shuts down all processes) and clears temp memory and powers Off. Subsequent Powering on, re-initializes the o/s
    ÿÿ- which, incidentally is the same results as Shift-Shutdown.
    ÿÿi.e. you don't need to the keystroke combo if Hibernation is disabled.

    Restart(when Hiberation is disabled) does the exact same clearing but instead of shutting down, powers the device back on and re-initializes the o/s.
    I have Hibernation set to never in my power profile. However, I have an APC UPS that will hibernate the machine in case of an extended power outage; in other words, the APC software is able to work around that setting. Does this setup change anything said in this thread so far?

    To do hibernation, as demanded by a single character sent across
    a UPS link, you need

    # As Administrator

    powercfg /h on

    That creates a C:\hiberfil.sys

    In a Command Prompt (cmd.exe) you can do:

    C:\
    cd \
    dir /ah

    and it should show any hidden items in the root of C: .

    You should test Hibernate from the Windows menu, and
    that should help you verify that any attempt by the
    UPS software, the wheels are greased for it to work.

    If hibernate is missing at menu level, ticking the box
    to bring it back, is here.

    https://www.windowsdigitals.com/wp-content/uploads/Change-settings-that-are-currently-unavailable-Windows-11.png

    Paul

    --- PyGate Linux v1.5.5
    * Origin: Dragon's Lair, PyGate NNTP<>Fido Gate (3:633/10)
  • From Jeff Barnett@3:633/10 to All on Saturday, January 24, 2026 12:56:35
    On 1/24/2026 10:07 AM, ...w­¤?ñ?¤ wrote:
    Jeff Barnett wrote on 1/24/2026 9:07 AM:
    On 1/23/2026 12:44 AM, ...w­¤?ñ?¤ wrote:
    micky wrote on 1/22/2026 4:26 PM:

    I suppose most of the readers of these newsgroups know that for a full >>>> start from scratch it's required to run Restart, instead of Shutdown
    followed by starting later.ÿ Even though I only learned this a year ago >>>> and even though it's a bit counter-intuitive, you all know that, right, >>>> (because if you're running with Fast Startup*** shutdown saves the
    kernel and reuses it, but Restart never uses Fast Startup and it
    rebuilds the kernel, with new values if the values have changed).

    But maybe you did not know that you can get the benefit of Restart and >>>> still turn your machine off if you press Shift while clicking on
    Shutdown.ÿÿ How about that!!


    If Hibernation (and by extension, Fast Startup) is disabled (e.g.,
    via powercfg -h off), the "Shutdown" button functions as a full,
    traditional shutdown - clears the system state(shuts down all
    processes) and clears temp memory and powers Off. Subsequent Powering
    on, re-initializes the o/s
    ÿÿ- which, incidentally is the same results as Shift-Shutdown.
    ÿÿi.e. you don't need to the keystroke combo if Hibernation is disabled. >>>
    Restart(when Hiberation is disabled) does the exact same clearing but
    instead of shutting down, powers the device back on and re-
    initializes the o/s.
    I have Hibernation set to never in my power profile. However, I have
    an APC UPS that will hibernate the machine in case of an extended
    power outage; in other words, the APC software is able to work around
    that setting. Does this setup change anything said in this thread so far?

    Afaik, the UPS Hibernation feature requires enabling Windows hibernation.
    ÿi.e. When a power outage occurs, the UPS has to communicate with
    Windows and validate Windows hibernation state(enabled/disabled), if
    enabled instruct Windows to hibernate, once done the UPS provides backup battery power for the duration of its capability.

    Lacking Windows hibernation, the UPS only provides battery power for the device(and Windows) for the duration of its backup battery capability.
    ÿ - no Windows hibernation

    I've not enabled hibernation (as said above) but the APC software seems
    to be able to do it anyway. Perhaps it changes the power profile when necessary. I remember one of the disk tester/diagnostic packages that
    turned sleep off when it was called and never bothered to restore it on
    its way out. So there is certainly some way to diddle the settings.
    --
    Jeff Barnett



    --- PyGate Linux v1.5.5
    * Origin: Dragon's Lair, PyGate NNTP<>Fido Gate (3:633/10)
  • From ...w¡ñ?±?ñ@3:633/10 to All on Saturday, January 24, 2026 17:37:42
    Jeff Barnett wrote on 1/24/2026 12:56 PM:
    On 1/24/2026 10:07 AM, ...w­¤?ñ?¤ wrote:
    Jeff Barnett wrote on 1/24/2026 9:07 AM:
    On 1/23/2026 12:44 AM, ...w­¤?ñ?¤ wrote:
    micky wrote on 1/22/2026 4:26 PM:

    I suppose most of the readers of these newsgroups know that for a full >>>>> start from scratch it's required to run Restart, instead of Shutdown >>>>> followed by starting later.ÿ Even though I only learned this a year ago >>>>> and even though it's a bit counter-intuitive, you all know that, right, >>>>> (because if you're running with Fast Startup*** shutdown saves the
    kernel and reuses it, but Restart never uses Fast Startup and it
    rebuilds the kernel, with new values if the values have changed).

    But maybe you did not know that you can get the benefit of Restart and >>>>> still turn your machine off if you press Shift while clicking on
    Shutdown.ÿÿ How about that!!


    If Hibernation (and by extension, Fast Startup) is disabled (e.g.,
    via powercfg -h off), the "Shutdown" button functions as a full,
    traditional shutdown - clears the system state(shuts down all
    processes) and clears temp memory and powers Off. Subsequent Powering >>>> on, re-initializes the o/s
    ÿÿ- which, incidentally is the same results as Shift-Shutdown.
    ÿÿi.e. you don't need to the keystroke combo if Hibernation is disabled. >>>>
    Restart(when Hiberation is disabled) does the exact same clearing but >>>> instead of shutting down, powers the device back on and re-
    initializes the o/s.
    I have Hibernation set to never in my power profile. However, I have
    an APC UPS that will hibernate the machine in case of an extended
    power outage; in other words, the APC software is able to work around
    that setting. Does this setup change anything said in this thread so far? >>
    Afaik, the UPS Hibernation feature requires enabling Windows hibernation.
    ÿÿi.e. When a power outage occurs, the UPS has to communicate with
    Windows and validate Windows hibernation state(enabled/disabled), if
    enabled instruct Windows to hibernate, once done the UPS provides
    backup battery power for the duration of its capability.

    Lacking Windows hibernation, the UPS only provides battery power for
    the device(and Windows) for the duration of its backup battery capability. >> ÿÿ - no Windows hibernation

    I've not enabled hibernation (as said above) but the APC software seems
    to be able to do it anyway. Perhaps it changes the power profile when necessary. I remember one of the disk tester/diagnostic packages that
    turned sleep off when it was called and never bothered to restore it on
    its way out. So there is certainly some way to diddle the settings.

    See Paul's response, that echo's my input.
    => Hibernation needs to be enabled in Windows.

    --
    ...w­¤?ñ?¤

    --- PyGate Linux v1.5.5
    * Origin: Dragon's Lair, PyGate NNTP<>Fido Gate (3:633/10)
  • From Jeff Barnett@3:633/10 to All on Saturday, January 24, 2026 18:29:16
    On 1/24/2026 5:37 PM, ...w­¤?ñ?¤ wrote:
    Jeff Barnett wrote on 1/24/2026 12:56 PM:
    On 1/24/2026 10:07 AM, ...w­¤?ñ?¤ wrote:
    Jeff Barnett wrote on 1/24/2026 9:07 AM:
    On 1/23/2026 12:44 AM, ...w­¤?ñ?¤ wrote:
    micky wrote on 1/22/2026 4:26 PM:

    I suppose most of the readers of these newsgroups know that for a >>>>>> full
    start from scratch it's required to run Restart, instead of Shutdown >>>>>> followed by starting later.ÿ Even though I only learned this a
    year ago
    and even though it's a bit counter-intuitive, you all know that,
    right,
    (because if you're running with Fast Startup*** shutdown saves the >>>>>> kernel and reuses it, but Restart never uses Fast Startup and it
    rebuilds the kernel, with new values if the values have changed).

    But maybe you did not know that you can get the benefit of Restart >>>>>> and
    still turn your machine off if you press Shift while clicking on
    Shutdown.ÿÿ How about that!!


    If Hibernation (and by extension, Fast Startup) is disabled (e.g.,
    via powercfg -h off), the "Shutdown" button functions as a full,
    traditional shutdown - clears the system state(shuts down all
    processes) and clears temp memory and powers Off. Subsequent
    Powering on, re-initializes the o/s
    ÿÿ- which, incidentally is the same results as Shift-Shutdown.
    ÿÿi.e. you don't need to the keystroke combo if Hibernation is
    disabled.

    Restart(when Hiberation is disabled) does the exact same clearing
    but instead of shutting down, powers the device back on and re-
    initializes the o/s.
    I have Hibernation set to never in my power profile. However, I have
    an APC UPS that will hibernate the machine in case of an extended
    power outage; in other words, the APC software is able to work
    around that setting. Does this setup change anything said in this
    thread so far?

    Afaik, the UPS Hibernation feature requires enabling Windows
    hibernation.
    ÿÿi.e. When a power outage occurs, the UPS has to communicate with
    Windows and validate Windows hibernation state(enabled/disabled), if
    enabled instruct Windows to hibernate, once done the UPS provides
    backup battery power for the duration of its capability.

    Lacking Windows hibernation, the UPS only provides battery power for
    the device(and Windows) for the duration of its backup battery
    capability.
    ÿÿ - no Windows hibernation

    I've not enabled hibernation (as said above) but the APC software
    seems to be able to do it anyway. Perhaps it changes the power profile
    when necessary. I remember one of the disk tester/diagnostic packages
    that turned sleep off when it was called and never bothered to restore
    it on its way out. So there is certainly some way to diddle the settings.

    See Paul's response, that echo's my input.
    Hibernation needs to be enabled in Windows.

    I believe (from my own experience) that Paul is incorrect in this
    specific case. The APC software (OS level stuff) can when it decides
    it's time to shutdown because of battery drain, etc, can arrange that hibernation works whether the user has enabled it or not. I've noted
    it's happening a few times.
    --
    Jeff Barnett



    --- PyGate Linux v1.5.5
    * Origin: Dragon's Lair, PyGate NNTP<>Fido Gate (3:633/10)
  • From Paul@3:633/10 to All on Saturday, January 24, 2026 21:23:15
    On Sat, 1/24/2026 8:29 PM, Jeff Barnett wrote:
    On 1/24/2026 5:37 PM, ...w­¤?ñ?¤ wrote:
    Jeff Barnett wrote on 1/24/2026 12:56 PM:
    On 1/24/2026 10:07 AM, ...w­¤?ñ?¤ wrote:
    Jeff Barnett wrote on 1/24/2026 9:07 AM:
    On 1/23/2026 12:44 AM, ...w­¤?ñ?¤ wrote:
    micky wrote on 1/22/2026 4:26 PM:

    I suppose most of the readers of these newsgroups know that for a full >>>>>>> start from scratch it's required to run Restart, instead of Shutdown >>>>>>> followed by starting later.ÿ Even though I only learned this a year ago >>>>>>> and even though it's a bit counter-intuitive, you all know that, right, >>>>>>> (because if you're running with Fast Startup*** shutdown saves the >>>>>>> kernel and reuses it, but Restart never uses Fast Startup and it >>>>>>> rebuilds the kernel, with new values if the values have changed). >>>>>>>
    But maybe you did not know that you can get the benefit of Restart and >>>>>>> still turn your machine off if you press Shift while clicking on >>>>>>> Shutdown.ÿÿ How about that!!


    If Hibernation (and by extension, Fast Startup) is disabled (e.g., via powercfg -h off), the "Shutdown" button functions as a full, traditional shutdown - clears the system state(shuts down all processes) and clears temp memory and powers Off. Subsequent Powering on, re-initializes the o/s
    ÿÿ- which, incidentally is the same results as Shift-Shutdown.
    ÿÿi.e. you don't need to the keystroke combo if Hibernation is disabled. >>>>>>
    Restart(when Hiberation is disabled) does the exact same clearing but instead of shutting down, powers the device back on and re- initializes the o/s.
    I have Hibernation set to never in my power profile. However, I have an APC UPS that will hibernate the machine in case of an extended power outage; in other words, the APC software is able to work around that setting. Does this setup change anything said in this thread so far?

    Afaik, the UPS Hibernation feature requires enabling Windows hibernation. >>>> ÿÿi.e. When a power outage occurs, the UPS has to communicate with Windows and validate Windows hibernation state(enabled/disabled), if enabled instruct Windows to hibernate, once done the UPS provides backup battery power for the duration of its capability.

    Lacking Windows hibernation, the UPS only provides battery power for the device(and Windows) for the duration of its backup battery capability.
    ÿÿ - no Windows hibernation

    I've not enabled hibernation (as said above) but the APC software seems to be able to do it anyway. Perhaps it changes the power profile when necessary. I remember one of the disk tester/diagnostic packages that turned sleep off when it was called and never bothered to restore it on its way out. So there is certainly some way to diddle the settings.

    See Paul's response, that echo's my input.
    Hibernation needs to be enabled in Windows.

    I believe (from my own experience) that Paul is incorrect in this specific case. The APC software (OS level stuff) can when it decides it's time to shutdown because of battery drain, etc, can arrange that hibernation works whether the user has enabled it or not. I've noted it's happening a few times.

    I think there has to be a hiberfile (C:\hiberfil.sys) and
    it is typically equal in size to 50% of memory or a larger
    percentage. Via compression, the RAM content written out to
    the hiberfile is smaller than the physical size. Most sessions
    on Windows are quite small, so only a fraction of the reserved
    hiberfile space is used.

    powercfg /a # check supported ACPI states.
    # Hibernation is S4. Mine is disabled right now.
    # A shutdown /h would generate an error of some sort.

    powercfg /h on # Add Hibernation, then verify with the first command
    # Check for hidden file on the root of C: with dir /ah in command prompt

    There is also some procedure at startup, which may be writing
    something to the header of the hiberfile. The hiberfile is "invalidated"
    as part of startup, such that it cannot be reused immediately to
    restore the same session ("like it was GroundHog day").

    Otherwise, without using the hibernation feature, little in the
    way of wear, happens because of the existence of the hiberfile.

    If you were installing the APC software, it is possible there is
    sufficient elevation at install time, for the APC software to be
    using powercfg and switching the hiberfile on and reserving the
    necessary space.

    Once the hiberfile exists, the normal set of system commands
    should work, to generate a hiberfile. The command from the UPS
    should be terse -- it isn't always a super-intelligent processing
    thing. Any application loaded into the host OS, has to do the
    more intelligent part. The UPS should not be sending this
    command, as written. That would be an exploit waiting to happen.

    shutdown /h

    Paul

    --- PyGate Linux v1.5.5
    * Origin: Dragon's Lair, PyGate NNTP<>Fido Gate (3:633/10)
  • From ...w¡ñ?±?ñ@3:633/10 to All on Saturday, January 24, 2026 21:04:27
    Jeff Barnett wrote on 1/24/2026 6:29 PM:
    On 1/24/2026 5:37 PM, ...w­¤?ñ?¤ wrote:
    Jeff Barnett wrote on 1/24/2026 12:56 PM:
    On 1/24/2026 10:07 AM, ...w­¤?ñ?¤ wrote:
    Jeff Barnett wrote on 1/24/2026 9:07 AM:
    On 1/23/2026 12:44 AM, ...w­¤?ñ?¤ wrote:
    micky wrote on 1/22/2026 4:26 PM:

    I suppose most of the readers of these newsgroups know that for a >>>>>>> full
    start from scratch it's required to run Restart, instead of Shutdown >>>>>>> followed by starting later.ÿ Even though I only learned this a
    year ago
    and even though it's a bit counter-intuitive, you all know that, >>>>>>> right,
    (because if you're running with Fast Startup*** shutdown saves the >>>>>>> kernel and reuses it, but Restart never uses Fast Startup and it >>>>>>> rebuilds the kernel, with new values if the values have changed). >>>>>>>
    But maybe you did not know that you can get the benefit of Restart >>>>>>> and
    still turn your machine off if you press Shift while clicking on >>>>>>> Shutdown.ÿÿ How about that!!


    If Hibernation (and by extension, Fast Startup) is disabled (e.g., >>>>>> via powercfg -h off), the "Shutdown" button functions as a full,
    traditional shutdown - clears the system state(shuts down all
    processes) and clears temp memory and powers Off. Subsequent
    Powering on, re-initializes the o/s
    ÿÿ- which, incidentally is the same results as Shift-Shutdown.
    ÿÿi.e. you don't need to the keystroke combo if Hibernation is
    disabled.

    Restart(when Hiberation is disabled) does the exact same clearing >>>>>> but instead of shutting down, powers the device back on and re-
    initializes the o/s.
    I have Hibernation set to never in my power profile. However, I have >>>>> an APC UPS that will hibernate the machine in case of an extended
    power outage; in other words, the APC software is able to work
    around that setting. Does this setup change anything said in this
    thread so far?

    Afaik, the UPS Hibernation feature requires enabling Windows
    hibernation.
    ÿÿi.e. When a power outage occurs, the UPS has to communicate with
    Windows and validate Windows hibernation state(enabled/disabled), if
    enabled instruct Windows to hibernate, once done the UPS provides
    backup battery power for the duration of its capability.

    Lacking Windows hibernation, the UPS only provides battery power for
    the device(and Windows) for the duration of its backup battery
    capability.
    ÿÿ - no Windows hibernation

    I've not enabled hibernation (as said above) but the APC software
    seems to be able to do it anyway. Perhaps it changes the power profile
    when necessary. I remember one of the disk tester/diagnostic packages
    that turned sleep off when it was called and never bothered to restore
    it on its way out. So there is certainly some way to diddle the settings. >>
    See Paul's response, that echo's my input.
    Hibernation needs to be enabled in Windows.

    I believe (from my own experience) that Paul is incorrect in this
    specific case. The APC software (OS level stuff) can when it decides it's time to shutdown because of battery drain, etc, can arrange that
    hibernation works whether the user has enabled it or not. I've noted it's happening a few times.

    Laptop or desktop?
    The former has different 'On Battery' Power Options which would seem to
    be necessary and configured with 'Hibernate' for any signal from the UPS
    to communicate a valid request to the device to re-enable Hibernation(if disabled).
    For desktop devices, it seems to reason that Windows would have to
    recognize the UPS as a battery(which a desktop by design does not have)
    for an 'On Battery' Power Option configured with 'Hibernate' for valid communication between the UPS and Windows to effect a hibernate condition.

    AS noted, UPS devices(alone and without other software(add-on or built
    in) can not instruct Window to hibernate without help from Windows.

    Are you also not including more info...<g>
    e.g. the device is a laptop with a battery, not desktop; the laptop's
    Power option for 'On Battery is configured to 'Hibernate', the device is
    a desktop with the UPS battery recognized by Windows Power Options and
    that battery in Power Options is configured to 'Hibernate' and/or your
    device is using UP@ or 3rd party software to force Windows to turn on hibernation when Windows hibernation is completely disabled and lacking
    a 'On Battery = Hibernate' setting(i.e. an extremely rare possibility).



    --
    ...w­¤?ñ?¤

    --- PyGate Linux v1.5.5
    * Origin: Dragon's Lair, PyGate NNTP<>Fido Gate (3:633/10)
  • From Jeff Barnett@3:633/10 to All on Saturday, January 24, 2026 21:26:01
    On 1/24/2026 7:23 PM, Paul wrote:
    On Sat, 1/24/2026 8:29 PM, Jeff Barnett wrote:
    On 1/24/2026 5:37 PM, ...w­¤?ñ?¤ wrote:
    Jeff Barnett wrote on 1/24/2026 12:56 PM:
    On 1/24/2026 10:07 AM, ...w­¤?ñ?¤ wrote:
    Jeff Barnett wrote on 1/24/2026 9:07 AM:
    On 1/23/2026 12:44 AM, ...w­¤?ñ?¤ wrote:
    micky wrote on 1/22/2026 4:26 PM:

    I suppose most of the readers of these newsgroups know that for a full >>>>>>>> start from scratch it's required to run Restart, instead of Shutdown >>>>>>>> followed by starting later.ÿ Even though I only learned this a year ago
    and even though it's a bit counter-intuitive, you all know that, right,
    (because if you're running with Fast Startup*** shutdown saves the >>>>>>>> kernel and reuses it, but Restart never uses Fast Startup and it >>>>>>>> rebuilds the kernel, with new values if the values have changed). >>>>>>>>
    But maybe you did not know that you can get the benefit of Restart and >>>>>>>> still turn your machine off if you press Shift while clicking on >>>>>>>> Shutdown.ÿÿ How about that!!


    If Hibernation (and by extension, Fast Startup) is disabled (e.g., via powercfg -h off), the "Shutdown" button functions as a full, traditional shutdown - clears the system state(shuts down all processes) and clears temp memory and powers Off. Subsequent Powering on, re-initializes the o/s
    ÿÿ- which, incidentally is the same results as Shift-Shutdown.
    ÿÿi.e. you don't need to the keystroke combo if Hibernation is disabled.

    Restart(when Hiberation is disabled) does the exact same clearing but instead of shutting down, powers the device back on and re- initializes the o/s.
    I have Hibernation set to never in my power profile. However, I have an APC UPS that will hibernate the machine in case of an extended power outage; in other words, the APC software is able to work around that setting. Does this setup change anything said in this thread so far?

    Afaik, the UPS Hibernation feature requires enabling Windows hibernation. >>>>> ÿÿi.e. When a power outage occurs, the UPS has to communicate with Windows and validate Windows hibernation state(enabled/disabled), if enabled instruct Windows to hibernate, once done the UPS provides backup battery power for the duration of its capability.

    Lacking Windows hibernation, the UPS only provides battery power for the device(and Windows) for the duration of its backup battery capability.
    ÿÿ - no Windows hibernation

    I've not enabled hibernation (as said above) but the APC software seems to be able to do it anyway. Perhaps it changes the power profile when necessary. I remember one of the disk tester/diagnostic packages that turned sleep off when it was called and never bothered to restore it on its way out. So there is certainly some way to diddle the settings.

    See Paul's response, that echo's my input.
    Hibernation needs to be enabled in Windows.

    I believe (from my own experience) that Paul is incorrect in this specific case. The APC software (OS level stuff) can when it decides it's time to shutdown because of battery drain, etc, can arrange that hibernation works whether the user has enabled it or not. I've noted it's happening a few times.

    I think there has to be a hiberfile (C:\hiberfil.sys) and
    it is typically equal in size to 50% of memory or a larger
    percentage. Via compression, the RAM content written out to
    the hiberfile is smaller than the physical size. Most sessions
    on Windows are quite small, so only a fraction of the reserved
    hiberfile space is used.

    powercfg /a # check supported ACPI states.
    # Hibernation is S4. Mine is disabled right now.
    # A shutdown /h would generate an error of some sort.

    powercfg /h on # Add Hibernation, then verify with the first command
    # Check for hidden file on the root of C: with dir /ah in command prompt

    There is also some procedure at startup, which may be writing
    something to the header of the hiberfile. The hiberfile is "invalidated"
    as part of startup, such that it cannot be reused immediately to
    restore the same session ("like it was GroundHog day").

    Otherwise, without using the hibernation feature, little in the
    way of wear, happens because of the existence of the hiberfile.

    If you were installing the APC software, it is possible there is
    sufficient elevation at install time, for the APC software to be
    using powercfg and switching the hiberfile on and reserving the
    necessary space.

    Once the hiberfile exists, the normal set of system commands
    should work, to generate a hiberfile. The command from the UPS
    should be terse -- it isn't always a super-intelligent processing
    thing. Any application loaded into the host OS, has to do the
    more intelligent part. The UPS should not be sending this
    command, as written. That would be an exploit waiting to happen.

    shutdown /h
    Paul, the power plan/profile that I've selected specifies "never" for hibernate. However, there is a ~27GB hiberfil.sys for my 64GB memory on
    the C disk. I presume that the APC software ensures that such a file
    exists and knows how to flip bits in the header to inform the BIOS that
    this is a hibernate. There was no hiberfil.sys with the "same" software
    and power plan/profile on my prior Windows 7 machines so I assume the necessary structures were consed when needed. I believe that APC takes responsibility to ensure this all works properly - I believe the
    majority of their users are office works using company machines. It
    would be lunacy on their part to expect them to know how to dick around
    with power plans, etc. In fact, their IT department has locked them out
    of anything at all interesting.
    --
    Jeff Barnett



    --- PyGate Linux v1.5.5
    * Origin: Dragon's Lair, PyGate NNTP<>Fido Gate (3:633/10)
  • From Paul@3:633/10 to All on Sunday, January 25, 2026 00:16:33
    On Sat, 1/24/2026 11:26 PM, Jeff Barnett wrote:
    On 1/24/2026 7:23 PM, Paul wrote:
    On Sat, 1/24/2026 8:29 PM, Jeff Barnett wrote:
    On 1/24/2026 5:37 PM, ...w­¤?ñ?¤ wrote:
    Jeff Barnett wrote on 1/24/2026 12:56 PM:
    On 1/24/2026 10:07 AM, ...w­¤?ñ?¤ wrote:
    Jeff Barnett wrote on 1/24/2026 9:07 AM:
    On 1/23/2026 12:44 AM, ...w­¤?ñ?¤ wrote:
    micky wrote on 1/22/2026 4:26 PM:

    I suppose most of the readers of these newsgroups know that for a full
    start from scratch it's required to run Restart, instead of Shutdown >>>>>>>>> followed by starting later.ÿ Even though I only learned this a year ago
    and even though it's a bit counter-intuitive, you all know that, right,
    (because if you're running with Fast Startup*** shutdown saves the >>>>>>>>> kernel and reuses it, but Restart never uses Fast Startup and it >>>>>>>>> rebuilds the kernel, with new values if the values have changed). >>>>>>>>>
    But maybe you did not know that you can get the benefit of Restart and
    still turn your machine off if you press Shift while clicking on >>>>>>>>> Shutdown.ÿÿ How about that!!


    If Hibernation (and by extension, Fast Startup) is disabled (e.g., via powercfg -h off), the "Shutdown" button functions as a full, traditional shutdown - clears the system state(shuts down all processes) and clears temp memory and powers Off. Subsequent Powering on, re-initializes the o/s
    ÿÿÿ- which, incidentally is the same results as Shift-Shutdown. >>>>>>>> ÿÿÿi.e. you don't need to the keystroke combo if Hibernation is disabled.

    Restart(when Hiberation is disabled) does the exact same clearing but instead of shutting down, powers the device back on and re- initializes the o/s.
    I have Hibernation set to never in my power profile. However, I have an APC UPS that will hibernate the machine in case of an extended power outage; in other words, the APC software is able to work around that setting. Does this setup change anything said in this thread so far?

    Afaik, the UPS Hibernation feature requires enabling Windows hibernation.
    ÿÿÿi.e. When a power outage occurs, the UPS has to communicate with Windows and validate Windows hibernation state(enabled/disabled), if enabled instruct Windows to hibernate, once done the UPS provides backup battery power for the duration of its capability.

    Lacking Windows hibernation, the UPS only provides battery power for the device(and Windows) for the duration of its backup battery capability.
    ÿÿÿ - no Windows hibernation

    I've not enabled hibernation (as said above) but the APC software seems to be able to do it anyway. Perhaps it changes the power profile when necessary. I remember one of the disk tester/diagnostic packages that turned sleep off when it was called and never bothered to restore it on its way out. So there is certainly some way to diddle the settings.

    See Paul's response, that echo's my input.
    ÿÿÿ=> Hibernation needs to be enabled in Windows.

    I believe (from my own experience) that Paul is incorrect in this specific case. The APC software (OS level stuff) can when it decides it's time to shutdown because of battery drain, etc, can arrange that hibernation works whether the user has enabled it or not. I've noted it's happening a few times.

    I think there has to be a hiberfile (C:\hiberfil.sys) and
    it is typically equal in size to 50% of memory or a larger
    percentage. Via compression, the RAM content written out to
    the hiberfile is smaller than the physical size. Most sessions
    on Windows are quite small, so only a fraction of the reserved
    hiberfile space is used.

    ÿÿÿ powercfg /aÿÿÿÿ # check supported ACPI states.
    ÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿ # Hibernation is S4. Mine is disabled right now.
    ÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿ # Aÿÿ shutdown /hÿÿ would generate an error of some sort.

    ÿÿÿ powercfg /h onÿ # Add Hibernation, then verify with the first command
    ÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿ # Check for hidden file on the root of C: with dir /ah in command prompt

    There is also some procedure at startup, which may be writing
    something to the header of the hiberfile. The hiberfile is "invalidated"
    as part of startup, such that it cannot be reused immediately to
    restore the same session ("like it was GroundHog day").

    Otherwise, without using the hibernation feature, little in the
    way of wear, happens because of the existence of the hiberfile.

    If you were installing the APC software, it is possible there is
    sufficient elevation at install time, for the APC software to be
    using powercfg and switching the hiberfile on and reserving the
    necessary space.

    Once the hiberfile exists, the normal set of system commands
    should work, to generate a hiberfile. The command from the UPS
    should be terse -- it isn't always a super-intelligent processing
    thing. Any application loaded into the host OS, has to do the
    more intelligent part. The UPS should not be sending this
    command, as written. That would be an exploit waiting to happen.

    ÿÿÿ shutdown /h
    Paul, the power plan/profile that I've selected specifies "never" for hibernate. However, there is a ~27GB hiberfil.sys for my 64GB memory on the C disk. I presume that the APC software ensures that such a file exists and knows how to flip bits in the header to inform the BIOS that this is a hibernate. There was no hiberfil.sys with the "same" software and power plan/profile on my prior Windows 7 machines so I assume the necessary structures were consed when needed. I believe that APC takes responsibility to ensure this all works properly - I believe the majority of their users are office works using company machines. It would be lunacy on their part to expect them to know how to dick around with power plans, etc. In fact, their IT department has locked them out of anything at all interesting.

    I don't think there is a way, to tell who did that :-)

    You could check the Event Viewer, for the evidence, but I don't
    know if it identifies the executable that is doing it.

    In any case, the weird hiberfil.sys size, suggests Windows
    didn't do that. I thought 50% was a "popular" Windows choice.
    While there are ways to select custom percentages, there is
    likely to be some lower limit on size choice.

    And dicking around with power plans, is what is expected of you :-)
    Really. I expect everyone here, has had a kick at that can,
    at some point. That would be this stuff. People multi-booting,
    need to disable Fast Startup for example.

    Power Options

    "Change settings that are currently unavailable"

    (which is a transitory state sfter switching on hiberfile,
    and the menu having hibernation added to it as an option)

    This is the interface that allows adding Hibernation to the
    shutdown menu. To do this from the registry, is an actual bitch
    (there are a couple hundred registry settings that control power states).
    While people have written up procedures for doing things that way,
    it's not a common topic of discussion.

    https://us1.discourse-cdn.com/spiceworks/optimized/4X/0/0/f/00ffd4fb8a2219c82c8e1897f64242d8ab94932b_2_690x409.png

    If you have a hiberfil.sys and no Hibernate in the menu, then that is a
    likely state that the APC created. As that is the materials
    it needs for the thing to work.

    Paul

    --- PyGate Linux v1.5.5
    * Origin: Dragon's Lair, PyGate NNTP<>Fido Gate (3:633/10)
  • From ...w¡ñ?±?ñ@3:633/10 to All on Saturday, January 24, 2026 23:05:35
    Paul wrote on 1/24/2026 10:16 PM:
    On Sat, 1/24/2026 11:26 PM, Jeff Barnett wrote:
    On 1/24/2026 7:23 PM, Paul wrote:
    On Sat, 1/24/2026 8:29 PM, Jeff Barnett wrote:
    On 1/24/2026 5:37 PM, ...w­¤?ñ?¤ wrote:
    Jeff Barnett wrote on 1/24/2026 12:56 PM:
    On 1/24/2026 10:07 AM, ...w­¤?ñ?¤ wrote:
    Jeff Barnett wrote on 1/24/2026 9:07 AM:
    On 1/23/2026 12:44 AM, ...w­¤?ñ?¤ wrote:
    micky wrote on 1/22/2026 4:26 PM:

    I suppose most of the readers of these newsgroups know that for a full
    start from scratch it's required to run Restart, instead of Shutdown >>>>>>>>>> followed by starting later.ÿ Even though I only learned this a year ago
    and even though it's a bit counter-intuitive, you all know that, right,
    (because if you're running with Fast Startup*** shutdown saves the >>>>>>>>>> kernel and reuses it, but Restart never uses Fast Startup and it >>>>>>>>>> rebuilds the kernel, with new values if the values have changed). >>>>>>>>>>
    But maybe you did not know that you can get the benefit of Restart and
    still turn your machine off if you press Shift while clicking on >>>>>>>>>> Shutdown.ÿÿ How about that!!


    If Hibernation (and by extension, Fast Startup) is disabled (e.g., via powercfg -h off), the "Shutdown" button functions as a full, traditional shutdown - clears the system state(shuts down all processes) and clears temp memory and powers Off. Subsequent Powering on, re-initializes the o/s
    ÿÿÿ- which, incidentally is the same results as Shift-Shutdown. >>>>>>>>> ÿÿÿi.e. you don't need to the keystroke combo if Hibernation is disabled.

    Restart(when Hiberation is disabled) does the exact same clearing but instead of shutting down, powers the device back on and re- initializes the o/s.
    I have Hibernation set to never in my power profile. However, I have an APC UPS that will hibernate the machine in case of an extended power outage; in other words, the APC software is able to work around that setting. Does this setup change anything said in this thread so far?

    Afaik, the UPS Hibernation feature requires enabling Windows hibernation.
    ÿÿÿi.e. When a power outage occurs, the UPS has to communicate with Windows and validate Windows hibernation state(enabled/disabled), if enabled instruct Windows to hibernate, once done the UPS provides backup battery power for the duration of its capability.

    Lacking Windows hibernation, the UPS only provides battery power for the device(and Windows) for the duration of its backup battery capability.
    ÿÿÿ - no Windows hibernation

    I've not enabled hibernation (as said above) but the APC software seems to be able to do it anyway. Perhaps it changes the power profile when necessary. I remember one of the disk tester/diagnostic packages that turned sleep off when it was called and never bothered to restore it on its way out. So there is certainly some way to diddle the settings.

    See Paul's response, that echo's my input.
    ÿÿÿ=> Hibernation needs to be enabled in Windows.

    I believe (from my own experience) that Paul is incorrect in this specific case. The APC software (OS level stuff) can when it decides it's time to shutdown because of battery drain, etc, can arrange that hibernation works whether the user has enabled it or not. I've noted it's happening a few times.

    I think there has to be a hiberfile (C:\hiberfil.sys) and
    it is typically equal in size to 50% of memory or a larger
    percentage. Via compression, the RAM content written out to
    the hiberfile is smaller than the physical size. Most sessions
    on Windows are quite small, so only a fraction of the reserved
    hiberfile space is used.

    ÿÿÿ powercfg /aÿÿÿÿ # check supported ACPI states.
    ÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿ # Hibernation is S4. Mine is disabled right now.
    ÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿ # Aÿÿ shutdown /hÿÿ would generate an error of some sort.

    ÿÿÿ powercfg /h onÿ # Add Hibernation, then verify with the first command >>> ÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿ # Check for hidden file on the root of C: with dir /ah in command prompt

    There is also some procedure at startup, which may be writing
    something to the header of the hiberfile. The hiberfile is "invalidated" >>> as part of startup, such that it cannot be reused immediately to
    restore the same session ("like it was GroundHog day").

    Otherwise, without using the hibernation feature, little in the
    way of wear, happens because of the existence of the hiberfile.

    If you were installing the APC software, it is possible there is
    sufficient elevation at install time, for the APC software to be
    using powercfg and switching the hiberfile on and reserving the
    necessary space.

    Once the hiberfile exists, the normal set of system commands
    should work, to generate a hiberfile. The command from the UPS
    should be terse -- it isn't always a super-intelligent processing
    thing. Any application loaded into the host OS, has to do the
    more intelligent part. The UPS should not be sending this
    command, as written. That would be an exploit waiting to happen.

    ÿÿÿ shutdown /h
    Paul, the power plan/profile that I've selected specifies "never" for hibernate. However, there is a ~27GB hiberfil.sys for my 64GB memory on the C disk. I presume that the APC software ensures that such a file exists and knows how to flip bits in the header to inform the BIOS that this is a hibernate. There was no hiberfil.sys with the "same" software and power plan/profile on my prior Windows 7 machines so I assume the necessary structures were consed when needed. I believe that APC takes responsibility to ensure this all works properly - I believe the majority of their users are office works using company machines. It would be lunacy on their part to expect them to know how to dick around with power plans, etc. In fact, their IT department has locked them out of anything at all interesting.

    I don't think there is a way, to tell who did that :-)

    You could check the Event Viewer, for the evidence, but I don't
    know if it identifies the executable that is doing it.

    In any case, the weird hiberfil.sys size, suggests Windows
    didn't do that. I thought 50% was a "popular" Windows choice.
    While there are ways to select custom percentages, there is
    likely to be some lower limit on size choice.

    And dicking around with power plans, is what is expected of you :-)
    Really. I expect everyone here, has had a kick at that can,
    at some point. That would be this stuff. People multi-booting,
    need to disable Fast Startup for example.

    Power Options

    "Change settings that are currently unavailable"

    (which is a transitory state sfter switching on hiberfile,
    and the menu having hibernation added to it as an option)

    This is the interface that allows adding Hibernation to the
    shutdown menu. To do this from the registry, is an actual bitch
    (there are a couple hundred registry settings that control power states). While people have written up procedures for doing things that way,
    it's not a common topic of discussion.

    https://us1.discourse-cdn.com/spiceworks/optimized/4X/0/0/f/00ffd4fb8a2219c82c8e1897f64242d8ab94932b_2_690x409.png

    If you have a hiberfil.sys and no Hibernate in the menu, then that is a likely state that the APC created. As that is the materials
    it needs for the thing to work.

    Paul


    After reading Jeff's and your reply...I noticed two items that seem to
    point to more info or comments needed.

    Jeff stated - Power Plan profile specifies never for 'Hibernate'
    That doesn't necessarily imply that hibernate was turned off, only that
    the Power Plan profile has a never Hibernate option.
    - Afaics, the only option for 'never' hibernate exists in the Power Options(Balanced or Performance) profile in the Sleep category
    * Hibernate after (On Battery or Plugged in)
    * HIbernate appears in a Power profile under the Battery
    settings(Critical Battery action and Low Battery action) where
    'Hibernate' is an option - the choice of 'Never' does not exist{Note: Low Battery action does contain a 'Do nothing' choice.

    This device has 24GB RAM...a 50% hibernate would be around 12 GB.
    - with hibernate enabled on this device, the hiberfil.sys is 4.7GB(~20%)...Jeff reported 27 GB for 64GB RAM(42%).

    I'm still of the position that
    a. if a hiberfil.sys exists, not mattering how it was created(Windows,
    user enabled, UPS Power unit), then Windows should show hibernation as
    being enabled via a admin Powershell or Command.com panel regardless of
    the presence of a 'Never' setting(somewhere in the Power Plan profile)
    powercfg /a
    and
    b. if a hiberfile.sys exists, 'Hibernate' may/should also be present in
    the Power Options 'Choose what the power buttons do' settings(along with
    the options for Fast Startup, Sleep, Lock'.

    --
    ...w­¤?ñ?¤

    --- PyGate Linux v1.5.5
    * Origin: Dragon's Lair, PyGate NNTP<>Fido Gate (3:633/10)
  • From Paul@3:633/10 to All on Sunday, January 25, 2026 02:23:42
    On Sun, 1/25/2026 1:05 AM, ...w­¤?ñ?¤ wrote:
    Paul wrote on 1/24/2026 10:16 PM:
    On Sat, 1/24/2026 11:26 PM, Jeff Barnett wrote:
    On 1/24/2026 7:23 PM, Paul wrote:
    On Sat, 1/24/2026 8:29 PM, Jeff Barnett wrote:
    On 1/24/2026 5:37 PM, ...w­¤?ñ?¤ wrote:
    Jeff Barnett wrote on 1/24/2026 12:56 PM:
    On 1/24/2026 10:07 AM, ...w­¤?ñ?¤ wrote:
    Jeff Barnett wrote on 1/24/2026 9:07 AM:
    On 1/23/2026 12:44 AM, ...w­¤?ñ?¤ wrote:
    micky wrote on 1/22/2026 4:26 PM:

    I suppose most of the readers of these newsgroups know that for a full
    start from scratch it's required to run Restart, instead of Shutdown
    followed by starting later.ÿ Even though I only learned this a year ago
    and even though it's a bit counter-intuitive, you all know that, right,
    (because if you're running with Fast Startup*** shutdown saves the >>>>>>>>>>> kernel and reuses it, but Restart never uses Fast Startup and it >>>>>>>>>>> rebuilds the kernel, with new values if the values have changed). >>>>>>>>>>>
    But maybe you did not know that you can get the benefit of Restart and
    still turn your machine off if you press Shift while clicking on >>>>>>>>>>> Shutdown.ÿÿ How about that!!


    If Hibernation (and by extension, Fast Startup) is disabled (e.g., via powercfg -h off), the "Shutdown" button functions as a full, traditional shutdown - clears the system state(shuts down all processes) and clears temp memory and powers Off. Subsequent Powering on, re-initializes the o/s
    ÿÿÿÿ- which, incidentally is the same results as Shift-Shutdown. >>>>>>>>>> ÿÿÿÿi.e. you don't need to the keystroke combo if Hibernation is disabled.

    Restart(when Hiberation is disabled) does the exact same clearing but instead of shutting down, powers the device back on and re- initializes the o/s.
    I have Hibernation set to never in my power profile. However, I have an APC UPS that will hibernate the machine in case of an extended power outage; in other words, the APC software is able to work around that setting. Does this setup change anything said in this thread so far?

    Afaik, the UPS Hibernation feature requires enabling Windows hibernation.
    ÿÿÿÿi.e. When a power outage occurs, the UPS has to communicate with Windows and validate Windows hibernation state(enabled/disabled), if enabled instruct Windows to hibernate, once done the UPS provides backup battery power for the duration of its capability.

    Lacking Windows hibernation, the UPS only provides battery power for the device(and Windows) for the duration of its backup battery capability.
    ÿÿÿÿ - no Windows hibernation

    I've not enabled hibernation (as said above) but the APC software seems to be able to do it anyway. Perhaps it changes the power profile when necessary. I remember one of the disk tester/diagnostic packages that turned sleep off when it was called and never bothered to restore it on its way out. So there is certainly some way to diddle the settings.

    See Paul's response, that echo's my input.
    ÿÿÿÿ=> Hibernation needs to be enabled in Windows.

    I believe (from my own experience) that Paul is incorrect in this specific case. The APC software (OS level stuff) can when it decides it's time to shutdown because of battery drain, etc, can arrange that hibernation works whether the user has enabled it or not. I've noted it's happening a few times.

    I think there has to be a hiberfile (C:\hiberfil.sys) and
    it is typically equal in size to 50% of memory or a larger
    percentage. Via compression, the RAM content written out to
    the hiberfile is smaller than the physical size. Most sessions
    on Windows are quite small, so only a fraction of the reserved
    hiberfile space is used.

    ÿÿÿÿ powercfg /aÿÿÿÿ # check supported ACPI states.
    ÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿ # Hibernation is S4. Mine is disabled right now.
    ÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿ # Aÿÿ shutdown /hÿÿ would generate an error of some sort.

    ÿÿÿÿ powercfg /h onÿ # Add Hibernation, then verify with the first command >>>> ÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿ # Check for hidden file on the root of C: with dir /ah in command prompt

    There is also some procedure at startup, which may be writing
    something to the header of the hiberfile. The hiberfile is "invalidated" >>>> as part of startup, such that it cannot be reused immediately to
    restore the same session ("like it was GroundHog day").

    Otherwise, without using the hibernation feature, little in the
    way of wear, happens because of the existence of the hiberfile.

    If you were installing the APC software, it is possible there is
    sufficient elevation at install time, for the APC software to be
    using powercfg and switching the hiberfile on and reserving the
    necessary space.

    Once the hiberfile exists, the normal set of system commands
    should work, to generate a hiberfile. The command from the UPS
    should be terse -- it isn't always a super-intelligent processing
    thing. Any application loaded into the host OS, has to do the
    more intelligent part. The UPS should not be sending this
    command, as written. That would be an exploit waiting to happen.

    ÿÿÿÿ shutdown /h
    Paul, the power plan/profile that I've selected specifies "never" for hibernate. However, there is a ~27GB hiberfil.sys for my 64GB memory on the C disk. I presume that the APC software ensures that such a file exists and knows how to flip bits in the header to inform the BIOS that this is a hibernate. There was no hiberfil.sys with the "same" software and power plan/profile on my prior Windows 7 machines so I assume the necessary structures were consed when needed. I believe that APC takes responsibility to ensure this all works properly - I believe the majority of their users are office works using company machines. It would be lunacy on their part to expect them to know how to dick around with power plans, etc. In fact, their IT department has locked them out of anything at all interesting.

    I don't think there is a way, to tell who did that :-)

    You could check the Event Viewer, for the evidence, but I don't
    know if it identifies the executable that is doing it.

    In any case, the weird hiberfil.sys size, suggests Windows
    didn't do that. I thought 50% was a "popular" Windows choice.
    While there are ways to select custom percentages, there is
    likely to be some lower limit on size choice.

    And dicking around with power plans, is what is expected of you :-)
    Really. I expect everyone here, has had a kick at that can,
    at some point. That would be this stuff. People multi-booting,
    need to disable Fast Startup for example.

    ÿÿÿÿ Power Options

    ÿÿÿÿ "Change settings that are currently unavailable"

    ÿÿÿÿÿ (which is a transitory state sfter switching on hiberfile,
    ÿÿÿÿÿÿ and the menu having hibernation added to it as an option)

    This is the interface that allows adding Hibernation to the
    shutdown menu. To do this from the registry, is an actual bitch
    (there are a couple hundred registry settings that control power states).
    While people have written up procedures for doing things that way,
    it's not a common topic of discussion.

    ÿÿÿ https://us1.discourse-cdn.com/spiceworks/optimized/4X/0/0/f/00ffd4fb8a2219c82c8e1897f64242d8ab94932b_2_690x409.png

    If you have a hiberfil.sys and no Hibernate in the menu, then that is a
    likely state that the APC created. As that is the materials
    it needs for the thing to work.

    ÿÿÿÿÿ Paul


    After reading Jeff's and your reply...I noticed two items that seem to point to more info or comments needed.

    Jeff stated - Power Plan profile specifies never for 'Hibernate'
    ÿThat doesn't necessarily imply that hibernate was turned off, only that the Power Plan profile has a never Hibernate option.
    - Afaics, the only option for 'never' hibernate exists in the Power Options(Balanced or Performance) profile in the Sleep category
    ÿ* Hibernate after (On Battery or Plugged in)
    ÿ* HIbernate appears in a Power profile under the Battery settings(Critical Battery action and Low Battery action) where 'Hibernate' is an option - the choice of 'Never' does not exist{Note: Low Battery action does contain a 'Do nothing' choice.

    This device has 24GB RAM...a 50% hibernate would be around 12 GB.
    ÿ- with hibernate enabled on this device, the hiberfil.sys is 4.7GB(~20%)...Jeff reported 27 GB for 64GB RAM(42%).

    I'm still of the position that
    a. if a hiberfil.sys exists, not mattering how it was created(Windows, user enabled, UPS Power unit), then Windows should show hibernation as being enabled via a admin Powershell or Command.com panel regardless of the presence of a 'Never' setting(somewhere in the Power Plan profile)
    ÿ powercfg /a
    and
    b. if a hiberfile.sys exists, 'Hibernate' may/should also be present in the Power Options 'Choose what the power buttons do' settings(along with the options for Fast Startup, Sleep, Lock'.


    Powercfg /a

    would indicate whether the "state" is ready. And it can be
    that way, without being added to a menu. And with the
    "state" indicating approval, an application should be able
    to access the state.

    If you just have a hiberfil.sys (like if I make one right now
    manually with fsutil or something), then that alone is not
    enough to support hibernation as the APC utility is likely
    to call a system routine that relies on the Registry for
    its integrity. Writing out the hiberfile, has to be done
    with the APC software "neutered", the execution state
    of any normal thing must be in "stasis" while the hiberfile
    is being filled up.

    So Powercfg /a right now, should be admitting to "S4 support".

    If my S4 is operational, I should be able to do

    shutdown /h

    even though my shutdown menu has no entry for that.

    If I just create a hiberfil.sys file in C: as a bodge,
    then shutdown /h will find there is no authorized S4 state.

    Paul

    --- PyGate Linux v1.5.5
    * Origin: Dragon's Lair, PyGate NNTP<>Fido Gate (3:633/10)
  • From Jeff Barnett@3:633/10 to All on Sunday, January 25, 2026 01:55:27
    On 1/24/2026 11:05 PM, ...w­¤?ñ?¤ wrote:
    Paul wrote on 1/24/2026 10:16 PM:
    On Sat, 1/24/2026 11:26 PM, Jeff Barnett wrote:
    On 1/24/2026 7:23 PM, Paul wrote:
    On Sat, 1/24/2026 8:29 PM, Jeff Barnett wrote:
    On 1/24/2026 5:37 PM, ...w­¤?ñ?¤ wrote:
    Jeff Barnett wrote on 1/24/2026 12:56 PM:
    On 1/24/2026 10:07 AM, ...w­¤?ñ?¤ wrote:
    Jeff Barnett wrote on 1/24/2026 9:07 AM:
    On 1/23/2026 12:44 AM, ...w­¤?ñ?¤ wrote:
    micky wrote on 1/22/2026 4:26 PM:

    I suppose most of the readers of these newsgroups know that >>>>>>>>>>> for a full
    start from scratch it's required to run Restart, instead of >>>>>>>>>>> Shutdown
    followed by starting later.ÿ Even though I only learned this >>>>>>>>>>> a year ago
    and even though it's a bit counter-intuitive, you all know >>>>>>>>>>> that, right,
    (because if you're running with Fast Startup*** shutdown >>>>>>>>>>> saves the
    kernel and reuses it, but Restart never uses Fast Startup and it >>>>>>>>>>> rebuilds the kernel, with new values if the values have >>>>>>>>>>> changed).

    But maybe you did not know that you can get the benefit of >>>>>>>>>>> Restart and
    still turn your machine off if you press Shift while clicking on >>>>>>>>>>> Shutdown.ÿÿ How about that!!


    If Hibernation (and by extension, Fast Startup) is disabled >>>>>>>>>> (e.g., via powercfg -h off), the "Shutdown" button functions >>>>>>>>>> as a full, traditional shutdown - clears the system
    state(shuts down all processes) and clears temp memory and >>>>>>>>>> powers Off. Subsequent Powering on, re-initializes the o/s >>>>>>>>>> ÿÿÿÿ- which, incidentally is the same results as Shift-Shutdown. >>>>>>>>>> ÿÿÿÿi.e. you don't need to the keystroke combo if Hibernation >>>>>>>>>> is disabled.

    Restart(when Hiberation is disabled) does the exact same
    clearing but instead of shutting down, powers the device back >>>>>>>>>> on and re- initializes the o/s.
    I have Hibernation set to never in my power profile. However, I >>>>>>>>> have an APC UPS that will hibernate the machine in case of an >>>>>>>>> extended power outage; in other words, the APC software is able >>>>>>>>> to work around that setting. Does this setup change anything >>>>>>>>> said in this thread so far?

    Afaik, the UPS Hibernation feature requires enabling Windows
    hibernation.
    ÿÿÿÿi.e. When a power outage occurs, the UPS has to communicate >>>>>>>> with Windows and validate Windows hibernation state(enabled/
    disabled), if enabled instruct Windows to hibernate, once done >>>>>>>> the UPS provides backup battery power for the duration of its >>>>>>>> capability.

    Lacking Windows hibernation, the UPS only provides battery power >>>>>>>> for the device(and Windows) for the duration of its backup
    battery capability.
    ÿÿÿÿ - no Windows hibernation

    I've not enabled hibernation (as said above) but the APC software >>>>>>> seems to be able to do it anyway. Perhaps it changes the power
    profile when necessary. I remember one of the disk tester/
    diagnostic packages that turned sleep off when it was called and >>>>>>> never bothered to restore it on its way out. So there is
    certainly some way to diddle the settings.

    See Paul's response, that echo's my input.
    ÿÿÿÿ=> Hibernation needs to be enabled in Windows.

    I believe (from my own experience) that Paul is incorrect in this
    specific case. The APC software (OS level stuff) can when it
    decides it's time to shutdown because of battery drain, etc, can
    arrange that hibernation works whether the user has enabled it or
    not. I've noted it's happening a few times.

    I think there has to be a hiberfile (C:\hiberfil.sys) and
    it is typically equal in size to 50% of memory or a larger
    percentage. Via compression, the RAM content written out to
    the hiberfile is smaller than the physical size. Most sessions
    on Windows are quite small, so only a fraction of the reserved
    hiberfile space is used.

    ÿÿÿÿ powercfg /aÿÿÿÿ # check supported ACPI states.
    ÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿ # Hibernation is S4. Mine is disabled right now.
    ÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿ # Aÿÿ shutdown /hÿÿ would generate an error of
    some sort.

    ÿÿÿÿ powercfg /h onÿ # Add Hibernation, then verify with the first
    command
    ÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿ # Check for hidden file on the root of C: with
    dir /ah in command prompt

    There is also some procedure at startup, which may be writing
    something to the header of the hiberfile. The hiberfile is
    "invalidated"
    as part of startup, such that it cannot be reused immediately to
    restore the same session ("like it was GroundHog day").

    Otherwise, without using the hibernation feature, little in the
    way of wear, happens because of the existence of the hiberfile.

    If you were installing the APC software, it is possible there is
    sufficient elevation at install time, for the APC software to be
    using powercfg and switching the hiberfile on and reserving the
    necessary space.

    Once the hiberfile exists, the normal set of system commands
    should work, to generate a hiberfile. The command from the UPS
    should be terse -- it isn't always a super-intelligent processing
    thing. Any application loaded into the host OS, has to do the
    more intelligent part. The UPS should not be sending this
    command, as written. That would be an exploit waiting to happen.

    ÿÿÿÿ shutdown /h
    Paul, the power plan/profile that I've selected specifies "never" for
    hibernate. However, there is a ~27GB hiberfil.sys for my 64GB memory
    on the C disk. I presume that the APC software ensures that such a
    file exists and knows how to flip bits in the header to inform the
    BIOS that this is a hibernate. There was no hiberfil.sys with the
    "same" software and power plan/profile on my prior Windows 7 machines
    so I assume the necessary structures were consed when needed. I
    believe that APC takes responsibility to ensure this all works
    properly - I believe the majority of their users are office works
    using company machines. It would be lunacy on their part to expect
    them to know how to dick around with power plans, etc. In fact, their
    IT department has locked them out of anything at all interesting.

    I don't think there is a way, to tell who did that :-)

    You could check the Event Viewer, for the evidence, but I don't
    know if it identifies the executable that is doing it.

    In any case, the weird hiberfil.sys size, suggests Windows
    didn't do that. I thought 50% was a "popular" Windows choice.
    While there are ways to select custom percentages, there is
    likely to be some lower limit on size choice.

    And dicking around with power plans, is what is expected of you :-)
    Really. I expect everyone here, has had a kick at that can,
    at some point. That would be this stuff. People multi-booting,
    need to disable Fast Startup for example.

    ÿÿÿÿ Power Options

    ÿÿÿÿ "Change settings that are currently unavailable"

    ÿÿÿÿÿ (which is a transitory state sfter switching on hiberfile,
    ÿÿÿÿÿÿ and the menu having hibernation added to it as an option)

    This is the interface that allows adding Hibernation to the
    shutdown menu. To do this from the registry, is an actual bitch
    (there are a couple hundred registry settings that control power states).
    While people have written up procedures for doing things that way,
    it's not a common topic of discussion.

    ÿÿÿ https://us1.discourse-cdn.com/spiceworks/optimized/4X/0/0/
    f/00ffd4fb8a2219c82c8e1897f64242d8ab94932b_2_690x409.png

    If you have a hiberfil.sys and no Hibernate in the menu, then that is a
    likely state that the APC created. As that is the materials
    it needs for the thing to work.

    ÿÿÿÿÿ Paul


    After reading Jeff's and your reply...I noticed two items that seem to
    point to more info or comments needed.

    Jeff stated - Power Plan profile specifies never for 'Hibernate'
    ÿThat doesn't necessarily imply that hibernate was turned off, only
    that the Power Plan profile has a never Hibernate option.
    - Afaics, the only option for 'never' hibernate exists in the Power Options(Balanced or Performance) profile in the Sleep category
    ÿ* Hibernate after (On Battery or Plugged in)
    ÿ* HIbernate appears in a Power profile under the Battery
    settings(Critical Battery action and Low Battery action) where
    'Hibernate' is an option - the choice of 'Never' does not exist{Note:
    Low Battery action does contain a 'Do nothing' choice.

    This device has 24GB RAM...a 50% hibernate would be around 12 GB.
    ÿ- with hibernate enabled on this device, the hiberfil.sys is 4.7GB(~20%)...Jeff reported 27 GB for 64GB RAM(42%).

    I'm still of the position that
    a. if a hiberfil.sys exists, not mattering how it was created(Windows,
    user enabled, UPS Power unit), then Windows should show hibernation as
    being enabled via a admin Powershell or Command.com panel regardless of
    the presence of a 'Never' setting(somewhere in the Power Plan profile)
    ÿ powercfg /a
    and
    b. if a hiberfile.sys exists, 'Hibernate' may/should also be present in
    the Power Options 'Choose what the power buttons do' settings(along with
    the options for Fast Startup, Sleep, Lock'.
    Since multiple power plans are defined and only one is selected, a few observations are in order: 1) some plans may specify hibernate and
    others may not and 2) just because the selected plan has not elected to
    enable hibernate does not mean that hiberfil.sys need not be available -
    a program or user can change the profile in use at any time or modify a
    plan's parameters. So the OS must be rather loosey-goosey with the
    management of all this stuff.

    I must note that I have no special knowledge on this topic and haven't
    read any M$ papers on it. Therefore I might be full of shit. My
    knowledge is simply that of a user reasoning from observation and a
    limited amount of experimentation.
    --
    Jeff Barnett



    --- PyGate Linux v1.5.5
    * Origin: Dragon's Lair, PyGate NNTP<>Fido Gate (3:633/10)
  • From Jeff Barnett@3:633/10 to All on Sunday, January 25, 2026 01:59:29
    On 1/25/2026 12:23 AM, Paul wrote:
    On Sun, 1/25/2026 1:05 AM, ...w­¤?ñ?¤ wrote:
    Paul wrote on 1/24/2026 10:16 PM:
    On Sat, 1/24/2026 11:26 PM, Jeff Barnett wrote:
    On 1/24/2026 7:23 PM, Paul wrote:
    On Sat, 1/24/2026 8:29 PM, Jeff Barnett wrote:
    On 1/24/2026 5:37 PM, ...w­¤?ñ?¤ wrote:
    Jeff Barnett wrote on 1/24/2026 12:56 PM:
    On 1/24/2026 10:07 AM, ...w­¤?ñ?¤ wrote:
    Jeff Barnett wrote on 1/24/2026 9:07 AM:
    On 1/23/2026 12:44 AM, ...w­¤?ñ?¤ wrote:
    micky wrote on 1/22/2026 4:26 PM:

    I suppose most of the readers of these newsgroups know that for a full
    start from scratch it's required to run Restart, instead of Shutdown
    followed by starting later.ÿ Even though I only learned this a year ago
    and even though it's a bit counter-intuitive, you all know that, right,
    (because if you're running with Fast Startup*** shutdown saves the >>>>>>>>>>>> kernel and reuses it, but Restart never uses Fast Startup and it >>>>>>>>>>>> rebuilds the kernel, with new values if the values have changed). >>>>>>>>>>>>
    But maybe you did not know that you can get the benefit of Restart and
    still turn your machine off if you press Shift while clicking on >>>>>>>>>>>> Shutdown.ÿÿ How about that!!


    If Hibernation (and by extension, Fast Startup) is disabled (e.g., via powercfg -h off), the "Shutdown" button functions as a full, traditional shutdown - clears the system state(shuts down all processes) and clears temp memory and powers Off. Subsequent Powering on, re-initializes the o/s
    ÿÿÿÿ- which, incidentally is the same results as Shift-Shutdown. >>>>>>>>>>> ÿÿÿÿi.e. you don't need to the keystroke combo if Hibernation is disabled.

    Restart(when Hiberation is disabled) does the exact same clearing but instead of shutting down, powers the device back on and re- initializes the o/s.
    I have Hibernation set to never in my power profile. However, I have an APC UPS that will hibernate the machine in case of an extended power outage; in other words, the APC software is able to work around that setting. Does this setup change anything said in this thread so far?

    Afaik, the UPS Hibernation feature requires enabling Windows hibernation.
    ÿÿÿÿi.e. When a power outage occurs, the UPS has to communicate with Windows and validate Windows hibernation state(enabled/disabled), if enabled instruct Windows to hibernate, once done the UPS provides backup battery power for the duration of its capability.

    Lacking Windows hibernation, the UPS only provides battery power for the device(and Windows) for the duration of its backup battery capability.
    ÿÿÿÿ - no Windows hibernation

    I've not enabled hibernation (as said above) but the APC software seems to be able to do it anyway. Perhaps it changes the power profile when necessary. I remember one of the disk tester/diagnostic packages that turned sleep off when it was called and never bothered to restore it on its way out. So there is certainly some way to diddle the settings.

    See Paul's response, that echo's my input.
    ÿÿÿÿ=> Hibernation needs to be enabled in Windows.

    I believe (from my own experience) that Paul is incorrect in this specific case. The APC software (OS level stuff) can when it decides it's time to shutdown because of battery drain, etc, can arrange that hibernation works whether the user has enabled it or not. I've noted it's happening a few times.

    I think there has to be a hiberfile (C:\hiberfil.sys) and
    it is typically equal in size to 50% of memory or a larger
    percentage. Via compression, the RAM content written out to
    the hiberfile is smaller than the physical size. Most sessions
    on Windows are quite small, so only a fraction of the reserved
    hiberfile space is used.

    ÿÿÿÿ powercfg /aÿÿÿÿ # check supported ACPI states.
    ÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿ # Hibernation is S4. Mine is disabled right now. >>>>> ÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿ # Aÿÿ shutdown /hÿÿ would generate an error of some sort.

    ÿÿÿÿ powercfg /h onÿ # Add Hibernation, then verify with the first command
    ÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿ # Check for hidden file on the root of C: with dir /ah in command prompt

    There is also some procedure at startup, which may be writing
    something to the header of the hiberfile. The hiberfile is "invalidated" >>>>> as part of startup, such that it cannot be reused immediately to
    restore the same session ("like it was GroundHog day").

    Otherwise, without using the hibernation feature, little in the
    way of wear, happens because of the existence of the hiberfile.

    If you were installing the APC software, it is possible there is
    sufficient elevation at install time, for the APC software to be
    using powercfg and switching the hiberfile on and reserving the
    necessary space.

    Once the hiberfile exists, the normal set of system commands
    should work, to generate a hiberfile. The command from the UPS
    should be terse -- it isn't always a super-intelligent processing
    thing. Any application loaded into the host OS, has to do the
    more intelligent part. The UPS should not be sending this
    command, as written. That would be an exploit waiting to happen.

    ÿÿÿÿ shutdown /h
    Paul, the power plan/profile that I've selected specifies "never" for hibernate. However, there is a ~27GB hiberfil.sys for my 64GB memory on the C disk. I presume that the APC software ensures that such a file exists and knows how to flip bits in the header to inform the BIOS that this is a hibernate. There was no hiberfil.sys with the "same" software and power plan/profile on my prior Windows 7 machines so I assume the necessary structures were consed when needed. I believe that APC takes responsibility to ensure this all works properly - I believe the majority of their users are office works using company machines. It would be lunacy on their part to expect them to know how to dick around with power plans, etc. In fact, their IT department has locked them out of anything at all interesting.

    I don't think there is a way, to tell who did that :-)

    You could check the Event Viewer, for the evidence, but I don't
    know if it identifies the executable that is doing it.

    In any case, the weird hiberfil.sys size, suggests Windows
    didn't do that. I thought 50% was a "popular" Windows choice.
    While there are ways to select custom percentages, there is
    likely to be some lower limit on size choice.

    And dicking around with power plans, is what is expected of you :-)
    Really. I expect everyone here, has had a kick at that can,
    at some point. That would be this stuff. People multi-booting,
    need to disable Fast Startup for example.

    ÿÿÿÿ Power Options

    ÿÿÿÿ "Change settings that are currently unavailable"

    ÿÿÿÿÿ (which is a transitory state sfter switching on hiberfile,
    ÿÿÿÿÿÿ and the menu having hibernation added to it as an option)

    This is the interface that allows adding Hibernation to the
    shutdown menu. To do this from the registry, is an actual bitch
    (there are a couple hundred registry settings that control power states). >>> While people have written up procedures for doing things that way,
    it's not a common topic of discussion.

    ÿÿÿ https://us1.discourse-cdn.com/spiceworks/optimized/4X/0/0/f/00ffd4fb8a2219c82c8e1897f64242d8ab94932b_2_690x409.png

    If you have a hiberfil.sys and no Hibernate in the menu, then that is a
    likely state that the APC created. As that is the materials
    it needs for the thing to work.

    ÿÿÿÿÿ Paul


    After reading Jeff's and your reply...I noticed two items that seem to point to more info or comments needed.

    Jeff stated - Power Plan profile specifies never for 'Hibernate'
    ÿThat doesn't necessarily imply that hibernate was turned off, only that the Power Plan profile has a never Hibernate option.
    - Afaics, the only option for 'never' hibernate exists in the Power Options(Balanced or Performance) profile in the Sleep category
    ÿ* Hibernate after (On Battery or Plugged in)
    ÿ* HIbernate appears in a Power profile under the Battery settings(Critical Battery action and Low Battery action) where 'Hibernate' is an option - the choice of 'Never' does not exist{Note: Low Battery action does contain a 'Do nothing' choice.

    This device has 24GB RAM...a 50% hibernate would be around 12 GB.
    ÿ- with hibernate enabled on this device, the hiberfil.sys is 4.7GB(~20%)...Jeff reported 27 GB for 64GB RAM(42%).

    I'm still of the position that
    a. if a hiberfil.sys exists, not mattering how it was created(Windows, user enabled, UPS Power unit), then Windows should show hibernation as being enabled via a admin Powershell or Command.com panel regardless of the presence of a 'Never' setting(somewhere in the Power Plan profile)
    ÿ powercfg /a
    and
    b. if a hiberfile.sys exists, 'Hibernate' may/should also be present in the Power Options 'Choose what the power buttons do' settings(along with the options for Fast Startup, Sleep, Lock'.


    Powercfg /a

    I think the above command tells what the motherboard supports, not what
    is enabled. For example, I have not enabled fast boot in the BIOS but
    that command shows it as possible.


    would indicate whether the "state" is ready. And it can be
    that way, without being added to a menu. And with the
    "state" indicating approval, an application should be able
    to access the state.

    If you just have a hiberfil.sys (like if I make one right now
    manually with fsutil or something), then that alone is not
    enough to support hibernation as the APC utility is likely
    to call a system routine that relies on the Registry for
    its integrity. Writing out the hiberfile, has to be done
    with the APC software "neutered", the execution state
    of any normal thing must be in "stasis" while the hiberfile
    is being filled up.

    So Powercfg /a right now, should be admitting to "S4 support".

    If my S4 is operational, I should be able to do

    shutdown /h

    even though my shutdown menu has no entry for that.

    If I just create a hiberfil.sys file in C: as a bodge,
    then shutdown /h will find there is no authorized S4 state.--
    Jeff Barnett



    --- PyGate Linux v1.5.5
    * Origin: Dragon's Lair, PyGate NNTP<>Fido Gate (3:633/10)
  • From ...w¡ñ?±?ñ@3:633/10 to All on Sunday, January 25, 2026 03:24:26
    Jeff Barnett wrote on 1/25/2026 1:59 AM:
    On 1/25/2026 12:23 AM, Paul wrote:
    Powercfg /a

    I think the above command tells what the motherboard supports, not what
    is enabled. For example, I have not enabled fast boot in the BIOS but
    that command shows it as possible.

    Jeff Barnett


    For powercfg /a with Hibernation enabled (i.e. powercfg /h off)
    PS C:\WINDOWS\system32> powercfg /a
    The following sleep states are available on this system:
    Standby (S3)
    Hibernate
    Hybrid Sleep

    The following sleep states are not available on this system:
    Standby (S1)
    The system firmware does not support this standby state.
    Standby (S2)
    The system firmware does not support this standby state.
    Standby (S0 Low Power Idle)
    The system firmware does not support this standby state.
    Fast Startup
    This action is disabled in the current system policy.

    For Powercfg /a with Hibernation disabled (i.e. powercfg /h on)
    The following sleep states are available on this system:
    Standby (S3)

    The following sleep states are not available on this system:
    Standby (S1)
    The system firmware does not support this standby state.
    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.

    ==>> Note the results when Hibernation is Off, indicates Hibernation
    has not been enabled.
    - Looks like the current condition, not what the motherboard supports.

    --
    ...w­¤?ñ?¤

    --- PyGate Linux v1.5.5
    * Origin: Dragon's Lair, PyGate NNTP<>Fido Gate (3:633/10)
  • From Paul@3:633/10 to All on Sunday, January 25, 2026 08:44:04
    On Sun, 1/25/2026 3:55 AM, Jeff Barnett wrote:
    On 1/24/2026 11:05 PM, ...w­¤?ñ?¤ wrote:
    Paul wrote on 1/24/2026 10:16 PM:
    On Sat, 1/24/2026 11:26 PM, Jeff Barnett wrote:
    On 1/24/2026 7:23 PM, Paul wrote:
    On Sat, 1/24/2026 8:29 PM, Jeff Barnett wrote:
    On 1/24/2026 5:37 PM, ...w­¤?ñ?¤ wrote:
    Jeff Barnett wrote on 1/24/2026 12:56 PM:
    On 1/24/2026 10:07 AM, ...w­¤?ñ?¤ wrote:
    Jeff Barnett wrote on 1/24/2026 9:07 AM:
    On 1/23/2026 12:44 AM, ...w­¤?ñ?¤ wrote:
    micky wrote on 1/22/2026 4:26 PM:

    I suppose most of the readers of these newsgroups know that for a full
    start from scratch it's required to run Restart, instead of Shutdown
    followed by starting later.ÿ Even though I only learned this a year ago
    and even though it's a bit counter-intuitive, you all know that, right,
    (because if you're running with Fast Startup*** shutdown saves the >>>>>>>>>>>> kernel and reuses it, but Restart never uses Fast Startup and it >>>>>>>>>>>> rebuilds the kernel, with new values if the values have changed). >>>>>>>>>>>>
    But maybe you did not know that you can get the benefit of Restart and
    still turn your machine off if you press Shift while clicking on >>>>>>>>>>>> Shutdown.ÿÿ How about that!!


    If Hibernation (and by extension, Fast Startup) is disabled (e.g., via powercfg -h off), the "Shutdown" button functions as a full, traditional shutdown - clears the system state(shuts down all processes) and clears temp memory and powers Off. Subsequent Powering on, re-initializes the o/s
    ÿÿÿÿ- which, incidentally is the same results as Shift-Shutdown. >>>>>>>>>>> ÿÿÿÿi.e. you don't need to the keystroke combo if Hibernation is disabled.

    Restart(when Hiberation is disabled) does the exact same clearing but instead of shutting down, powers the device back on and re- initializes the o/s.
    I have Hibernation set to never in my power profile. However, I have an APC UPS that will hibernate the machine in case of an extended power outage; in other words, the APC software is able to work around that setting. Does this setup change anything said in this thread so far?

    Afaik, the UPS Hibernation feature requires enabling Windows hibernation.
    ÿÿÿÿi.e. When a power outage occurs, the UPS has to communicate with Windows and validate Windows hibernation state(enabled/ disabled), if enabled instruct Windows to hibernate, once done the UPS provides backup battery power for the duration of its capability.

    Lacking Windows hibernation, the UPS only provides battery power for the device(and Windows) for the duration of its backup battery capability.
    ÿÿÿÿ - no Windows hibernation

    I've not enabled hibernation (as said above) but the APC software seems to be able to do it anyway. Perhaps it changes the power profile when necessary. I remember one of the disk tester/ diagnostic packages that turned sleep off when it was called and never bothered to restore it on its way out. So there is certainly some way to diddle the settings.

    See Paul's response, that echo's my input.
    ÿÿÿÿ=> Hibernation needs to be enabled in Windows.

    I believe (from my own experience) that Paul is incorrect in this specific case. The APC software (OS level stuff) can when it decides it's time to shutdown because of battery drain, etc, can arrange that hibernation works whether the user has enabled it or not. I've noted it's happening a few times.

    I think there has to be a hiberfile (C:\hiberfil.sys) and
    it is typically equal in size to 50% of memory or a larger
    percentage. Via compression, the RAM content written out to
    the hiberfile is smaller than the physical size. Most sessions
    on Windows are quite small, so only a fraction of the reserved
    hiberfile space is used.

    ÿÿÿÿ powercfg /aÿÿÿÿ # check supported ACPI states.
    ÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿ # Hibernation is S4. Mine is disabled right now. >>>>> ÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿ # Aÿÿ shutdown /hÿÿ would generate an error of some sort.

    ÿÿÿÿ powercfg /h onÿ # Add Hibernation, then verify with the first command
    ÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿ # Check for hidden file on the root of C: with dir /ah in command prompt

    There is also some procedure at startup, which may be writing
    something to the header of the hiberfile. The hiberfile is "invalidated" >>>>> as part of startup, such that it cannot be reused immediately to
    restore the same session ("like it was GroundHog day").

    Otherwise, without using the hibernation feature, little in the
    way of wear, happens because of the existence of the hiberfile.

    If you were installing the APC software, it is possible there is
    sufficient elevation at install time, for the APC software to be
    using powercfg and switching the hiberfile on and reserving the
    necessary space.

    Once the hiberfile exists, the normal set of system commands
    should work, to generate a hiberfile. The command from the UPS
    should be terse -- it isn't always a super-intelligent processing
    thing. Any application loaded into the host OS, has to do the
    more intelligent part. The UPS should not be sending this
    command, as written. That would be an exploit waiting to happen.

    ÿÿÿÿ shutdown /h
    Paul, the power plan/profile that I've selected specifies "never" for hibernate. However, there is a ~27GB hiberfil.sys for my 64GB memory on the C disk. I presume that the APC software ensures that such a file exists and knows how to flip bits in the header to inform the BIOS that this is a hibernate. There was no hiberfil.sys with the "same" software and power plan/profile on my prior Windows 7 machines so I assume the necessary structures were consed when needed. I believe that APC takes responsibility to ensure this all works properly - I believe the majority of their users are office works using company machines. It would be lunacy on their part to expect them to know how to dick around with power plans, etc. In fact, their IT department has locked them out of anything at all interesting.

    I don't think there is a way, to tell who did that :-)

    You could check the Event Viewer, for the evidence, but I don't
    know if it identifies the executable that is doing it.

    In any case, the weird hiberfil.sys size, suggests Windows
    didn't do that. I thought 50% was a "popular" Windows choice.
    While there are ways to select custom percentages, there is
    likely to be some lower limit on size choice.

    And dicking around with power plans, is what is expected of you :-)
    Really. I expect everyone here, has had a kick at that can,
    at some point. That would be this stuff. People multi-booting,
    need to disable Fast Startup for example.

    ÿÿÿÿ Power Options

    ÿÿÿÿ "Change settings that are currently unavailable"

    ÿÿÿÿÿ (which is a transitory state sfter switching on hiberfile,
    ÿÿÿÿÿÿ and the menu having hibernation added to it as an option)

    This is the interface that allows adding Hibernation to the
    shutdown menu. To do this from the registry, is an actual bitch
    (there are a couple hundred registry settings that control power states). >>> While people have written up procedures for doing things that way,
    it's not a common topic of discussion.

    ÿÿÿ https://us1.discourse-cdn.com/spiceworks/optimized/4X/0/0/ f/00ffd4fb8a2219c82c8e1897f64242d8ab94932b_2_690x409.png

    If you have a hiberfil.sys and no Hibernate in the menu, then that is a
    likely state that the APC created. As that is the materials
    it needs for the thing to work.

    ÿÿÿÿÿ Paul


    After reading Jeff's and your reply...I noticed two items that seem to point to more info or comments needed.

    Jeff stated - Power Plan profile specifies never for 'Hibernate'
    ÿÿThat doesn't necessarily imply that hibernate was turned off, only that the Power Plan profile has a never Hibernate option.
    - Afaics, the only option for 'never' hibernate exists in the Power Options(Balanced or Performance) profile in the Sleep category
    ÿÿ* Hibernate after (On Battery or Plugged in)
    ÿÿ* HIbernate appears in a Power profile under the Battery settings(Critical Battery action and Low Battery action) where 'Hibernate' is an option - the choice of 'Never' does not exist{Note: Low Battery action does contain a 'Do nothing' choice.

    This device has 24GB RAM...a 50% hibernate would be around 12 GB.
    ÿÿ- with hibernate enabled on this device, the hiberfil.sys is 4.7GB(~20%)...Jeff reported 27 GB for 64GB RAM(42%).

    I'm still of the position that
    a. if a hiberfil.sys exists, not mattering how it was created(Windows, user enabled, UPS Power unit), then Windows should show hibernation as being enabled via a admin Powershell or Command.com panel regardless of the presence of a 'Never' setting(somewhere in the Power Plan profile)
    ÿÿ powercfg /a
    and
    b. if a hiberfile.sys exists, 'Hibernate' may/should also be present in the Power Options 'Choose what the power buttons do' settings(along with the options for Fast Startup, Sleep, Lock'.
    Since multiple power plans are defined and only one is selected, a few observations are in order: 1) some plans may specify hibernate and others may not and 2) just because the selected plan has not elected to enable hibernate does not mean that hiberfil.sys need not be available - a program or user can change the profile in use at any time or modify a plan's parameters. So the OSÿ must be rather loosey-goosey with the management of all this stuff.

    I must note that I have no special knowledge on this topic and haven't read any M$ papers on it. Therefore I might be full of shit. My knowledge is simply that of a user reasoning from observation and a limited amount of experimentation.

    The ACPI is machine wide.

    The materials governed by the 200 registry settings,
    one of the multiplicative factors there was likely
    the power plans.

    When you shut down a machine or sleep a machine or hibernate
    a machine, you do that for all the Fast User switching users.
    You might see a notification, warning you there are other
    users on the machine, when doing that.

    ACPI consists of C states (C12 is CPU unloaded and functionally
    switched off), P states (FID/VID/multiplier/frequency changes),
    and the S states are S0 thru S5 (sleep and hibernate). And those
    all have machine-wide effect. There are HIPM and DIPM for
    bus states (disconnecting a bus to save power).

    In the Advanced Power Settings, are things like min processor
    and max processor, and on High Performance, those are both set to
    100%, which is the highest P state. But in the Advanced Power Settings
    there are no controls to turn hibernation in the menu on and off.

    When we look at the "Choose what the power buttons do", it says (via OCR)

    Define power buttons and turn on password protection

    Choose the power settings that you want for your computer.

    The changes you make to the settings on this page apply to all of your power plans.

    [ Change settings that are currently unavailable ]

    Some things have wider applicability than others, and with the
    Fast User Switching, I can't see two accounts belonging to the
    Administrators Group and defining different settings, is going
    to work all that well. If one person sets the power button to OFF
    and the other person sets the power button to SLEEP, someone
    is going to be unhappy when that button is pressed. Some things
    on the machine are shared and machine-wide. If one person sets
    the power button to sleep, then it has to sleep for everyone.

    You would need a map of the 200 settings in the Registry, to
    figure out what dimensions each part of those has. I was just
    told there were 200 of those, I didn't count them :-) There are
    some people skilled enough, to have the numeric strings of
    those, for fiddling them manually. What are the odds such surgery
    ever gets done correctly that way (if done by hand).

    Paul

    --- PyGate Linux v1.5.5
    * Origin: Dragon's Lair, PyGate NNTP<>Fido Gate (3:633/10)
  • From ...w¡ñ?±?ñ@3:633/10 to All on Sunday, January 25, 2026 07:02:49
    Jeff Barnett wrote on 1/25/2026 1:55 AM:
    On 1/24/2026 11:05 PM, ...w­¤?ñ?¤ wrote:
    Paul wrote on 1/24/2026 10:16 PM:
    On Sat, 1/24/2026 11:26 PM, Jeff Barnett wrote:
    On 1/24/2026 7:23 PM, Paul wrote:
    On Sat, 1/24/2026 8:29 PM, Jeff Barnett wrote:
    On 1/24/2026 5:37 PM, ...w­¤?ñ?¤ wrote:
    Jeff Barnett wrote on 1/24/2026 12:56 PM:
    On 1/24/2026 10:07 AM, ...w­¤?ñ?¤ wrote:
    Jeff Barnett wrote on 1/24/2026 9:07 AM:
    On 1/23/2026 12:44 AM, ...w­¤?ñ?¤ wrote:
    micky wrote on 1/22/2026 4:26 PM:

    I suppose most of the readers of these newsgroups know that >>>>>>>>>>>> for a full
    start from scratch it's required to run Restart, instead of >>>>>>>>>>>> Shutdown
    followed by starting later.ÿ Even though I only learned this >>>>>>>>>>>> a year ago
    and even though it's a bit counter-intuitive, you all know >>>>>>>>>>>> that, right,
    (because if you're running with Fast Startup*** shutdown >>>>>>>>>>>> saves the
    kernel and reuses it, but Restart never uses Fast Startup and it >>>>>>>>>>>> rebuilds the kernel, with new values if the values have >>>>>>>>>>>> changed).

    But maybe you did not know that you can get the benefit of >>>>>>>>>>>> Restart and
    still turn your machine off if you press Shift while clicking on >>>>>>>>>>>> Shutdown.ÿÿ How about that!!


    If Hibernation (and by extension, Fast Startup) is disabled >>>>>>>>>>> (e.g., via powercfg -h off), the "Shutdown" button functions >>>>>>>>>>> as a full, traditional shutdown - clears the system
    state(shuts down all processes) and clears temp memory and >>>>>>>>>>> powers Off. Subsequent Powering on, re-initializes the o/s >>>>>>>>>>> ÿÿÿÿ- which, incidentally is the same results as Shift-Shutdown. >>>>>>>>>>> ÿÿÿÿi.e. you don't need to the keystroke combo if Hibernation >>>>>>>>>>> is disabled.

    Restart(when Hiberation is disabled) does the exact same >>>>>>>>>>> clearing but instead of shutting down, powers the device back >>>>>>>>>>> on and re- initializes the o/s.
    I have Hibernation set to never in my power profile. However, I >>>>>>>>>> have an APC UPS that will hibernate the machine in case of an >>>>>>>>>> extended power outage; in other words, the APC software is able >>>>>>>>>> to work around that setting. Does this setup change anything >>>>>>>>>> said in this thread so far?

    Afaik, the UPS Hibernation feature requires enabling Windows >>>>>>>>> hibernation.
    ÿÿÿÿi.e. When a power outage occurs, the UPS has to communicate >>>>>>>>> with Windows and validate Windows hibernation state(enabled/ >>>>>>>>> disabled), if enabled instruct Windows to hibernate, once done >>>>>>>>> the UPS provides backup battery power for the duration of its >>>>>>>>> capability.

    Lacking Windows hibernation, the UPS only provides battery power >>>>>>>>> for the device(and Windows) for the duration of its backup
    battery capability.
    ÿÿÿÿ - no Windows hibernation

    I've not enabled hibernation (as said above) but the APC software >>>>>>>> seems to be able to do it anyway. Perhaps it changes the power >>>>>>>> profile when necessary. I remember one of the disk tester/
    diagnostic packages that turned sleep off when it was called and >>>>>>>> never bothered to restore it on its way out. So there is
    certainly some way to diddle the settings.

    See Paul's response, that echo's my input.
    ÿÿÿÿ=> Hibernation needs to be enabled in Windows.

    I believe (from my own experience) that Paul is incorrect in this >>>>>> specific case. The APC software (OS level stuff) can when it
    decides it's time to shutdown because of battery drain, etc, can
    arrange that hibernation works whether the user has enabled it or >>>>>> not. I've noted it's happening a few times.

    I think there has to be a hiberfile (C:\hiberfil.sys) and
    it is typically equal in size to 50% of memory or a larger
    percentage. Via compression, the RAM content written out to
    the hiberfile is smaller than the physical size. Most sessions
    on Windows are quite small, so only a fraction of the reserved
    hiberfile space is used.

    ÿÿÿÿ powercfg /aÿÿÿÿ # check supported ACPI states.
    ÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿ # Hibernation is S4. Mine is disabled right now. >>>>> ÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿ # Aÿÿ shutdown /hÿÿ would generate an error of >>>>> some sort.

    ÿÿÿÿ powercfg /h onÿ # Add Hibernation, then verify with the first
    command
    ÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿ # Check for hidden file on the root of C: with >>>>> dir /ah in command prompt

    There is also some procedure at startup, which may be writing
    something to the header of the hiberfile. The hiberfile is
    "invalidated"
    as part of startup, such that it cannot be reused immediately to
    restore the same session ("like it was GroundHog day").

    Otherwise, without using the hibernation feature, little in the
    way of wear, happens because of the existence of the hiberfile.

    If you were installing the APC software, it is possible there is
    sufficient elevation at install time, for the APC software to be
    using powercfg and switching the hiberfile on and reserving the
    necessary space.

    Once the hiberfile exists, the normal set of system commands
    should work, to generate a hiberfile. The command from the UPS
    should be terse -- it isn't always a super-intelligent processing
    thing. Any application loaded into the host OS, has to do the
    more intelligent part. The UPS should not be sending this
    command, as written. That would be an exploit waiting to happen.

    ÿÿÿÿ shutdown /h
    Paul, the power plan/profile that I've selected specifies "never" for >>>> hibernate. However, there is a ~27GB hiberfil.sys for my 64GB memory
    on the C disk. I presume that the APC software ensures that such a
    file exists and knows how to flip bits in the header to inform the
    BIOS that this is a hibernate. There was no hiberfil.sys with the
    "same" software and power plan/profile on my prior Windows 7 machines >>>> so I assume the necessary structures were consed when needed. I
    believe that APC takes responsibility to ensure this all works
    properly - I believe the majority of their users are office works
    using company machines. It would be lunacy on their part to expect
    them to know how to dick around with power plans, etc. In fact, their >>>> IT department has locked them out of anything at all interesting.

    I don't think there is a way, to tell who did that :-)

    You could check the Event Viewer, for the evidence, but I don't
    know if it identifies the executable that is doing it.

    In any case, the weird hiberfil.sys size, suggests Windows
    didn't do that. I thought 50% was a "popular" Windows choice.
    While there are ways to select custom percentages, there is
    likely to be some lower limit on size choice.

    And dicking around with power plans, is what is expected of you :-)
    Really. I expect everyone here, has had a kick at that can,
    at some point. That would be this stuff. People multi-booting,
    need to disable Fast Startup for example.

    ÿÿÿÿ Power Options

    ÿÿÿÿ "Change settings that are currently unavailable"

    ÿÿÿÿÿ (which is a transitory state sfter switching on hiberfile,
    ÿÿÿÿÿÿ and the menu having hibernation added to it as an option)

    This is the interface that allows adding Hibernation to the
    shutdown menu. To do this from the registry, is an actual bitch
    (there are a couple hundred registry settings that control power states). >>> While people have written up procedures for doing things that way,
    it's not a common topic of discussion.

    ÿÿÿ https://us1.discourse-cdn.com/spiceworks/optimized/4X/0/0/
    f/00ffd4fb8a2219c82c8e1897f64242d8ab94932b_2_690x409.png

    If you have a hiberfil.sys and no Hibernate in the menu, then that is a
    likely state that the APC created. As that is the materials
    it needs for the thing to work.

    ÿÿÿÿÿ Paul


    After reading Jeff's and your reply...I noticed two items that seem to
    point to more info or comments needed.

    Jeff stated - Power Plan profile specifies never for 'Hibernate'
    ÿÿThat doesn't necessarily imply that hibernate was turned off, only
    that the Power Plan profile has a never Hibernate option.
    - Afaics, the only option for 'never' hibernate exists in the Power
    Options(Balanced or Performance) profile in the Sleep category
    ÿÿ* Hibernate after (On Battery or Plugged in)
    ÿÿ* HIbernate appears in a Power profile under the Battery
    settings(Critical Battery action and Low Battery action) where
    'Hibernate' is an option - the choice of 'Never' does not exist{Note:
    Low Battery action does contain a 'Do nothing' choice.

    This device has 24GB RAM...a 50% hibernate would be around 12 GB.
    ÿÿ- with hibernate enabled on this device, the hiberfil.sys is
    4.7GB(~20%)...Jeff reported 27 GB for 64GB RAM(42%).

    I'm still of the position that
    a. if a hiberfil.sys exists, not mattering how it was created(Windows,
    user enabled, UPS Power unit), then Windows should show hibernation as
    being enabled via a admin Powershell or Command.com panel regardless of
    the presence of a 'Never' setting(somewhere in the Power Plan profile)
    ÿÿ powercfg /a
    and
    b. if a hiberfile.sys exists, 'Hibernate' may/should also be present in
    the Power Options 'Choose what the power buttons do' settings(along
    with the options for Fast Startup, Sleep, Lock'.
    Since multiple power plans are defined and only one is selected, a few observations are in order: 1) some plans may specify hibernate and others may not and 2) just because the selected plan has not elected to enable hibernate does not mean that hiberfil.sys need not be available - a
    program or user can change the profile in use at any time or modify a
    plan's parameters. So the OSÿ must be rather loosey-goosey with the management of all this stuff.

    I must note that I have no special knowledge on this topic and haven't
    read any M$ papers on it. Therefore I might be full of shit. My knowledge
    is simply that of a user reasoning from observation and a limited amount
    of experimentation.

    For powercfg /a with Hibernation enabled (i.e. powercfg /h on)
    PS C:\WINDOWS\system32> powercfg /a
    The following sleep states are available on this system:
    Standby (S3)
    Hibernate
    Hybrid Sleep

    The following sleep states are not available on this system:
    Standby (S1)
    The system firmware does not support this standby state.
    Standby (S2)
    The system firmware does not support this standby state.
    Standby (S0 Low Power Idle)
    The system firmware does not support this standby state.
    Fast Startup
    This action is disabled in the current system policy.

    For Powercfg /a with Hibernation disabled (i.e. powercfg /h off)
    The following sleep states are available on this system:
    Standby (S3)

    The following sleep states are not available on this system:
    Standby (S1)
    The system firmware does not support this standby state.
    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.

    ==>> Note the results when Hibernation is Off, indicates Hibernation
    has not been enabled.
    - Looks like the current condition, not what the motherboard supports.


    --
    ...w­¤?ñ?¤

    --- PyGate Linux v1.5.5
    * Origin: Dragon's Lair, PyGate NNTP<>Fido Gate (3:633/10)
  • From Stan Brown@3:633/10 to All on Sunday, January 25, 2026 08:00:17
    On Sun, 25 Jan 2026 01:59:29 -0700, Jeff Barnett wrote:
    I think the above command tells what the motherboard supports, not what
    is enabled. For example, I have not enabled fast boot in the BIOS but
    that command shows it as possible.

    I think it's more complicated than that. Here's my output. Notice
    that Fast Startup is disabled by system policy, not in firmware.

    The following sleep states are available on this system:
    Standby (S3)
    Hibernate
    Hybrid Sleep
    The following sleep states are not available on this system:
    Standby (S1)
    The system firmware does not support this standby state.
    Standby (S2)
    The system firmware does not support this standby state.
    Standby (S0 Low Power Idle)
    The system firmware does not support this standby state.
    Fast Startup
    This action is disabled in the current system policy.

    --
    "The power of accurate observation is frequently called cynicism by
    those who don't have it." --George Bernard Shaw

    --- PyGate Linux v1.5.5
    * Origin: Dragon's Lair, PyGate NNTP<>Fido Gate (3:633/10)
  • From Jeff Barnett@3:633/10 to All on Sunday, January 25, 2026 10:30:46
    On 1/25/2026 7:02 AM, ...w­¤?ñ?¤ wrote:
    Jeff Barnett wrote on 1/25/2026 1:55 AM:
    On 1/24/2026 11:05 PM, ...w­¤?ñ?¤ wrote:
    Paul wrote on 1/24/2026 10:16 PM:
    On Sat, 1/24/2026 11:26 PM, Jeff Barnett wrote:
    On 1/24/2026 7:23 PM, Paul wrote:
    On Sat, 1/24/2026 8:29 PM, Jeff Barnett wrote:
    On 1/24/2026 5:37 PM, ...w­¤?ñ?¤ wrote:
    Jeff Barnett wrote on 1/24/2026 12:56 PM:
    On 1/24/2026 10:07 AM, ...w­¤?ñ?¤ wrote:
    Jeff Barnett wrote on 1/24/2026 9:07 AM:
    On 1/23/2026 12:44 AM, ...w­¤?ñ?¤ wrote:
    micky wrote on 1/22/2026 4:26 PM:

    I suppose most of the readers of these newsgroups know that >>>>>>>>>>>>> for a full
    start from scratch it's required to run Restart, instead of >>>>>>>>>>>>> Shutdown
    followed by starting later.ÿ Even though I only learned >>>>>>>>>>>>> this a year ago
    and even though it's a bit counter-intuitive, you all know >>>>>>>>>>>>> that, right,
    (because if you're running with Fast Startup*** shutdown >>>>>>>>>>>>> saves the
    kernel and reuses it, but Restart never uses Fast Startup >>>>>>>>>>>>> and it
    rebuilds the kernel, with new values if the values have >>>>>>>>>>>>> changed).

    But maybe you did not know that you can get the benefit of >>>>>>>>>>>>> Restart and
    still turn your machine off if you press Shift while >>>>>>>>>>>>> clicking on
    Shutdown.ÿÿ How about that!!


    If Hibernation (and by extension, Fast Startup) is disabled >>>>>>>>>>>> (e.g., via powercfg -h off), the "Shutdown" button functions >>>>>>>>>>>> as a full, traditional shutdown - clears the system
    state(shuts down all processes) and clears temp memory and >>>>>>>>>>>> powers Off. Subsequent Powering on, re-initializes the o/s >>>>>>>>>>>> ÿÿÿÿ- which, incidentally is the same results as Shift- >>>>>>>>>>>> Shutdown.
    ÿÿÿÿi.e. you don't need to the keystroke combo if
    Hibernation is disabled.

    Restart(when Hiberation is disabled) does the exact same >>>>>>>>>>>> clearing but instead of shutting down, powers the device >>>>>>>>>>>> back on and re- initializes the o/s.
    I have Hibernation set to never in my power profile. However, >>>>>>>>>>> I have an APC UPS that will hibernate the machine in case of >>>>>>>>>>> an extended power outage; in other words, the APC software is >>>>>>>>>>> able to work around that setting. Does this setup change >>>>>>>>>>> anything said in this thread so far?

    Afaik, the UPS Hibernation feature requires enabling Windows >>>>>>>>>> hibernation.
    ÿÿÿÿi.e. When a power outage occurs, the UPS has to
    communicate with Windows and validate Windows hibernation >>>>>>>>>> state(enabled/ disabled), if enabled instruct Windows to
    hibernate, once done the UPS provides backup battery power for >>>>>>>>>> the duration of its capability.

    Lacking Windows hibernation, the UPS only provides battery >>>>>>>>>> power for the device(and Windows) for the duration of its >>>>>>>>>> backup battery capability.
    ÿÿÿÿ - no Windows hibernation

    I've not enabled hibernation (as said above) but the APC
    software seems to be able to do it anyway. Perhaps it changes >>>>>>>>> the power profile when necessary. I remember one of the disk >>>>>>>>> tester/ diagnostic packages that turned sleep off when it was >>>>>>>>> called and never bothered to restore it on its way out. So
    there is certainly some way to diddle the settings.

    See Paul's response, that echo's my input.
    ÿÿÿÿ=> Hibernation needs to be enabled in Windows.

    I believe (from my own experience) that Paul is incorrect in this >>>>>>> specific case. The APC software (OS level stuff) can when it
    decides it's time to shutdown because of battery drain, etc, can >>>>>>> arrange that hibernation works whether the user has enabled it or >>>>>>> not. I've noted it's happening a few times.

    I think there has to be a hiberfile (C:\hiberfil.sys) and
    it is typically equal in size to 50% of memory or a larger
    percentage. Via compression, the RAM content written out to
    the hiberfile is smaller than the physical size. Most sessions
    on Windows are quite small, so only a fraction of the reserved
    hiberfile space is used.

    ÿÿÿÿ powercfg /aÿÿÿÿ # check supported ACPI states.
    ÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿ # Hibernation is S4. Mine is disabled right now. >>>>>> ÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿ # Aÿÿ shutdown /hÿÿ would generate an error
    of some sort.

    ÿÿÿÿ powercfg /h onÿ # Add Hibernation, then verify with the first >>>>>> command
    ÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿ # Check for hidden file on the root of C:
    with dir /ah in command prompt

    There is also some procedure at startup, which may be writing
    something to the header of the hiberfile. The hiberfile is
    "invalidated"
    as part of startup, such that it cannot be reused immediately to
    restore the same session ("like it was GroundHog day").

    Otherwise, without using the hibernation feature, little in the
    way of wear, happens because of the existence of the hiberfile.

    If you were installing the APC software, it is possible there is
    sufficient elevation at install time, for the APC software to be
    using powercfg and switching the hiberfile on and reserving the
    necessary space.

    Once the hiberfile exists, the normal set of system commands
    should work, to generate a hiberfile. The command from the UPS
    should be terse -- it isn't always a super-intelligent processing
    thing. Any application loaded into the host OS, has to do the
    more intelligent part. The UPS should not be sending this
    command, as written. That would be an exploit waiting to happen.

    ÿÿÿÿ shutdown /h
    Paul, the power plan/profile that I've selected specifies "never"
    for hibernate. However, there is a ~27GB hiberfil.sys for my 64GB
    memory on the C disk. I presume that the APC software ensures that
    such a file exists and knows how to flip bits in the header to
    inform the BIOS that this is a hibernate. There was no hiberfil.sys >>>>> with the "same" software and power plan/profile on my prior Windows >>>>> 7 machines so I assume the necessary structures were consed when
    needed. I believe that APC takes responsibility to ensure this all
    works properly - I believe the majority of their users are office
    works using company machines. It would be lunacy on their part to
    expect them to know how to dick around with power plans, etc. In
    fact, their IT department has locked them out of anything at all
    interesting.

    I don't think there is a way, to tell who did that :-)

    You could check the Event Viewer, for the evidence, but I don't
    know if it identifies the executable that is doing it.

    In any case, the weird hiberfil.sys size, suggests Windows
    didn't do that. I thought 50% was a "popular" Windows choice.
    While there are ways to select custom percentages, there is
    likely to be some lower limit on size choice.

    And dicking around with power plans, is what is expected of you :-)
    Really. I expect everyone here, has had a kick at that can,
    at some point. That would be this stuff. People multi-booting,
    need to disable Fast Startup for example.

    ÿÿÿÿ Power Options

    ÿÿÿÿ "Change settings that are currently unavailable"

    ÿÿÿÿÿ (which is a transitory state sfter switching on hiberfile,
    ÿÿÿÿÿÿ and the menu having hibernation added to it as an option)

    This is the interface that allows adding Hibernation to the
    shutdown menu. To do this from the registry, is an actual bitch
    (there are a couple hundred registry settings that control power
    states).
    While people have written up procedures for doing things that way,
    it's not a common topic of discussion.

    ÿÿÿ https://us1.discourse-cdn.com/spiceworks/optimized/4X/0/0/
    f/00ffd4fb8a2219c82c8e1897f64242d8ab94932b_2_690x409.png

    If you have a hiberfil.sys and no Hibernate in the menu, then that is a >>>> likely state that the APC created. As that is the materials
    it needs for the thing to work.

    ÿÿÿÿÿ Paul


    After reading Jeff's and your reply...I noticed two items that seem
    to point to more info or comments needed.

    Jeff stated - Power Plan profile specifies never for 'Hibernate'
    ÿÿThat doesn't necessarily imply that hibernate was turned off, only
    that the Power Plan profile has a never Hibernate option.
    - Afaics, the only option for 'never' hibernate exists in the Power
    Options(Balanced or Performance) profile in the Sleep category
    ÿÿ* Hibernate after (On Battery or Plugged in)
    ÿÿ* HIbernate appears in a Power profile under the Battery
    settings(Critical Battery action and Low Battery action) where
    'Hibernate' is an option - the choice of 'Never' does not exist{Note:
    Low Battery action does contain a 'Do nothing' choice.

    This device has 24GB RAM...a 50% hibernate would be around 12 GB.
    ÿÿ- with hibernate enabled on this device, the hiberfil.sys is
    4.7GB(~20%)...Jeff reported 27 GB for 64GB RAM(42%).

    I'm still of the position that
    a. if a hiberfil.sys exists, not mattering how it was
    created(Windows, user enabled, UPS Power unit), then Windows should
    show hibernation as being enabled via a admin Powershell or
    Command.com panel regardless of the presence of a 'Never'
    setting(somewhere in the Power Plan profile)
    ÿÿ powercfg /a
    and
    b. if a hiberfile.sys exists, 'Hibernate' may/should also be present
    in the Power Options 'Choose what the power buttons do'
    settings(along with the options for Fast Startup, Sleep, Lock'.
    Since multiple power plans are defined and only one is selected, a few
    observations are in order: 1) some plans may specify hibernate and
    others may not and 2) just because the selected plan has not elected
    to enable hibernate does not mean that hiberfil.sys need not be
    available - a program or user can change the profile in use at any
    time or modify a plan's parameters. So the OSÿ must be rather loosey-
    goosey with the management of all this stuff.

    I must note that I have no special knowledge on this topic and haven't
    read any M$ papers on it. Therefore I might be full of shit. My
    knowledge is simply that of a user reasoning from observation and a
    limited amount of experimentation.

    For powercfg /a with Hibernation enabled (i.e. powercfg /h on)
    PS C:\WINDOWS\system32> powercfg /a
    The following sleep states are available on this system:
    ÿÿÿ Standby (S3)
    ÿÿÿ Hibernate
    ÿÿÿ Hybrid Sleep

    The following sleep states are not available on this system:
    ÿÿÿ Standby (S1)
    ÿÿÿÿÿÿÿ The system firmware does not support this standby state.
    ÿÿÿ Standby (S2)
    ÿÿÿÿÿÿÿ The system firmware does not support this standby state.
    ÿÿÿ Standby (S0 Low Power Idle)
    ÿÿÿÿÿÿÿ The system firmware does not support this standby state.
    ÿÿÿ Fast Startup
    ÿÿÿÿÿÿÿ This action is disabled in the current system policy.

    For Powercfg /a with Hibernation disabled (i.e. powercfg /h off)
    The following sleep states are available on this system:
    ÿÿÿ Standby (S3)

    The following sleep states are not available on this system:
    ÿÿÿ Standby (S1)
    ÿÿÿÿÿÿÿ The system firmware does not support this standby state.
    ÿÿÿ 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.

    Note the results when Hibernation is Off, indicates Hibernation
    has not been enabled.
    ÿ- Looks like the current condition, not what the motherboard supports.
    It seems that "powercfg /h off" is quite different to hibernate set to
    never in the selected power profile. And the APC software can use direct appeal to powercfg to ensure hibernate is available in an emergency.
    Your post clears up some of the mystery for me!
    --
    Jeff Barnett



    --- PyGate Linux v1.5.5
    * Origin: Dragon's Lair, PyGate NNTP<>Fido Gate (3:633/10)