this post was submitted on 07 Jun 2024
1355 points (97.5% liked)
linuxmemes
21465 readers
1219 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 members of the community for any reason.
- 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.
- These rules are somewhat loosened when the subject is a public figure. Still, do not attack their person or incite harrassment.
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
sudo
in Windows. - No porn. Even if you watch it on a Linux machine.
4. No recent reposts
- Everybody uses Arch btw, can't quit Vim, and wants to interject for a moment. You can stop now.
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 fork-bomb your computer.
founded 1 year ago
MODERATORS
you are viewing a single comment's thread
view the rest of the comments
view the rest of the comments
This is why you check your equipment before any important events
What if Windows decided to update after you finished checking the equipment? I mean, they do use AI to determine the worst time for an update...
They update on two Tuesdays a month, and have done that at least since XP. Even with the most reboot-keen settings, the update doesn't happen until the time of day you're least likely to be using the machine based on when you typically do it. It tells you when that time will be and gives you several hours of notice with a popup with the option to delay. Depending on the variant of Windows you're using, you have settings to delay a forced reboot for up to a week (Home), a month (Pro) or forever (Enterprise). Obviously, that's not enough to make sure no one ever gets updates forced on them when they don't want them, and it would be nice if there was a way to distinguish users who know what they're doing from users who don't so people who do could be given more power to control if and when they install updates, but it is enough to ensure that checking the equipment before you use it is enough, potentially two weeks in advance.
Correction: It updates every second Tuesday of the month. (Not including any potential "Preview" updates which might get released. Those are all optional updates, though.)