There are literally so many ways to inject patches to your WIM file nowadays, I’ve been done a little research and I find this way the most appropriate.
This guide is based on this blog:
https://execmgr.net/2018/06/07/windows-10-image-maintenance/
but with a final touch on how to do almost everything with PowerShell, even import it to SCCM. Ok, lets go!
- Make a folder on the Site server example: “C:\WIM-Servicing”
- Download and unzip this file, WIM-Servicing (Includes two scripts
- Copy these two scripts to the Server
- Now its time to Mount the .ISO file to this server
- Copy the “D:\sources\install.wim” to this folder “C:\WIM-Servicing”
D: is the mounted .ISO - Now we need to download the .MSU files to your server, this step need some manually, unfortunately.
In my enviorment, I want to patch the 1803 version with Cumulative, Stack update and Adobe Flash
1. November 2018 – KB4467702 Cumulative Update for Windows 10 Version 1803 for x64-based Systems
2. November 13, 2018 – KB4465663 Servicing stack update for Windows 10, version 1803
3. November – KB4462930 Update for Adobe Flash Player for Windows 10 Version 1803
To find these patches you go to https://www.catalog.update.microsoft.com/home.aspx - After you download them, make another folder in that WIM-Servicing folder, and name it to the month with first 3 letters.
- One important thing is to rename the stack update with a “1-” in the name. like this
1-windows10.0-kb4465663-x64_f38417e1deb1550dd84c0d414d325735279acd9c.msu
Because if the Cumulative patch injects before the stack update, it could cause problems. So make sure you change this. So the stack comes first!
- Now we have everything settle to start the progress, Open up the Service_WIM_Proper_Way.ps1, right-click and Edit.
- Change variables to match your wishes.
- Run the script.
- What’s happening now is
* Injection of patches
* Moving the .wim file to your location
* Importing the operating system image to sccm - So now you can distribute your .wim file, and ready to Test.
Good luck!
