@garlin, this may be of particular interest to you.
I have been struggling to get my scripts and program that inject Windows updates into an image to work properly with 24H2. For months I have been trying to figure this out, but I finally resolved it today.
Garlin, I don't know if you will recall that we had a brief discussion about files that need to be moved from the boot.wim into the main install.wim file. You had asked me about that, and I sent a link showing where I had gotten that information. I was on the right track with that. It turns out that there is simply one additional file that needs to be copied with 24H2.
I have now updated my scripts and program, injected the updates into 26100.1742 to bring it up to 26100.2033 and then tested. I was now able to successfully install both manually and using unattended installation.
Here is how I figured it out...
First, take a look at this article related to updating installation media using dynamic updates:
Scroll down to the section called "Update remaining media files". You will note that what they are doing is copying several files from the boot.wim to the install.wim. I was missing one file: "setuphost.exe". It is that simple. That one change fixed everything for me.
What's odd is that I have poured over this doc before. It shows a date of July 15, 2024, but I swear that this change must have been snuck in later than that. Either that or I simply missed the change.
In any case, it all works perfectly now. Manual updates as well as unattended installations using media that I inject the updates into are working flawlessly. It even handles the new Checkpoint / Incremental updates perfectly.
With my batch file script, I update only a single edition in the ISO image, but with my program, it can recurse through all the editions and update them all. It takes maybe 2 hours or to update every edition in an ISO image, but it is entirely automated. I can just start the process and 2 hours lately I have a fully patched and up to date ISO image with all the latest SSU, LCU, Safe OS, and Setup updates plus the latest .NET updates.
I have been struggling to get my scripts and program that inject Windows updates into an image to work properly with 24H2. For months I have been trying to figure this out, but I finally resolved it today.
Garlin, I don't know if you will recall that we had a brief discussion about files that need to be moved from the boot.wim into the main install.wim file. You had asked me about that, and I sent a link showing where I had gotten that information. I was on the right track with that. It turns out that there is simply one additional file that needs to be copied with 24H2.
I have now updated my scripts and program, injected the updates into 26100.1742 to bring it up to 26100.2033 and then tested. I was now able to successfully install both manually and using unattended installation.
Here is how I figured it out...
First, take a look at this article related to updating installation media using dynamic updates:
Update Windows installation media with Dynamic Update
Learn how to acquire and apply Dynamic Update packages to existing Windows images prior to deployment
learn.microsoft.com
Scroll down to the section called "Update remaining media files". You will note that what they are doing is copying several files from the boot.wim to the install.wim. I was missing one file: "setuphost.exe". It is that simple. That one change fixed everything for me.
What's odd is that I have poured over this doc before. It shows a date of July 15, 2024, but I swear that this change must have been snuck in later than that. Either that or I simply missed the change.
In any case, it all works perfectly now. Manual updates as well as unattended installations using media that I inject the updates into are working flawlessly. It even handles the new Checkpoint / Incremental updates perfectly.
With my batch file script, I update only a single edition in the ISO image, but with my program, it can recurse through all the editions and update them all. It takes maybe 2 hours or to update every edition in an ISO image, but it is entirely automated. I can just start the process and 2 hours lately I have a fully patched and up to date ISO image with all the latest SSU, LCU, Safe OS, and Setup updates plus the latest .NET updates.
My Computers
System One System Two
-
- OS
- Win11 Pro 24H2
- Computer type
- PC/Desktop
- Manufacturer/Model
- Kamrui Mini PC, Model CK10
- CPU
- Intel i5-12450H
- Memory
- 32GB
- Graphics Card(s)
- No GPU - Built-in Intel Graphics
- Sound Card
- Integrated
- Monitor(s) Displays
- HP Envy 32
- Screen Resolution
- 2560 x 1440
- Hard Drives
- 1 x 2TB NVMe SSD
1 x 4TB NVMe SSD
1 x 4TB 2.5" SSD
- PSU
- 120W "Brick"
- Keyboard
- Corsair K70 Mechanical Keyboard
- Mouse
- Logitech MX Master 3
- Internet Speed
- 1Gb Up / 1 Gb Down
- Browser
- Edge
- Antivirus
- Windows Defender
-
- Operating System
- Win11 Pro 23H2
- Computer type
- Laptop
- Manufacturer/Model
- Lenovo ThinkBook 13x Gen 2
- CPU
- Intel i7-1255U
- Memory
- 16 GB
- Graphics card(s)
- Intel Iris Xe Graphics
- Sound Card
- Realtek® ALC3306-CG codec
- Monitor(s) Displays
- 13.3-inch IPS Display
- Screen Resolution
- WQXGA (2560 x 1600)
- Hard Drives
- 2 TB 4 x 4 NVMe SSD
- PSU
- USB-C / Thunderbolt 4 Power / Charging
- Mouse
- Buttonless Glass Precision Touchpad
- Keyboard
- Backlit, spill resistant keyboard
- Internet Speed
- 1Gb Up / 1Gb Down
- Browser
- Edge
- Antivirus
- Windows Defender
- Other Info
- WiFi 6e / Bluetooth 5.1 / Facial Recognition / Fingerprint Sensor / ToF (Time of Flight) Human Presence Sensor