To Integrate Monthly Update Patch Into install.wim File or Not To Integrate

Hi all.

I wanted to integrate this month's KB5072033 into build 26200.7171 which I downloaded from Microsoft using MCT.

I went to Microsoft Update catalog and searched for KB5072033, the latest update package for 26200.xxxx build. Two .msu files appeared. One was KB5043080 and the other was KB5072033. I downloaded both.

I prepared a .bat file to apply both packages into install.wim file in order of release dates. Beforehand, I extracted the proper edition .wim file from the downloaded .esd file in the .iso.

When I ran the .bat file to integrate the packages, first KB5043080, I received an error. The error read: An error occurred applying the Unattend.xml file from the .msu package.

The following screenshot explains it all.



Then my .bat file continued to integrate the second .msu file. This package installed properly. It didn't complain about Unattend.xml file.

Can someone please explain why the KB5043080 file is not integrated into the .wim file, complaining about a mysterious Unattend.xml file ?

It is a mystery to me why Microsoft bundles KB5043080 file into every monthly patch uploaded to Microsoft Update catalog in spite of the fact that it doesn't install.

Of course, there are people that know how to use that .msu package and its contents inside. But they may also know they can find it when they need it.

Happy computing.

Just integrate the larger msu of the two. It will handle the smaller one.

Edit: The smaller update is a checkpoint cumulative update.

"To install the checkpoint(s) when servicing the Windows OS and WinPE, call Add-WindowsPackage with the target cumulative update. The folder from -PackagePath is used to discover and install one or more checkpoints as needed. Only the target cumulative update and checkpoint cumulative updates should be in the -PackagePath folder. Cumulative update packages with a revision <= the target cumulative update are processed."

Thank you for the concise explanation and the link to Microsoft document. I see better now.

If I understand correctly, even if I integrate a patch into an offline image, the patch may call other files from within the same folder or from MS servers when needed.

Thanks again.

This guide will teach you how to add the Windows updates to the Windows installation media so that you don't need to check for updates on each computer each time you make a fresh installation.

FreeBooter said:

This guide will teach you how to add the Windows updates to the Windows installation media so that you don't need to check for updates on each computer each time you make a fresh installation.

Click to expand...

Thanks for the video. That was basically what I was doing. But my issue was, Microsoft presents another .msu file along with the main monthly patch .msu file. In slipstreaming the main monthly patch .msu file, I didn't know what to do with the other .msu file. It was giving me the error and talking about an Unattend.xml file. The youtube video did not mention this.

@pseymour explained the situation.

Normally, the Windows.iso file I download from Microsoft should already have the smaller .msu file integrated in it if the Windows.iso file is released later than the release date of that smaller file, in this case KB5043080.

Under 24H2/25H2, the Checkpoint CU (KB5043080) is only required in the following cases:

The last two actions trigger a need to re-apply KB5043080, before adding the latest monthly CU.

If you're not adding LP's or playing around with FOD's, then the Checkpoint doesn't get involved. You can simply append the current CU (basically anything after Oct. 2024) without needing the Checkpoint. All current 24H2/25H2 MCT builds have the Checkpoint pre-installed.

For a better explanation:
Checkpoint cumulative updates and Microsoft Update Catalog usage

Thank you all. You are being very helpful about intricate sides of the Windows OS. It is honestly appreciated.