System hibernates despite "hibernate after" set to "never"

Yes. Both the OP and I have tried to disable the curse of S0 Modern standby [reported in other threads]. We both suffered serious side-effects.

I've been collating my old notes in the hope that I spot a potential remedy that I did not think of at the time. I'll be staring at them later today and might make a fourth attempt.
- Both the OP & I suffered network adapter problems with S0 disabled.
- I also found that Event viewer kept crashing.
- In my case [I can't remember what the OP's experience was], S0 was successfully disabled but S3 Sleep remained disabled.
- If I could fix the network+events side-effects, I would happily accept the limitation and just use On/Hibernation/Off.
- I would be particularly pleased if disabling S0 led to Task scheduler being able to wake the computer from hibernation. Despite all the right settings being made, mine refuses to do so. The OP's S0 computer can do this anyway which surprises me because all the MS documentation I've seen indicates that this should not be possible.

Thanks for reporting that EventID 507 for exiting S0. I have been able to identify the event for entering S0 [506] and I have also found that the events are recorded for both S0 Connected & Disconnected standby. I've just finished editing my post #40 with the results of my experiments.


All the best,
Denis

I'm amazed. In Various Sleep / ModernStandby Issues, Related to Battery Drain I knew what the entering & leaving S0 Modern standby events were over a year ago and I had put them into a custom view yet there is nothing in my backups or my notes about it.

Thanks,
Denis

I have improved the script I posted in #22 for waking up the display and keeping it on without altering any Power options settings.
- I have replaced the double-use of NumLock with a single use of another key because I discovered that NumLock was sometimes left in its unwanted state.
- I assume that the problem was caused by the second use being skipped because Windows had not completed actioning the first use in time for the second one to get noticed.

Keep display on.bat

Code:

:: Posted by Denis, Try3 in My KeepDisplayOn.bat [posts #22, #45] - TenForums  https://www.tenforums.com/performance-maintenance/187868-system-hibernates-despite-hibernate-after-set-never-post2332632.html#post2332632
:: Purpose - Stop the display turning off without changing power options and, if called as a SubRoutine from another script, wake the display.
:: Common usage - Run this script independently from a dedicated shortcut set to run it minimised and with a chosen icon
:: Common usage - Closure 1  By closing its window manually, or
:: Common usage - Closure 2  by running the companion independent script EndKeepDisplayOn which is a single line command -  taskkill /fi "WINDOWTITLE eq Keep display on"
:: Method - Use VBS SendKeys to simulate pressing a keyboard key.  
:: Method - I've chosen the unimplemented F14 key to avoid side-effects.  Thank you sriramkannan95 for the F14 suggestion - https://gist.github.com/valdergallo/0e05d9e0c90b7be77458
:: Method - Echos are not suppressed because I always run it minimised.  Others might choose to suppress them by deleting the leading ::  from the line @Echo Off below
:: Testing - This script has been tested on three S3 Sleep computers and one S0 Modern standby computer.  No side-effects were seen.

:: @Echo Off

Title Keep display on

set ThisVBScript="%TEMP%\KeepDisplayOn-%RANDOM%.vbs"
    Echo Set WshShell = WScript.CreateObject("WScript.Shell") > %ThisVBScript%
    Echo WshShell.SendKeys "{F14}" >> %ThisVBScript%
:ReRunKeepDisplayOn
    Call %ThisVBScript%
:: Wait a while before re-running the vbs
    TimeOut /T 20 /NOBREAK >nul
    GoTo ReRunKeepDisplayOn

:: Pause during testing

All the best,
Denis