Read back your post you said LTSC but not 2019 or 2021. In order to remove the components for W10 Enterprise LTSC 2021 you need to integrate the specified CU first.
From my own post, friend: "I'm running the latest TK, and have removed all Edge components. My source is 10 Enterprise LTSC, I believe it was released around November/December 2021 (not sure on that, but its' checksum matches what I've seen elsewhere)." I did *IN FACT* specify 2021.
UOTE="graver.x, post: 1740784, member: 1338604"] @MSMG recommends using the methods in the following order: 1. DISM method 2. ToolkitHelper method (The results of my tests are in some of my other posts).[/QUOTE] I don't recommend using both the methods to remove the components, even if you want to use both the methods then only remove the components that are not removed by the ToolKitHelper.
If you had specified it as Enterprise LTSC 2021 then it would have been clear, specifying it has released around November/December 2021 will also make people to think it as regular monthly refreshed images released by the Microsoft.
I don't recommend using both the methods to remove the components, even if you want to use both the methods then only remove the components that are not removed by the ToolKitHelper.[/QUOTE] Well, the TK GUI (which from what I've been told uses the helper method) clearly doesn't cleanly and fully remove Edge in my case, so it's not like I have any other choice but to try a 2nd method.
I noticed that Webview goes crazy if you try to remove Edge on Pro/Home and then you start having issues with some Store apps just like how IE was needed with certain win32 apps.
Using Remove Windows Component menu and Remove Windows Component using Package List (ToolKitHelper method) uses the ToolKitHelper to remove components. In my previous reply you can see I have done a fresh test to remove all components including Edge and there are no traces of Edge in the Start Menu. You need to use the correct CU before removing the components if using ToolKitHelper method and use the latest uploaded ToolKitHelper.exe.
According to winver, my current installed LTSC version is 19044.1288. So it is indeed the LTSC from December 2021. I couldn't remember the exact date MS released that ISO. My currently installed OS hasn't connected to Internet at all, therefore updates haven't had a chance to install, which in turn means the version # hasn't had a chance to change. And I haven't manually installed any updates offline. It seems you're saying that I will need to integrate a CU before doing component removal. I have searched the changelog.txt for all instances of "cumulative", "cu", and "kb", yet I can't find any mention of the needed CU. If someone can specify which KB(s) are needed, then I'll just download it from Microsoft Update Catalog and have another crack at this tonight. I'm not really a fan of the "add more junk so I can remove more junk" concept. It just seems backwards to me. I thought the whole point of the TK is to debloat Windows rather than add cruft to it. But if it's necessary for component removal to work properly then so be it.
From Readme.txt Code: [G] - Remove Windows Components using Remove menu. [1] If using Remove Windows Components menu then [A] Select the Components to be removed using [Remove Windows Components->Select Windows Components] menu. [B] Remove the selected Windows Components using [Remove Windows Components-> Start Removing Windows Components] menu. Note: Only for Client editions source images with integrated cumulative update specified in the changelog.txt. From Changelog.txt v12.2 Code: + Updated the Feature "Remove Windows Component" to support Windows 10 Client v1809/LTSC2019 (v10.0.17763.1/v10.0.17763.2803) Source OS. + Updated the Feature "Remove Windows Component" to support Windows 10 Client v1903 (v10.0.18362.1) & v1903/v1909 (v10.0.1836x.2212) Source OS. + Updated the Feature "Remove Windows Component" to support Windows 10 Client v2004 (v10.0.19041.1) & v2004/v20H2/v21H1/v21H2/LTSC2021 (v10.0.1904x.1645) Source OS. + Updated the Feature "Remove Windows Component" to support Windows 11 Client v21H2 (v10.0.22000.1/v10.0.22000.613) Source OS.
Yes, I saw that at the top of the changelog. But since the needed KB isn't explicitly specified in that file, then I'm still clueless as to exactly which KB update needs to be integrated for removals to work properly. Your changelog merely says that the TK supports component removal for those versions, without mentioning which updates need to be applied first.
I created an ISO of 22621.105 last night (UUPdump) and the same message appears. "Package_for_ServicingStack_105"
Can someone say which KB update I need to integrate to LTSC 2021 19044.1288? I'm seeing this in the changelog.txt: "Remove Windows Component" to support Windows 10 Client v2004 (v10.0.19041.1) & v2004/v20H2/v21H1/v21H2/LTSC2021 (v10.0.1904x.1645) Source OS." That info helps me understand which versions the TK supports for component removal, but it doesn't explicitly give any clue what update needs to be integrated on top of what I have. I asked once before, I guess I can't be any more direct in my questioning.
If you download the last ToolkitHelper_Preview.exe and rename to ToolkitHelper.exe, the supported service pack will no longer be this 1645. It will be the respective that was announced with the publication of this ToolkitHelper Preview. In UUP Dump you download the last updates, or: https://forums.mydigitallife.net/th...-21h1-2-vb_release.80763/page-16#post-1571109
Just to be clear, I don't even want to integrate any updates. But @MSMG seems to have implied above that component removal won't work properly on LTSC 19044.1288, unless updates are added beforehand. Hopefully I didn't read him wrong. This would be the 1st time I've had to integrate updates just to ensure that removals work correctly. I'm still browsing around on the forum, trying to determine the bare minimum updates I would need. Once the OS is up and running, I don't plan to install any updates, and will use Windows Update Blocker to prevent them. I generally view updates as unnecessary, unless they fix a specific issue that I'm experiencing, or provide some kind of enhancement that directly affects my usage of the OS in a positive way. LTSC isn't supposed to receive feature updates anyway, so that's a non issue. And most "features" MS likes to add, are things that I consider non-essential. I'm a minimalist at my core.
You read it correctly. https://forums.mydigitallife.net/threads/msmg-toolkit.50572/page-1148#post-1740342 I update my isos. But simply block Windows Update. If I want to make an update of my installed version, I prepare an ISO and do the Inplace Update. Since you will have the job of preparing a custom iso, you have no reason to not to install it already updated.
I will respectfully say that your statement is very presumptious, TBH. I have every reason to not want it updated if not absolutely necessary: 1. Updates eat away at space that I would rather put to use elsewhere 2. Most of the updates (IMO) add things that I have no use for, and just generally don't enhance my experience or fix issues that directly affect me 3. Updates tend to revert user settings to what MS thinks is "right", making me work harder to put things back how I want them. And nowadays, they add back components that I've explicitly removed 4. I like to boot Windows in a ramdisk every now and then, which serves certain personal purposes. In this case, smaller is better, loading more stuff into RAM takes longer. And of course you are limited by how much RAM you have, and the max your hardware supports. 4. I like to move things like Program Files/Program Files (x86)/ProgramData off the C drive and onto other volumes. In my case it keeps things compartmentalized and makes for easier imaging backups. Obviously, most updates won't install with this arrangement, since MS doesn't support it. For some reason they are anal about this. And yet, Unix-like OSes like Linux are perfectly happy even when most critical directories are mountpointed onto other partitions.