Wondering if it a “phone home” app keeping it awake. Something that ms won’t allow to be shut off, or will keep reenacting it with updates?
Yes, which is why I think looking at the sleep=hibernate state and their settings is like looking at a result and not a cause. I don’t think the core sleep/hibernate functions are failing in any general sense. I think there are core conditions even they must acknowledge and give higher authority to, and some such condition is refusing to give up control to sleep/hibernate just because the sleep/hibernate settings suggest everything should allow sleep/hibernate to begin and remain in place as long as they should.
If I knew how to set up a background app to keep making snapshots of all processes in a task-manager screen, including the many parameters they can show for the processes, I would recommend using that as a tool to try to identify what, each time, is running (& using memory and making I/Os) at each stage from the appointed onset of sleep/hibernate until the system “reawakened”.
But alas, I can only imagine such a tool but cannot create it.
It would require making a .bat file that would:
(a) the entire batch procedure would run a loop until it was stopped by either some setting in the procedure or by rebooting/restarting the system
(b) it would start by setting a value based on obtaining the time and another value to be wait time value representing either minutes or seconds you want the system to wait between task list results.
(c) it would use the command line prompt: c\>tasklist
(d) it could use any/any combination of the additional parameters to show various conditions for each entry in the task list:
/C (Priority) /O(rder by PID)
/D (show modules) /P(ause)
/H (threads) /T(ime)
/I(ntegrity) /U(ser names)
/L (Startup command) /U”owner”
/M(emory) /X (hex)
/N (class names) /Z (parent PIDs)
(d) the command noted in (c) would have the additional command setting of something like >>c:\log\test_%date:~10%%date:~4,2%%date:~7,2%-%time:~0,2%%time:~3,2%%time:~6,2%.log 2>&1
to create a logfile for each tasklist result with a unique time stamp in the name of each log file
(e) then a check of the system time will have to check how much greater is the system time than the system ti time value set in (b) and is the difference equal to or greater than the wait time you told (b) to set.
(f) then if wait time value has not been reached, the batch instruction would use goto, to go back to (e), else
the batch instruction would use goto to back to (b).
The entire .bat process would keep making tiny little log files of the running list of processes in tasklist until you stopped the batch file by rebooting/restarting the system.
Then the log files could be checked.
However, couple of task parameters I thought would be useful are not available in the parameters you can add to the tasklist command, and they would be disk usage (was anything writing to disk) and cache-memory page I/Os (activity writing & reading from cache-memory). Changes in those things could help determine what was the most “in use” activity(ies) when “sleep” or “hibernate” settings failed to achieve their set parameters. Somewhere in that might be an activity that the sleep or hibernate function should have been able to turn-off/set to sleep.