All the power setting have been reviewed extensively - including this item - which was wreaking havoc with my audio interfaces.
To be clear - the only setting in this plan that was not addressed (originally) was in my opening post:
The only way I could get this value to show in my Power Plan was to use Power Settings Explorer and expose it.
Now - on the Win 11 box - this timeout value IS bang on - the machine goes right back to sleep after 2 minutes of no activity.
But this setting is identical to the Win 10 machine here - and that one wakes up and stays up - regardless of this two minute setting- which is exactly what I want.
This tutorial does what it says - but the setting is not actually removed (as in stripped from the system) - just hidden from view.
This setting (and many many more) are built right into the power subsystem. You can get a fascinating look under the "power" hood by using the Power Settings Explorer tool (easily found on the Internet).
I was astounded by what we cannot see - after you give this tool a whirl.
Haven't changed anything yet. That initial screenacap was simply to see what that "hidden" value was on the Win 11 machine (2). But when I found out the same setting with the identical value - is also set on this Win 10 machine - and it behaves exactly the way I want it to - that is the mystery.
To be honest - I have never given any of these obscure power settings a single thought over at least 7-10 years with my last 2-3 builds of my studio machine. I simply set S3 in the BIOS - kick in the High-Performance Power Plan (in Windows 10) set it and forget it.
This machine then would wake at 5:10am - and stay awake all day if I choose - without ever touching a key or even going near the machine.
All (presumably) with this Unattended 2-minute timeout set over that entire 7-10 year period.
What it appears is that when you tell Windows 10 (via the Power Plan settings) to NEVER sleep - it actually listens.
But Windows 11 does not get that memo - I say Never sleep and it does what it wants anyway.
I discovered that unattended setting in windows 10 because I had the exact issue on 10 that you’re having on 11. Set it to a value of 0 and see if that resolves your issue.
