The problem is that the new Windows Update system requires the WinSXS to be left intact for proper functioning and the CU model does restores the removed stuffs from the WinSXS and updates them. I've been stuck with several issues personally for quite some time now and due to which I'm working on this issue only when I do get good amount of free time. I do understand it's difficult to keep re-installing the OS for every CU, will do my best to fix the components returning issue and also will explore the option to add the functionality to use the ToolKitHelper in live system environments. Will also see if the ToolKitHelper can be adapted to use within WinPE environment too, that can make it easy for removing the returned components from installed system. Also you can use Live Windows 10 OS or a secondary OS with ToolKitHelper and point the mount pah to the installed OS drive and try removing the components too. Occasionally you may need to keep the latest version of ToolKitHelper to deal with the CU changes.
In Windows 10 the Firewall is part of the Defender, try the below command in command prompt to disable it netsh advfirewall set allprofiles state off The MS is trying it's best to make the package removal to be more difficult by merging them deep into other main packages, will add the option to remove the firewall in upcoming versions.
I have added the support for W10 v2004 (10.0.19041) in next version and been fixing the WHD integration, will post the new version soon. You can manually add the MS Dart for W10 v2004 (10.0.19041) by these commands. - Download the <Packs\Dart\w10\Dart.tpk> and <Packs\Dart\w10\DebugTools_10.0.19041.tpk> files. - Mount the Boot or WinRE image using the ToolKit. - Use the below commands to integrate the Dart For Boot.wim (x64) Code: Dism /Apply-Image /ImageFile:Packs\Dart\w10\Dart.tpk /Index:2 /ApplyDir:Mount\Boot\2 Dism /Apply-Image /ImageFile:Packs\Dart\w10\DebugTools_10.0.19041.tpk /Index:2 /ApplyDir:Mount\Boot\2 For WinRE.wim (x64) Code: Dism /Apply-Image /ImageFile:Packs\Dart\w10\Dart.tpk /Index:2 /ApplyDir:Mount\WinRE Dism /Apply-Image /ImageFile:Packs\Dart\w10\DebugTools_10.0.19041.tpk /Index:2 /ApplyDir:Mount\WinRE
I never heard that it was possible to remove the defender and SmartScreen packages from windows, as far as I know, this is possible only on the server. Are there any innovations in removing components in the insider build? If this is true, I want to see it in my work. Please write me the build number and the command to remove the defender. p.s. Naturally, my assumption turned out to be true, that is, the system becomes more and more closed, on the other hand, third-party developers put pressure on them. Commands for the command line also do not work, because after a while the system itself does what it wants.
Which is why I said "Without meaning to put pressure on you". I just get a sense, that despite how brilliant you are with this stuff, that Microsoft may have finally made it impossible to remove components permanently. If that's how it is, then that's how it is. I'm not planning to rebuild the ISO via toolkit every month, that would drive everyone insane. So, a smaller, automated script that I can run after I install a CU will have to be enough. Microsoft's habit of breaking patches every month actually works in my favor. I just install every third or fourth one, then run a cut down script and be done with it.
I've been out of the loop for a while, my initial experience with W10 having been so dire that I've been muddling along on W7. However I need to move to W10 now unfortunately. Am I to understand that even if we remove components prior to installation, via either this / NTLite / other, or remove them via Power Shell once installed, that all the junk will be reinstalled with each CU? They've completely removed the ability to have minimal installations without constant intervention on the user's part? How on earth can this work for corporate or education deployments? Or does it not apply to Enterprise / Education / LTSC editions? Just built a new PC and was dreading sorting the W10 installation enough already before reading this
Corporate can use the typewriter OS Enterprise LTSB/C or normal Enterprise. Education can use Education.
Remember it is quite unnecessary to remove anything from Windows 10. Sure, there is a small size difference, but there is virtually no performance gain. You can just as easily unpin programs you don't want from the Start Menu. The Windows 10 Start Menu is very easy to customize. Much easier than Windows 7. As @Enthousiast said Education environments, and manufacturing/corporate environments can use LTSC, Enterprise, or Education which do not have the extra added games beyond MS Solitaire suite, and don't have News apps, etc. Personally I use Professional Workstation.
So up to date 19xx or the new 20xx, even on Enterprise / Education, will force re-installation of removed components via CU? This seems extraordinary to me, even by MS' standards. I don't doubt that LTSC doesn't, but that's less than ideal in my case. I'm running Zen2, and LTSC doesn't have any of the scheduler updates.
MS standards can be at the level of, this is what we created and this is what is working, chopping will create future problems (with all respect for MSMG), and will be more difficult with every new build.
That's correct, but you'll likely only notice the impact with heavy workloads (several VM's for example). I'm running LTSC on Zen2 and would not consider upgrading to 1903 or later with the current situation of components being restored. Maybe I won't update at all until the new LTS flavor comes out in a couple of years. Cheers.
You can remove the packages from Client editions too, starting with Redstone 2, the Microsoft changed the packages by merging many standalone packages into sub packages of other main packages. Windows Defender back-end can be removed using it's package names using the DISM but this method won't completely remove the packages, many left over items will be there. You may need to un-hide the package visibility to make them removable via DISM or use tools like Install_wim_tweak or ToolKit's remove components using package list to remove them. Code: Windows-Defender-AM-Default-Definitions-Package~31bf3856ad364e35~amd64~~10.0.18362.1 Windows-Defender-AppLayer-Group-Package~31bf3856ad364e35~amd64~~10.0.18362.1 Windows-Defender-ApplicationGuard-Inbox-Package~31bf3856ad364e35~amd64~~10.0.18362.1 Windows-Defender-Client-Package~31bf3856ad364e35~amd64~~10.0.18362.1 Windows-Defender-Core-Group-amcore-Package~31bf3856ad364e35~amd64~~10.0.18362.1 Windows-Defender-Core-Group-onecore-Package~31bf3856ad364e35~amd64~~10.0.18362.1 Windows-Defender-Core-Group-Package~31bf3856ad364e35~amd64~~10.0.18362.1 Windows-Defender-Group-Policy-Package~31bf3856ad364e35~amd64~~10.0.18362.1 Windows-Defender-Management-Group-amcore-Package~31bf3856ad364e35~amd64~~10.0.18362.1 Windows-Defender-Management-Group-onecore-Package~31bf3856ad364e35~amd64~~10.0.18362.1 Windows-Defender-Management-Group-Package~31bf3856ad364e35~amd64~~10.0.18362.1 Windows-Defender-Management-MDM-Group-Package~31bf3856ad364e35~amd64~~10.0.18362.1 Windows-Defender-Management-Powershell-Group-Package~31bf3856ad364e35~amd64~~10.0.18362.1 Windows-Defender-Nis-Group-Package~31bf3856ad364e35~amd64~~10.0.18362.1 The below system apps need to be manually removed Windows Defender Front-end UI is a System Appx (Microsoft.Windows.SecHealthUI_cw5n1h2txyewy) SmartScreen is a System Appx (Microsoft.Windows.AppRep.ChxApp_cw5n1h2txyewy) I haven't checked with the Insider preview builds to know what major changes the MS has done to packages.
Yes can be integrated, just need to capture the installation and convert it into a pack compatible for ToolKit.