33
Sysadmin shock as Windows Server 2025 installs itself after update labeling error
(www.theregister.com)
this post was submitted on 07 Nov 2024
33 points (97.1% liked)
Technology
1421 readers
824 users here now
Which posts fit here?
Anything that is at least tangentially connected to the technology, social media platforms, informational technologies and tech policy.
Rules
1. English only
Title and associated content has to be in English.
2. Use original link
Post URL should be the original link to the article (even if paywalled) and archived copies left in the body. It allows avoiding duplicate posts when cross-posting.
3. Respectful communication
All communication has to be respectful of differing opinions, viewpoints, and experiences.
4. Inclusivity
Everyone is welcome here regardless of age, body size, visible or invisible disability, ethnicity, sex characteristics, gender identity and expression, education, socio-economic status, nationality, personal appearance, race, caste, color, religion, or sexual identity and orientation.
5. Ad hominem attacks
Any kind of personal attacks are expressly forbidden. If you can't argue your position without attacking a person's character, you already lost the argument.
6. Off-topic tangents
Stay on topic. Keep it relevant.
7. Instance rules may apply
If something is not covered by community rules, but are against lemmy.zip instance rules, they will be enforced.
Companion communities
!globalnews@lemmy.zip
!interestingshare@lemmy.zip
Icon attribution | Banner attribution
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
The issue seems to be that Microsoft has started to reuse KB#s for updates across different channels, meaning update KB 5044284 (the update in question) can be a Security update for Windows (Desktop) 11, and be an optional OS upgrade for Windows (Server) 2022, just shaeing the same name.
Because that's obviously a wonderful idea with no potential downsides.
That appears to be what happened here, but additionally a mistake was made and the Server patch was labelled with the details (that it's just a security update) for the Desktop one.
Also doesn't help that Microsoft only has one documentation page for any given update number, and the one for this one only lists the details of the desktop update.
It was a mistake on Microsofts part I think. They don't normally reused KBs.