Today I wanted to discuss small tips for making Windows Update via DISM.
The goal is that often on IoT terminal the Windows Update services is off and often not configured correctly, as the goal of IoT is often to create never changing terminal for a specific’s task. This kind of setup bring some headache sometime as to update it mean sometime when we put back on the Windows Update’s service, misconfiguration can happen.
The other goal is that often the image file is used to deploy such terminal, as such applying a patch offline to them help for future deployment.
Today I will talk the second’s goal.
DISM is a powerfull tool, but it’s to know it’s force that is a challenge.
To update a offline image the first step is to get the DISM that is shipped in the Windows Assessment and Deployment Kit (Windows ADK) (https://docs.microsoft.com/en-us/windows-hardware/get-started/adk-install)
After installing it we need to mount our WIM’s file with the /mount-wim command’s line.
dism /mount-wim /wimfile:”c:\en_windows_10_enterprise_2016_ltsb_x64_dvd_9059483\sources\install.wim” /mountdir:”c:\win10″ /index:1
After we add the package with /add-package
dism /image:”c:\win10″ /add-package /packagepath:”c:\patch\windows10.0-kb4576750-x64_c4e0b5e0f0835db971a40058aa17ae9a0d2f1e2a.msu”
After we need to commit the file back with /commit
dism.exe /Unmount-wim /mountdir:”c:\win10″ /commit
For reference if you see a DISM error #0x800f0823 it can mean you are using the wrong DISM, not the one provided with the ADK’s toolkit.
The error look like that;
That conclude today talk,
Thanks everyone !