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????
18362.30 is v1903, for component removal the Toolkit requires the v1909 (18363.418) as base and also does work with the latest CU. - Mount the 18362.30 image. - Copy all the required latest updates including the v1909 Enablement package to WHD folder structure in ToolKit. - Integrate using the Toolkit's WHD Update Pack Menu. - Remove the Components using the ToolKit's Remove->Windows Components Menu.
Pro should be sufficient for average user but if you go for Enterprise you will get the option to set the Telemetry level to security only.
You misled me when I talked about Windows Server; I meant that it can be deleted through PowerShell on Windows 10. It cannot be deleted by standard Windows tools. Or is all this possible? p.s. All my attempts are unsuccessful, in that case!
May be I miss read your query, well be it Windows 7, 8, 8.1 or 10 (Client, Embedded and Server) the standard packages listed by the below command can be removed by standard DISM tool. Code: Dism /Online /Get-Packages The packages present in C:\Windows\Servicing\Packages and not listed by the above command needs a small registry modification which can be done by standard regedit.exe tool to make them visible with the above command and then it can be removed using the DISM. I do know the PowerShell uses the DISM Cmdlet's to handle the packages but I don't know whether it can handle the packages for whom there's no associated .mum files. So my answer for removal of packages like Cortana, Smartscreen using the standard DISM tool is not possible.
registry tweak? Okay, I think I have to limit myself to a normal shutdown. There is one good news, they are unlikely to change Trustedinstaller, because it can cause a global problem. Code: reg load "HKLM\TK_SOFTWARE" "%~dp0mount\Windows\System32\config\SOFTWARE" reg add "HKLM\TK_SOFTWARE\Microsoft\Windows Defender\Features" /v "TamperProtection" /t REG_DWORD /d "0" /f >nul 2>&1 reg add "HKLM\TK_SOFTWARE\Policies\Microsoft\Windows Defender" /v "DisableAntiSpyware" /t REG_DWORD /d "1" /f >nul 2>&1 reg unload "HKLM\TK_SOFTWARE" Will it be enough for a complete shutdown or not? This question arose on its own, because the defender’s settings seem endless. For example, a small part of them ... Code: + Computer Configuration > Administrative Templates > Windows Components > File Explorer: + Double-click "Configure Windows Defender SmartScreen" : Disabled -> OK reg add "HKLM\SOFTWARE\Policies\Microsoft\Windows\System" /v "EnableSmartScreen" /t REG_DWORD /d "0" /f ------------------------ + Computer Configuration > Administrative Templates > Windows Components > Windows Defender Antivirus: + Double-click "Turn Off Windows Defender Antivirus" : Enabled -> OK reg add "HKLM\SOFTWARE\Policies\Microsoft\Windows Defender" /v "DisableAntiSpyware" /t REG_DWORD /d "1" /f ------------------------ + Computer Configuration > Administrative Templates > Windows Components > Windows Defender Antivirus > MAPS: + Double-click "Join Microsoft MAPS" : Enabled; in the options select "Disabled" -> OK + Double-click "Send file samples when further analysis is required": Enabled; in the options select "Never send" -> OK reg add "HKLM\SOFTWARE\Policies\Microsoft\Windows Defender\Spynet" /v "SpynetReporting" /t "REG_DWORD" /d "0" /f reg add "HKLM\SOFTWARE\Policies\Microsoft\Windows Defender\Spynet" /v "SubmitSamplesConsent" /t "REG_DWORD" /d "2" /f ------------------------ + Computer Configuration > Administrative Templates > Windows Components > Windows Defender SmartScreen: + Double-click "Configure Windows Defender SmartScreen" : Disabled -> OK reg add "HKLM\SOFTWARE\Policies\Microsoft\MicrosoftEdge\PhishingFilter" /v "EnabledV9" /t "REG_DWORD" /d "0" /f