kennysarmy Posted December 17, 2019 Posted December 17, 2019 Since rolling out Windows 10 I've been able to take the WIM file from our WDS/MDT setup and slipstream in any major updates to save time when imaging PC's. The process has been: Take a backup of the WIM file from the MDT server (DeploymentShare\Operating Systems\etc) Copy the WIM file from the MDT server rename wim.wim Download any recent updates from Microsoft Update Catalog Then run the following commands to slipstream in any new updates dism /mount-wim /wimfile:D:WIM\wim.wim /mountdir:D:WIMTEMP /index:1 dism /image:D:WIMTEMP /Add-Package /PackagePath:D:updates dism /Unmount-Wim /MountDir:d:\WIMTEMP /commit Copy the wim file back to MDT. This week I carried out this process, attempting to slip-stream in the following file : windows10.0-kb4530689-x64_a7cbdbcf320f1c56dace2424dedd4d468cd46d3d.msu This is the 2019-12 Cumulative Update! The DISM process completes without error and the WIM file size grows. However, when I re-image a test and subsequent PC's they all still find the 2019-12 Cumulative Update and re-install it again. Can anyone advise what might be going wrong here?
kennysarmy Posted December 17, 2019 Author Posted December 17, 2019 How can an update be installed AND ALSO be required???
kennysarmy Posted December 17, 2019 Author Posted December 17, 2019 Files being slip-streamed in successfully.
computer_expert Posted December 17, 2019 Posted December 17, 2019 Are you missing the latest SSU (Servicing Stack Update)? Sometimes you have to apply the SSU first before the updates apply correctly. What happens if you use a fresh wim with OSDBuilder or WimWitch to apply the updates? 1
kennysarmy Posted December 18, 2019 Author Posted December 18, 2019 Are you missing the latest SSU (Servicing Stack Update)? Sometimes you have to apply the SSU first before the updates apply correctly. What happens if you use a fresh wim with OSDBuilder or WimWitch to apply the updates? Yes, KB4520724 from the screenshot also gets successfully installed. I'm going to try slip streaming in from another PC running a different version of the ADK.
kennysarmy Posted December 18, 2019 Author Posted December 18, 2019 Same issue on another PC with a different ADK installed. Updated the WIM, copied back to the MDT, imaged a PC, then it finds the 2019-12 CU again from our WSUS Not sure what else to try now... Perhaps installing the SSU, unmounting the image and going through the process again to install the CU. Otherwise I'm stuck
ITGuyNW Posted December 18, 2019 Posted December 18, 2019 Maybe wait until next months updates and try that one? 1
Recommended Posts
Create an account or sign in to comment
You need to be a member in order to leave a comment
Create an account
Sign up for a new account in our community. It's easy!
Register a new accountSign in
Already have an account? Sign in here.
Sign In Now