Path: ...!news.nobody.at!2.eu.feeder.erje.net!feeder.erje.net!fu-berlin.de!uni-berlin.de!individual.net!not-for-mail
From: Frank Slootweg <this@ddress.is.invalid>
Newsgroups: alt.comp.os.windows-11,comp.os.linux.advocacy
Subject: Re: This Is Why They Say Windows Is A Great OS -- If  Your Time Is Worth Nothing
Date: 31 Dec 2024 20:45:03 GMT
Organization: NOYB
Lines: 20
Message-ID: <vl1ok6.7ro.1@ID-201911.user.individual.net>
References: <vl1ff6$2c41l$1@dont-email.me>
X-Trace: individual.net YqJo9iR6PVUMgL1KW9+/rQ4QBcdd3uey6pfdwPPglblL/zYoJe
X-Orig-Path: not-for-mail
Cancel-Lock: sha1:DRLzzoPTwxWV43TvSkLCg61BxH0= sha256:JsdP+a1A9Uf/Gih0jPtUJ8o69A3M+DFxYIICEIpDgiE=
User-Agent: tin/1.6.2-20030910 ("Pabbay") (UNIX) (CYGWIN_NT-10.0-WOW/2.8.0(0.309/5/3) (i686)) Hamster/2.0.2.2
Bytes: 1832

Lawrence D'Oliveiro <ldo@nz.invalid> wrote:
> Yet another
> <https://www.zdnet.com/article/new-windows-11-24h2-bug-could-block-future-security-updates-see-whos-affected/>
> in the ongoing stream of bugs from Microsoft resulting from the
> Windows update process itself. This one breaks the ability to receive
> further security updates. So once you get it, how do you get an update
> to fix it? Particularly when there have already been updates that kept
> introducing their own new bugs?

  This is a bit of a corner case, i.e. limited timeframe, uncommon
way to update and somewhat uncommon way to install.

  Also the article is messing up the terminology, so I would take it
with quite a lot of salt.

  FWIW, my updates went without any glitches. Knock on wood.

  And FTR, in 20+ years I've had only one case - on only one of two
systems - where Windows Update was somwhat messed up. Not broken, but
re-offering already installed updates, so I wanted to clean it up.