NotHereToPlayGames

Chromium FIRST LOAD AFTER STARTUP on LTSB 2016: As timed by PassMark AppTimer -- https://www.passmark.com/products/apptimer/ And waiting for the "new tab" page to fully load. FORTY D@MN SECONDS every FIRST LOAD after any startup or resume from hibernate (so I go into hibernate with my Chromium left open to prevent the delay "tomorrow" when I wake up).

Well, 1511 was pretty lean and mean in comparison to Win10 releases that came afterwards. Without "re-learning" tweaks of that era and just doing some minor tweaking, I can get its startup-surge-43 down to 34 and its settled-37 to 30. That 30 is inline with my LTSC's 32. With a threads count LOWER by only 5 (with an occasional 8 to 13) and the handles count LOWER by ~2100. Thread count is a measurement of how many "sequential lines of code" the CPU is processing. We've already achieved an LTSC de-bloating VERY similar to that of 1511. BUT... memory management in operating systems took a GIGANTIC LEAP right around 2021 or so. The way that "chunks" of code (think large .dll files) are "allocated" into RAM is a sh#tload tons FASTER with OSs newer than 2021 or so (ie, the 21H2 that LTSC is based on!). Best example that pertains to my hardware is *any* Chromium-based browser FIRST LOAD AFTER STARTUP. This is true (for me and my hardware) for Supermium, Chromium, Chrome, e3k-blah, *ALL* Chromium browsers do this! I've never found a "fix". UNTIL starting to use 21H2 and higher OSs !!! They do not have this first-load launch-lag. It's all about memory allocation and DON'T WASTE YOUR TIME on anything older than 21H2. I'll post a screencap of a FIRST LOAD AFTER STARTUP for Chromium on my 2016 LTSB and then a screencap of a FIRST LOAD AFTER STARTUP for Chromium on my 2021 LTSC.

Well, for one, I've never heard of 1511 referred to as "10586", so it was literally in one ear and out the other, I thought it was some Texas Instrument OS on an old "DX2" cpu. Once I realized it was just another name for 1511 (aka, "November Update"), the upgrade lag kind of does NOT surprise me at all. No, not everything boils down to process count, thread count, and handle count, but it has served as a good comparison for everything I do. This is 1511 *as-is*, no tweaks at all, just an as-is install, right down to OneDrive and all of the other BLOAT that even 1511 had back in the day. So yeah, going from 1511 with an as-is process count of settled-37 to startup-surge-43 or so to an LTSC IoT with an as-is process count of settled-92 to startup-surge-110 or so is a GIGANTIC LEAP in everything that cpu is chugging in the background before even trying to do anything requested by the user.

👍🏻

This is my Phase 4. This is equivalent to where my WinReducer EX-100 process gets me in terms of cutting out all of the bloat but not in terms of how much disk space the installation consumes. As in all previous screencaps, TWO of the processes are technically VirtualBox processes. So my tweaking gets an as-is Win10 from 90 (100+ at startup, settles to 90) all the way down to 30 !!!

Recap: there are only THREE items in ALL of Phase 3 that "might not" be for 'everybody'. 1) sc.exe config Spooler start= disabled -- replace disabled with auto if you install a printer 2) sc.exe config WpnService start= disabled -- breaks "Open Network and Internet settings" but does not break internet connection, breaks various "toast notifications" 3) sc.exe config WpnUserService start= disabled -- breaks "Open Network and Internet settings" but does not break internet connection, breaks various "toast notifications" Phase 4, on the other hand, "definitely" (intentionally!) breaks some of Win10. Actually VERY minor, I'll post that later. But again, ALL of Phase 3 should be FINE for "the average user" (even including #2 and #3 above, but "mileage may vary").

I used to use Directory Opus for syncing files between internal HDD and external archive HDD. But note that it isn't free but does offer a free trial to see if if works for you. Mine is a very old version and I've not bothered to see if it migrates to Win10 with my current (old) license.

Phase 3, Step 2: Save the below as a <name>.reg and double-click to add to registry.

Phase 3, Step 1: Save the below as a <name>.bat file and Run as administrator.

Guide for Half Baked Phase 3: TWO steps. Next two posts.

Here's where my Phase 3 gets me:

