Integrating cumulative updates into the image

I have v1803 image, the most recent 17134.112 version.
I am trying to integrate the latest monthly cumulative update into the image, just like I was used to on Windows 7. With Win7, there were prerequisite updates that had to be applied first, but nothing is mentioned for the cumulative updates for Win 10, so I presume there are none.
It keeps failing though, and I can't figure out why.

This is the cmd output:

Code:

Processing 1 of 1 - Adding package d:\install\OS\Win10 updates\windows10.0-kb4346783-x64_145555faf4e3e494c20f22508f9c28fe12af387a.msu
[==========================100.0%==========================]
d:\install\OS\Win10 updates\windows10.0-kb4346783-x64_145555faf4e3e494c20f22508f9c28fe12af387a.msu: An error occurred applying the Unattend.xml file from the .msu package.
For more information, review the log file.
 Error: 0x800710fe

Error: 4350

This file is currently not available for use on this computer.

Looking through the DISM log, I can find stuff like this:
Extraction of file: update.ses failed because it is not present in the container (\\?\C:\TEMP\EF0AB51F-FF7A-4FA8-9C1E-32C6435F0BBB\Windows10.0-KB4346783-x64.CAB).
and possibly
Exec: Processing complete. Session: 4048_14798171, Package: Package_for_RollupFix~31bf3856ad364e35~amd64~~17134.254.1.2, Identifier: KB4346783 [HRESULT = 0x800710fe - ERROR_FILE_OFFLINE]


Googling the error messages brings no help at all.
Is there anyone else who does this sort of stuff who could help me out troubleshoot this?

Ha, I managed to figure it out - purely accidentally.
It turned out there IS a prerequisite to integrating this - it's called "servicing stack" and these KBs are released more or less along with the cumulative updates (sometimes like once per two CUs).
Of course, this is not explained anywhere (the connection and dependency).

The another catch is that when you try to integrate all this, you have to do it twice. WTF.
So you have to mount the image, do whatever customizations you have prepared, then integrate the servicing stack, THEN unmount and save the image, AND THEN mount it again and finally integrate the large update.

This is almost as annoying as booting into safe mode in Windows 10 compared to Windows 7.
just-pure-WTF

I prefer five lines of batch file rather than 500 of Powershell.

Octopuss said:

I prefer five lines of batch file rather than 500 of Powershell.

You are being disingenuous. There are only 3 lines of powershell that perform the operation - from @Kari's link :

Code:

Mount-WindowsImage -ImagePath $WimFolder\Sources\install.wim -Index $Index -Path $Mount
Add-WindowsPackage -Path $Mount -PackagePath $File.FullName
Dismount-WindowsImage -Path $Mount -Save

The rest is error checking, checking for existance of files/directories, prompting the user and so on. This is normal (or should be) in any script unless you want to hard code everything and assume it will work/everything exists without checking before and after.

Why don't you download from the catalogue and see if mount/apply/dismount works (either with powershell or dism - they are the same as powershell is just a wrapper).

My guess is you didn't download the file so only have the delta which would explain your "missing file" error.

Did you even read my post where I explain how I figured it out? I guess not.
It's working perfectly now.

sorry to bring this old thread back but using abbodi1406's W10UI batch script from here would be a lot easier when slipstreaming win10 updates onto usb install media, especially if that install media contains multiple editions that contain both home & pro.

I'd been quite busy creating updated/slipstreamed install media using his w10ui scripts