@ MSMG thank you so much for Toolkit version 9.4.2 it is just awesome! There was absolutely no mistake with this my last job adding / removing the necessary; i couldn't be happier can believe deep down my heart again i just have to say congratulations for your endless dedication and love for everything you do here at MDL
Good morning. I ask for confirmation, the cumulative updates downloaded from Microsoft Update Catalog in which Toolkit folder should be entered? Thanks
@MSMG - Sir, there is no template to add to EnableFeaturesList.txt and DisableFeaturesList.txt. I also checked the main archive folder and there is no template to add the entries to the text files. Can i use the same RemovePkgsList.txt which was prepared for toolkit v9.4.1 under 9.4.2 ? If i remove the non-english cab files for DotNetFx and place only the english related files in packs folder for integration will it work ? Thanks.
@MSMG - Sir, toolkit 9.4.2 doesn't support WIN 8.1 ?. Since there is removepkglist template for WIN 8.1, i tried the toolkit with 9.4.2, but when attempting to remove components i get error that support for WIN 8.1 is available with toolkit v8.8 only.
Just check in ToolKit's <WHD\w10\x64> folder, you will find the folder for each updates. I'm planning to merge Windows Update and WHD Updates in future to simply the process.
Yes there are no templates for Features, since the features differ for each OS and with client/server builds. Users need to add the features names they wish to disable/enable. Yes you can use the RemovePkgsList.txt entries from v9.4.1. If you don't need the language packs for NETFX 48, then download them, just copy only the required cab files, the ToolKit will integrate them.
I have remove Insider Hub, but... Spoiler Did not integrate cumulative update and uninstall all applications and components. After installing the system, I completely denied access to the WinSxS folder and when we try to install the update we get an error: Spoiler
You could make list generators so people can see what they have: Under [8] Tools Add [4] Generate Lists with individual options for each and the last option being All of them. [1] Features [2] Packages [3] Provisioned Apps [4] Drivers [5] Capabilities [6] All Code: Echo -------------------------------------------------------------------------------- Echo "Listing Packages/Apps" Echo -------------------------------------------------------------------------------- "%DISMX64% /Image:%MOUNT% /Get-Packages /Format:Table>"%BUILD%\10 Build\10 Features\Pre-Packages.txt" "%DISMX64% /Image:%MOUNT% /Get-Features /Format:Table>"%BUILD%\10 Build\10 Features\Pre-Features.txt" "%DISMX64% /Image:%MOUNT% /Get-ProvisionedAppxPackages /Format:Table>"%BUILD%\10 Build\10 Features\Pre-ProvisionedAppx.txt" "%DISMX64% /Image:%MOUNT% /Get-Drivers>"%BUILD%\10 Build\10 Features\Pre-Drivers.txt" "%DISMX64% /Image:%MOUNT% /Get-Capabilities /Format:Table>"%BUILD%\10 Build\10 Features\Pre-Capabilities.txt"
Currently testing other things and removal of WindowsApps does not appear to work. Spoiler: Remove Windows Components Using Package List =============================================================================== MSMG ToolKit - Remove Windows Components Using Package List =============================================================================== ------------------------------------------------------------------------------- ####Starting Removing Windows Components Using Package List#################### ------------------------------------------------------------------------------- Image : Install.wim Image Index : 1 Image Architecture : x86 Image Version : 10.0.18362.30.0 Image Edition : Enterprise Image Default Language : en-GB ------------------------------------------------------------------------------- ####Removing Windows Components Using Package List############################# ------------------------------------------------------------------------------- ------------------------------------------------------------------------------- Removing WindowsApps Package... ------------------------------------------------------------------------------- The specified package has already been removed... ------------------------------------------------------------------------------- ####Finished Removing Windows Components Using Package List#################### ------------------------------------------------------------------------------- =============================================================================== I had hoped to remove Remove all metro apps (4 > 1 > 7 > 8) from my existing method by adding WindowsApps to RemovePkgsList.txt.
Those are two different things. For metro apps, you should use RemoveAppsList.txt, not package list. Cheers.
Having peeked around a bit in the appmanifest. Windows Camera: Code: <Dependencies> <TargetDeviceFamily Name="Windows.Desktop" MinVersion="10.0.17134.0" MaxVersionTested="10.0.17663.0" /> <PackageDependency Name="Microsoft.NET.Native.Framework.2.2" MinVersion="2.2.27011.0" Publisher="CN=Microsoft Corporation, O=Microsoft Corporation, L=Redmond, S=Washington, C=US" /> <PackageDependency Name="Microsoft.NET.Native.Runtime.2.2" MinVersion="2.2.27011.0" Publisher="CN=Microsoft Corporation, O=Microsoft Corporation, L=Redmond, S=Washington, C=US" /> <PackageDependency Name="Microsoft.VCLibs.140.00" MinVersion="14.0.26706.0" Publisher="CN=Microsoft Corporation, O=Microsoft Corporation, L=Redmond, S=Washington, C=US" /> </Dependencies> Windows Alarms: Code: <Dependencies> <TargetDeviceFamily Name="Windows.Universal" MinVersion="10.0.17134.0" MaxVersionTested="10.0.17763.0"/> <PackageDependency Name="Microsoft.UI.Xaml.2.1" MinVersion="2.11904.5004.0" Publisher="CN=Microsoft Corporation, O=Microsoft Corporation, L=Redmond, S=Washington, C=US"/> <PackageDependency Name="Microsoft.VCLibs.140.00" MinVersion="14.0.26706.0" Publisher="CN=Microsoft Corporation, O=Microsoft Corporation, L=Redmond, S=Washington, C=US"/> </Dependencies> Store: Code: <Dependencies> <TargetDeviceFamily Name="Windows.Universal" MinVersion="10.0.14393.0" MaxVersionTested="10.0.17749.0"/> <TargetDeviceFamily Name="Windows.Holographic" MinVersion="10.0.14393.0" MaxVersionTested="10.0.14393.0"/> <PackageDependency Name="Microsoft.NET.Native.Framework.1.7" MinVersion="1.7.25531.0" Publisher="CN=Microsoft Corporation, O=Microsoft Corporation, L=Redmond, S=Washington, C=US"/> <PackageDependency Name="Microsoft.NET.Native.Runtime.1.7" MinVersion="1.7.25531.0" Publisher="CN=Microsoft Corporation, O=Microsoft Corporation, L=Redmond, S=Washington, C=US"/> <PackageDependency Name="Microsoft.VCLibs.140.00" MinVersion="14.0.24123.0" Publisher="CN=Microsoft Corporation, O=Microsoft Corporation, L=Redmond, S=Washington, C=US"/> </Dependencies> DesktopAppInstaller: Code: <Dependencies> <TargetDeviceFamily Name="Windows.Universal" MinVersion="10.0.14393.0" MaxVersionTested="10.0.18307.0"/> <PackageDependency Name="Microsoft.VCLibs.140.00.UWPDesktop" MinVersion="14.0.25426.0" Publisher="CN=Microsoft Corporation, O=Microsoft Corporation, L=Redmond, S=Washington, C=US"/> <PackageDependency Name="Microsoft.VCLibs.140.00" MinVersion="14.0.26706.0" Publisher="CN=Microsoft Corporation, O=Microsoft Corporation, L=Redmond, S=Washington, C=US"/> </Dependencies> So, it seems some apps can be used even on 1607 (LTSB). Others can be used from 1803 onwards. And the Adguard site is right about offering a s**tload of dependencies. Strangly, I did include the dependencies for Windows Alarms and Clock, but it wouldn't work until I updated from Store. Cheers.