In this information I’ll present methods to combine new Windows replace packages into the offline set up picture of Windows 10 or Windows eight.1 utilizing built-in instruments. The similar means you’ll be able to slipstream the latest safety patches into the Windows Server 2012 R2 / 2016 set up ISO photos.
In this instance, I’ll present the method of including the latest cumulative safety updates (December 2018) to the set up picture of Windows 10 1803. So, we’ll want:
Create the next listing construction in your pc:
- C:updatesmnt is the folder wherein the file set up.wim with the Windows set up picture will probably be mounted;
- C:updatesmsu is a folder wherein you’ll want to place the MSU updates on your Windows model (on this instance, I downloaded 2 safety updates for Windows 10 1803, launched in December 2018 – KB4471331 and KB4471324);
- C:updatesWin10Image on this folder you’ll want to copy the set up.wim file out of your Windows 10 set up picture. In our instance, we mounted and unpacked the contents of the unique Windows 10 ISO picture Windows10x64-1803.iso. However, it may be a wim file from a digital machine, VM template, WDS picture or picture saved in one other OS automated deployment software program (for instance, SCCM), and many others.
If your Windows 10 ISO picture accommodates solely the file c:sourcesinstall.esd, you’ll be able to to WIM file utilizing the DISM utility:
dism /export-image /SourceImageFile:"C:updatesWin10Imageset up.esd" /SourceIndex:four /Vacation spotImageFile:C:updatesWin10Imagewin10professional.wim /Compress:max /TestIntegrity
Mount the Windows 10 set up picture (set up.wim) to the C:updatesmnt folder by operating the next command within the command immediate as an administrator:
dism /mount-wim /wimfile:C:updatesWin10Imageset up.wim /index:1 /mountdir:C:updatesmnt
DISM /Get-WimInfo /WimFile:C:updatesWin10set up.wim
In our instance, the picture accommodates just one OS version – the Windows 10 Pro with the index 1, due to this fact within the command we’d like specify set up.wim /index:1.
Now you’ll be able to run the mixing of appropriate MSU updates situated within the specified listing into the Windows 10 picture:
dism /picture:C:updatesmnt /add-package /packagepath:C:updatesmsu
If the system detects a improper replace (a one that isn’t appropriate for this OS model and bitness, or if the replace is already put in), it will likely be ignored and the corresponding data will probably be written to C:WindowsLogsDISMdism.log.
To scale back the scale of a picture by deleting previous replace information (see the article about ), run the command:
dism /picture:C:updatesmnt /Cleanup-Image /StartPartCleanup /ResetBase /ScratchDir:C:Temp
If you have already got a pc with an identical model of Windows 10 that already has the latest safety updates put in, you will get all the required replace information straight from it. In this case, you don’t have to manually obtain MSU replace information from the Microsoft Update Catalog. The trick is that Windows saves CAB information of the updates which have been downloaded from Windows Update servers or a server to the C:WindowsSoftwareDistributionDownload folder.
Using the next command, you’ll begin integration into the set up.wim picture of replace information which have already been downloaded and put in on one other pc by way of the native community:
Start /w for /R Win10x64AlreadyPatchedPCC$WindowsSoftwareDistributionDownload %f in (*.cab) do dism /picture:C:updatesmnt /add-package /packagepath:”%f”
In this instance, Win10x64AlreadPatchedPC is the identify of the distant pc on which the required updates are already put in (the OS model and bitness should match). Of course, this pc ought to be accessible over the community, and your account ought to be added to the native directors group on it. In the window that opens, you’ll be able to watch the method of putting in updates to the offline Windows picture. DISM will attempt to add to your WIM picture every discovered CAB file on a distant pc.
If you encounter an error whereas integrating updates into a Windows picture: “Error 0xc0000135 An error occurred whereas trying to begin the servicing course of for the picture situated at C:Updatemount. For extra data, evaluate the log file”, be sure to are utilizing the latest model of DISM. For instance, you are attempting to change a Windows Server 2016 picture from Windows eight.1. Install the latest obtainable model Windows Assessment and Deployment Kit (Windows ADK) on your OS and run DISM straight from the catalog
C:Program Files (x86)Windows Kits10Assessment and Deployment KitDeployment Toolsamd64DISM.
And the final step is to save lots of the modifications and unmount the Windows 10 picture:
dism /unmount-wim /mountdir:C:updatesmnt /commit
You solely have to repeat set up.wim to the supply listing/digital machine or rebuild the set up ISO picture, e. g., utilizing oscdimg,UltraISO or
If the scale of your set up.wim file is greater than four GB it’s possible you’ll encounter the error “Windows can not open the required file D:sourcesinstall.wim. Error code: 0x8007000D” throughout Windows set up on the system. In this case, you’ll want to cut up the supply set up.wim into smaller information with the command:
dism /split-Image /imagefile:C:UpdateWin10Imageset up.wim /swmfile:C:UpdateWin10Imageset up.swm /filesize:4096
(see the articles and
After that, the unique set up.wim may be eliminated.
Now you’ll be able to deploy your Windows set up picture with the latest safety updates built-in on a computer systems in your community. By recurrently integrating the latest safety updates into your Windows picture deployed on new computer systems, you enhance the safety of your infrastructure in opposition to the latest vulnerabilities and scale back the danger of infecting new computer systems till they begin updating from WSUS.