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!
Why can't the clipboard work on WIN+V ?19041.208 Remove ToolKitHelper Mount AdobeFlashForWindows ToolKitHelper Mount CEIP_SQM ToolKitHelper Mount KernelDebugging ToolKitHelper Mount UnifiedTelemetryClient ToolKitHelper Mount WindowsInsiderHub ToolKitHelper Mount SecurityCenter ToolKitHelper Mount ContentDeliveryManager ToolKitHelper Mount EdgeDevToolsClient ToolKitHelper Mount Edge ToolKitHelper Mount MapControl ToolKitHelper Mount OneDrive ToolKitHelper Mount QuickAssist ToolKitHelper Mount WindowsMixedReality ToolKitHelper Mount WindowsReaderPDF ToolKitHelper Mount WindowsDefender ToolKitHelper Mount PPIProjection ToolKitHelper Mount XboxGameCallableUI ToolKitHelper Mount GameExplorer ToolKitHelper Mount FileExplorer ToolKitHelper Mount PeopleExperienceHost ToolKitHelper Mount 3DViewer ToolKitHelper Mount AdvertisingXaml ToolKitHelper Mount Alarms ToolKitHelper Mount BingWeather ToolKitHelper Mount Calculator ToolKitHelper Mount Camera ToolKitHelper Mount CommunicationsApps ToolKitHelper Mount DesktopAppInstaller ToolKitHelper Mount FeedbackHub ToolKitHelper Mount GetHelp ToolKitHelper Mount Getstarted ToolKitHelper Mount Maps ToolKitHelper Mount Messaging ToolKitHelper Mount MixedRealityPortal ToolKitHelper Mount OfficeHub ToolKitHelper Mount OfficeOneNote ToolKitHelper Mount OneConnect ToolKitHelper Mount Paint3D ToolKitHelper Mount People ToolKitHelper Mount Photos ToolKitHelper Mount Print3D ToolKitHelper Mount ScreenSketch ToolKitHelper Mount SkypeApp ToolKitHelper Mount SolitaireCollection ToolKitHelper Mount SoundRecorder ToolKitHelper Mount StickyNotes ToolKitHelper Mount WalletService ToolKitHelper Mount XboxApp ToolKitHelper Mount XboxIdentityProvider ToolKitHelper Mount YourPhone ToolKitHelper Mount ZuneMusic ToolKitHelper Mount ZuneVideo
@MSMG Forgive my very brief post, am very quickly testing 20H2 with ToolKit v10.6. This is my normal removal list: Spoiler: RemovePkgsList.txt GameExplorer MapControl OneDrive PeopleExperienceHost RetailDemoContent SecureAssessmentBrowser SkypeORTC WindowsMixedReality XboxGameCallableUI 3DViewer AdvertisingXaml Alarms BingWeather Calculator Camera CommunicationsApps Cortana DesktopAppInstaller FeedbackHub GetHelp Getstarted HEIFImageExtension Maps MixedRealityPortal OfficeHub OfficeOneNote Paint3D People Photos ScreenSketch SkypeApp SolitaireCollection SoundRecorder StickyNotes VP9VideoExtensions WalletService WebMediaExtensions WebpImageExtensions WindowsStore XboxApp XboxIdentityProvider YourPhone ZuneMusic ZuneVideo I get the message "The specified component has already been removed..." for the following components (if the ToolKitHelper.exe follows the order that my list is in): Spoiler: The specified component has already been removed... 3DViewer Alarms BingWeather Calculator Camera CommunicationsApps Cortana DesktopAppInstaller FeedbackHub GetHelp Getstarted HEIFImageExtension Maps MixedRealityPortal OfficeHub OfficeOneNote Paint3D People Photos ScreenSketch SkypeApp SolitaireCollection SoundRecorder StickyNotes VP9VideoExtensions WalletService WebMediaExtensions WebpImageExtensions XboxIdentityProvider YourPhone ZuneMusic ZuneVideo Have names for these changed, or does the ToolKitHelper.exe just need a small update to completely support 20H2? Files used, including those used to create my single edition ISO: ESD Decrypter: esd-decrypter-wimlib-56.7z x86 ESD: 19042.572.201009-1947.20h2_release_svc_refresh_CLIENTBUSINESS_VOL_x86FRE_en-gb.esd x86 ISO: 19042.572.201009-2202.20H2_RELEASE_SVC_REFRESH_CLIENTENTERPRISE_VOL_X86FRE_EN-GB.ISO x64 ESD: 19042.572.201009-1947.20h2_release_svc_refresh_CLIENTBUSINESS_VOL_x64FRE_en-gb.esd x64 ISO: 19042.572.201009-2225.20H2_RELEASE_SVC_REFRESH_CLIENTENTERPRISE_VOL_X64FRE_EN-GB.ISO Please note: I have only tested with x86 so far, not had time to do x64.
question, is v1809 the best to stay on, so components won't get restored by windows updates? and will v1809 have a clean sfc scan after removing everything?
Right now the option to remove language packs or set the image default language have not been added yet so you can manually run these commands from command prompt when the image is mounted using the Toolkit. To remove a language pack from boot.wim and install.wim Code: DISM /Image:Mount\Boot\1 /Remove-Package /PackageName:<Language-Pack-Name> DISM /Image:Mount\Boot\2 /Remove-Package /PackageName:<Language-Pack-Name> DISM /Image:Mount\Install\<Index-No> /Remove-Package /PackageName:<Language-Pack-Name> To set the image default language to boot.wim Code: DISM /Image:Mount\Boot\1 /Set-InputLocale:<Language-Locale-Code> DISM /Image:Mount\Boot\1 /Set-UILangFallback:<Language-Locale-Code> DISM /Image:Mount\Boot\1 /Gen-LangINI /Distribution:DVD DISM /Image:Mount\Boot\2 /Set-InputLocale:<Language-Locale-Code> DISM /Image:Mount\Boot\2 /Set-UILangFallback:<Language-Locale-Code> DISM /Image:Mount\Boot\2 /Gen-LangINI /Distribution:DVD To set the image default language to install.wim Code: DISM /Image:Mount\Install\<Index-No> /Set-InputLocale:<Language-Locale-Code> DISM /Image:Mount\Install\<Index-No> /Set-UILangFallback:<Language-Locale-Code> DISM /Image:Mount\Install\<Index-No> /Gen-LangINI /Distribution:DVD Run the commands from the Toolkit folder using Command prompt, do change the <Index-No>, <Language-Pack-Name> and <Language-Locale-Code> to your needs.
Did you added the supported CU to 19041.208 image? try retaining UnifiedTelemetryClient and see if the clipboard works.
No names have been changed, will check with this issue once I do complete the fix for removing left-over resources entries in component removal.
Lately the component removal for v1809 was updated to support images with updates and some non English resource entries are left-out which needs a fix to avoid SFC errors. Yes v1809 is best build to avoid components getting restored.