This is how I compare bloat from one install to the next. I'm not claiming it to be the best comparison, it's just how I compare. This is Win10 Pro 22H2 installed in a VirtualBox VM with 2 GB RAM allocated and 4 cores. As-is, no debloat. Reference Point to base future debloat against. Zero internet allowed at this stage. The six security options during install all set to "no". This is immediately after install, no Guest Additions installed, no reboot after install, just watched it at idle. After about 10 minutes or so, the handles had settled to just below 30,400 and processes settled to 67. Consumed nearly 18 GB of hard drive space. Idle RAM never dropped below 1.0 GB (50%) of 2 GB available. 39! Links or folders in Start Menu. Holy Crap, been using LTSB/LTSC for so long I forgot about all of this "crap". Spoiler: Baseline: Task Manager Spoiler: Baseline: Disk Space
@LTSC-Ten suggest you "SPOILER" tag your images, so the Mods don't get pissed off, and it's really not hard to do -- and you can and fun, zany messages... Also you can screen grab just the Task Manager (or any specific window) by having it as top window and hitting Alt+PrintSreen instead of just PrintScreen. And yes, generally this is how I do it too, wait for 3 minutes (for consistency, because some Services & Processes wrestle with some de-pooping approaches) and look at Processes, Services, the Commit Charge, and if it's an install I think I might consider using I'll measure DPC latency...
Task Manager screencap doesn't paint the full picture, IMO. All that *crap* in the taskbar also reveals how bloated that install is. I have absolutely ZERO use for the MS Store on my installs. ZERO ZERO ZERO And I don't even recognize what that "widget" is to the left of the up-caret. ZERO use for it. Same goes for that "Meet Now". No clue what it is, don't care what it is, it's useless "overhead" to me. If the "feature" is something I needed, then I'd have a third-party app for it and added it myself. The OS is supposed to just be the "core" that WHAT I WANT is added on top of. In fact, I should have also included the two "hidden" POS (my opinion, they will not exist in my debloats, assuming these "playbooks" can remove them). Spoiler: Baseline: Hidden Taskbar Icons
RE: TBOK There is an issue ( at least my end ) Once everything is applied, File Explorer ( Full Screen ) keeps refreshing and continually goes back to the top of any folder you are in does not happen when Windows are reduced....
Alpha Test. I had to learn what these "playbooks" actually "do". Maybe it was only this one that I tried, maybe it was because this one recommended the older wizard, maybe this, maybe that. Not knowing how these worked, I made a few changes to my install first (disable d@mn Defender and a few other BS stuff that always GETS IN MY WAY). I didn't know (perhaps I should have) that these "playbooks" only alter a LIVE INSTALL (ie, not an .iso that future installs are installed from). So this test will actually need to be reran on an untouched/unmodified install. So strictly just an Alpha Test, I'll have to run all future tests WITHOUT disabling d@mn Defender and the few other BS stuff that I disabled before running the "playbook". That said though, handles going from 30,400+ all the way down to 18,500+ at startup and just a tad under 18,000 after 10/15 minutes of idle "seems" worthwhile. BUT... how much of that is because I disabled d@mn Defender first and foremost ??? Spoiler: Alpha Test: RebuildOS
The "RebuildOS" playbook requires an internet connection. Kinda hate that. That means that my comparison process will change. My installs are OFFLINE, no internet connection. I will have to *disable* Windows Updates !!! !!! Then enable the internet connection for the playbook. I don't want any (d@mn) Windows Updates sneaking in and affecting the before-and-after comparisons. I just want the baseline install and how the playbook affected it, how much it debloated. No more for tonight though...