I still do not recommend to use the component removal for non en-GB/en-US source images until the support is added for them. Since Flash is a standalone update and the ToolKit doesn't cleanup the WinSxS folder for removed components, The WU offers the update.
Since Flash is a standalone update and the ToolKit doesn't cleanup the WinSxS folder for removed components, The WU offers the update.
That's because the ToolKitHelper.exe has been coded based upon the base image, updating the ToolKitHelper for every refreshed images is not worthy. Do integrate the latest updates to the base image after removing the components and there by you will have an lite and also updated image without any bugs or issues.
You may not see any errors but the updated component files/registry entries of the removed components will be still there, which may or may not give problems later.
Finished uploading the Windows 10 Redstone 5 Language Packs + Language Features Pack + WinPE Language Packs. Thanks to MDL members @roedel and @windows builder for providing mirrors for Windows 10 Redstone 5 Language Packs.
1) Use the vanilla Windows 10 Redstone 5 (10.0.17763.1) as the source image. 2) Remove Windows Components, Windows Apps, System Apps, Advanced Windows Components are same for all Editions except Enterprise (N) LTSC 2019. Do post the screenshot of the Menu you are getting.
thx for your great app. although i can't get a functional ltsc image with 9.0, same problem as jjxaker - after installing image i get the message 'setup could not configure windows to run on this computers hardware', (hints to oobe issue) despite vanilla en-en ltsc. my steps (on fully functional image made with 8.8 - 17763.165) cleanup. remove everything. integrate updates. cleanup. apply, rebuild. i've played around with different approaches like: cleanup, remove everything. cleanup. integrate. at second cleanup i get weird numbers no matter which way i try like install.wim: 27,9 % completion succesfull.
Will wait and see. I prefer some errors into event viewer than messing the registry. For the time being, I have installed a bunch of programs (non MS) on my 1809.134 lite, and no issue.
MSMG: would you knwo if removal in windows server is easier? i remember powershell was able to remove windows defender, but not windows 10. im strongly considering switching to server...
The same problem for me. Starting from version 8.7 to version 9.0 , I have never managed to use the image cropped with MSMG toolkit. Although i read the readme file millions of times and although i applied all steps correctly , it always gives the error 'setup could not configure windows to run on this computers hardware' I posted messages about this problem 2-3 times in this thread and still no answer and still no solution by MSMG and by others. Thank you
Hello MSMG, do you know if is there some instruction or guide to integrate the convenience rollup update package for windows 7 SP1, I have read in this topic but I have not found anything, thank you.
Good evening, I have a small observation regarding the v9.0, namely I can't remove anything from a Windows server 2019 datacenter install media as the option 4 (remove) from the main screen leads me into the sub-menu of option 5 (customize). How could it be? And if it is possible, how and where can I find these options? Thanks in advance.
Yes the fix will be available in next version. Now you can use the below commands to integrate the Store to image using the Administrator Command prompt under ToolKit folder, make sure you have downloaded the files from the download link and copied them to <Packs\Apps\W10> folder. Code: dism /image:mount\install /Add-ProvisionedAppxPackage /PackagePath:Packs\Apps\w10\Microsoft.DesktopAppInstaller_2018.720.2137.0_x86__8wekyb3d8bbwe.appxbundle /LicensePath:Packs\Apps\w10\Microsoft.DesktopAppInstaller_8wekyb3d8bbwe.xml /DependencyPackagePath:Packs\Apps\w10\Microsoft.NET.Native.Framework.1.6_1.6.24903.0_x86__8wekyb3d8bbwe.Appx /DependencyPackagePath:Packs\Apps\w10\Microsoft.NET.Native.Framework.1.6_1.6.24903.0_x64__8wekyb3d8bbwe.Appx /DependencyPackagePath:Packs\Apps\w10\Microsoft.NET.Native.Runtime.1.6_1.6.24903.0_x86__8wekyb3d8bbwe.Appx /DependencyPackagePath:Packs\Apps\w10\Microsoft.NET.Native.Runtime.1.6_1.6.24903.0_x64__8wekyb3d8bbwe.Appx /DependencyPackagePath:Packs\Apps\w10\Microsoft.VCLibs.140.00_14.0.26706.0_x86__8wekyb3d8bbwe.Appx /DependencyPackagePath:Packs\Apps\w10\Microsoft.VCLibs.140.00_14.0.26706.0_x64__8wekyb3d8bbwe.Appx dism /image:mount\install /Add-ProvisionedAppxPackage /PackagePath:Packs\Apps\w10\Microsoft.StorePurchaseApp_11809.1001.113.0_neutral_~_8wekyb3d8bbwe.AppxBundle /LicensePath:Packs\Apps\w10\Microsoft.StorePurchaseApp_8wekyb3d8bbwe.xml /DependencyPackagePath:Packs\Apps\w10\Microsoft.NET.Native.Framework.1.6_1.6.24903.0_x86__8wekyb3d8bbwe.Appx /DependencyPackagePath:Packs\Apps\w10\Microsoft.NET.Native.Framework.1.6_1.6.24903.0_x64__8wekyb3d8bbwe.Appx /DependencyPackagePath:Packs\Apps\w10\Microsoft.NET.Native.Runtime.1.6_1.6.24903.0_x86__8wekyb3d8bbwe.Appx /DependencyPackagePath:Packs\Apps\w10\Microsoft.NET.Native.Runtime.1.6_1.6.24903.0_x64__8wekyb3d8bbwe.Appx /DependencyPackagePath:Packs\Apps\w10\Microsoft.VCLibs.140.00_14.0.26706.0_x86__8wekyb3d8bbwe.Appx /DependencyPackagePath:Packs\Apps\w10\Microsoft.VCLibs.140.00_14.0.26706.0_x64__8wekyb3d8bbwe.Appx dism /image:mount\install /Add-ProvisionedAppxPackage /PackagePath:Packs\Apps\w10\Microsoft.WindowsStore_11810.1001.1213.0_neutral_~_8wekyb3d8bbwe.AppxBundle /LicensePath:Packs\Apps\w10\Microsoft.WindowsStore_8wekyb3d8bbwe.xml /DependencyPackagePath:Packs\Apps\w10\Microsoft.NET.Native.Framework.1.6_1.6.24903.0_x86__8wekyb3d8bbwe.Appx /DependencyPackagePath:Packs\Apps\w10\Microsoft.NET.Native.Framework.1.6_1.6.24903.0_x64__8wekyb3d8bbwe.Appx /DependencyPackagePath:Packs\Apps\w10\Microsoft.NET.Native.Runtime.1.6_1.6.24903.0_x86__8wekyb3d8bbwe.Appx /DependencyPackagePath:Packs\Apps\w10\Microsoft.NET.Native.Runtime.1.6_1.6.24903.0_x64__8wekyb3d8bbwe.Appx /DependencyPackagePath:Packs\Apps\w10\Microsoft.VCLibs.140.00_14.0.26706.0_x86__8wekyb3d8bbwe.Appx /DependencyPackagePath:Packs\Apps\w10\Microsoft.VCLibs.140.00_14.0.26706.0_x64__8wekyb3d8bbwe.Appx dism /image:mount\install /Add-ProvisionedAppxPackage /PackagePath:Packs\Apps\w10\Microsoft.XboxIdentityProvider_12.45.6001.0_neutral_~_8wekyb3d8bbwe.AppxBundle /LicensePath:Packs\Apps\w10\Microsoft.XboxIdentityProvider_8wekyb3d8bbwe.xml /DependencyPackagePath:Packs\Apps\w10\Microsoft.NET.Native.Framework.1.6_1.6.24903.0_x86__8wekyb3d8bbwe.Appx /DependencyPackagePath:Packs\Apps\w10\Microsoft.NET.Native.Framework.1.6_1.6.24903.0_x64__8wekyb3d8bbwe.Appx /DependencyPackagePath:Packs\Apps\w10\Microsoft.NET.Native.Runtime.1.6_1.6.24903.0_x86__8wekyb3d8bbwe.Appx /DependencyPackagePath:Packs\Apps\w10\Microsoft.NET.Native.Runtime.1.6_1.6.24903.0_x64__8wekyb3d8bbwe.Appx /DependencyPackagePath:Packs\Apps\w10\Microsoft.VCLibs.140.00_14.0.26706.0_x86__8wekyb3d8bbwe.Appx /DependencyPackagePath:Packs\Apps\w10\Microsoft.VCLibs.140.00_14.0.26706.0_x64__8wekyb3d8bbwe.Appx
I have tested the component removal in a specific order : Removed all Windows Apps Removed all System Apps Removed all Advanced Windows Components This way the OS get's installed and the WU installs the updates. But removing the components in random order sometimes may give errors due to some components sharing same files/registry entries, if you had removed the components in some specific order then do share the order so that I can identify the component that is breaking the OS. Since you have specified LTSC as the source image, I assume you are using the x64 build and so will test the same and report back. The image cleanup giving random numbers usually 20% on second and consecutive cleanup is normal and nothing to worry.
Be it Client or Sever, the manual method will use the same procedure, but still I haven't added the support for Sever. I don't know whether using the PowerShell, it will remove the Defender Security Center.
Yes it works with Windows 10 v1809 10.0.17763.1 en-GB/en-US source images without any bugs as far as I have tested.