@[email protected] to [email protected]English • 2 months agoSysadmin shock as Windows Server 2025 installs itselfwww.theregister.commessage-square93fedilinkarrow-up1576cross-posted to: [email protected]
arrow-up1564external-linkSysadmin shock as Windows Server 2025 installs itselfwww.theregister.com@[email protected] to [email protected]English • 2 months agomessage-square93fedilinkcross-posted to: [email protected]
minus-square@[email protected]linkfedilinkEnglish7•2 months agoWrong. Microsoft labelled the update as a security update
minus-square@[email protected]linkfedilinkEnglish-1•edit-21 month agoDo you know that’s not a mistake and done fully malicously knowing that? Please give me your source.
minus-square@[email protected]linkfedilinkEnglish7•edit-21 month agoRead the fucking article. The patch id couldnt be any clearer.
minus-square@[email protected]linkfedilinkEnglish-1•edit-21 month agoAnd you make absolutely no error? Besides that: 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 not 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 that:
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?