Adding Custom Drivers For Winpe in Ghost Solution Suite 3.x
Note: You are locating a driver that will work for the client pc based on your current WinPE environment, not the version of Windows that is running Ghost, or you intend to deploy. For example, if you are using WinPE 10, you need to find drivers for Windows 10.
Here are the steps to locate which version of Windows PE your preboot environment is using:
For Boot Disk Creator:
WinPE Versions (ADKSetup.exe):
Use the system information tool on the client as outlined below:
There are 3 specific lines from this tool that will help here: "Name, PNP Device ID & Driver". See the below sample for reference.
Name  Intel(R) Ethernet Connection I217-LM
PNP Device ID PCI\VEN_8086&DEV_153A&SUBSYS_221017AA&REV_04\3&42FFD25&0&C8
Driver c:\windows\system32\drivers\e1d62x64.sys (184.108.40.206, 369.27 KB (378,136 bytes), 7/9/2015 11:59 AM)
Since the samples above are from a Dell system, based on the above information we are going to be looking for an Intel i217-LM driver for this Dell. A good place to start is navigate to the Dell cab file website and download the driver pack that is relevant to your WinPE environment. (Note the correct driver may not be present in the Dell Cab files. If this is the case there are additional resources linked at the bottom of this document).
Select "Download Now" and continue once this has successfully downloaded
Once these have downloaded, navigate to the download folder and unzip the "WinPE5.0-Drivers-A06-MGRG0.CAB". Any compression utility such as WinRAR, WinZip, 7zip, etc. can be used. To download any of these, simply search the web for compression or zip utilities to get a list of websites that provide these.
Once the CAB file is decompressed you will see multiple folders and drivers located inside the folder. The best way to find the needed driver is to look up at step 4 above. The last line "driver", states that the adapter uses the "e1d62x64" driver. The driver name in this case is systematic:
Driver Name, OS, Chipset
Let's break this down for further explanation. Other drivers may not be setup with this naming convention.
Driver Name: E1D
(You might also see E1C...)
62 : Windows 7 / Winpe3
63 : Windows 8 / Winpe4
64 : Windows 8.1 / Winpe5
65 : Windows 10 / Winpe10
Chipset: 64bit (the last bit of the driver name signifies the chipset bit, either x64 or 32)
E1D62x32 is the "E1D" driver for OS 62 (Which is Windows 7), 32 bit.
E1D64x64 is the "E1D" driver for OS 64 (Which is Windows 8.1), 64 bit.
E1D65x64 is the "E1D" driver for OS 65 (Which is Windows 10), 64 bit. (This is the most commonly added driver.)
If you are still not sure which driver file is appropriate you can use Windows Search to find the PNP Device ID of that you found in step 4 above to check if the correct driver is available on your system.
Use only the first part of the string right before any &&REV including the characters through SUBSYS_xxxxxxxx as in the following example:
If a potential driver exists the search results will show something similar to:
Sometimes a driver doesn't exist in the manufacture provided cab files. In this case we suggest getting an additional driver from the manufacturer website. You have 3 options:
KB 180718 goes over that procedure.
Microsoft Driver Catalog (Only viewable in Internet Explorer) - https://catalog.update.microsoft.com/v7/site/home.aspx
Dell Driver Packs - https://www.dell.com/support/kbdoc/en-us/000107478/dell-command-deploy-winpe-driver-packs
HP Driver Packs - http://whp-hou4.cold.extweb.hp.com/pub/caps-softpaq/cmit/HP_WinPE_DriverPack.html
Lenovo Driver Packs - https://support.lenovo.com/us/en/documents/ht074984
NOTE: This information is provided as a guide only. It is meant to assist our customers with finding, often difficult to find, drivers for network adapters that are needed to leverage network communication in a Microsoft Windows PE environment. Ultimately the existence of drivers for your specific adapter is completely up to the manufacturer of the network adapter and/or the OEM who built the system the network adapter is in. Symantec can make no warranties or assurances that a NIC driver exists or works with your specific adapter in any environment.