Windows after pressing shutdown and update: you wanted to use me still right????
this post was submitted on 27 Aug 2025
500 points (94.2% liked)
linuxmemes
27039 readers
998 users here now
Hint: :q!
Sister communities:
Community rules (click to expand)
1. Follow the site-wide rules
- Instance-wide TOS: https://legal.lemmy.world/tos/
- Lemmy code of conduct: https://join-lemmy.org/docs/code_of_conduct.html
2. Be civil
- Understand the difference between a joke and an insult.
- Do not harrass or attack users for any reason. This includes using blanket terms, like "every user of thing".
- Don't get baited into back-and-forth insults. We are not animals.
- Leave remarks of "peasantry" to the PCMR community. If you dislike an OS/service/application, attack the thing you dislike, not the individuals who use it. Some people may not have a choice.
- Bigotry will not be tolerated.
3. Post Linux-related content
- Including Unix and BSD.
- Non-Linux content is acceptable as long as it makes a reference to Linux. For example, the poorly made mockery of
sudoin Windows. - No porn, no politics, no trolling or ragebaiting.
4. No recent reposts
- Everybody uses Arch btw, can't quit Vim, <loves/tolerates/hates> systemd, and wants to interject for a moment. You can stop now.
5. π¬π§ Language/ΡΠ·ΡΠΊ/Sprache
- This is primarily an English-speaking community. π¬π§π¦πΊπΊπΈ
- Comments written in other languages are allowed.
- The substance of a post should be comprehensible for people who only speak English.
- Titles and post bodies written in other languages will be allowed, but only as long as the above rule is observed.
6. (NEW!) Regarding public figures
We all have our opinions, and certain public figures can be divisive. Keep in mind that this is a community for memes and light-hearted fun, not for airing grievances or leveling accusations. - Keep discussions polite and free of disparagement.
- We are never in possession of all of the facts. Defamatory comments will not be tolerated.
- Discussions that get too heated will be locked and offending comments removed. Β
Please report posts and comments that break these rules!
Important: never execute code or follow advice that you don't understand or can't verify, especially here. The word of the day is credibility. This is a meme community -- even the most helpful comments might just be shitposts that can damage your system. Be aware, be smart, don't remove France.
founded 2 years ago
MODERATORS
me turning off the power supply: (i didn't have anything open so hopefully it's fine...)
load more comments
(1 replies)
I do yes | sudo pacman -Syu && sudo poweroff
(Update and poweroff)
"&&" will only run shutdown if the update runs correctly.
I do ";" to definitely run the shutdown after the update process exits. (Don't want to keep the system running if nothing is happening any more.)
I do "|" so it updates and shuts down at the same time
I do ";" to definitely run the shutdown after the update process exits.
If you're able to successfully boot the machine afterwards is not your concern?
what's fun in a successfully booting system? we are arch users for a reason!
Well, as I'm using Debian, maybe I'm a more cautious type.
I don't know about arch but my system usually boots fine after an upgrade. (Gentoo here)
If the update is successful. If there are failures in critical steps, well...
Doesn't it roll back to a previous state then?
No. It will boot the previous kernel, but the user experience will be at least suboptimal if some packages have already been removed during the upgrade, but the upgrade stopped at some point because a downloaded package was corrupt, leaving lots of dependent packages unconfigured. In case networking doesn't work, it's also inconvenient to manually download the affected package on another machine and transfer it with a usb stick onto the computer to restart the upgrade.
You don't need sudo to run poweroff on Arch, provided there's no other users logged into the system
And it's a login shell.
Assuming you enter your password upon running sudo, isn't there the risk of sudo's privilege timing out if pacman takes too long to complete? I believe I tried something similar, intending to run a one-liner I could start then walk away from. However, I ended up returning to see the system not rebooted hours later.
Or is yes somehow supposed to take care of this? Sorry, newish Debian user here who hasn't ventured outside the distribution much.
Yes, in this ~~command~~ one liner, the system should not power off when the update took too long.
Or is
yessomehow supposed to take care of this?
No, yes is simply answering all questions asked during the update procedure (start upgrade, replace config files, restart services) with "yes".
~~There's no timeout for sudo. When permitted, a process runs as root and then closes.~~
~~Also, the system will still shutdown when update fails because pipes do not care if previous commands exit with a nonzero code, unless pipefail is set.~~
Edit: i'm blind.
The command after && runs only if the previous command returns non-error exit status (0), if pacman returns error the latter command won't be executed.
Additionally there's probably a configuration option for sudo for it to not time out, but it doesn't matter since you can just use systemctl reboot as a normal user to reboot your system (at least on Debian). If that's too long I recommend to add this to your .bashrc (if you use Bash): alias reb='systemctl reboot' or something similar.
Maybe this is just a yay thing but I think if sudo priveleges run out while downloading the files it prompts you for your password again before performing the changes. That would lead to it either trying to use the yes output or getting stuck in the password prompt, only failing in the prior.
This entire problem could be solved by just running it as the root user.
load more comments
(2 replies)
ya'll aint just pulling out the power plug?
I flip the breaker whenever it's time to shut down.
Just do sysrq+s, sysrq+c (triggers panic) and flip the power switch for instant power off.
windows: installing updates, do not power off
me: the fuck you are dismantles laptop and rips out battery
Linux: shutdown now
One thing I've seen my computer do a few times: log me out, by itself. Some rare times I try and unlock back into my session, my current open and active user with my programs running, and instead I am greeted not by my desktop as it was when I locked the screen, but rather the lock screen as it was before I even logged in the first time around
Y'all don't delete WSUS, block all of the M$ IPs at both your HOSTS file and your router, and stop all update processes?
Do you even know how Windows works?
load more comments
(3 replies)
I thought the Windows update system is actually not too bad. At least compared to Mac.
Yea, it has a robust rollback system, which is part of why it takes so long now.
But... I only do updates a couple times a year to minimize the headache on my personal machines.
My work machines it's not my problem, but I reboot them at night a couple times a week, just in case.
Compared to Mac? Macβs is so much better? The number of times windows has fucked me over by updating on a restart.
load more comments
(4 replies)