I 'must'? Or else? While the process and services 'count' across same kernel SKUs may vary, the dependences do not, it's just a different starting place for crap removal. Again, as I've answered you previously elsewhere, and in posts I've linked you to, multiple times: I only use Windows 10 IoT LTSC, and Windows Server (kernel 10 10240-26100). Why does this make it 'especially'? And why do you need two to five posts to respond to one post? Here I'm responding to two posts with just one and it works just fine. Eleven is arbitrary and based on what I use, as far as what Windows Kernel Developers have said re. Windows kernel 10 10240-26100 there are really only ten essential Services for a running OS: · Plug and Play (PlugPlay) · Power (Power) · Windows Audio (Audiosrv) · Remote Procedure Call / RPC (RpcSs) · COM+ Event System (EventSystem) · Windows Management Instrumentation / WMI (Winmgmt) · Task Scheduler (Schedule) · DHCP Client (Dhcp) · DNS Client (Dnscache) · Network List Service (Netprofm) Everything else, is everything else: compatibility poop, fluffy poop, poop for the sake of poop, spy on you poop, sell you more poop poop, poop because Microsoft can. Pretty sad one of the original benefits of a Service -- that it would only run when it was needed and stop, has all but been abandoned by the Vole and the Slopware Marketing team in Developer drag...
I hope you have better luck than I have! Getting under 29, and you're testing all kinds of compatibility hooks and fake dependencies. Some you can get around by using portable applications and/or brute force disabling some 'SystemApps' -- though this is pretty crude (on what's really a pretty crude bodge OS anyway) so I don't feel bad about it. I do understand people that desire a superficially 'clean' or at least 'cleaner' aesthetic. But Windows is like a toilet that won't properly flush, or like putting up a new sheetrock wall over a wet water (and poop, because Microsoft loves poop) damaged wall. All my affection and nostalgia for Windows is slipping...
I'll have to move on now. All of the poop talk feels like I'm talking to a 3rd grader instead of a serious adult. Sorry, just not my way of communicating. Not that I'm the best communicator to begin with.
In the sprit of completeness I'm adding @pm67310's Script and @sainfo's WimDirector -- as neither of these have a GitHub page, specifies a license, and WimDirector doesn't even have its own thread on MDL (it's kind of a PS1 spin on Slimdown11), I just parked them at the end of the list as 'Unclassified Indie Projects.'...
Because of this observation on my own hardware - https://forums.mydigitallife.net/th...me-startup-on-ltsb-2016-ltsc-2019-21h2.90646/ I have taken my build in a different direction. I have been a BIG FAN of the LTSB/LTSC Windows 10 versions since I was introduced to them only about 3yrs ago. I was literally still using XP x64 up until that point. I emphasize because most people I run across [in real life] think XP only ever came in x86 and that XP was limited to 4 GB RAM. Not true, obviously. So at 3yrs on the Win10 side of things, I'm still a "toddler". Getting process count to under 29 is a noble endeavor. But I admit that I see it a tad differently. While I place a high emphasis on process/thread/handle count, my hardware observation linked above can't be totally ignored. ie, I went from an XP setup that idled after startup at low-teens for process count, under 3,000 for handles, and consumed less than 65 MB RAM. But took over three minutes just to launch Chrome for the very first launch of the day. Sure, grab a cup of coffee and just wait it out, lol. But consider each and every version of Win10 installed since, same exact hardware, same exact portable Chrome, same exact Chrome profile. That first launch in the morning startup time has been basically CUT IN HALF with each and every new version of Win10. ie, from a latency perspective, running a few more processes and a little bit more RAM for the sake of an app taking SECONDS to launch is WELL WORTHWHILE. From memory management efficiency or whatever it is, that 13yr old hardware actually works better with Win10 installed than it ever did with XP. And it has been better and better with each newer version of Win10 (debloated, of course). I have been experimenting with Win11 LTSC 2024. It is only VM Testing at this stage. But it will end up landing on that 13yr old machine *IF* it improves that first-launch Chrome startup time coming out of hibernate. Once debloated, the everyday throughout the day performance is all but identical from 2016 to 2019 to 2021. I'm not far enough in to see if 2024 took a step backwards or continued the trajectory that 2016 to 2019 to 2021 has already demonstrated. And I think most of us already have seen that trajectory for themselves - ie, most here use 2021 and not 2019 or 2016. So far, this is where I've managed to get Win11 LTSC 2024 debloated to. Before debloat, it ran at 108 processes and 36,540 handles at startup and after 3-5 minutes of idle. My last VM notes has it down to 43 processes and 15,060 handles. Varies a little, of course, 5min idle screencap below. I have some settings tweaks still to do before sending to real hardware (that 13yr old Dell) and testing first-launch Chrome coming out of hibernate. If that Chrome performance improves, then I kind of don't mind bumping the OS up from my 2021 at 37 to 39 processes and 12,600 to 13,900 handles. Spoiler: 2024 in VM
Okay, this probably only confirms what most already knew. I installed a debloated Win11 LTSC 2024 onto my 13yr old Dell. And while not the best barometer, it basically serves as a DAILY reminder of how well the OS is doing. ie, launching Chrome and the HUGE delay on this particular hardware. My real-world observations, again strictly as it pertains to my 13yr old Dell - Win10 LTSC 2021 gets that first launch right out of hibernate done 2 seconds faster (three samples from each OS). While 2 seconds might not sound like a big deal, it does represent 10% to 15% when talking about launch times in the low 20-second range.
Why not use a more performant browser? Chrome is a not only a terrible resource pig, it's less respectful of your privacy, security and time than Windows... There are lots of better options with the Chrome browser engine and de-Googled Chrome engine...
Work forces my hand. I don't have anything against non-Chrome/Chromium/Edge, but again, work forces my hand. AND, after using them, I've actually come to like them. But no, my long-term history is with the *THREE PERCENT* global market share browser, lol.
You weren't entirely wrong. But not entirely right either. I'll update my other thread. No traction on that thread, but OT here.
Install Wim Tweak is a phenomenal utility to cleanly strip Windows. It not only gives you the full control but also get around the Windows internal limitations of what can be stripped using the DISM, by making the packages available to strip that DISM hides otherwise. It's a low level tool that strips the components by targeting their packages like DISM does so it works natively inline how Windows expects to be customized which leaves less room for unrelated errors. Just don't forget to run componentstorecleanup command post install wim tweak operation so related packages and their payloads can also be purged from component store.