We would like to create a Windows 10 1709 image that contains additional language packs. When looking at the documentation for servicing the InBox Apps for Windows 10 1703, there is the following note:
“Note: Starting with Windows 10, version 1703, app bundles contain only dependency packages that pertain to the app. You don't have to check the prov.xml to see which dependencies to install. Install all dependency packages found in the app's folder.”
There is then the following example (for 64-bit):
DISM /image:c:\mount\windows /add-ProvisionedAppxPackage /packagepath:e:\apps\amd64\Microsoft.3DBuilder_8wekyb3d8bbwe.appxbundle /licensepath:e:\apps\amd64\Microsoft.3DBuilder_8wekyb3d8bbwe.xml /dependencypackagepath:e:\apps\amd64\Microsoft.VCLibs.x64.14.00.appx /dependencypackagepath:e:\apps\amd64\Microsoft.VCLibs.x86.14.00.appx
However, in the DVD image for the Inbox Apps for 1709 (X21-50436), there are 33 apps all in one folder (amd64fre) with 18 dependency packages. The example above only installs 2 of the 18 dependency packages available. 3D Builder does not even appear to be one of the In-Box Apps in 1709 (or the name has changed significantly). How do we know what dependency packages should be installed for the 33 apps listed in the In-Box App DVD ?
With 1507 and 1511, the dependencies were defined in an XML file, for 1607, a batch file was posted on the Microsoft website. For 1703, we were told to use the Express Deployment Tool to service the In-Box Apps, but EDT does not support 1709. Needless to say the process appears to have changed with almost every release of Windows 10. Is this something OEMs should expect with every release
of Windows 10 ?
Regards,
Jimmy Griffith
