To be fair, VCLibs and the .NET Frameworks (in the Appx-version) are actually primarily used for Microsoft Store applications. Most Win32 applications distributed outside the store come with their own redistributables. Considering this method removes the Microsoft Store, there is a very good chance that if your are only running Win32-based applications, you will not notice the loss. Particular example: .NET Native, which is actually a UWP-only technology despite the important-sounding name. If you have no UWP / Microsoft Store apps, its absence is irrelevant. Another one: VCLibs is primarily used for the Desktop Bridge which allows Win32 apps to run from Microsoft Store packages. But if you have no Microsoft Store packages...
This is why I recommend using a fresh install, in a virtual machine first, in the article, just in case.
So I get your point, but it also sounds awfully optimistic... ;)
(I see you got downvoted, but it wasn't me.)
You aren't presenting it as something everyone should do to clean up their relatives crufty loaded up pc's while visiting for holidays.
It is what it is and it's quite cool and useful for what it's useful for.
For those who think "oh I can do this on windows 11 too", This has a high risk of blowing away your shell too, which is distributed now as an AppX, also Defender and its update runtime which are distributed via AppX/Store so you're risking destroying your whole machine.
From the winds of change that I've been hearing: Most of the OS is going to be distributed via AppX packages, which means that pretty quickly, doing this will leave you limping and hurt.
I'd be interested in hearing what the issue on Windows 10 is, especially considering how it compares to Windows 10 LTSC which seems quite similar.
Edit: As for "That's hilariously stupid," I updated the article for my thoughts on that. Considering this is going to be used on a computer that cost me $150, has storage on a separate NAS, for a machine that could cause safety issues and a lot of money in wasted material if literally anything goes wrong (CNC router), running software that runs only on Windows and requires precise USB timing (no VM or Wine from Linux), I think it would be more stupid to not de-bloat for all the failure methods Windows has added. The last thing I need is Windows Game Bar popping up over the CNC Control Window and blocking the Emergency Stop button. [If you think this sounds horrifying, brand new CNCs have software that still runs great on Windows XP, it's called Mach3 and it's arcane.]
You mean the extremely dumbed down Windows 11 shell with huge everything? Good riddance. I'd like a command to run on my VM to get rid of this atrocity specifically, actually.
I deal with many OT/ICS vendors and they would all refuse to support their app on a Windows system modified in this manner. I think such an article should mention the -WhatIf option, so you get an idea of all the important things about to be removed.
On my systems that includes VCLibs, .Net frameworks. I would not do this.