@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.
I have mounted source from DVD folder Integrated Language Pack to both images in boot.wim and 7 images in install.wim What is a correct procedure to remove original language pack? 1) Ideally script to remove packages 2) Commands to set default new one - /Set-UILangFallback, /Set-UILang/Gen-LangINI /Set-InputLocale in boot.wim and install.wim? Anyone done the task? MSMG 10.7beta, 19041 image
@Yanta These are the packages removed when Defender is removed from W10 v1809/LTSC2019 Code: Microsoft-OneCoreUAP-AppRuntime-RemoteAppLifetimeManager-Package~31bf3856ad364e35~amd64~~10.0.17763.1 Microsoft-Windows-HVSI-Components-Package~31bf3856ad364e35~amd64~~10.0.17763.1 Microsoft-Windows-HVSI-Components-WOW64-Package~31bf3856ad364e35~amd64~~10.0.17763.1 Microsoft-Windows-HVSI-Package~31bf3856ad364e35~amd64~~10.0.17763.1 Microsoft-Windows-HVSI-WOW64-Package~31bf3856ad364e35~amd64~~10.0.17763.1 Microsoft-Windows-SenseClient-amcore-Package~31bf3856ad364e35~amd64~~10.0.17763.1 Microsoft-Windows-SenseClient-onecore-Package~31bf3856ad364e35~amd64~~10.0.17763.1 Microsoft-Windows-SenseClient-Package~31bf3856ad364e35~amd64~~10.0.17763.1 Windows-Defender-AM-Default-Definitions-Package~31bf3856ad364e35~amd64~~10.0.17763.1 Windows-Defender-AppLayer-Group-Package~31bf3856ad364e35~amd64~~10.0.17763.1 Windows-Defender-ApplicationGuard-Inbox-Package~31bf3856ad364e35~amd64~~10.0.17763.1 Windows-Defender-Client-Package~31bf3856ad364e35~amd64~~10.0.17763.1 Windows-Defender-Core-Group-amcore-Package~31bf3856ad364e35~amd64~~10.0.17763.1 Windows-Defender-Core-Group-onecore-Package~31bf3856ad364e35~amd64~~10.0.17763.1 Windows-Defender-Core-Group-Package~31bf3856ad364e35~amd64~~10.0.17763.1 Windows-Defender-Group-Policy-Package~31bf3856ad364e35~amd64~~10.0.17763.1 Windows-Defender-Management-Group-amcore-Package~31bf3856ad364e35~amd64~~10.0.17763.1 Windows-Defender-Management-Group-onecore-Package~31bf3856ad364e35~amd64~~10.0.17763.1 Windows-Defender-Management-Group-Package~31bf3856ad364e35~amd64~~10.0.17763.1 Windows-Defender-Management-MDM-Group-Package~31bf3856ad364e35~amd64~~10.0.17763.1 Windows-Defender-Management-Powershell-Group-Package~31bf3856ad364e35~amd64~~10.0.17763.1 Windows-Defender-Nis-Group-Package~31bf3856ad364e35~amd64~~10.0.17763.1 Microsoft-OneCoreUAP-AppRuntime-RemoteAppLifetimeManager-Package~31bf3856ad364e35~amd64~en-US~10.0.17763.1 Microsoft-Windows-HVSI-Components-Package~31bf3856ad364e35~amd64~en-US~10.0.17763.1 Microsoft-Windows-HVSI-Components-WOW64-Package~31bf3856ad364e35~amd64~en-US~10.0.17763.1 Microsoft-Windows-HVSI-Package~31bf3856ad364e35~amd64~en-US~10.0.17763.1 Microsoft-Windows-HVSI-WOW64-Package~31bf3856ad364e35~amd64~en-US~10.0.17763.1 Microsoft-Windows-SenseClient-amcore-Package~31bf3856ad364e35~amd64~en-US~10.0.17763.1 Microsoft-Windows-SenseClient-onecore-Package~31bf3856ad364e35~amd64~en-US~10.0.17763.1 Microsoft-Windows-SenseClient-Package~31bf3856ad364e35~amd64~en-US~10.0.17763.1 Windows-Defender-AM-Default-Definitions-Package~31bf3856ad364e35~amd64~en-US~10.0.17763.1 Windows-Defender-AppLayer-Group-Package~31bf3856ad364e35~amd64~en-US~10.0.17763.1 Windows-Defender-ApplicationGuard-Inbox-Package~31bf3856ad364e35~amd64~en-US~10.0.17763.1 Windows-Defender-Client-Package~31bf3856ad364e35~amd64~en-US~10.0.17763.1 Windows-Defender-Core-Group-amcore-Package~31bf3856ad364e35~amd64~en-US~10.0.17763.1 Windows-Defender-Core-Group-onecore-Package~31bf3856ad364e35~amd64~en-US~10.0.17763.1 Windows-Defender-Core-Group-Package~31bf3856ad364e35~amd64~en-US~10.0.17763.1 Windows-Defender-Group-Policy-Package~31bf3856ad364e35~amd64~en-US~10.0.17763.1 Windows-Defender-Management-Group-amcore-Package~31bf3856ad364e35~amd64~en-US~10.0.17763.1 Windows-Defender-Management-Group-onecore-Package~31bf3856ad364e35~amd64~en-US~10.0.17763.1 Windows-Defender-Management-Group-Package~31bf3856ad364e35~amd64~en-US~10.0.17763.1 Windows-Defender-Management-MDM-Group-Package~31bf3856ad364e35~amd64~en-US~10.0.17763.1 Windows-Defender-Management-Powershell-Group-Package~31bf3856ad364e35~amd64~en-US~10.0.17763.1 Windows-Defender-Nis-Group-Package~31bf3856ad364e35~amd64~en-US~10.0.17763.1 For Integration only the parent package needs to be captured and all its sub-packages are included with the parent packages, so these are the packages required to integrate Windows Defender to W10 v1809/LTSC2019 Code: Microsoft-Windows-HVSI-Package~31bf3856ad364e35~amd64~~10.0.17763.1 Microsoft-Windows-HVSI-Package~31bf3856ad364e35~amd64~en-US~10.0.17763.1 Microsoft-Windows-HVSI-WOW64-Package~31bf3856ad364e35~amd64~~10.0.17763.1 Microsoft-Windows-HVSI-WOW64-Package~31bf3856ad364e35~amd64~en-US~10.0.17763.1 Microsoft-Windows-SenseClient-Package~31bf3856ad364e35~amd64~~10.0.17763.1 Microsoft-Windows-SenseClient-Package~31bf3856ad364e35~amd64~en-US~10.0.17763.1 Windows-Defender-ApplicationGuard-Inbox-Package~31bf3856ad364e35~amd64~~10.0.17763.1 Windows-Defender-ApplicationGuard-Inbox-Package~31bf3856ad364e35~amd64~en-US~10.0.17763.1 Windows-Defender-Client-Package~31bf3856ad364e35~amd64~~10.0.17763.1 Windows-Defender-Client-Package~31bf3856ad364e35~amd64~en-US~10.0.17763.1 Windows-Defender-Group-Policy-Package~31bf3856ad364e35~amd64~~10.0.17763.1 Windows-Defender-Group-Policy-Package~31bf3856ad364e35~amd64~en-US~10.0.17763.1 It's around 181 MB Here's the command to integrate the packages Code: DISM /Image:<Mount-Folder> /Add-Package /PackagePath:Windows-Defender-Client-Package~31bf3856ad364e35~amd64~~10.0.17763.1.cab /PackagePath:Windows-Defender-Client-Package~31bf3856ad364e35~amd64~en-US~10.0.17763.1.cab /PackagePath:Windows-Defender-Group-Policy-Package~31bf3856ad364e35~amd64~~10.0.17763.1.cab /PackagePath:Windows-Defender-Group-Policy-Package~31bf3856ad364e35~amd64~en-US~10.0.17763.1.cab /PackagePath:Microsoft-Windows-HVSI-Package~31bf3856ad364e35~amd64~~10.0.17763.1.cab /PackagePath:Microsoft-Windows-HVSI-Package~31bf3856ad364e35~amd64~en-US~10.0.17763.1.cab /PackagePath:Microsoft-Windows-HVSI-WOW64-Package~31bf3856ad364e35~amd64~~10.0.17763.1.cab /PackagePath:Microsoft-Windows-HVSI-WOW64-Package~31bf3856ad364e35~amd64~en-US~10.0.17763.1.cab /PackagePath:Microsoft-Windows-SenseClient-Package~31bf3856ad364e35~amd64~~10.0.17763.1.cab /PackagePath:Microsoft-Windows-SenseClient-Package~31bf3856ad364e35~amd64~en-US~10.0.17763.1.cab /PackagePath:Windows-Defender-ApplicationGuard-Inbox-Package~31bf3856ad364e35~amd64~~10.0.17763.1.cab /PackagePath:Windows-Defender-ApplicationGuard-Inbox-Package~31bf3856ad364e35~amd64~en-US~10.0.17763.1.cab Windows Security Center UI is a central app for all security related components like Defender, SmartScreen, Firewall, Parental Controls, Will get-back to you with how to restore the Windows Security Center UI (Microsoft.Windows.SecHealthUI_cw5n1h2txyewy) System App.
It's due to the new update system the components do return back, experimenting various methods to fix it, will update when there's a progress in the test.
Okay. When will new methods of cheating the system appear? The question is even more pressing because they have started to promote their garbage ads (apps) more aggressively! The demand is extremely high!