shutdown -h now

You can shut down Windows even with a pending update. With Active Hours set up properly you can never have an unexpected reboot.

@kamen omg I have to crawl through that horrible settings screen constructed just in a way of prevention spyware disabling just set up some garbage shit like “Active Hours (c) (tm) (please don’t sue me)”? Miss me with that shit.

@kamen I ran a machine learning training model overnight. I expected hours upon hours of data in the morning, and there was no indication that an update was waiting to install when I went to bed. I woke up and found that Windows had updated and rebooted anyway, barely an hour after I went to bed. The whole night was wasted.

Active hours didn't help since I'm not usually active at night. It doesn't help with the weird outliers where I stay up late or wake up early. All I want is for my computer to just do what I tell it to do, and stop doing things without being told to do them. That's it. And that's what Linux gives me, which is why it's now my primary OS and I only use Windows for gaming (and even that isn't necessary as much any more with all the advancements in wine lately).

And let's not even get into the lack of QA testing with updates. Every major feature update, something huge breaks and Microsoft warns people to wait. Every single one. For YEARS.

@uyouthe Yeah, it sucks that it does shit like this by default, but it still can be set.

@kamen they're only like half a solution for a problem that didn't need to exist in the first place.

Windows is God awful and I look down on every one my colleagues who go “Ah windows is so much better than Linux”

For any operating system unplug the cable works all the time.

@kamen yeah it’s fine that they come and fuck me in the ass every single day but I can cancel that for one day in settings exactly at 3am in 48 simple steps!

@LotsOfCaffeine et. al.

One, you can just disable auto-restart, two, there's nothing stopping you from running "shutdown /p now" on Windows (it's been there since XP), and third, since too many people are still butthurt about receiving updates when shutting down their computer, Windows 10 now has separate buttons for "restart" and "update & restart" (same for shutdown). Also, a fresh installation of Windows 10 won't automatically restart your computer unless you've clicked a button on that "set up active hours" notification.

And as a side note, every single person complaining about Windows updates restarting their computer is guilty of having "System restart required" message on their Linux server for months, because they never bothered setting up proper failover and restart policies. Most likely restarting one of those devices would bring down their entire company...

@hitko not sure what you're talking about since I'm still getting force reboots
If I don't click "wait an hour", every hour, the system will just shut down.

@LotsOfCaffeine Sounds like you're still running a build from 2017 (that's when they've changed this whole thing with "wait an hour") which kinda makes your point irrelevant.

More recent builds give you what you can see below, which is "restart now", "schedule restart" (up to 7 days in the future), and "turn on [active hours]" which enables automatic restarts. Since I haven't turned active hours on, I can freely use my computer without disruptions, and it won't automatically restart.

And here's what the power options look like in recent Windows 10 builds:

@hitko well since the update utility is broken to hell, I'm stuck on old that version unless I completely reinstall, as usual.

This is an issue that Microsoft created themselves, for no reason at all.
Why was any of this considered okay to begin with?

@LotsOfCaffeine it's funny, I complain about updates always happening when I don't want them to, but now I actually want the new 2004 update and it won't even install. Still says it's not available yet.

@EmberQuill I still don't get how any of this gets messed up. Unix like systems have had package managers to do all of that for decades.

@LotsOfCaffeine Exactly! I've had fewer problems with Arch Linux than I've had with Windows, which is ridiculous. I've had maybe two problems updating Arch in the five or six years I've been using it. Both problems were easily fixed and were usually due to a well-documented breaking change that is fully explained on the front page of their website.

Meanwhile, every Windows feature update fails repeatedly for weeks on end with useless error messages and my only solution is to either wait and try again later or reinstall the whole OS. It's not like I've done anything special either. I've barely touched any registry settings or System32 files. But my Linux machine is customized to hell and still updates with few issues.

I am a simple Linux user; I see Windows or macOS - I hate. With that being said, fuck windows.

chad poweroff

@LotsOfCaffeine Right. You've been blocking updates for 3 years, and somehow it's still Microsoft's fault. And when the regular "[a significant percent] of Windows devices are still vulnerable to [an old CVE]" article comes around, you'll comment "fuck Windows", even though it's been fixed long ago and it's people like you who don't update their computers that are the problem. Which is ultimately the reason Microsoft at one point decided to force mandatory updates and minimise exposure to known CVEs, and the reason you have to deal with that annoying message.

@hitko it's not that I don't want to update, but rather that I can't, since the update utility fails constantly.

Had this on 3 separate machines, with separate version, ISOs, hardware and network.

You can talk as much as you want, i will blame ms for this.
And it's one of the reasons I never touch a Windows system unless I have to.

Not a lot of people know this, but the -p switch is shorthand for '--please'

@kamen unfortunately you can't set your active hours to "don't fucking shut down"

My computer has no rights, it can take its break once i have a replacement for it ready.

that top right face cracked me up

@Homuncoolus alternative version

@LotsOfCaffeine thank you😂