And there are a lot more to choose from. As far as a recommendation that's wasn't really the intention of the thread, and you'd have to be a lot more specific about what you're intend or think you want/need. Do you use Windows 10, 11, Server or some other SKU? What do you use your PC or Laptop for primarily? How important are privacy and security to you? Do you really like/need any of Microsoft's braded purloin-ware? Is your system performance constrained? Do you need something that's easy with a GUI or are you find with a command line script interface?
what a list! if it was a food menu, I'll sure take it all home. I'm also in the middle of cooking an automation script, but too shy to emerge up the water. pro's and con's in your list had been taken into consideration and optimized, but mine is a hybrid cmd + ps1 not an interactive GUI model. nah... , letter for details now just self-consumed for my eyes-only, too shy to share in public. nice thread friend, keep it updated!
Don't be shy, and if you want to put an interface on PS1 script, and feel like you don't have the script chops to do that -- do a little free vibe coding, even free general algos like Google Gemini read PS, and can create great script, add menus, and even help you debug what you're doing. Counting on people like you to help me do that! Seriously, if you get to a place where you have something that you like, for how you use Windows, chance are there's more than one other person that is looking for exactly that too -- as long as you make it clear what you're doing. Glad you're here!
Taking your advice, as good as a lot of the software you have listed... A lot of them are deprecated or, out of date (Re: Windows 11) It might be worth your while creating a division between the Two OSs (10 - !!)) and which listed apps is best suited (works with) the relevant OSs Apologies, Just Nit Picking also, maybe break it down to categories, Sub Catrgories? OFFLINE Debloat = More Efficient ONLINE Debloat + Subject to M$ reversion (via LCU Updates) Advice... Don"t use a Script, and when it effs up, use another Script to correct it, research Please.
Will do some of that as I have time, but the main intention here was more as a repository and FOSS resource -- for people like jagoanku that are making scripts themselves, as all of these are FOSS, have borrowed a lot of what they use, anyone making scripts trying to improve on or customize what others have done can use anything found in any of these applications in their own work. Some of your premises are not just wrong, they're ridiculous: offline debloat is not necessarily 'more efficient', online or post install debloating is not necessarily any more subject to reversion from LCU updates than offline custom install media. As far as 'research please' I'd encourage you to do more yourself, some of what you assume to be true could get you in trouble, in fact that's true about assumptions in general. Intellege Quid Agatur
Debloating an offline image can be "more efficient" in the sense that less cleanup is required. For example, if Defender or OneDrive are already present on a live system, you have to clean up the registry for both system and user entries. If the features were never present to begin with, that action is avoided. Some script dev's only know how to approach live removals, and don't do offline images. If someone were creating a survey of debloating projects, it's useful to note which ones take advantage of CBS servicing, and those that "brute force" removals with takeown/icacls.
In principle you are correct, 'can be' sure, in practice however this is not entirely, or always the case, depending on the application, component, Windows sub-system being removed, method available for that feature for removal, and approach taken... In fact you will still find some registry entries for Defender or OneDrive regardless of method applied, and the similar over-generalization that 'some script dev's only know how to approach live removals' while it may well be the case for some is not always true. There are very capable script Developers that document limitations of both approaches. As well the Windows OS is a moving target, Microsoft takes overt steps to obfuscate and break things. There are many good arguments for post install clean-up, like the ability to do/un-do removed crap if needed like when Microsoft decides they're going to shove it down your throat with an update, or by other means, and a lot of Users just don't have the time or wherewithal to research the finer points of Microsoft's obtuse, erratic, and dysfunctional approach to OS design and capitalization, and have the time to be frequently clean reinstalling Windows. Choosing a post install method that works around these constraints can have just as much veracity. That would be outstanding if 'someone were creating a survey' -- are you volunteering?! The time commitment just to looking at every the FOSS projects I've listed so far, and to document every feature they offer as you describe would be a full time job for someone, for...a long time. I love your enthusiasm and commitment! This however is as it stands just a 'Repo' -- and as I've made the effort to only include projects that have a GitHub page, it might be more practical for someone with the time and the chops to write a good AI prompt to do something a long the lines you and others describe as scraping GitHub for information is something AI can easily do effectively. What I find especially discouraging that I see on these forums is a virtually relentless expectation of people expecting other people to make effort on their behalf, and even asking for it -- they themselves are unwilling to make...
Hi friend, I asked my lazy ai to build a documentation and compile the 29 tools you've mentioned earlier. If you don't mind to re-arrange the html docs as to side-by-side with your tool list. I'm unable to do that, so could you assist to tidy up the documentation, pls. Big Thanks to @hoak and everyone keeping the Windows tweaking community alive. Keep building, keep sharing, and keep making Windows a little less annoying.