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.
Don't worry will come up with some workaround for removing returned components on live systems until a full fix is complete.
Only the regular Windows components and System Apps will be returned when updating with CU. if you are thinking of only removing the Windows Apps that are available through the store then you can use the ToolKit safely to remove them since they won't be returned with the CU installation.
by using dism to remove defender leaving leftovers, would it render the leftovers unusable? i mean if its just a few files, cant we leave em there?
i wanna remove xbox, telemetry stuff, obvious bloat stuff . i could just use registry changes to disable defender, smartscreen, right? will CU still bring em back? at this point i dont even mind leaving edge on
The only issue using this method is that it may break other shared components. Some components like Xbox, Store, Maps have back-end files that are restored by CU, Yes the CU may restore the disabled keys sometimes which may have to be monitored and disabled.
I have uploaded the Edge Chromium Pack (W7/W81) for Toolkit, do test the pack and report for any issues. Code: 15efb00ec63714a4e9546dc58a4e60ce39e82b11 Packs\EdgeChromium\EdgeChromium_w7_x64.reg cff5db9332504a8bbf52af070e18b8c2733c385e Packs\EdgeChromium\EdgeChromium_w7_x64.tpk f40c2c26db8db6f4dfbd6c2fc0c29f051446022e Packs\EdgeChromium\EdgeChromium_w7_x86.reg 6b5379ff33f8860e77c0ebbe91297049a273c2e2 Packs\EdgeChromium\EdgeChromium_w7_x86.tpk 9da6336a04fb13d317f669d6efaa0b2034b519a4 Packs\EdgeChromium\EdgeChromium_w81_x64.reg 4ce0ed38b4f8937d42c81a6357a52cc158147555 Packs\EdgeChromium\EdgeChromium_w81_x64.tpk Will upload the newer pack for W10 tomorrow.
Hi! How can I install DirectX9c; Games ; Sidebar for Win10Pro_2004-19041 via the command line ? Thanks !
If you can wait for one or two days I will be uploading the next version of Toolkit with support for W10 v2004 packs integration.
Are you waiting for the next Cumulative Update, which is expected to be released next Tuesday? AKA: Patch Tuesday on the second Tuesday of each month.
No already I have updated the ToolKitHelper for the current CU (18363.693) and since the change-log for v9.6 has become lengthy, so thought it's time to release one.
Provisioned apps (Windows apps) are not reinstalled with CU. You can remove all of them even in 2004 with just one Powershell command. If removed with MSMG or NTLite I am not sure if the apps are not reinstalled because with them more things are removed. And you can prevent system apps from being deployed. Corporate use tools supported by microsoft. Powershell/Dism to remove apps and the rest is disabled via script and group policies. Removing components is no longer interesting as it does not decrease the size of install.wim from 1809 onwards with the advent of the PSFX format for updates and the need to keep component files in WinSxS so as not to break Windows Update.
I agree to a point. There are other reasons. I installed a vanilla W10, disabled every feature I could, and Windows 10 still sends several hundreds of megabytes of telemetry back to several dozen IPs non-stop. Several processes continue to run which thrash the HDDs/SSDs. The total processes is well over 100, the system feels less responsive even with a 970 Pro SSD. My 1809 trimmed image on the other hand runs 57 processes, feels much more responsive, and sends less than 40mb of data to M$ IPs each day.My CPU averages 0.5%-1.0% utilization on idle and the activity on my drives is negligible compared to a vanilla image with everything disabled. FPS in some games are noticeably better too Now it is possible I missed something when disabling stuff via registry, services, secpol and GPO, as I'm most definitely not an expert at this stuff, but I'm fairly confident I got most stuff. Size doesn't matter. If size were the only driving reason for removing components then yes, that would be quite pointless.
The latest version of toolkit helper does not work for v1909, build 18362.30, full iso name 18362.30.190401-1528.19h1_release_svc_refresh_clientbusiness_vol_x64fre_en-us. I'm using the Enterprise VL image in the index of this build and component removal does not work, and toolkit helper says it only works for v1803 and v1909 and I'm using v1909 but it doesn't work. The latest MSMG Toolkit doesn't work for component removal even though I've read through this thread you have said that the newest version of toolkithelper works but it doesn't. Neither the old version, or the latest released version copied into MSMG. Someone please explain how the hell I'm supposed to be able to remove components from this build that says is supported but apparently is not????