In this text, we’ll present you ways to add the required gadget drivers immediately into the Windows set up picture. The integration of the gadget drivers into your offline Windows picture is extensively used once you want to deploy a massive variety of workstations and servers on the identical . Instead of manually putting in particular drivers (together with AHCI/ RAID/ NVMe) on every gadgets, you’ll be able to considerably simplify and speed up OS deployment course of by integrating the drivers immediately into the Driver Store of the Windows set up picture within the ISO/WIM or the VHD/VHDX file. When putting in such a picture, the Plug and Play service (PnP) will routinely set up the required drivers for the detected .
This guide concerning the integration of gadget drivers into a Windows picture can be utilized each on desktop editions of Windows 10, Windows eight.1 and on Windows Server 2016, 2012 R2.
In fashionable Windows editions you’ll be able to add drivers to the set up ISO picture in two methods:
- utilizing the DISM utility;
- utilizing the PowerShell CLI.
In truth, each methods carry out the identical operation: add extra drivers into the offline Windows picture. How to use it’s a matter of private administrator desire. Let us contemplate in additional element each methods on the instance of integrating drivers into the Windows 10 set up picture.
Note. In Windows Server 2008 R2 and Windows 7, it was attainable to add a driver to the Windows set up picture utilizing the imagex command line software (included into the WAIK), however it isn’t supported in Windows Server 2012 and later.
- How to Inject Driver into a Windows 10 Install Image utilizing PowerShell
- Adding Drivers to an Offline Windows Server 2012 R2 Image Using DISM
How to Inject Driver into a Windows 10 Install Image utilizing PowerShell
First of all you want to obtain and place all the required gadget drivers in a single listing (for every driver you want to create a separate folder). Please notice that many distributors (together with Dell, HP) provide their drivers within the type of self-extracting exe or zip archive recordsdata. Such archives should be unpacked to native drive in order that the listing with drivers incorporates inf, cat and sys recordsdata.
Before you begin, create the next listing construction in your native drive:
- The Drivers folder – it incorporates unpacked driver recordsdata on your Windows 10 version (that are supposed to be built-in into the set up media);
You can obtain and unpack the required driver recordsdata manually or export all third-party drivers from a reference Windows 10 laptop, on which all the required drivers are already put in (utilizing the cmdlet).
- The ISO folder – this listing incorporates the unpacked iso picture of Windows 10. You solely want the Install.wim file from the Sources listing;
If your Windows 10 ISO picture incorporates solely the file ..sourcesinstall.esd, you’ll be able to to WIM format utilizing the DISM software:
dism /export-image /SourceImageFile:"C:WinWorkISOinstall.esd" /SourceIndex:four /Vacation spotImageFile:C:WinWorkISOinstall.wim /Compress:max /VerifyIntegrity
- The Mount folder – an empty listing into which the Windows set up WIM picture can be mounted later.
List all Windows editions contained within the Install.wim file utilizing the Get-WindowsImage PowerShell cmdlet. This is critical so as to specify the Widows version into which it’s deliberate to combine the extra drivers.
Get-WindowsImage -ImagePath C:WinWorkISOinstall.wim
In our instance, the WIM file incorporates just one Windows 10 Pro version with the index 1 (ImageIndex: 1).
Next you want to mount the picture of the chosen Windows version within the listing Mount. The Windows picture index, which you want to mount, should be specified as an argument of the Index parameter:
Mount-WindowsImage -Path C:WinWorkMount -ImagePath C:WinWorkISOinstall.wim -Index 1
After the picture is mounted, you’ll be able to add drivers to it from the Drivers listing utilizing the command:
Add-WindowsDriver -Path C:WinWorkMount -Driver C:WinWorkDrivers -Recurse
The Add-WindowsDriver cmdlet will recursively search (the -Recurse parameter) the desired folder for all *.inf recordsdata with driver description. According to the outline within the inf file, the cmdlet will add the dependent INF, DLL, CAT, PNF, and so forth. recordsdata to the Driver Store of your Windows picture.
So, the drivers are copied, and the present picture may be unmounted with saving modifications:
Dismount-WindowsImage -Path C:WinWorkMount –Save
In the above instance, we added drivers to the Install.wim picture file. This is the Windows picture that can be deployed to a laptop native disk. If you want to add drivers to a Windows boot picture (from which the pc boots once you set up Windows), you want to add drivers to the Boot.wim file. This is normally obligatory if, when putting in Windows, the pc doesn’t detect native exhausting drives or doesn’t join to LAN. Usually, solely drivers of disk controllers and community adapters want to be built-in into the boot.wim picture.
You can convert your set up.wim file containing the Windows set up picture with built-in drivers into the set up.esd format utilizing the DISM compress choice:
DISM /Export-Image /SourceImageFile C:WinWorkISOinstall.wim /SourceIndex:1 /Vacation spotImageFile:C:WinWorkISOinstall.esd /Compress:restoration
It stays to create an ISO file utilizing or the oscdimg command and write it to a disk or :
oscdimg -n -m -bc:ISObootetfsboot.com C:ISO C:new_win10pro_image.iso
Adding Drivers to an Offline Windows Server 2012 R2 Image Using DISM
Now we’ll present an instance of integrating drivers into the set up picture of Windows Server 2012 R2. If you might be constructing a picture on Windows eight.1, you’ll need to obtain and set up Windows eight ADK (http://www.microsoft.com/en-us/obtain/particulars.aspx?id=30652) to proceed working with the latest model of DISM. You want to set up the Deployment Tools element.
Use the identical listing construction: Drivers (drivers and *.inf recordsdata are saved), ISO (unpacked picture of Windows Server 2012 R2), Mount (picture mount listing). It is assumed that within the set up.wim file we have an interest within the Windows Server 2012 R2 Datacenter version with index three.
Mount the set up.wim set up picture:
dism /Mount-Wim /WimFile:c:isosourcesinstall.wim /Index:three /MountDir:c:mount
Run a recursive search and integration of the brand new drivers into the driving force retailer of the Windows Server 2012 R2 picture :
dism /picture:c:mount /Add-Driver "/driver:c:drivers" /recurse
Save the modifications to the WIM picture:
dism /unmount-wim /mountdir:d:mount /commit
You may additionally have to combine drivers for community adapters and disk controllers into the boot picture file boot.wim.
If you want to add drivers to all Windows Server editions contained within the wim file, these operations should be carried out for all indexes of OS variations that the command returned:
dism /get-wiminfo /wimfile:d:set up.wim
In addition to driver integration, it’s normally obligatory to inject safety updates to the Windows picture to be put in (). This will enhance the safety of your OS instantly after the set up. It stays to write the ensuing set up picture to the DVD disk or USB flash drive or convert it to the ISO picture.