It should work as long as there are no major changes in CU but the ToolkitHelper was updated last for 18363.535. Was about to add the support for 18363.I.592 but now a new CU 18363.628 has come out, will update to the latest one itself.
The Toolkit removes almost all the Windows Defender packages except few like the Windows Defender Firewall, Only testing can know if it will break the SFC.
Only Apps won't return back and updating with a new CU will completely restore the all other components removed. If the WU is failing, you can do try installing it with offline .msu or .cab file to see if it's working. Yes, disabling components can be achieved by registry and tasks setting, will explore which components can be disabled and try to provide an option for that too.
The latest version had been updated for both the 1809 and 1909, right now working on support for 18363.628 and will be adding fixes for 1809 too, just wait for two-three days will upload the newer version.
It requires some major changes to the script, have added the feature to my To-Do list, will implement it in future.
You mean the MRT, In Toolkit when the Defender is removed, I have added the tweak to disable MRT from getting downloaded through the WU.
1) Yes it uses a variable to set yes/no for the registry load and unload function and depending on it's value the menu text is changed dynamically. 2) Yes most client recovery images are same in each index, may be in server it might be differing. This option was made to reduce the time it takes to mount and integrate updates to each recovery image. Will checkout if it needs any changes for the server images.
Although for LTSC 2019, the Toolkit have set the 17763.1 as the base image since it can update to latest update without returning components but still the ideal method would be to remove components with updates integrated as some registry keys or files may get changed at some point breaking the OS functionality. If you are removing some components like Cortana, Defender than don't again choose the same in Tweaks section since it will be already there in the removal process. Would like to add support for LTSC 2019 image with updates integrated but don't know when I will be doing it due to lack of time.
Still I haven't started it, when I do start updating the Toolkit script will be updating some of the packs and will be working on the Edge Chromium pack together.
List of problems identified by me 1. After uninstalling Internet Explorer, DirectX 9.29.1974 (Web Installer) is not installed. An offline package is installed 2. After uninstalling MapControl, the "File Information" item in Photos does not work No damage detected An example used 18363.592 ru_windows_10_consumer_editions_version_1909_updated_jan_2020_x64_dvd_93c0a102 3. When I delete Speech, it detects damage. Maybe Speech needs to be deleted with something 4. When I took the previous image and integrated the updates, and then removed the components, instagram did not start. After the release of the January image of 18363.592, the problemma disappeared. While the problem is removed
Yes, I have a copy of Explorer++ which I'm also going to try. Just haven't had a chance yet, though that's more about hiding the problem than finding and fixing it.
Ah, that would be Windows Defender that I disabled from the tweaks menu. Did that bork my image and I need to start again? I did notice that the final image was 6GB, the largest I have ever seen. My base ISO image was 17763.1, and following the readme.txt file, I integrated the updates as per the following order... [F] - Remove all required Windows Components using [Remove->Remove Windows Components] menu. [G] - Integrate Windows Updates using [Integrate->Windows Updates->Windows Updates] menu. So, should I have created the image without integrating updates at all, or integrated the update (G) before doing (F)? Also on line 175 of the readme you say 1803/1909. I assume the should read 1803/1809?
@Yanta Hi as I said yesterday something I learned and fantastic is also: after finishing all the work of option 6, enter option 2 and convert the WIM image to ESD and then use option 7 to create the ISO reduces a barbarity see the mine for example was only 2.6GB but note that this conversion from WIM to ISO takes a long time and look that I have a very fast machine (AMD) just be patient because it pays and you can believe
Lol. That would be fine (swap F and G), except the toolkit only works with 17763.1, so if updates are integrated before the removal it no longer works!