I have experienced and verified all stated errant behaviors on two devices. Given this was initially narrowed down to something to do with UAC, SecureDesktop, Elevated apps, etc., and the primary app seeming to be involved most often in relation to the inability to hibernate or lock the screen was Windows Terminal, that's where the gaze was directed, which uncovered this hidden nugget which caught my eye:
Windows Terminal v1.21.2701.0 - GitHub
"We have encountered a pretty annoying hanging issue on Windows 11 23H2, for which we have***paused the rollout of Terminal 1.21 Stable.***If you encounter a hang when resuming from sleep mode or unlocking your display, sorry! Relief is coming in the form of a Windows Update."
- I further suspect this may also be impacting only devices which have both discrete and onboard GPUs.... for the rest of you, is this the case for you?
- This was first encountered on a domain-joined device, which has undergone multiple Windows "re-install-in-place" events using various MS-provided images or generated via uupdump.
- For the initial and subsequent devices, Spotlight has never been enabled.
- Attempted:
- power settings resets,
- All available MS troubleshooters
- reinstallation of all pnp devices
- disablement of audio devices
- adjustment of power plan to set hdd to never turn off
- multiple sfc /scannow or dism repairs
- laptop manufacturer-provided drivers only
- component manufacturer-provided drivers
- disablement of discrete gpu
- bios-set hybrid graphics
- bios-set os auto graphics\
- manually and completely uninstalling windows terminal
- installing alternate and preview builds of windows terminal
- New user profiles
- Redeploying system using 100% laptop manufacturer provided image
- Deploying system using 100% microsoft provided image
- No AV - stock Win11 24H2
- Latest cumulative preview update(s) that hit today.
- completely disabling uac
- Likely a lot more stuff that was a waste of time over the past month (or two?)
The ONLY thing that has worked: grant user account local admin rights... HOWEVER! The problem still technically persists, and is seemingly directly related to:
Elevated applications which utilize credentials OTHER than the logged on user. Period... I can have WT launched and elevated using the logged in user account with local admin rights, and hibernate or lock the screen. I can then launch another WT, elevated, using credentials other than the logged in user, and hibernation or locking fails.
One more odd quirk to add to this fantastic-fun-time-annoying-as-expletive-list: If the user does not have admin rights, and attempts to launch an application such as say, VirtualBox, which will demand elevation, the SecureDesktop loads (screen is dimmed,) however NO login prompt appears... After the typical timeout period, the system then behaves as all have previously described, identical to the hibernate/lock failure... The curious bit is that other applications which may otherwise demand admin rights, like say, Windows-X+A, dims the screen and presents the login prompt fine. Of course, don't dare hibernate with THAT subsequent window open! ;)
I suppose one final bit to mention that I haven't seen referenced: For the hibernation failure, specifically, if I simply let the system sit, after about 30 minutes it will rather reliably bluescreen with an internal_power_error, with a very sparse and largely unhelpful dump.
I further suspect this issue seems to be under-reported simply due to the userbase it is impacting: higher-end hardware, and based on the responses, those with either IT administrative functions, or those in environments with very specific security restrictions imposed, all likely leading to a somewhat marginal group of users whose probability of encountering these particular problems is lowered still by the specific workflows required to forcibly self-impose a rage quit for the day when you lose all your work after issuing a command designed to save your work - hibernate!
I still love you to pieces, Microsoft, but please, please, for my sanity, and the benefit of everyone else suffering this silly glitch, fix this.