Use SxSv1 1.Mount untouched install.wim to C:\mount 2.Set path to mounted install.wim in SxSv1\_Helper\SxSExport.cmd goto ::Examples and set the path Code: set Path_Image=C:\mount\Windows Code: _Packagelist_Base.txt 549; Windows-Defender-AM-Default-Definitions-Package 550; Windows-Defender-AppLayer-Group-Package 551; Windows-Defender-ApplicationGuard-Inbox-Package 552; Windows-Defender-ApplicationGuard-Inbox-WOW64-Package 553; Windows-Defender-Client-Package 554; Windows-Defender-Core-Group-Package 555; Windows-Defender-Group-Policy-Package 556; Windows-Defender-Management-Group-Package 557; Windows-Defender-Management-MDM-Group-Package 558; Windows-Defender-Management-Powershell-Group-Package 559; Windows-Defender-Nis-Group-Package Code: Generating Base-Packagelist... ------------------------------------------------------------------------------ Please look in: 'C:\Users\User\Desktop\SxSv1\_Packagelist_Base.txt' and type the number of the Base-Package you want to export. ------------------------------------------------------------------------------ >549 In prog.: Windows-Defender-AM-Default-Definitions-Package In prog.: Windows-Defender-AM-Default-Definitions-Package (en-US) >550 In prog.: Windows-Defender-AppLayer-Group-Package In prog.: Windows-Defender-AppLayer-Group-Package (en-US) >551 In prog.: Windows-Defender-ApplicationGuard-Inbox-Package In prog.: Windows-Defender-ApplicationGuard-Inbox-Package (en-US) >552 In prog.: Windows-Defender-ApplicationGuard-Inbox-WOW64-Package In prog.: Windows-Defender-ApplicationGuard-Inbox-WOW64-Package (en-US) >553 In prog.: Windows-Defender-Client-Package In prog.: Windows-Defender-Client-Package (en-US) >554 In prog.: Windows-Defender-Core-Group-Package In prog.: Windows-Defender-Core-Group-Package (en-US) >555 In prog.: Windows-Defender-Group-Policy-Package In prog.: Windows-Defender-Group-Policy-Package (en-US) >556 In prog.: Windows-Defender-Management-Group-Package In prog.: Windows-Defender-Management-Group-Package (en-US) >557 In prog.: Windows-Defender-Management-MDM-Group-Package In prog.: Windows-Defender-Management-MDM-Group-Package (en-US) >558 In prog.: Windows-Defender-Management-Powershell-Group-Package In prog.: Windows-Defender-Management-Powershell-Group-Package (en-US) >559 In prog.: Windows-Defender-Nis-Group-Package In prog.: Windows-Defender-Nis-Group-Package (en-US) > Work's for me. Update: installed packages Code: Microsoft Windows [Version 10.0.19041.572] (c) 2020 Microsoft Corporation. All rights reserved. C:\Windows\system32>dism /online /add-package /packagepath:C:\10.0.19041.1 Deployment Image Servicing and Management tool Version: 10.0.19041.572 Image Version: 10.0.19041.572 Processing 1 of 11 - Adding package Windows-Defender-AM-Default-Definitions-Package~31bf3856ad364e35~amd64~~10.0.19041.1 [==========================100.0%==========================] Processing 2 of 11 - Adding package Windows-Defender-AppLayer-Group-Package~31bf3856ad364e35~amd64~~10.0.19041.1 [==========================100.0%==========================] Processing 3 of 11 - Adding package Windows-Defender-ApplicationGuard-Inbox-Package~31bf3856ad364e35~amd64~~10.0.19041.1 [==========================100.0%==========================] Processing 4 of 11 - Adding package Windows-Defender-ApplicationGuard-Inbox-WOW64-Package~31bf3856ad364e35~amd64~~10.0.19041.1 [==========================100.0%==========================] Processing 5 of 11 - Adding package Windows-Defender-Client-Package~31bf3856ad364e35~amd64~~10.0.19041.1 [==========================100.0%==========================] Processing 6 of 11 - Adding package Windows-Defender-Core-Group-Package~31bf3856ad364e35~amd64~~10.0.19041.1 [==========================100.0%==========================] Processing 7 of 11 - Adding package Windows-Defender-Group-Policy-Package~31bf3856ad364e35~amd64~~10.0.19041.1 [==========================100.0%==========================] Processing 8 of 11 - Adding package Windows-Defender-Management-Group-Package~31bf3856ad364e35~amd64~~10.0.19041.1 [==========================100.0%==========================] Processing 9 of 11 - Adding package Windows-Defender-Management-MDM-Group-Package~31bf3856ad364e35~amd64~~10.0.19041.1 [==========================100.0%==========================] Processing 10 of 11 - Adding package Windows-Defender-Management-Powershell-Group-Package~31bf3856ad364e35~amd64~~10.0.19041.1 [==========================100.0%==========================] Processing 11 of 11 - Adding package Windows-Defender-Nis-Group-Package~31bf3856ad364e35~amd64~~10.0.19041.1 [==========================100.0%==========================] The operation completed successfully. C:\Windows\system32>dism /online /add-package /packagepath:C:\10.0.19041.1\en-US Deployment Image Servicing and Management tool Version: 10.0.19041.572 Image Version: 10.0.19041.572 Processing 1 of 11 - Adding package Windows-Defender-AM-Default-Definitions-Package~31bf3856ad364e35~amd64~en-US~10.0.19041.1 [==========================100.0%==========================] Processing 2 of 11 - Adding package Windows-Defender-AppLayer-Group-Package~31bf3856ad364e35~amd64~en-US~10.0.19041.1 [==========================100.0%==========================] Processing 3 of 11 - Adding package Windows-Defender-ApplicationGuard-Inbox-Package~31bf3856ad364e35~amd64~en-US~10.0.19041.1 [==========================100.0%==========================] Processing 4 of 11 - Adding package Windows-Defender-ApplicationGuard-Inbox-WOW64-Package~31bf3856ad364e35~amd64~en-US~10.0.19041.1 [==========================100.0%==========================] Processing 5 of 11 - Adding package Windows-Defender-Client-Package~31bf3856ad364e35~amd64~en-US~10.0.19041.1 [==========================100.0%==========================] Processing 6 of 11 - Adding package Windows-Defender-Core-Group-Package~31bf3856ad364e35~amd64~en-US~10.0.19041.1 [==========================100.0%==========================] Processing 7 of 11 - Adding package Windows-Defender-Group-Policy-Package~31bf3856ad364e35~amd64~en-US~10.0.19041.1 [==========================100.0%==========================] Processing 8 of 11 - Adding package Windows-Defender-Management-Group-Package~31bf3856ad364e35~amd64~en-US~10.0.19041.1 [==========================100.0%==========================] Processing 9 of 11 - Adding package Windows-Defender-Management-MDM-Group-Package~31bf3856ad364e35~amd64~en-US~10.0.19041.1 [==========================100.0%==========================] Processing 10 of 11 - Adding package Windows-Defender-Management-Powershell-Group-Package~31bf3856ad364e35~amd64~en-US~10.0.19041.1 [==========================100.0%==========================] Processing 11 of 11 - Adding package Windows-Defender-Nis-Group-Package~31bf3856ad364e35~amd64~en-US~10.0.19041.1 [==========================100.0%==========================] The operation completed successfully. C:\Windows\system32>
Yes, I agreed this is a good strategy for a long time. At the same time we are close to the moment when enthusiasts can make a modded image based on any rescent version even better than LTSC using modern hacky instruments. In the last Windows versions we have more relaxed limitations with removing Cortana, removing + switching to alternative Search, Start, AV, Browsers, etc. More alternative parts = more security/privacy.
Yes it's due to the left over of Windows Defender resource entries that's giving error, making changes to the removal program and will see how it works. For an experiment did checked with the DISM /Remove-Package for Defender removal on 64-bit Live system and tried to install the CU it failed. Will update the results with the ToolKitHelper program.
The Toolkit uses the same DISM to integrate updates without any changes and while applying the changes only the WinSXS temporary files which are safe are cleaned. DISM /Cleanup-Image with /ResetBase was having issues with W10 v1809 but with later versions it was working, though the MS disables it by default, The Toolkit also by default doesn't use the /ResetBase switch unless it's enabled in the Tweaks section. Starting from v1909 WinSxS files needs to be retained for installing updates due to new update format.
MSMG, Code: Reg add "HKLM\TK_SOFTWARE\Microsoft\Windows\CurrentVersion\DeliveryOptimization\Config" /v "DODownloadMode" /t REG_DWORD /d "0" /f >nul 2>&1 Reg add "HKLM\TK_SOFTWARE\Policies\Microsoft\Windows\DeliveryOptimization" /v "DODownloadMode" /t REG_DWORD /d "0" /f >nul 2>&1 These settings are added by O&O ShutUp10 Code: Reg add "HKLM\TK_SOFTWARE\Microsoft\Windows\CurrentVersion\DeliveryOptimization" /v "OptInOOBE" /t REG_DWORD /d "0" /f >nul 2>&1 Reg add "HKLM\TK_SOFTWARE\Policies\Microsoft\Windows\DeliveryOptimization" /v "DODownloadMode" /t REG_DWORD /d "0" /f >nul 2>&1 Reg add "HKLM\TK_SOFTWARE\Policies\Microsoft\Windows\DeliveryOptimization" /v "DODownloadMode" /t REG_DWORD /d "63" /f >nul 2>&1 What settings do I need to completely block Delivery Optimization, but for Windows updates to work? p.s I am using LTSC version!
Code: [HKEY_LOCAL_MACHINE\TK_SOFTWARE\Policies\Microsoft\Windows\DeliveryOptimization] "DODownloadMode"=dword:00000000
@MSMG If I understood your answer correctly and how things are connected, then I can imagine smth. like this after user selection: • Enable DISM Image Cleanup with Full ResetBase Code: Set how "Cleanup Source Images" works: whether /ResetBase switch will be used for WinSxS cleanup or not. Do you really want to switch DISM Image Cleanup to use Full ResetBase? | [Y]:Yes / [N]:No (recommended) WARNING: ----------------- Starting from v1909 WinSxS files needs to be retained for installing updates in the future due to new update format. The Toolkit doesn't use the /ResetBase switch by default. (My English is not perfect, sorry)
@MSMG hi, would it be possible for you to add support to remove the Delivery Optimization component and sub components? the components that allow you to download windows updates via peer to peer file shareing? thanks, Majid
With the reinstall of Defender, there are two lists offered. Would just like to confirm which I should be using. @Ace2 do single entries on your list actually include multiple entries from the @MSMG list?
MSMG, I still don’t understand if the components will recover after the update or not? Will you make any attempts to solve this problem? p.s I cannot have any guarantees that any other application will block more effectively than you!
I didn't see anything in the first post, so I'll ask: Does anyone have a list of all the safe-to-remove bloat that I can use to remove everything in batch? Right now I'm having to individually go from the main menu -> remove > windows components,etc > again and again But the software is able to read a text-file list (from somewhere...) and use that.
Sorry for being this ignorant, but... Why bother on removing things that will come back whenever you upgrade from WU? I'm still on v1809 for this matter. Thanks.