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.
They already gave the solution to your problem, you don't agree... Use Linux so don't use Windows if it's too much work
Inplace updates, do not add things explicitly removed if your updated ISO has the components removed. If your ISO is a base image, 19041.1 it will not have updates, and the application of the latest updates will make a minimal difference in space occupation, for more occupation or even for less occupation. Update from outside Windows Update, rarely, some update has caused performance problem. In the vast majority of cases, it increases performance. Yes, updates will bring back what you have removed. That's why in Toolkit you integrate, and then remove. If you integrate updates in an image that already has an implemented servicestack such as LTSC 2021 with Stack 1288, you risk getting undesirable remnants and generating increased space occupation. It is very difficult to happen, but it is not a disposable hypothesis. I also went through what you go through, in the sense of "Updates tend to revert user settings to what MS thinks is "right", making me work harder to put things back how I want them." But currently, I create an ISO in 30 minutes and when finishing an installation everything is like I want, all configured. With suggestion to install applications updated directly from the web to my development stack among others, right after the first logon and the first connection. So it's all a matter of automating some things. I no longer make the scheme of reducing everything possible in ISO ... But from what you said, this is your case. I don't know if you need Winre, but it's something you can remove that you will release a good space, too. It seems to me that you are presenting experience with Windows Update, not with Inplace Update for daily use. About the image for use in Ramddisk is another story. My recommendation is that you open up to new possibilities and do these other tests. EDIT: NOTE: Perhaps I am wrong about being able to obtain the LTSC 2021 by means of an IoT Enterprise with No AddUpdates (19041.1) from UUPDump. EDIT2: Typo from 19044.1 to 19041.1. And, to get the bump from 19041.1 to 19044 it needs the EP + at least the 1147 LCU
Easier said than done. I have a need to use certain programs which will only run 100% on Windows. And I'm an extreme gamer. While many games released for Windows do also work in Linux, there are also many that don't. Like for instance, games that use DRMs like Denuvo. And then there are cases where a game can be made to work in either OS, but getting it to work in Linux is much more effort. In addition, certain anti cheat softwares aren't Linux-friendly. I was once permabanned in Arma 3 multiplayer, and all because I ran the game via WINE instead of Windows. No cheating was involved on my part. It took a lot of emails to the devs to get their decision reversed.
Ok, so, I think I've decided. If I have to integrate a cumulative update to get component removals working for LTSC 2021, then I might as well go with the latest available CU update and nothing else if it's not necessary. Which in this case appears to be 19044.1766. In the linked post, I see an SSU and and LCU. Do I need both, or just the LCU (I think SSU is a servicing stack update, but from what I've read elsewhere the servicing stacks are already included in cumulative updates)? I also see alot of other update links in that post, but I'm not convinced that I need all of them, besides the LCU and maybe the SSU. I'm also not looking to try to add any "feature pack" updates to LTSC that weren't intended for it, since it's not supposed to receive regular feature updates anyway. I just want to make sure that applying this won't add anything that is intended only for non-LTSC editions.
Yes at least after that CU gets integrated if it's in full cab file or msu format, but if the cab + psfx extracted folder is used it fails for W11 v22H2 Windows 11 v21H2 10.0.22000 WHD integration works Code: =============================================================================== MSMG ToolKit - Integrate WHD General Updates to Windows Setup Install Image =============================================================================== ------------------------------------------------------------------------------- ##################Starting Integrating WHD General Updates##################### ######################to Windows Setup Install Image########################### ------------------------------------------------------------------------------- Image : Install.wim Image Index : 1 Image Architecture : x64 Image Version : 10.0.22000.1.0 ------------------------------------------------------------------------------- ####Processing WHD General Updates Packages#################################### ------------------------------------------------------------------------------- Creating WHD General Updates Temporary folder... Extracting Update Package files to Temporary folder... Finished Extracting Update Package files to Temporary folder... ------------------------------------------------------------------------------- ####Integrating WHD General Updates to Windows Setup Install Image############# ------------------------------------------------------------------------------- ===========================[Install.wim, Index : 1]============================ ------------------------------------------------------------------------------- Integrating Windows 11 Servicing Stack Update Package... ------------------------------------------------------------------------------- Deployment Image Servicing and Management tool Version: 10.0.25140.1000 Image Version: 10.0.22000.1 Processing 1 of 1 - Adding package Package_for_ServicingStack_761~31bf3856ad364e35~amd64~~22000.761.1.0 [==========================100.0%==========================] The operation completed successfully. ------------------------------------------------------------------------------- Integrating Windows 11 Cumulative Update Package... ------------------------------------------------------------------------------- Deployment Image Servicing and Management tool Version: 10.0.25140.1000 Image Version: 10.0.22000.1 Processing 1 of 1 - Adding package Package_for_RollupFix~31bf3856ad364e35~amd64~~22000.776.1.10 [==========================100.0%==========================] The operation completed successfully. ------------------------------------------------------------------------------- Integrating Microsoft .NET Cumulative Update Package... ------------------------------------------------------------------------------- Deployment Image Servicing and Management tool Version: 10.0.25140.1000 Image Version: 10.0.22000.776 Processing 1 of 1 - Adding package Package_for_DotNetRollup~31bf3856ad364e35~amd64~~10.0.4515.1 [==========================100.0%==========================] The operation completed successfully. ------------------------------------------------------------------------------- Generating WHD General Updates Integration Log File... ------------------------------------------------------------------------------- Writing WHD General Updates Integration Log. ------------------------------------------------------------------------------- ####Cleaning Up Temporary files & Folders###################################### ------------------------------------------------------------------------------- Cleaning Up WHD General Updates Temporary folder. ------------------------------------------------------------------------------- ##################Finished Integrating WHD General Updates##################### ######################to Windows Setup Install Image########################### ------------------------------------------------------------------------------- =============================================================================== Press any key to continue . . . Windows 11 v22H2 10.0.22621 WHD integration fails Code: =============================================================================== MSMG ToolKit - Integrate WHD General Updates to Windows Setup Install Image =============================================================================== ------------------------------------------------------------------------------- ##################Starting Integrating WHD General Updates##################### ######################to Windows Setup Install Image########################### ------------------------------------------------------------------------------- Image : Install.wim Image Index : 1 Image Architecture : x64 Image Version : 10.0.22621.1.0 ------------------------------------------------------------------------------- ####Processing WHD General Updates Packages#################################### ------------------------------------------------------------------------------- Creating WHD General Updates Temporary folder... Extracting Update Package files to Temporary folder... Finished Extracting Update Package files to Temporary folder... ------------------------------------------------------------------------------- ####Integrating WHD General Updates to Windows Setup Install Image############# ------------------------------------------------------------------------------- ===========================[Install.wim, Index : 1]============================ ------------------------------------------------------------------------------- Integrating Windows 11 Servicing Stack Update Package... ------------------------------------------------------------------------------- Deployment Image Servicing and Management tool Version: 10.0.25140.1000 Image Version: 10.0.22621.1 Processing 1 of 1 - Adding package Package_for_ServicingStack_2~31bf3856ad364e35~amd64~~22621.2.1.1 [==========================100.0%==========================] The changes due to package Package_for_ServicingStack_2 requires the current servicing session to be reloaded. All the packages will be processed again. The operation completed successfully. ------------------------------------------------------------------------------- Integrating Windows 11 Cumulative Update Package... ------------------------------------------------------------------------------- Deployment Image Servicing and Management tool Version: 10.0.25140.1000 Image Version: 10.0.22621.1 Processing 1 of 1 - Adding package Package_for_RollupFix~31bf3856ad364e35~amd64~~22621.105.1.7 [==========================100.0%==========================] An error occurred - Package_for_RollupFix Error: 0x800f0988 Error: 0x800f0988 DISM failed. No operation was performed. For more information, review the log file. The DISM log file can be found at D:\Work\Toolkit\Logs\Dism.txt ------------------------------------------------------------------------------- Integrating Microsoft .NET Cumulative Update Package... ------------------------------------------------------------------------------- Deployment Image Servicing and Management tool Version: 10.0.25140.1000 Image Version: 10.0.22621.1 Processing 1 of 1 - Adding package Package_for_DotNetRollup~31bf3856ad364e35~amd64~~10.0.4460.20 [==========================100.0%==========================] The operation completed successfully. ------------------------------------------------------------------------------- Generating WHD General Updates Integration Log File... ------------------------------------------------------------------------------- Writing WHD General Updates Integration Log. ------------------------------------------------------------------------------- ####Cleaning Up Temporary files & Folders###################################### ------------------------------------------------------------------------------- Cleaning Up WHD General Updates Temporary folder. ------------------------------------------------------------------------------- ##################Finished Integrating WHD General Updates##################### ######################to Windows Setup Install Image########################### ------------------------------------------------------------------------------- =============================================================================== Press any key to continue . . .