To be perfectly honest, one of the primary reasons that I tweak and optimize myself is because one of Conan's releases that I was testing PUNCHED ME IN THE FACE with an uncalled for SOLICITATION to purchase a LICENSE for StartIsBack/StartAllBack. A never-asked-for and nowhere referenced on his website that his builds INCLUDED a *third-party* BUNDLE that I do not want, did not ask for, will NEVER use BECAUSE of that UNSOLICITED punch in the face! "To each their own."

I only use 11 on one of my laptops but also inside a VM here on my primary workhorse. Tweaked, of course. I prefer (heavily!) to tweak myself and kind of "boycott" things like X-Lite. X-Lite is VERY GOOD. I just DO NOT TRUST IT for my use. Not to be misread, I don't have any reason to not trust it, I just trust MY OWN tweaked OS's far far FAR better.

Agreed! I've stopped fighting with XP also, almost two years or so now. It's been a GIANT godsend !!! I run Win10 LTSC and everything just runs a HELLAVUALOT better !!! With VASTLY better memory management !!! An outright GODSEND.

<del> testing [co de] inside [spo iler]

Step 4: Disable "smartscreen", disable the search APP, and disable nonessential services. Reminder: don't disable SPOOLER [set first line to auto instead of disabled) if you have a printer installed. Note: for those that want to INTENTIONALLY break some GUI "dialogs" (BS things like "toast notifications", "badges", and "live tiles"), set the two Wpn services from auto to disabled. Caution: the GUI breaks are not restored simply by returning those to auto! Source: none, just standard "public knowledge" across multiple tech forums Save the below as a <name>.bat file then right-click and Run as administrator.

Step 3: Remove "Get Started", "Windows Backup", and "Edge". Forum software kept "double-indenting" when posting as a "spoiler" so I had to post as a "code inside a spoiler" instead. Source: forgot, it's two or three scripts all merged into one and edited to REMOVE where the original author threw in Firefox BS, will add after I reinvent that wheel. Save the below in a <name>.ps1 file then right-click and select Run with PowerShell.

Step 2: Disable "search indexing". Note: this is technically only HALF of Win10's "search" and the APP is disabled in Step 4. Top Half Source: copied out of one of Chris Titus Tech's scripts but I forget the actual source. It allows me to simply right-click "Run with PowerShell" and it AUTOMATICALLY elevates to ADMIN. Just a helluvalot easier than the way that Win10's PowerShells are normally "ran as administrator" compared to how command prompts can be "ran as administrator". Bottom Half Source: https://github.com/PowerShellLibrary/Hacker-Scripts/blob/master/system-setup/disable-windows-search-indexing.ps1 Save the below in a <name>.ps1 file then right-click and select Run with PowerShell.

Step 1: Disable the "Action Center". To be honest, I've never really tracked how (or if?) the "Action Center" consumes a ton of resources or not, I just have ZERO use for it. Source: https://www.tenforums.com/tutorials/6004-enable-disable-action-center-windows-10-a.html Obtain from above link or save the below in a <name>.reg file and double-click to add to your registry.

Guide for Half Baked Phase 2: FOUR posts below. (multiple spoilers in one post weren't working correctly, didn't want to debug "why")

<del> mishap with multiple spoilers in one post

Before: 92 processes, 693 threads, 29102 handles, 1.1 GB RAM (ie, this is a normal as-is Win10 IoT install without doing any tweaking, just running as-is [with all of the install questions set to "no"]). After: 46 processes, 344 threads, 14210 handles, 0.6 GB RAM (the threads and handles counts is a better quantifiable measurement of "bloat" than the process count) This has seemed to be a good Rule of Thumb for every version of Windows (including XP!). A tweaked and optimized runs at *HALF* the resources when compared to a "normal as-is" install. I have additional tweaks that gets me down to 34 processes! But it (intentionally!) breaks some of Win10's GUI so those should probably be eliminated from this discussion. I don't even run those tweaks on my "everyday" computers, just in some VMs that were more for testing my tweaks before realizing I squeezed the turnip a little too hard for everyday use.

This is where my Half Baked Phase 2 dials in at, this is the first minute at startup: 48 processes, 535 threads, 14904 handles, 1.0 GB RAM (note that RAM will be higher on real hardware based on drivers for that hardware) This is after letting it sit idle and monitoring where everything "settled" after the startup process fully completes: 46 processes, 344 threads, 14210 handles, 0.6 GB RAM

Possible. But I'll let somebody else undertake that endeavor. I prefer the WinReducer EX-100 route over the winntsetup route.

I'll paste into a "spoiler tag" here and see if it works. It's part of my Phase 2 process so I'll post that shortly.