One of the things I really dislike about recent Microsoft operating
systems - ever since Windows 8 - is that updates have become
mandatory. Oh sure, you can put them off for a week or four, but in
the end they're going to be applied.* It's a problem because Microsoft
has repeatedly shown that their updates can be very problematic.
Case in point: a recent update to Windows 11, which has caused
numerous problems. Most reported was how it - seeing an installed
printer - detected it as an HP printer and installed an "HP Smart App"
for it... even if the printer was an Epson or Brother or whatever.**
Oops. More concernedly, a number of people have reported slow-downs
following the update (mostly AMD Ryzen owners, or people with 13th
generation+ Intel CPUs).**
And then, there's always the fun of uninstalling the cruft Microsoft
insists on reinstalling on your PC, and re-engaging all the privacy
settings.
I escaped the printer issue (my Brother remains a Brother, as far as
Windows is concerned) but the CPU hit? Yeah, I saw that; I had a 10%
performance drop... at least according to benchmarks. It wasn't
something I actually noticed in actual usage. The fix (see below)
cured the issue, but still... Microsoft ought to be embarrassed.
Microsoft these days is more interested in pushing its services than
actually creating a product people want. Windows 11 remains a
shitshow: buggy, unpolished and generally a unsatisfying experience to
use. And now even its updates - the thing intended to make it better -
are problematic.
Some days it makes me wonder why we ever left DOS...
---------------
* Well, unless you completely disconnect from the Internet... and even
then I'm not completely sure Microsoft hasn't snuck in some component
that will somehow get those updates installed. Brainwashed mice
carrying USB drives, maybe.
**
https://www.yahoo.com/lifestyle/windows-11-installs-hp-smart-134915531.html
*** The latter is apparently fixable: for a step-by-step, visit:
https://www.pcworld.com/article/2161898/if-your-cpu-performance-fell-after-updating-windows-try-this.html