Path: ...!eternal-september.org!feeder3.eternal-september.org!news.eternal-september.org!eternal-september.org!.POSTED!not-for-mail
From: Lawrence D'Oliveiro <ldo@nz.invalid>
Newsgroups: comp.os.linux.advocacy,alt.comp.os.windows-11
Subject: Dimdows Decay Syndrome Continues
Date: Sat, 1 Feb 2025 21:55:15 -0000 (UTC)
Organization: A noiseless patient Spider
Lines: 32
Message-ID: <vnm582$9u05$1@dont-email.me>
MIME-Version: 1.0
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: 8bit
Injection-Date: Sat, 01 Feb 2025 22:55:15 +0100 (CET)
Injection-Info: dont-email.me; posting-host="b1fe2ea66eb772c2639db01df9bb4638";
	logging-data="325637"; mail-complaints-to="abuse@eternal-september.org";	posting-account="U2FsdGVkX19jZvGx1q3CpvCyvNJdw4PP"
User-Agent: Pan/0.161 (Chasiv Yar; )
Cancel-Lock: sha1:8t3qQeHd5Uf3foW6IhAsFm2h0IQ=
Bytes: 2441

Many years ago, a software engineer named Fred Brooks predicted that
some systems could get so complex that they would exceed a manageable
threshold of complexity, where every attempt to fix a bug would just
create new ones.

Microsoft passed this point a long time ago. Read this
<https://www.zdnet.com/article/windows-11-24h2s-wild-ride-some-fixes-are-in-but-other-bugs-still-linger/>
and think: how many times have you heard of this sort of thing, just
in the past year? Some choice quotes:

    When Microsoft rolled out another Windows 11 24H2 update for
    January's Patch Tuesday, instead of fixing existing issues, the
    update created more havoc, causing conflicts with audio,
    Bluetooth, webcams, and more. But a preview update released on
    Jan. 28 finally fixed several glitches -- both old and new.

But then qualifies this by saying:

    But before you dive into the 2024 update, know that you may run
    into some problems and conflicts. The new version has been plagued
    by bugs that could prevent you from using Windows reliably and
    effectively.

So fix some problems, add new ones. Conclusion:

    The number of bugs in Windows 11 24H2 also seems greater than in
    past annual Windows updates. The ongoing spread of one bug after
    another and Microsoft's need to stall the update for many people
    both point to a problem with this latest version.

Not the first time Windows has had this sort of trouble! It has become
a regular occurrence the past few years.