Today I woke up, went to check the progress and wouldn't you know, Windows Update updated the computer and rebooted, and what I was waiting for was aborted... So fucking tiresome to use shit like this.
Today I woke up, went to check the progress and wouldn't you know, Windows Update updated the computer and rebooted, and what I was waiting for was aborted... So fucking tiresome to use shit like this.
It's annoying to have to shuffle files over to it, if that's needed for its job, but I think it's still a worthwhile thing to consider (it's insane that we've gotten to this point, but such is life). If it isn't workable, then fine. But if it is, the hassle of shuffling files using external SSDs or whatever is probably better, or at the very least more consistent, than turning on your machine one day and finding it corrupted itself due to an update, or the software in question got a UI update which breaks your workflow for a month.
Regardless, thanks for the ideas!
The Windows Update processes were really a stubborn bunch in W10 - not sure if anything have changed in W11. These probably were given the highest privileges that made them spawn periodically outside any scheduled tasks settings somehow. Some 3rd-party tools were able to neuter most of them but these were like zombies. Continuously rising up.
Hibernate? Gone by default.
Sleep? Ineffective 1/2 the time because a Microsoft utility force-wakes it.
It's sad that 15 year old Windows system was more usable than one today.
1. Laptop has most of its battery life still because it slept successfully and predictably
2. Laptop drained battery to 5% and only then slept
E.g. https://gist.github.com/LuisAGC/843a2a45617d7ad05687c2f8a15c... or https://github.com/TheBear1616/CapsLock-PreventSleep-Script/...
Scroll lock and F13 are commonly used