Integrating Setup DU KB5047134 into Windows Setup: Missing from boot.wim
- Thread starter Lakitna
- Start date
Setup Dynamic Update is a complicated KB, it needs to update files in boot.wim, install.wim and the Windows ISO.
When NTLite applies Setup DU, it knows all the internal steps in order to proceed. There's actually a ridiculously long chart from MS docs on how this works manually. All the steps are followed, so Setup DU doesn't need to be separately integrated at the same time to boot.wim.
In fact, the general answer is you don't need to apply Integrate - Updates to boot.wim. Mostly any required Drivers. If you're using the HW bypasses, then you must apply Configure - Settings to boot.wim, if you want to process both images in a single pass.
Update Windows installation media
When NTLite applies Setup DU, it knows all the internal steps in order to proceed. There's actually a ridiculously long chart from MS docs on how this works manually. All the steps are followed, so Setup DU doesn't need to be separately integrated at the same time to boot.wim.
In fact, the general answer is you don't need to apply Integrate - Updates to boot.wim. Mostly any required Drivers. If you're using the HW bypasses, then you must apply Configure - Settings to boot.wim, if you want to process both images in a single pass.
Update Windows installation media
| Task | WinRE (winre.wim) | Operating system (install.wim) | WinPE (boot.wim) | New media |
|---|---|---|---|---|
| Add servicing stack Dynamic Update | 1 | 9 | 17 | |
| Add language pack | 2 | 10 | 18 | |
| Add localized optional packages | 3 | 19 | ||
| Add font support | 4 | 20 | ||
| Add text-to-speech | 5 | 21 | ||
| Update Lang.ini | 22 | |||
| Add Features on Demand | 11 | |||
| Add Safe OS Dynamic Update | 6 | |||
| Add Setup Dynamic Update | 26 | |||
| Add setup.exe and setuphost.exe from WinPE | 27 | |||
| Add boot manager from WinPE | 28 | |||
| Add latest cumulative update | 12 | 23 | ||
| Clean up the image | 7 | 13 | 24 | |
| Add Optional Components | 14 | |||
| Add .NET and .NET cumulative updates | 15 | |||
| Export image | 8 | 16 | 25 |
- Messages
- 3,944
- Reaction score
- 1,649
The Dynamic update is for the entire ISO, thus it's targeting only the main image.
It is true that the process actually mounts the boot.wim as well and updates it.
Will think about moving it visually to the boot.wim, good point.
Hi guys, thanks for the clarifications!
Even after applying the changes and creating a new image, the KB5047134 update keeps coming back when I load the image again. This makes me wonder if there's something I'm missing or a specific step required to fully incorporate this update.
From what I understand:
Appreciate any insights, especially if there’s a specific setting or workflow tweak I should follow!
Even after applying the changes and creating a new image, the KB5047134 update keeps coming back when I load the image again. This makes me wonder if there's something I'm missing or a specific step required to fully incorporate this update.
From what I understand:
- Setup Dynamic Update targets the entire ISO and requires updating files in boot.wim, install.wim, and possibly other parts of the image.
- Tools like NTLite automate the internal steps, so updates to boot.wim don’t need to be manually applied.
- The update isn't fully applied during the process?
- Some files or dependencies from the update aren’t properly integrated into boot.wim or install.wim?
Appreciate any insights, especially if there’s a specific setting or workflow tweak I should follow!
- Messages
- 3,944
- Reaction score
- 1,649
Setup Dynamic Update existing version detection is not there, indeed.
You can confirm it's applied by looking inside the CAB file of it, and compare files to those in .\Sources dir.
Tool also updates boot.wim, so make sure not to mix and match boot.wim after the update process, keep them together.
Since the setup dynamic update is a special type of an update, it's just a bunch of files to be copied to the image, it's not easy to detect versioning.
It's not always the same combination of files to begin with.
Tool would need to compare all files from the update, making it resource intensive and unnecessary.
It's all done by Microsoft instructions here.
TLDR: it's just a bunch of files to be copied, not a normal package to be integrated with DISM.
Here’s a response you can use that acknowledges their explanation and politely asks for guidance regarding .exe updates:
Thank you for the detailed explanation!
It makes sense now why Setup Dynamic Updates like KB5047134 are handled differently, I’ll make sure to double-check the extracted CAB files and compare them with the .Sources directory, as well as ensure the updated boot.wim and install.wim stay in sync.
I appreciate the clarification!
I do have a follow-up question about integrating .exe updates, such as:
How would I go about properly incorporating these into a Windows ISO or setup? Are there any special steps or considerations for .exe updates compared to CAB files?
Thank you again for the guidance.
This keeps the tone friendly and understanding while requesting clear guidance on the next steps for .exe files.
Thank you for the detailed explanation!
It makes sense now why Setup Dynamic Updates like KB5047134 are handled differently, I’ll make sure to double-check the extracted CAB files and compare them with the .Sources directory, as well as ensure the updated boot.wim and install.wim stay in sync.
I appreciate the clarification!
I do have a follow-up question about integrating .exe updates, such as:
How would I go about properly incorporating these into a Windows ISO or setup? Are there any special steps or considerations for .exe updates compared to CAB files?
Thank you again for the guidance.
This keeps the tone friendly and understanding while requesting clear guidance on the next steps for .exe files.
KB5047486 can be replaced by the normal .NET 6 offline installer. Same software, but in a different package format.
- Download .NET 6.0
- .NET Desktop Runtime 6.0.36 (x64)
Code:
windowsdesktop-runtime-6.0.36-win-x64.exe /install /quiet /norestart- Messages
- 3,944
- Reaction score
- 1,649
That's a Windows question, DISM cleanup has tons of issues and dependencies.
For example if adding .NET 3.5 it blocks it, also after Feature configuration or certain updates in the Image, until installed, it also can return that error.
You can also see extra info in C:\Windows\Logs\CBS\cbs.log, but it's quite cluttered, don't expect much.
What do you recommend when I want to clean-up the image? I used this order: https://www.ntlite.com/community/in...gic-beginners-question-sorry.5027/#post-48429
- Messages
- 3,944
- Reaction score
- 1,649
Use a fresh downloaded ISO from Microsoft, add updates with NTLite and enable Update Cleanup DISM Compatible option.
It will then clean when possible, it times it as appropriate and repeats the cleanup a few times.
Last time it may be skipped, due to the mentioned dependencies, but it will clean at least the biggest chunks after CU integration if allowed to do so.
Do let me know if you see some quirks with the mentioned scenario, provide a preset for me to test with.
It will then clean when possible, it times it as appropriate and repeats the cleanup a few times.
Last time it may be skipped, due to the mentioned dependencies, but it will clean at least the biggest chunks after CU integration if allowed to do so.
Do let me know if you see some quirks with the mentioned scenario, provide a preset for me to test with.
This order worked like a charm, cheers!
SergioMontejo
New Member
- Messages
- 1
- Reaction score
- 0
Good evening, after installing the SS, DU, and CU updates in the Windows installer, it is necessary to copy the binaries for setup.exe, setuphost.exe, bootmgfw.efi, and bootmgr.efi. The .exe files go in the "sources\" folder, bootmgr.efi goes in the root directory of the installation DVD files, and bootmgfw.efi must be copied to "\efi\boot" and renamed to "bootx64.efi". These files should be copied from "Windows\boot\efi\" of the mounted WinPE that functions as the installer, and the .exe binaries are located in "sources\" of the same WinPE. If the binaries are not copied, the installer won’t boot because the build number of the new update must match what's in sources\ where the install.wim is located
That's covered by Steps 27-28 of the table, in post #2. NTLite already does this for you.