Win10XPE - How to add problem drivers in 7 steps

I spent a few hours reading documentation and forum posts trying to understand the steps needed to get my network card working in Win10XPE.  Hope these steps help:

1) After creating Win10XPE_64.iso and booting into it, open Device Manager to identify which devices don't have properly installed drivers i.e. yellow triangles with explanation points (From what I understood in forum, driver installation for these devices probably require a reboot during installation which I can’t do using WinPE i.e. the WinPE image will not be updated as a result of a reboot.  So some drivers need to be integrated into the Win10PXE build (i.e. when .iso is being created) after which these device drivers will be installed correctly). 

In my case, under "Other devices" was "Ethernet Controller" with a yellow triangle and exclamation point.

2) While in Device Manager, examine the properties of those devices with driver problems:

  Device Manager>Right-click device with problem>Properties>Details:
    In my case, I examined the property "Hardware IDs" and found the string "PCI\ven_8086&dev_15bc&subsys_e0001458&rev_10".
   
3) Reboot to Windows 10 and identify the device in Device Manager.  In my case, I have a Network card "Intel(R) Ethernet Connection (7) I219-V".
  Device Manager>Right-click the network card>Properties>Details>Property>Hardware Ids: "PCI\ven_8086&dev_15bc&subsys_e0001458&rev_10" which is the same Hardware ID from step 2 above.

  Navigate to Driver tab>Driver Details:
    In my case, it listed "Driver files: e1d68x64.inf_amd64_691712a04a41c1cd.sys"

4) In Win10XPE WinBuilder: Win10XPE>Build Core:Script>
  Integrate Drivers pane (Bottom right): click “Export” to copy all host PC drivers to ...\Win10XPE\Custom\x64\ExportDrivers

5) In ExportDrivers folder, locate the matching driver folder, in my case, "e1d68x64.inf_amd64_691712a04a41c1cd" and copy it to ...\Win10XPE\Custom\x64\Drivers folder (you can navigate there from WinBuilder, Integrate Drivers pane by clicking on "Copy Drivers Here")

6) Click on the "Play" icon located BETWEEN the "Copy Drivers Here" and "Export" buttons.  This will integrate the drivers in ...\Win10XPE\Custom\x64\Drivers folder into the Win10XPE build.

7) Press the big blue Play button to create a new Win10XPE_64.iso

That's std. procedure.
If you use a PENetwork plugin, it has an drivers integration option.

It's a little bit strange that there is no driver for I219-V in std. package.

I do not use Win10XPE project than a Win10PESE project and it has Net drivers plugin that integrates Atheros, Broadcom, Intel, Realtek, Ralink, Marvell network drivers.
I don't know if someone made a version for Win10XPE project.

That's std. procedure.

It's clear to me now - after hours of researching and reading - but if there was a similar post explaining this standard procedure with step by step for a newbie, I seem to have missed it

If you use a PENetwork plugin, it has an drivers integration option.

Tried that after booting into WinPE, but it didn't work in getting ethernet adapter working (I suspect because reboot is needed)

Hi Nikky,

It's a little bit strange that there is no driver for I219-V in std. package.

Let me know if you know the driver to use from the windows 10 source
I searched, a bit quickly, I found net1ic64.inf in winre.wim (so included) and install.wim for "Intel(R) Ethernet Connection (7) I219-V"
But the Hardware Ids: "PCI\ven_8086&dev_15bc&subsys_e0001458&rev_10" does not seem to be included.

I do not use Win10XPE project than a Win10PESE project and it has Net drivers plugin that integrates Atheros, Broadcom, Intel, Realtek, Ralink, Marvell network drivers.
I don't know if someone made a version for Win10XPE project.

There is ~the same Net drivers plugin in Win10XPE (Build Core > Network drivers checkbox)
It is a little improved by using RegAddDriver.cmd  to register drivers from the Windows 10 sources used and not from a previous extraction (10240).
It takes a little time during the 1st build, then it is saved in cache to gain time for the following constructions

Thanks snkj3n4 for writing this procedure, standard indeed. it will probably be useful for other users 

Are we not using DoubleDriver to do this and dropping the uncompressed files into driver integration anymore?

For a long time now I assumed that was standard for selectively exporting host drivers, this should work for all projects (Win7/8/10 PESE/XPE).. http://theoven.org/index.php?topic=1366.msg17697#msg17697

Seems much easier.. 

XPE Core uses DISM Export-Driver Function

Are we not using DoubleDriver to do this and dropping the uncompressed files into driver integration anymore?

With DoubleDriver or DISM Export-Driver Function, the process remains ~the same, export + copy for driver integration

Dism export is more up-to-date and seems more reliable to retrieve the required files
But the exported drivers are not categorized and thus a little less easy to use, DD is better for that

Also, For those that do not want to integrate Drivers into the Boot.wim... (Via Build Core Option)
You can create a "Drivers" Folder on the root (Y Drive) and include your custom drivers...
Then edit pecmd.ini and unmark the line to add the drivers from Y:\Drivers

Code: [Select]

//EXEC @!%WinDir%\System32\pnputil.exe /add-driver Y:\Drivers\*.inf /subdirs
==>
EXEC @!%WinDir%\System32\pnputil.exe /add-driver Y:\Drivers\*.inf /subdirs

@ChrisR
You may have incorrectly connected, colleague snkj3n4 has problems with I219-V driver, not me.