From Newsgroup: alt.comp.os.windows-11
On Wed, 7/1/2026 1:52 PM, Stan Brown wrote:
It's at <https://github.com/Raphire/Win11DeBloat>
One thing I like is the fine-grained control, as shown by the
screenshot.
Apologies if this has already been discussed. Last I heard, Google
doesn't index this newsgroup. I know the general topic has come up
before, but I don't remember discussion of this specific tool.
There is a review here.
https://ca.pcmag.com/windows/15078/i-put-4-windows-debloating-tools-to-the-test-the-results-were-embarrassing
A question then, is what metric is suited to checking the results.
1) Smaller amount of C: usage ?
2) Smaller resident RAM size ?
Windows should be able to shut down subsystems, in a low resource situation. For example, if the sandbox-OS-image stored in RAM, there isn't room
for it, it should be switched off. I think I may have seen signs of
that in the past. But the other option is for the OS to crash at some
point.
That was one of the beauties of the OSes. You could install them
on a "capable" machine, then move the hard drive over to your
less capable machine (that Optiplex 780 refurb you bought), and
as the OS boots, stuff gets shut off as a function of whether
the OS thinks there is sufficient RAM for it to work.
What won't work, is a W11 25H2 HDD moved to the Optiplex 780 (E8400 with
no POPCNT instruction), is that will crash and there is no obvious
cure (like trapping on the errant instruction and replacing
the instruction with a macro). But for other subsystems, the HDD should be
able to "boot on anything" and adjust posture to suit.
Paul
--- Synchronet 3.21d-Linux NewsLink 1.2