Using DISM SlipStream Win 2016 RTM with all the new patches.


yup. _

Thread starter #1
Hey All,

My intention here is to merge a Win 2016 RTM ISO (1607-14393.447) from MSDN with the latest updates. Likely after a new install, I see kb4049065 & kb4053579 showing up in the available update listing which I download & slipstream using steps as under;

Mount the extracted WMI file from the source media

Source Media D:\SlipStream\dump\sources\install.wim

Target Path D:\SlipStream\heap

dism /mount-wim /wimfile:"D:\SlipStream\dump\sources\install.wim" /mountdir:"D:\SlipStream\heap" /index:1

Import downloaded package into the Target

dism /image:D:\SlipStream\heap /add-package /packagepath:D:\SlipStream\AMD64-all-windows10.0-kb4049065-x64_f92abbe03d011154d52cf13be7fb60e2c6feb35b.msu

dism /image:D:\SlipStream\heap /add-package /packagepath:D:\SlipStream\AMD64-all-windows10.0-kb4053579-x64_c8f23cbaf60b5093a6902ce64520c354cfe360c7.msu

After the slipstream commit the image & un-mount it.

dism /unmount-wim /mountdir:D:\SlipStream\heap /commit

However, after installing OS with this new ISO. I'm still seeing these two come up as updates that need be installed. Unsure if these two KB4049065 & KB4053579 aren’t properly absorbed in the slip stream or why do they appear for the download again.

If someone can guide me if the process I'm following is flawed or the behavior isn’t what I expect.



Continue reading...