Is it not a thing on Desktop? I don't know if it was ever available, I just turned all that stuff off via command line, and powercfg /a lists only normal standby (S3) and hibernation as available, nothing else.
Are you saying the only difference between hibernation and "actually off" is that the PC can wakeup from peripherials or network events? Unplugging the power cable after hibernation and plugging it in again will force the PC from S4 to S5, but it will resume normally from hibernation when it's...
That's useful to see which devices have the wakeup enabled (powercfg -devicequery wake_armed), but everything else does exactly what the device manager GUI does. I need some setting or group policy to disable wakeup altogether. Or in the worst case, a command to disable wakeup for every device...
I know it's a real pain to hunt down all the different settings which make the PC wake up in the middle of the night, such as wake timers in the power options, automatic maintenance, and individual devices (see screenshot).
I disabled everything that can wake up the PC but it still happens...
Actually only Enable the Built-in Admin at boot applies (I said only offline file system access is possible in that scenario).
However, the recovery boot console won't work with TPM-secured Bitlocker (if you don't have the recovery key). Even if you can read the Bitlocker volume master key...
Add an admin account with only having (offline!) access to the file system.
I already achieved what I needed to achieve, I was just wondering if there's possibly an easier and/or smarter way when the utilman method is blocked.
I don't need to use it often, so I didn't test it extensively, i.e. whether that's now default out-of-the-box behavior or whether it requires specific Defender settings. I encoutered this behavior on a domain-connected laptop with a fresh Win 11 (so it might have been a group policy thing as...
A few years ago MS "fixed" the most widely used exploit for resetting a user password by replacing any of the "ease of access" tools (utilman.exe, osk.exe, sethc.exe and so on) with a copy of cmd.exe to get a console with system privileges. Of course you already needed file system access for...
It sounds promising, but it looks like "just" a core affinity tool that blocks processes from using E-cores. I want the encoder to use all cores, not just P-cores, but prevent Windows from kicking it off the P-cores when it's in the background.
It's (I suppose) a Win11 problem and our applications are a small niche for these CPUs. Dedicated "high performance computing" tends to be done with Threadrippers or straight away server CPUs and on other OSes, so nobody will ever care about this, unfortunately.