For ignoring backdoor Windows 11 updates to older PC's that do not pass
the CPU test. My 2 laptops were updated to 26H2 and fully patched this weekend.
Simple process if you want to try. Install the current Flyby11 utility
and start it up. Download the full 26H2 .ISO from Microsoft to the
downloads folder. Drag that to the Fly11 Install box and answer a few questions.
Main ones are what is your language pack and do you want to retain
programs, settings and files or do a wipe and install. Depending on your machine specs this takes from 30 minutes or less to an hour or more.
Check for updates after done.
This is my 3rd time to update this way and no issues - yet.
On 11/1/2026 7:11 PM, Tom Elam wrote:
For ignoring backdoor Windows 11 updates to older PC's that do not pass
the CPU test. My 2 laptops were updated to 26H2 and fully patched this
weekend.
Simple process if you want to try. Install the current Flyby11 utility
and start it up. Download the full 26H2 .ISO from Microsoft to the
downloads folder. Drag that to the Fly11 Install box and answer a few
questions.
Main ones are what is your language pack and do you want to retain
programs, settings and files or do a wipe and install. Depending on your
machine specs this takes from 30 minutes or less to an hour or more.
Check for updates after done.
This is my 3rd time to update this way and no issues - yet.
It's OK, but they've already extended Win10 updates again, and I bet
that will be done again next year, because they stand to lose a lot
without reluctant upgraders of hardware, who may not wish to hack Win11.
Joel W. Crump <joelcrump@gmail.com> wrote:
On 11/1/2026 7:11 PM, Tom Elam wrote:
For ignoring backdoor Windows 11 updates to older PC's that do not pass
the CPU test. My 2 laptops were updated to 26H2 and fully patched this
weekend.
Simple process if you want to try. Install the current Flyby11 utility
and start it up. Download the full 26H2 .ISO from Microsoft to the
downloads folder. Drag that to the Fly11 Install box and answer a few
questions.
Main ones are what is your language pack and do you want to retain
programs, settings and files or do a wipe and install. Depending on your >>> machine specs this takes from 30 minutes or less to an hour or more.
Check for updates after done.
This is my 3rd time to update this way and no issues - yet.
It's OK, but they've already extended Win10 updates again, and I bet
that will be done again next year, because they stand to lose a lot
without reluctant upgraders of hardware, who may not wish to hack Win11.
No one is rCLhackingrCY Windows 11. Flyby11/Rufus/whatever are using legitimate, documented settings to work their rCLmagicrCY. Documented by Microsoft, in fact. These settings are created by Microsoft and used by
IT departments in large corporations (IOW, the customers MS actually cares about) to create custom installations by adding/removing whatever the large corporations want to add/remove.
There are MANY settings that can be changed to create custom installations.
However, all that is typically happening in this case is that the checks for TPM 2.0 and 11th gen Intel CPUs are removed. The result is a fully functioning, legal install of Windows 11 that receives updates, etc.
I have personally used Rufus on a few rCLunsupported rCL laptops to install Windows 11. The install runs fine and the rCLunsupportedrCY laptops run Windows 11 just fine.
Microsoft has no reason to block this, because they are desperate to get as many people running Windows 11 as possible.
On 11/2/26 12:49 PM, Nick Charles wrote:
Joel W. Crump <joelcrump@gmail.com> wrote:
On 11/1/2026 7:11 PM, Tom Elam wrote:
For ignoring backdoor Windows 11 updates to older PC's that do not pass >>>> the CPU test. My 2 laptops were updated to 26H2 and fully patched this >>>> weekend.
Simple process if you want to try. Install the current Flyby11 utility >>>> and start it up. Download the full 26H2 .ISO from Microsoft to the
downloads folder. Drag that to the Fly11 Install box and answer a few
questions.
Main ones are what is your language pack and do you want to retain
programs, settings and files or do a wipe and install. Depending on
your
machine specs this takes from 30 minutes or less to an hour or more.
Check for updates after done.
This is my 3rd time to update this way and no issues - yet.
It's OK, but they've already extended Win10 updates again, and I bet
that will be done again next year, because they stand to lose a lot
without reluctant upgraders of hardware, who may not wish to hack Win11.
No one is rCLhackingrCY Windows 11.-a-a Flyby11/Rufus/whatever are using
legitimate, documented settings to work their rCLmagicrCY.-a-a Documented by >> Microsoft, in fact.-a These settings are created by Microsoft-a and used by >> IT departments in large corporations (IOW, the customers MS actually
cares
about) to create custom installations by adding/removing whatever the
large
corporations want to add/remove.
There are MANY settings that can be changed to create custom
installations.
-a However, all that is typically happening in this case is that the
checks
for TPM 2.0 and 11th gen Intel CPUs are removed.-a-a The result is a fully >> functioning, legal install of Windows 11 that receives updates, etc.
I have personally used Rufus on a few rCLunsupported rCL-a laptops to install
Windows 11.-a-a The install runs fine and the rCLunsupportedrCY laptops run >> Windows 11 just fine.
Microsoft has no reason to block this, because they are desperate to
get as
many people running Windows 11 as possible.
Thanks for that clarification. By backdoor I meant that the update is
not offered by Windows update on these laptops. If you try to use Microsoft's update process you get "This computer does not meet the
minimum requirements for Windows 11." Or some such. Anyway I have
manually installed 24H2, 25H2 and 26H2. Both are getting all other W11 updates. Both are running just fine.
So why does Microsoft just allow a W11 OS update on any computer with
TPM 2.0 and Secure Boot? If it runs slow, and one of mine does due to
not enough RAM? That is my problem, not there's.
Joel W. Crump <joelcrump@gmail.com> wrote:
On 11/1/2026 7:11 PM, Tom Elam wrote:
For ignoring backdoor Windows 11 updates to older PC's that do not pass
the CPU test. My 2 laptops were updated to 26H2 and fully patched this
weekend.
Simple process if you want to try. Install the current Flyby11 utility
and start it up. Download the full 26H2 .ISO from Microsoft to the
downloads folder. Drag that to the Fly11 Install box and answer a few
questions.
Main ones are what is your language pack and do you want to retain
programs, settings and files or do a wipe and install. Depending on your >>> machine specs this takes from 30 minutes or less to an hour or more.
Check for updates after done.
This is my 3rd time to update this way and no issues - yet.
It's OK, but they've already extended Win10 updates again, and I bet
that will be done again next year, because they stand to lose a lot
without reluctant upgraders of hardware, who may not wish to hack Win11.
No one is rCLhackingrCY Windows 11. Flyby11/Rufus/whatever are using legitimate, documented settings to work their rCLmagicrCY. Documented by Microsoft, in fact. These settings are created by Microsoft and used by
IT departments in large corporations (IOW, the customers MS actually cares about) to create custom installations by adding/removing whatever the large corporations want to add/remove.
There are MANY settings that can be changed to create custom installations.
However, all that is typically happening in this case is that the checks for TPM 2.0 and 11th gen Intel CPUs are removed. The result is a fully functioning, legal install of Windows 11 that receives updates, etc.
I have personally used Rufus on a few rCLunsupported rCL laptops to install Windows 11. The install runs fine and the rCLunsupportedrCY laptops run Windows 11 just fine.
Microsoft has no reason to block this, because they are desperate to get as many people running Windows 11 as possible.
On 2026-11-02 2:29 p.m., Tom Elam wrote:
On 11/2/26 12:49 PM, Nick Charles wrote:
Joel W. Crump <joelcrump@gmail.com> wrote:
On 11/1/2026 7:11 PM, Tom Elam wrote:No one is rCLhackingrCY Windows 11. Flyby11/Rufus/whatever are using
For ignoring backdoor Windows 11 updates to older PC's that do not pass >>>>> the CPU test. My 2 laptops were updated to 26H2 and fully patched this >>>>> weekend.
Simple process if you want to try. Install the current Flyby11 utility >>>>> and start it up. Download the full 26H2 .ISO from Microsoft to the
downloads folder. Drag that to the Fly11 Install box and answer a few >>>>> questions.
Main ones are what is your language pack and do you want to retain
programs, settings and files or do a wipe and install. Depending on
your
machine specs this takes from 30 minutes or less to an hour or more. >>>>> Check for updates after done.
This is my 3rd time to update this way and no issues - yet.
It's OK, but they've already extended Win10 updates again, and I bet
that will be done again next year, because they stand to lose a lot
without reluctant upgraders of hardware, who may not wish to hack Win11. >>>
legitimate, documented settings to work their rCLmagicrCY. Documented by >>> Microsoft, in fact. These settings are created by Microsoft and used by >>> IT departments in large corporations (IOW, the customers MS actually
cares
about) to create custom installations by adding/removing whatever the
large
corporations want to add/remove.
There are MANY settings that can be changed to create custom
installations.
However, all that is typically happening in this case is that the
checks
for TPM 2.0 and 11th gen Intel CPUs are removed. The result is a fully >>> functioning, legal install of Windows 11 that receives updates, etc.
I have personally used Rufus on a few rCLunsupported rCL laptops to install
Windows 11. The install runs fine and the rCLunsupportedrCY laptops run >>> Windows 11 just fine.
Microsoft has no reason to block this, because they are desperate to
get as
many people running Windows 11 as possible.
Thanks for that clarification. By backdoor I meant that the update is
not offered by Windows update on these laptops. If you try to use
Microsoft's update process you get "This computer does not meet the
minimum requirements for Windows 11." Or some such. Anyway I have
manually installed 24H2, 25H2 and 26H2. Both are getting all other W11
updates. Both are running just fine.
So why does Microsoft just allow a W11 OS update on any computer with
TPM 2.0 and Secure Boot? If it runs slow, and one of mine does due to
not enough RAM? That is my problem, not there's.
Why does Apple not offer operating system updates for certain models
after a set number of years? It's the same story: they don't want to
support machines that don't hold a certain technology. It's their right,
but if there are ways around it, you're free to use them. If I hated a company's policies as much as I do theirs, I would either switch brands
(as I did) or use Linux rather than keep fighting their software.
Microsoft ... are desperate to get as many people running Windows 11
as possible.
Nick Charles wroteNever seen that, let alone every other month
Microsoft ... are desperate to get as many people running Windows 11If that were true, why do they let the quality of Windows updates keep> deteriorating so badly? Seems every other month some rCLfixrCY for some
as possible.
problem ends up creating another, or not even fixing the original
problem properly in the first place.
If you look at their last financials, theyrCOve regrouped things so the--- Synchronet 3.22a-Linux NewsLink 1.2
whole Windows business is now lumped together in a division that
includes Xbox, search and advertising -- in other words, the also-rans> -- that in total account for only 17% of the companyrCOs total revenues.
The outlook for Windows revenue, according to the CFO, is to keep
falling for the next year.
WhererCOs the rest of the money coming from? Cloud, mainly. The Azure business alone is over twice the size of the above Windows-including division. And MicrosoftrCOs cloud business is primarily built on Linux.
The conclusion is inescapable: Linux is now more important to
Microsoft than Windows.
Lawrence DrCOOliveiro <ldo@nz.invalid> wrote
Nick Charles wrote
Microsoft ... are desperate to get as many people running Windows 11
as possible.
If that were true, why do they let the quality of Windows updates keep
deteriorating so badly? Seems every other month some rCLfixrCY for some
problem ends up creating another, or not even fixing the original
problem properly in the first place.
Never seen that, let alone every other month
If you look at their last financials, theyrCOve regrouped things so the
whole Windows business is now lumped together in a division that
includes Xbox, search and advertising -- in other words, the also-rans
-- that in total account for only 17% of the companyrCOs total revenues.
The outlook for Windows revenue, according to the CFO, is to keep
falling for the next year.
WhererCOs the rest of the money coming from? Cloud, mainly. The Azure
business alone is over twice the size of the above Windows-including
division. And MicrosoftrCOs cloud business is primarily built on Linux.
The conclusion is inescapable: Linux is now more important to
Microsoft than Windows.
On Mon, 02 Nov 2026 17:49:12 +0000, Nick Charles wrote:
Microsoft ... are desperate to get as many people running Windows 11
as possible.
If that were true, why do they let the quality of Windows updates keep deteriorating so badly? Seems every other month some rCLfixrCY for some problem ends up creating another, or not even fixing the original
problem properly in the first place.
If you look at their last financials, theyrCOve regrouped things so the
whole Windows business is now lumped together in a division that
includes Xbox, search and advertising -- in other words, the also-rans
-- that in total account for only 17% of the companyrCOs total revenues.
The outlook for Windows revenue, according to the CFO, is to keep
falling for the next year.
WhererCOs the rest of the money coming from? Cloud, mainly. The Azure business alone is over twice the size of the above Windows-including division. And MicrosoftrCOs cloud business is primarily built on Linux.
The conclusion is inescapable: Linux is now more important to
Microsoft than Windows.
On Nov 2, 2026 at 3:16:37rC>PM EST, "CrudeSausage" <crude@sausa.ge> wrote:
On 2026-11-02 2:29 p.m., Tom Elam wrote:
On 11/2/26 12:49 PM, Nick Charles wrote:
Joel W. Crump <joelcrump@gmail.com> wrote:
On 11/1/2026 7:11 PM, Tom Elam wrote:No one is rCLhackingrCY Windows 11. Flyby11/Rufus/whatever are using >>>> legitimate, documented settings to work their rCLmagicrCY. Documented by >>>> Microsoft, in fact. These settings are created by Microsoft and used by >>>> IT departments in large corporations (IOW, the customers MS actually
For ignoring backdoor Windows 11 updates to older PC's that do not pass >>>>>> the CPU test. My 2 laptops were updated to 26H2 and fully patched this >>>>>> weekend.
Simple process if you want to try. Install the current Flyby11 utility >>>>>> and start it up. Download the full 26H2 .ISO from Microsoft to the >>>>>> downloads folder. Drag that to the Fly11 Install box and answer a few >>>>>> questions.
Main ones are what is your language pack and do you want to retain >>>>>> programs, settings and files or do a wipe and install. Depending on >>>>>> your
machine specs this takes from 30 minutes or less to an hour or more. >>>>>> Check for updates after done.
This is my 3rd time to update this way and no issues - yet.
It's OK, but they've already extended Win10 updates again, and I bet >>>>> that will be done again next year, because they stand to lose a lot
without reluctant upgraders of hardware, who may not wish to hack Win11. >>>>
cares
about) to create custom installations by adding/removing whatever the
large
corporations want to add/remove.
There are MANY settings that can be changed to create custom
installations.
However, all that is typically happening in this case is that the
checks
for TPM 2.0 and 11th gen Intel CPUs are removed. The result is a fully >>>> functioning, legal install of Windows 11 that receives updates, etc.
I have personally used Rufus on a few rCLunsupported rCL laptops to install
Windows 11. The install runs fine and the rCLunsupportedrCY laptops run >>>> Windows 11 just fine.
Microsoft has no reason to block this, because they are desperate to
get as
many people running Windows 11 as possible.
Thanks for that clarification. By backdoor I meant that the update is
not offered by Windows update on these laptops. If you try to use
Microsoft's update process you get "This computer does not meet the
minimum requirements for Windows 11." Or some such. Anyway I have
manually installed 24H2, 25H2 and 26H2. Both are getting all other W11
updates. Both are running just fine.
So why does Microsoft just allow a W11 OS update on any computer with
TPM 2.0 and Secure Boot? If it runs slow, and one of mine does due to
not enough RAM? That is my problem, not there's.
Why does Apple not offer operating system updates for certain models
after a set number of years? It's the same story: they don't want to
support machines that don't hold a certain technology. It's their right,
but if there are ways around it, you're free to use them. If I hated a
company's policies as much as I do theirs, I would either switch brands
(as I did) or use Linux rather than keep fighting their software.
Exactly. MS does not want to support that. But it is easy to do update installs for each new version, using Rufus or whatever.
On 11/3/2026 7:30 AM, Lawrence DrCOOliveiro wrote:
On Mon, 02 Nov 2026 17:49:12 +0000, Nick Charles wrote:
Microsoft ... are desperate to get as many people running Windows 11
as possible.
If that were true, why do they let the quality of Windows updates keep
deteriorating so badly? Seems every other month some rCLfixrCY for some
problem ends up creating another, or not even fixing the original
problem properly in the first place.
If you look at their last financials, theyrCOve regrouped things so the
whole Windows business is now lumped together in a division that
includes Xbox, search and advertising -- in other words, the also-rans
-- that in total account for only 17% of the companyrCOs total revenues.
The outlook for Windows revenue, according to the CFO, is to keep
falling for the next year.
WhererCOs the rest of the money coming from? Cloud, mainly. The Azure
business alone is over twice the size of the above Windows-including
division. And MicrosoftrCOs cloud business is primarily built on Linux.
The conclusion is inescapable: Linux is now more important to
Microsoft than Windows.
Isn't that a good reason to ditch Linux?
If that were true, why do they let the quality of Windows updates keep deteriorating so badly? Seems every other month some |fixi for some
problem ends up creating another, or not even fixing the original
problem properly in the first place.
On Mon, 2 Nov 2026 23:30:22 -0000 (UTC), Lawrence DrCOOliveiro wrote:
If that were true, why do they let the quality of Windows updates keep
deteriorating so badly? Seems every other month some rCLfixrCY for some
problem ends up creating another, or not even fixing the original
problem properly in the first place.
Bugs are Microsoft's life. They can fix all of the bugs, but they won't. Because without bugs, there won't be updates except for new features which they're reluctantly giving. Without updates, the OS won't look "fresh", "maintained", and "supported". They intentionally add more bugs to keep that status.
On 11/03/26 7:53 PM, JJ wrote:
On Mon, 2 Nov 2026 23:30:22 -0000 (UTC), Lawrence DrCOOliveiro wrote:
If that were true, why do they let the quality of Windows updates keep
deteriorating so badly? Seems every other month some rCLfixrCY for some
problem ends up creating another, or not even fixing the original
problem properly in the first place.
Bugs are Microsoft's life. They can fix all of the bugs, but they won't.
Because without bugs, there won't be updates except for new features which >> they're reluctantly giving. Without updates, the OS won't look "fresh",
"maintained", and "supported". They intentionally add more bugs to keep that >> status.
That's not an accurate assessment.
Not a single operating system development intentionally adds more bugs(Windows, MacOS, Android, iOs, Linux, etc.).
Nor does any operating system exist that doesn't need patches to existing or new code for functionality, features or vulnerabilities.
And a lot of things are handled in the [Windows] OS in two steps.
That can include an Emergency Patch to stop an instantaneous
problem, plus a "followup patch" that fixes the rest of it properly.
You should not assume when they fix 1400 things, that each one of
those was a one-and-done. On purpose, there could be multiple steps
involved.
Software always has "hot spots". There are modules in Windows, that
when you open them, breaking something is almost guaranteed (File
Explorer). The Kernel is a hot spot, in terms of exploits or
performance issues. Practically every month that file needs a patch,
just the same as Linux needs patching for its kernel stream.
One other thing on Windows, was a GDI module (something associated
with graphics). The current graphics stack has more component parts,
than previous stacks.
By supporting only an x64 OS, now the machine has enough space that
Windows Update is unlikely to run out of RAM.
On Wed, 4 Nov 2026 00:32:29 -0500, Paul wrote:
And a lot of things are handled in the [Windows] OS in two steps.
That can include an Emergency Patch to stop an instantaneous
problem, plus a "followup patch" that fixes the rest of it properly.
You should not assume when they fix 1400 things, that each one of
those was a one-and-done. On purpose, there could be multiple steps
involved.
That doesnrCOt really jibe with the reality that quite a few of those
initial patches actually make things worse in some way. And this seems
to be happening increasingly often.
Software always has "hot spots". There are modules in Windows, that
when you open them, breaking something is almost guaranteed (File
Explorer). The Kernel is a hot spot, in terms of exploits or
performance issues. Practically every month that file needs a patch,
just the same as Linux needs patching for its kernel stream.
The difference is, Linux is cleanly modularized, so you can fix
problems in one area with minimal chance of causing unexpected
problems in some seemingly unrelated place.
By comparison, Windows is a crawling can of worms.
One other thing on Windows, was a GDI module (something associated
with graphics). The current graphics stack has more component parts,
than previous stacks.
The GUI shouldnrCOt be in the kernel. Even the graphics engine shouldnrCOt
be in the kernel. All Linux has graphics-related in there is the
lowest-level drivers and the rCLDirect Rendering ManagerrCY.
All the rest is in userland. This is why it is easy to switch between
an X11 server and a Wayland server -- you donrCOt need different kernels
to do that.
By supporting only an x64 OS, now the machine has enough space that
Windows Update is unlikely to run out of RAM.
Where was there another OS in the history of the world that could run
out of RAM just doing an OS update??
If you install 150 patches on a 32 bit machine, there is some RAM
usage by WU, but each patch, as it installs, there is no
particularly aggressive RAM cleanup between patches, and then, even
with 3.25GB of memory available on the machine, it cannot finish all
150 of them.
On 11/03/26 7:53 PM, JJ wrote:
On Mon, 2 Nov 2026 23:30:22 -0000 (UTC), Lawrence DrCOOliveiro wrote:
If that were true, why do they let the quality of Windows updates keep
deteriorating so badly? Seems every other month some rCLfixrCY for some
problem ends up creating another, or not even fixing the original
problem properly in the first place.
Bugs are Microsoft's life. They can fix all of the bugs, but they won't.
Because without bugs, there won't be updates except for new features which >> they're reluctantly giving. Without updates, the OS won't look "fresh",
"maintained", and "supported". They intentionally add more bugs to keep that >> status.
That's not an accurate assessment.
Not a single operating system development intentionally adds more bugs(Windows, MacOS, Android, iOs, Linux, etc.).
Nor does any operating system exist that doesn't need patches to
existing or new code for functionality, features or vulnerabilities.
w-i|#-o-#-n|# wrote this screed in ALL-CAPS (fixed):
On 11/03/26 7:53 PM, JJ wrote:
On Mon, 2 Nov 2026 23:30:22 -0000 (UTC), Lawrence DrCOOliveiro wrote:
If that were true, why do they let the quality of Windows updates keep >>>> deteriorating so badly? Seems every other month some rCLfixrCY for some >>>> problem ends up creating another, or not even fixing the original
problem properly in the first place.
Bugs are Microsoft's life. They can fix all of the bugs, but they won't. >>> Because without bugs, there won't be updates except for new features which >>> they're reluctantly giving. Without updates, the OS won't look "fresh",
"maintained", and "supported". They intentionally add more bugs to keep that
status.
That's not an accurate assessment.
Not a single operating system development intentionally adds more
bugs(Windows, MacOS, Android, iOs, Linux, etc.).
Nor does any operating system exist that doesn't need patches to
existing or new code for functionality, features or vulnerabilities.
"The reason we come up with new versions is not to fix bugs.
It's absolutely not. It's the stupidest reason to buy a new
version I ever heard. When we do a new version we put in lots
of new things that people are asking for. And so, in no sense,
is stability a reason to move to a new version. It's never a
reason."
-- Bill Gates circa 1995
w-i|#-o-#-n|# wrote this screed in ALL-CAPS (fixed):
On 11/03/26 7:53 PM, JJ wrote:
On Mon, 2 Nov 2026 23:30:22 -0000 (UTC), Lawrence DrCOOliveiro wrote:
If that were true, why do they let the quality of Windows updates keep >>>> deteriorating so badly? Seems every other month some rCLfixrCY for some >>>> problem ends up creating another, or not even fixing the original
problem properly in the first place.
Bugs are Microsoft's life. They can fix all of the bugs, but they won't. >>> Because without bugs, there won't be updates except for new features which >>> they're reluctantly giving. Without updates, the OS won't look "fresh",
"maintained", and "supported". They intentionally add more bugs to keep that
status.
That's not an accurate assessment.
Not a single operating system development intentionally adds more
bugs(Windows, MacOS, Android, iOs, Linux, etc.).
Nor does any operating system exist that doesn't need patches to
existing or new code for functionality, features or vulnerabilities.
"The reason we come up with new versions is not to fix bugs.
It's absolutely not. It's the stupidest reason to buy a new
version I ever heard. When we do a new version we put in lots
of new things that people are asking for. And so, in no sense,
is stability a reason to move to a new version. It's never a
reason."
-- Bill Gates circa 1995
On Wed, 11/4/2026 6:50 AM, Chris Ahlstrom wrote:
w-i|#-o-#-n|# wrote this screed in ALL-CAPS (fixed):
On 11/03/26 7:53 PM, JJ wrote:
On Mon, 2 Nov 2026 23:30:22 -0000 (UTC), Lawrence DrCOOliveiro wrote: >>>>>
If that were true, why do they let the quality of Windows updates keep >>>>> deteriorating so badly? Seems every other month some rCLfixrCY for some >>>>> problem ends up creating another, or not even fixing the original
problem properly in the first place.
Bugs are Microsoft's life. They can fix all of the bugs, but they won't. >>>> Because without bugs, there won't be updates except for new features which >>>> they're reluctantly giving. Without updates, the OS won't look "fresh", >>>> "maintained", and "supported". They intentionally add more bugs to keep that
status.
That's not an accurate assessment.
Not a single operating system development intentionally adds more
bugs(Windows, MacOS, Android, iOs, Linux, etc.).
Nor does any operating system exist that doesn't need patches to
existing or new code for functionality, features or vulnerabilities.
"The reason we come up with new versions is not to fix bugs.
It's absolutely not. It's the stupidest reason to buy a new
version I ever heard. When we do a new version we put in lots
of new things that people are asking for. And so, in no sense,
is stability a reason to move to a new version. It's never a
reason."
-- Bill Gates circa 1995
This must be from the "Book of 640K clever things Bill said".
It wasn't that many years after 1995, that cooperative multitasking
got changed to preemptive multitasking, and we had real OSes then.
They didn't have to crash :-) The OSes went downhill after that.
It seems all we could do after that, was add deck chairs.
On Mon, 2 Nov 2026 23:30:22 -0000 (UTC), Lawrence DrCOOliveiro wrote:
If that were true, why do they let the quality of Windows updates keep
deteriorating so badly? Seems every other month some rCLfixrCY for some
problem ends up creating another, or not even fixing the original
problem properly in the first place.
Bugs are Microsoft's life. They can fix all of the bugs, but they won't. Because without bugs, there won't be updates except for new features which they're reluctantly giving. Without updates, the OS won't look "fresh", "maintained", and "supported". They intentionally add more bugs to keep that status.
It wasn't that many years after 1995, that cooperative multitasking
got changed to preemptive multitasking, and we had real OSes then.
They didn't have to crash :-)
The OSes went downhill after that.
On Wed, 4 Nov 2026 02:52:21 -0500, Paul wrote:
If you install 150 patches on a 32 bit machine, there is some RAM
usage by WU, but each patch, as it installs, there is no
particularly aggressive RAM cleanup between patches, and then, even
with 3.25GB of memory available on the machine, it cannot finish all
150 of them.
That is a really stupid design.
w-i|#-o-#-n|# wrote this screed in ALL-CAPS (fixed):
On 11/03/26 7:53 PM, JJ wrote:
On Mon, 2 Nov 2026 23:30:22 -0000 (UTC), Lawrence DrCOOliveiro wrote:
If that were true, why do they let the quality of Windows updates keep >>>> deteriorating so badly? Seems every other month some rCLfixrCY for some >>>> problem ends up creating another, or not even fixing the original
problem properly in the first place.
Bugs are Microsoft's life. They can fix all of the bugs, but they won't. >>> Because without bugs, there won't be updates except for new features which >>> they're reluctantly giving. Without updates, the OS won't look "fresh",
"maintained", and "supported". They intentionally add more bugs to keep that
status.
That's not an accurate assessment.
Not a single operating system development intentionally adds more
bugs(Windows, MacOS, Android, iOs, Linux, etc.).
Nor does any operating system exist that doesn't need patches to
existing or new code for functionality, features or vulnerabilities.
"The reason we come up with new versions is not to fix bugs.
It's absolutely not. It's the stupidest reason to buy a new
version I ever heard. When we do a new version we put in lots
of new things that people are asking for. And so, in no sense,
is stability a reason to move to a new version. It's never a
reason."
-- Bill Gates circa 1995
On 2026-11-03 9:53 p.m., JJ wrote:
On Mon, 2 Nov 2026 23:30:22 -0000 (UTC), Lawrence DrCOOliveiro wrote:
If that were true, why do they let the quality of Windows updates keep
deteriorating so badly? Seems every other month some rCLfixrCY for some
problem ends up creating another, or not even fixing the original
problem properly in the first place.
Bugs are Microsoft's life. They can fix all of the bugs, but they won't.
Because without bugs, there won't be updates except for new features which >> they're reluctantly giving. Without updates, the OS won't look "fresh",
"maintained", and "supported". They intentionally add more bugs to keep that >> status.
The worst part is that the operating system itself is not the only issue. Hardware manufacturers also produce buggy software that you are more or less forced to use with their machines. ASUS's Armoury Crate is an excellent example. In other cases, the problems are at the BIOS level, and these manufacturers are routinely unwilling to bother updating it. MSI is particularly bad in this area whereas ASUS is pretty good at updating theirs.
On Wed, 11/4/2026 6:50 AM, Chris Ahlstrom wrote:That's bullshit with networking and the internet alone and the UI
w-i|#-o-#-n|# wrote this screed in ALL-CAPS (fixed):
On 11/03/26 7:53 PM, JJ wrote:"The reason we come up with new versions is not to fix bugs.
On Mon, 2 Nov 2026 23:30:22 -0000 (UTC), Lawrence DrCOOliveiro wrote: >>>>>
If that were true, why do they let the quality of Windows updates >>>>> keep
deteriorating so badly? Seems every other month some rCLfixrCY for some >>>>> problem ends up creating another, or not even fixing the original
problem properly in the first place.
Bugs are Microsoft's life. They can fix all of the bugs, but they >>>> won't.
Because without bugs, there won't be updates except for new features >>>> which
they're reluctantly giving. Without updates, the OS won't look >>>> "fresh",
"maintained", and "supported". They intentionally add more bugs to >>>> keep that
status.
That's not an accurate assessment.
Not a single operating system development intentionally adds more
bugs(Windows, MacOS, Android, iOs, Linux, etc.).
Nor does any operating system exist that doesn't need patches to
existing or new code for functionality, features or vulnerabilities.>>
It's absolutely not. It's the stupidest reason to buy a new
version I ever heard. When we do a new version we put in lots
of new things that people are asking for. And so, in no sense,
is stability a reason to move to a new version. It's never a
reason."
-- Bill Gates circa 1995
This must be from the "Book of 640K clever things Bill said".
It wasn't that many years after 1995, that cooperative multitasking
got changed to preemptive multitasking, and we had real OSes then.
They didn't have to crash :-) The OSes went downhill after that.
It seems all we could do after that, was add deck chairs.More bullshit
YepOn Wed, 11/4/2026 6:50 AM, Chris Ahlstrom wrote:
w-i|#-o-#-n|# wrote this screed in ALL-CAPS (fixed):
On 11/03/26 7:53 PM, JJ wrote:
On Mon, 2 Nov 2026 23:30:22 -0000 (UTC), Lawrence DrCOOliveiro wrote: >>>>>>
If that were true, why do they let the quality of Windows updates >>>>>> keep
deteriorating so badly? Seems every other month some rCLfixrCY for some >>>>>> problem ends up creating another, or not even fixing the original>>>>>> problem properly in the first place.
Bugs are Microsoft's life. They can fix all of the bugs, but they >>>>> won't.
Because without bugs, there won't be updates except for new features >>>>> which
they're reluctantly giving. Without updates, the OS won't look >>>>> "fresh",
"maintained", and "supported". They intentionally add more bugs to >>>>> keep that
status.
That's not an accurate assessment.
Not a single operating system development intentionally adds more
bugs(Windows, MacOS, Android, iOs, Linux, etc.).
Nor does any operating system exist that doesn't need patches to
existing or new code for functionality, features or vulnerabilities.
"The reason we come up with new versions is not to fix bugs.
It's absolutely not. It's the stupidest reason to buy a new
version I ever heard. When we do a new version we put in lots
of new things that people are asking for. And so, in no sense,
is stability a reason to move to a new version. It's never a
reason."
-- Bill Gates circa 1995
This must be from the "Book of 640K clever things Bill said".
It wasn't that many years after 1995, that cooperative multitasking
got changed to preemptive multitasking, and we had real OSes then.
They didn't have to crash :-) The OSes went downhill after that.
This is more to life than Microsoft OSes. MacOS and Linux do not crash > on
app updates. In fact, both MacOS and Linux have gone WAY uphill since
1995.
Bullshit with networking aloneIt seems all we could do after that, was add deck chairs.ThatrCOs all Microsoft could do. Because thatrCOs all they CAN do with Windows.
Paul <nospam@needed.invalid> wrote:[...]
On Wed, 11/4/2026 6:50 AM, Chris Ahlstrom wrote:
"The reason we come up with new versions is not to fix bugs.
It's absolutely not. It's the stupidest reason to buy a new
version I ever heard. When we do a new version we put in lots
of new things that people are asking for. And so, in no sense,
is stability a reason to move to a new version. It's never a
reason."
-- Bill Gates circa 1995
This must be from the "Book of 640K clever things Bill said".
It wasn't that many years after 1995, that cooperative multitasking
got changed to preemptive multitasking, and we had real OSes then.
They didn't have to crash :-) The OSes went downhill after that.
This is more to life than Microsoft OSes. MacOS and Linux do not crash on app updates. In fact, both MacOS and Linux have gone WAY uphill since
1995.
That said, I am sorry to rain on your parade, but ever since the
NT-family of Windows systems, i.e. Windows NT to 11, I have never had
Windows crash "on app updates" or any other 'app' related crash for that matter.
On 11/5/2026 11:38 AM, Frank Slootweg wrote:
That said, I am sorry to rain on your parade, but ever since the
NT-family of Windows systems, i.e. Windows NT to 11, I have never
had Windows crash "on app updates" or any other 'app' related
crash for that matter.
Having seen Windows 2000 on a PC, when it was still a new release,
I can definitely say there were certain things Microsoft was
"first" on. But A Linux system of the time was impressive,
already. And Macs were getting "OS X" or macOS in the same time
frame.
Nick Charles <none@none.none> wrote:
Paul <nospam@needed.invalid> wrote:[...]
On Wed, 11/4/2026 6:50 AM, Chris Ahlstrom wrote:
"The reason we come up with new versions is not to fix bugs.
It's absolutely not. It's the stupidest reason to buy a new
version I ever heard. When we do a new version we put in lots
of new things that people are asking for. And so, in no sense,
is stability a reason to move to a new version. It's never a
reason."
-- Bill Gates circa 1995
This must be from the "Book of 640K clever things Bill said".
It wasn't that many years after 1995, that cooperative multitasking
got changed to preemptive multitasking, and we had real OSes then.
They didn't have to crash :-) The OSes went downhill after that.
This is more to life than Microsoft OSes. MacOS and Linux do not crash on >> app updates. In fact, both MacOS and Linux have gone WAY uphill since
1995.
As mentioned by Lawrence, the 1995 date is rather silly, because there
were reliable preemptive multitasking/multiprogramming systems long,
long before that. My experience with them goes back to the early 70s for pre-UNIX systems and the early 80s for UNIX systems.
That said, I am sorry to rain on your parade, but ever since the
NT-family of Windows systems, i.e. Windows NT to 11, I have never had
Windows crash "on app updates" or any other 'app' related crash for that matter.
On Thu, 05 Nov 2026 08:55:14 +1100, Nick Charles <none@none.none> wrote:
Paul <nospam@needed.invalid> wrote:
On Wed, 11/4/2026 6:50 AM, Chris Ahlstrom wrote:
w-i|#-o-#-n|# wrote this screed in ALL-CAPS (fixed):
On 11/03/26 7:53 PM, JJ wrote:
On Mon, 2 Nov 2026 23:30:22 -0000 (UTC), Lawrence DrCOOliveiro wrote: >>>>>>>
If that were true, why do they let the quality of Windows updates >>>>>>> keep
deteriorating so badly? Seems every other month some rCLfixrCY for some >>>>>>> problem ends up creating another, or not even fixing the original >>>>>>> problem properly in the first place.
Bugs are Microsoft's life. They can fix all of the bugs, but they >>>>>> won't.
Because without bugs, there won't be updates except for new features >>>>>> which
they're reluctantly giving. Without updates, the OS won't look
"fresh",
"maintained", and "supported". They intentionally add more bugs to >>>>>> keep that
status.
That's not an accurate assessment.
Not a single operating system development intentionally adds more
bugs(Windows, MacOS, Android, iOs, Linux, etc.).
Nor does any operating system exist that doesn't need patches to
existing or new code for functionality, features or vulnerabilities.
"The reason we come up with new versions is not to fix bugs.
It's absolutely not. It's the stupidest reason to buy a new
version I ever heard. When we do a new version we put in lots
of new things that people are asking for. And so, in no sense,
is stability a reason to move to a new version. It's never a
reason."
-- Bill Gates circa 1995
This must be from the "Book of 640K clever things Bill said".
It wasn't that many years after 1995, that cooperative multitasking
got changed to preemptive multitasking, and we had real OSes then.
They didn't have to crash :-) The OSes went downhill after that.
This is more to life than Microsoft OSes. MacOS and Linux do not crash >> on
app updates. In fact, both MacOS and Linux have gone WAY uphill since
1995.
Yep
It seems all we could do after that, was add deck chairs.
ThatrCOs all Microsoft could do. Because thatrCOs all they CAN do with
Windows.
Bullshit with networking alone
Frank Slootweg <this@ddress.is.invalid> wrote:
That said, I am sorry to rain on your parade, but ever since the
NT-family of Windows systems, i.e. Windows NT to 11, I have never had
Windows crash "on app updates" or any other 'app' related crash for that
matter.
Then you need to get out more. In the last year or so there were screens
in airports around the world with crashed Windows Blue Screens due to a broken non-OS update.
Just because you have never personally seen Windows crash and burn does not mean it never happens. Windows is far too easy to crash.
What MS did with networking was nothing even remotely like deck chairsOn Thu, 05 Nov 2026 08:55:14 +1100, Nick Charles <none@none.none> wrote:
Paul <nospam@needed.invalid> wrote:
On Wed, 11/4/2026 6:50 AM, Chris Ahlstrom wrote:
w-i|#-o-#-n|# wrote this screed in ALL-CAPS (fixed):
On 11/03/26 7:53 PM, JJ wrote:"The reason we come up with new versions is not to fix bugs.
On Mon, 2 Nov 2026 23:30:22 -0000 (UTC), Lawrence DrCOOliveiro wrote: >>>>>>>>
If that were true, why do they let the quality of Windows updates >>>>>>>> keep
deteriorating so badly? Seems every other month some rCLfixrCY for >>>>>>>> some
problem ends up creating another, or not even fixing the original >>>>>>>> problem properly in the first place.
Bugs are Microsoft's life. They can fix all of the bugs, but they >>>>>>> won't.
Because without bugs, there won't be updates except for new >>>>>>> features
which
they're reluctantly giving. Without updates, the OS won't look
"fresh",
"maintained", and "supported". They intentionally add more bugs to >>>>>>> keep that
status.
That's not an accurate assessment.
Not a single operating system development intentionally adds more>>>>>> bugs(Windows, MacOS, Android, iOs, Linux, etc.).
Nor does any operating system exist that doesn't need patches to
existing or new code for functionality, features or vulnerabilities. >>>>>
It's absolutely not. It's the stupidest reason to buy a new
version I ever heard. When we do a new version we put in lots
of new things that people are asking for. And so, in no sense,
is stability a reason to move to a new version. It's never a
reason."
-- Bill Gates circa 1995
This must be from the "Book of 640K clever things Bill said".
It wasn't that many years after 1995, that cooperative multitasking>>>> got changed to preemptive multitasking, and we had real OSes then.
They didn't have to crash :-) The OSes went downhill after that.
This is more to life than Microsoft OSes. MacOS and Linux do not >>> crash
on
app updates. In fact, both MacOS and Linux have gone WAY uphill since
1995.
Yep
It seems all we could do after that, was add deck chairs.
ThatrCOs all Microsoft could do. Because thatrCOs all they CAN do with
Windows.
Bullshit with networking alone
ThatrCOs twice you have said rCLbullshit with networkingrCY. What does that mean?
But those [big machines] were computers that were not available to
consumers.
Frank Slootweg <this@ddress.is.invalid> wrote:
That said, I am sorry to rain on your parade, but ever since the
NT-family of Windows systems, i.e. Windows NT to 11, I have never had
Windows crash "on app updates" or any other 'app' related crash for that
matter.
Then you need to get out more. In the last year or so there were screens
in airports around the world with crashed Windows Blue Screens due to a broken non-OS update.
Just because you have never personally seen Windows crash and burn does not mean it never happens. Windows is far too easy to crash.
On 11/05/26 1:20 PM, Nick Charles wrote:
Frank Slootweg <this@ddress.is.invalid> wrote:
That said, I am sorry to rain on your parade, but ever since the
NT-family of Windows systems, i.e. Windows NT to 11, I have never had
Windows crash "on app updates" or any other 'app' related crash for that >> matter.
Then you need to get out more. In the last year or so there were screens in airports around the world with crashed Windows Blue Screens due to a broken non-OS update.
Just because you have never personally seen Windows crash and burn does not mean it never happens. Windows is far too easy to crash.
Yes, the global airport screens and system failures were caused by a software app update.
That update was provided, not by Microsoft, but Crowdstrike.--- Synchronet 3.22a-Linux NewsLink 1.2
Microsoft updates do not include updates from Crowdstrike.
- Crowdstrike updates are managed and delivered independently from
Windows Updates - pulling their own signature/channel def updates automatically via their 'own' cloud infrastructure.
- updates are pushed down by Crowdstrike, not Microsoft.
Two months prior to the Crowdstrike update impacting Windows,
Crowdstrike pushed down an app update for Debian Linux causing server crashes and looped booting.
- i.e. your earlier point that app updates don't crash on Linux is incorrect. In this from the exact same source => Crowdstrike
There was one particular point you made that could be somewhat true.
- Your comment that the airport screen crashing in the last year or so could be accurate if liberty was given to the 'or so' timeframe.
- nothing of the above happened in this year or last year(2025) thus
'or so' would be 2.5 years ago for Windows and 2.75 years ago for Linux.
Frank Slootweg <this@ddress.is.invalid> wrote:
Nick Charles <none@none.none> wrote:
Paul <nospam@needed.invalid> wrote:[...]
On Wed, 11/4/2026 6:50 AM, Chris Ahlstrom wrote:
"The reason we come up with new versions is not to fix bugs.
It's absolutely not. It's the stupidest reason to buy a new
version I ever heard. When we do a new version we put in lots
of new things that people are asking for. And so, in no sense,
is stability a reason to move to a new version. It's never a
reason."
-- Bill Gates circa 1995
This must be from the "Book of 640K clever things Bill said".
It wasn't that many years after 1995, that cooperative multitasking
got changed to preemptive multitasking, and we had real OSes then.
They didn't have to crash :-) The OSes went downhill after that.
This is more to life than Microsoft OSes. MacOS and Linux do not crash on
app updates. In fact, both MacOS and Linux have gone WAY uphill since
1995.
As mentioned by Lawrence, the 1995 date is rather silly, because there were reliable preemptive multitasking/multiprogramming systems long,
long before that. My experience with them goes back to the early 70s for pre-UNIX systems and the early 80s for UNIX systems.
My experience also. But those were computers that were not available to consumers.
That said, I am sorry to rain on your parade, but ever since the NT-family of Windows systems, i.e. Windows NT to 11, I have never had Windows crash "on app updates" or any other 'app' related crash for that matter.
Then you need to get out more. In the last year or so there were screens
in airports around the world with crashed Windows Blue Screens due to a broken non-OS update.
Just because you have never personally seen Windows crash and burn does not mean it never happens. Windows is far too easy to crash.
...w-i|#-o-#-n|# <winstonmvp@gmail.com> wrote:
Yes, the global airport screens and system failures were caused by a
software app update.
Was this *really* caused by a software 'app' update, or did the (Crowdstrike) 'app' also include low-level components - such as drivers,
etc. - and were on or more of these these low-level components, the
cause?
--That update was provided, not by Microsoft, but Crowdstrike.
Microsoft updates do not include updates from Crowdstrike.
- Crowdstrike updates are managed and delivered independently from
Windows Updates - pulling their own signature/channel def updates
automatically via their 'own' cloud infrastructure.
- updates are pushed down by Crowdstrike, not Microsoft.
Two months prior to the Crowdstrike update impacting Windows,
Crowdstrike pushed down an app update for Debian Linux causing server
crashes and looped booting.
- i.e. your earlier point that app updates don't crash on Linux is
incorrect. In this from the exact same source => Crowdstrike
There was one particular point you made that could be somewhat true.
- Your comment that the airport screen crashing in the last year or so
could be accurate if liberty was given to the 'or so' timeframe.
- nothing of the above happened in this year or last year(2025) thus
'or so' would be 2.5 years ago for Windows and 2.75 years ago for Linux.
...w-i|#-o-#-n|# <winstonmvp@gmail.com> wrote:
On 11/05/26 1:20 PM, Nick Charles wrote:
Frank Slootweg <this@ddress.is.invalid> wrote:
That said, I am sorry to rain on your parade, but ever since the
NT-family of Windows systems, i.e. Windows NT to 11, I have never had
Windows crash "on app updates" or any other 'app' related crash for that >>>> matter.
Then you need to get out more. In the last year or so there were screens >>> in airports around the world with crashed Windows Blue Screens due to a
broken non-OS update.
Just because you have never personally seen Windows crash and burn does not >>> mean it never happens. Windows is far too easy to crash.
Yes, the global airport screens and system failures were caused by a
software app update.
Was this *really* caused by a software 'app' update, or did the (Crowdstrike) 'app' also include low-level components - such as drivers,
etc. - and were on or more of these these low-level components, the
cause?
On Fri, 11/6/2026 10:07 AM, Frank Slootweg wrote:
...wi+o#n+ <winstonmvp@gmail.com> wrote:
On 11/05/26 1:20 PM, Nick Charles wrote:
Frank Slootweg <this@ddress.is.invalid> wrote:
That said, I am sorry to rain on your parade, but ever since the
NT-family of Windows systems, i.e. Windows NT to 11, I have never had >>>> Windows crash "on app updates" or any other 'app' related crash for that >>>> matter.
Then you need to get out more. In the last year or so there were screens >>> in airports around the world with crashed Windows Blue Screens due to a >>> broken non-OS update.
Just because you have never personally seen Windows crash and burn
does not mean it never happens. Windows is far too easy to
crash.
Yes, the global airport screens and system failures were caused by a
software app update.
Was this *really* caused by a software 'app' update, or did the (Crowdstrike) 'app' also include low-level components - such as drivers, etc. - and were on or more of these these low-level components, the
cause?
https://www.computerweekly.com/opinion/One-year-on-from-the-CrowdStrike-outageWhat-have-we-learned
"The underlying nature of its Windows operating system, to which
it provided Ring 0 equivalent kernel access to CrowdStrike making
the issue possible in the first instance, was also a contributing
factor."
This is one reason Microsoft wants to chase AV products out of Ring0.--- Synchronet 3.22a-Linux NewsLink 1.2
https://www.ghacks.net/2025/06/27/microsoft-is-moving-antivirus-programs-from-running-at-kernel-level/
| Sysop: | Amessyroom |
|---|---|
| Location: | Fayetteville, NC |
| Users: | 76 |
| Nodes: | 6 (0 / 6) |
| Uptime: | 55:02:25 |
| Calls: | 1,265 |
| Calls today: | 1 |
| Files: | 1,362 |
| D/L today: |
3 files (2,684K bytes) |
| Messages: | 285,585 |