@[email protected] to [email protected]English • 1 day agoSysadmin shock as Windows Server 2025 installs itselfwww.theregister.commessage-square83fedilinkarrow-up1552arrow-down112
arrow-up1540arrow-down1external-linkSysadmin shock as Windows Server 2025 installs itselfwww.theregister.com@[email protected] to [email protected]English • 1 day agomessage-square83fedilink
minus-square@[email protected]linkfedilinkEnglish4•21 hours agoWrong. Microsoft labelled the update as a security update
minus-square@[email protected]linkfedilinkEnglish-1•15 hours agoDo you know that’s nor a mistake and done fully malicously knowing that? Please give me your source.
minus-square@[email protected]linkfedilinkEnglish5•edit-212 hours agoRead the fucking article. The patch id couldnt be any clearer.
minus-square@[email protected]linkfedilinkEnglish1•5 hours agoAnd you make absolutely no error? Besides tbat: Should MS have caught the errorenous ID (assuming it truly was errourneous and not knowingly falsely labeled)? Absolutely. Should the patch management team blindly release all updates that MS releases? No?
Wrong.
Microsoft labelled the update as a security update
Do you know that’s nor a mistake and done fully malicously knowing that? Please give me your source.
Read the fucking article.
The patch id couldnt be any clearer.
And you make absolutely no error?
Besides tbat:
Should MS have caught the errorenous ID (assuming it truly was errourneous and not knowingly falsely labeled)? Absolutely. Should the patch management team blindly release all updates that MS releases? No?