DHCP failure with Intel I219-V

[scan80269]

Not sure if this can help, but I've noticed that Intel keeps adding additional flavors of I219-V (and I219-LM), with different device IDs. Looking at the latest Intel LAN driver (e1d65x64.inf, 12.18.8.4, 10/10/2018), they have gone to "Intel ® Ethernet Connection (9) I219-V" (ditto for I219-LM). I bought an Intel NUC8i7BEH PC a few days ago and discovered it has "Intel ® Ethernet Connection (6) I219-V", which is not supported by the inbox Intel LAN driver that comes with Windows 10 1803 (RS4, build 17134). I was trying to install this OS over the network into an iSCSI disk for this NUC8i7BEH, and ended up having to manually inject the latest Intel LAN driver into the install.wim of the Win10 installation files, as well as for WinPE.

I did have an HP EliteBook 840 G3 for about a year before it got replaced a month ago, and unfortunately I did not note the flavor of I219-V this notebook had. If you can identify the PCI VEN & DEV IDs of the Intel LAN in the 840 G3, it should be possible to check which of the I219-V it has, i.e. "Intel ® Ethernet Connection (?) I219-V", then check whether the legacy PXE driver has caught up to supporting that I219-V flavor. I just checked ROM-o-Matic and the drop-down menu for NIC driver selection does not go beyond I219V-5.

In short: Intel I219-V is not just I219-V as there are now at least 9 flavors each with unique PCI VEN & DEV IDs, and they may not all be supported by the legacy PXE driver unless the code undergoes a systematic update to add the recent IDs.