I'm having a hard time in making my customized Windows 10 image. The goal is to start from an original Windows 10 IoT Enterprise 2016 LTSB image, then add some cumulative updates.
I've added the following updates to the Workbench:
Please note that the order is very important here. To apply the RollupFix (last row), the KB4521858 must be installed first, otherwhise I receive the error " The specified package cannot be added to this Windows Image due to a version
mismatch.". Tested manually on a virtual machine.
The problem is that once I start the deployment, the OS is installed first, then it creates the unattend.xml file and starts the "Apply Updates" phase, then the error still occurs.
The logfile (no package name is reported though)
<![LOG[Command has been started (process ID 2576)]LOG]!><time="17:27:42.000+000" date="10-10-2019" component="LTIApply" context="" type="1" thread="" file="LTIApply"><![LOG[ Console > Deployment Image Servicing and Management tool]LOG]!><time="17:27:42.000+000" date="10-10-2019" component="LTIApply" context="" type="1" thread="" file="LTIApply"><![LOG[ Console > Version: 10.0.17763.1]LOG]!><time="17:27:42.000+000" date="10-10-2019" component="LTIApply" context="" type="1" thread="" file="LTIApply"><![LOG[ Console > Image Version: 10.0.14393.0]LOG]!><time="17:27:46.000+000" date="10-10-2019" component="LTIApply" context="" type="1" thread="" file="LTIApply"><![LOG[ Console > Error: 0x800f0823]LOG]!><time="17:28:10.000+000" date="10-10-2019" component="LTIApply" context="" type="1" thread="" file="LTIApply"><![LOG[ Console > The specified package cannot be added to this Windows Image due to a version mismatch. ]LOG]!><time="17:28:10.000+000" date="10-10-2019" component="LTIApply" context="" type="1" thread="" file="LTIApply"><![LOG[ Console > Update the Windows image and try the operation again.]LOG]!><time="17:28:10.000+000" date="10-10-2019" component="LTIApply" context="" type="1" thread="" file="LTIApply"><![LOG[ Console > The DISM log file can be found at X:\windows\Logs\DISM\dism.log]LOG]!><time="17:28:10.000+000" date="10-10-2019" component="LTIApply" context="" type="1" thread="" file="LTIApply"><![LOG[Return code from command = -2146498525]LOG]!><time="17:28:10.000+000" date="10-10-2019" component="LTIApply" context="" type="1" thread="" file="LTIApply"><![LOG[FAILURE ( 5627 ): -2146498525 0x800F0823: Run DISM.exe]LOG]!><time="17:28:10.000+000" date="10-10-2019" component="LTIApply" context="" type="3" thread="" file="LTIApply">
So I believe the order is still not maintained and the RollupFix starts first. I've retrieved the generated unattend.xml file and the order of the <packages> section seems ok:
<package action="install"><assemblyIdentity name="Package_for_KB4494175" version="10.0.3.0" processorArchitecture="amd64" publicKeyToken="31bf3856ad364e35" language="neutral"></assemblyIdentity><source location="F:\Deploy\Packages\Update\amd64_Package_for_KB4494175_10.0.3.0_neutral_31bf3856ad364e35_\Windows10.0-KB4494175-v3-x64.cab"></source></package><package action="install"><assemblyIdentity name="Package_for_KB4516115" version="10.0.1.2" processorArchitecture="amd64" publicKeyToken="31bf3856ad364e35" language="neutral"></assemblyIdentity><source location="F:\Deploy\Packages\SecurityUpdate\amd64_Package_for_KB4516115_10.0.1.2_neutral_31bf3856ad364e35_\Windows10.0-KB4516115-x64.cab"></source></package><package action="install"><assemblyIdentity name="Package_for_KB4521858" version="14393.3262.1.0" processorArchitecture="amd64" publicKeyToken="31bf3856ad364e35" language="neutral"></assemblyIdentity><source location="F:\Deploy\Packages\SecurityUpdate\amd64_Package_for_KB4521858_14393.3262.1.0_neutral_31bf3856ad364e35_\Windows10.0-KB4521858-x64.cab"></source></package><package action="install"><assemblyIdentity name="Package_for_RollupFix" version="14393.3274.1.9" processorArchitecture="amd64" publicKeyToken="31bf3856ad364e35" language="neutral"></assemblyIdentity><source location="F:\Deploy\Packages\SecurityUpdate\amd64_Package_for_RollupFix_14393.3274.1.9_neutral_31bf3856ad364e35_\Windows10.0-KB4519998-x64.cab"></source></package>
Again, if I install the base OS on a virtual machine, then manually install the packages in that order, everything goes fine.
Is there a reason for this?
Alessandro Francesconi http://www.alessandrofrancesconi.it