Trying to find correct WinPE network driver

[antbyrd12]

I am trying to find the correct WinPE drivers for the HP ProOne 600 G4 21.5-in Non-Touch AiO. The driver I am missing has the following PnP:  PCI\VEN_8086&DEV_15BB&SUBSYS_83EA103C&REV_10

Apparently I have PCI\VEN_8086&DEV_15BB but that is not good enough for MDT it has the be the specific driver above. Does anyone have any suggestions? I have injected the 1709 and the 1803 drivers from HPs driver pack and still I get this issue. 

[Paul_Tikkanen]

Hi:

The only suggestiion I can offer, would be to try changing the generic hardware ID in the driver setup information file to the specific one you see listed as the hardware ID.

I checked the driver from the Intel site, and it is exactly the same as the HP one.  No lists of different hardware ID subsys.

So, I would try changing the second descriptor as follows in the setup information file:    In the E1D folder...

Original:

%E15BBNC.DeviceDesc%            = E15BB.10.0.1,       PCI\VEN_8086&DEV_15BB
%E15BBNC.DeviceDesc%            = E15BB.10.0.1,       PCI\VEN_8086&DEV_15BB&SUBSYS_00008086

Change to:

%E15BBNC.DeviceDesc%            = E15BB.10.0.1,       PCI\VEN_8086&DEV_15BB

%E15BBNC.DeviceDesc%            = E15BB.10.0.1,       PCI\VEN_8086&DEV_15BB&SUBSYS_83EA103C

[antbyrd12]

Hello Paul,

Thanks for the quick response! So I will need to make this change in the .ini file and reupload the driver?

[Paul_Tikkanen]

You're very welcome.

Yes, that is correct.

I have zipped up and attached the driver folder with my suggested mod below.

You can probably just try unzipping and injecting this driver folder and see if it works.

[antbyrd12]

Ok I will give this a try and report back thanks!

[antbyrd12]

So I tried this with PCI\VEN_8086&DEV_15BB&SUBSYS_83EA103C and PCI\VEN_8086&DEV_15BB&SUBSYS_83EA103C&REV_10  and I'm still getting the same. 'Could not connect to the deployment share' error in the MDT PXE environment. 

[Paul_Tikkanen]

Sorry that didn't work.

I guess you will have to contact HP technical support for further assistance, or try installing the driver by running the exe file in W10.

[nimble123]

Did you ever get this figured out?