Ven 8086 dev 15b8 windows server 2019

Какой антивирус лучше?

Все программное обеспечение, размещённое на GetDrivers.net, является бесплатным. Все названия и торговые марки являются собственностью соответствующих обладателей.

Вы искали драйвер для:

Выберите драйвер для своей операционной системы и ее разрядности. Рекомендуется устанавливать более позднюю версию драйвера (смотрите на дату выхода).
Для перехода к скачиванию файла нажмите на ссылку.

Результаты поиска:

	Драйвер / Устройство	Операционная система	Дата выхода Версия	Ссылка на скачивание
	Intel Network Connections Software	Windows 8.1, Windows 10, Windows 11 64-bit (x64)	2022-04-05 27.2
	Intel Network Connections Software v.25.6 & PCI Ethernet Drivers	Windows 7, Windows 8, Windows 8.1, Windows 10 64-bit (x64)	2020-12-08 25.6 1.0.2.8 12.19.1.32
	Intel Ethernet Connections CD Driver Pack	Windows 7, Windows 8, Windows 8.1, Windows 10 32-bit (x86), 64-bit (x64)	2018-01-23 23.0
	Intel Network Adapter Driver Pack	Windows 7, Windows 8, Windows 8.1, Windows 10 32-bit (x86), 64-bit (x64)	2016-05-20 21.0
	Lan Intel v.20.3 Windows 7 CD	Linux, Windows 7, 8 32-bit (x86), 64-bit (x64)	2015-08-04 20.3
	Lan Intel driver v.19.5	Linux, Windows 7, 8 32-bit (x86), 64-bit (x64)	2014-05-02 19.5
	ATI I/O Communications Processor LPC Controller Driver	Windows XP, Windows Vista, Windows 7 32-bit (x86), 64-bit (x64)	2006-06-21 6.1.7601.17514

Используемая вами версия браузера не рекомендована для просмотра этого сайта.
Установите последнюю версию браузера, перейдя по одной из следующих ссылок.

Hi wb,

Thanks for the clarification.

At this point I’m trying to understand Intel’s reasoning for I219-V supporting older Windows Server 2012 but not more recent Windows Server 2012 R2 or Windows Server 2016.

I’ve been trying to get my NUC6i5SYH to run Windows Server 2012 R2 or Windows Server 2016 as part of an experimental audio setup. Since Intel LAN driver will not install for I219-V with WS2012 R2 and WS2016, I have lost the ability to get the NUC6i5SYH to boot one of these two server OS in a diskless configuration (using Microsoft iSCSI virtual disk). This is very unfortunate. Had this NUC featured I219-LM LOM there would have been no trouble with WS2012 R2 or WS2016, but this is not the case.

Ironically, I have another much cheaper NUC5PPYH featuring Realtek gigabit Ethernet that has no trouble working with Windows Server 2012 R2 or Windows Server 2016. It looks like I’ll just have to give up trying to get my NUC6i5SYH to run WS2012 R2 or WS2016.

Can Intel confirm I219-V is supported with Windows Server 2012? Looking at Intel’s supported driver matrix PDF it shows even Windows Server 2012 as not being supported with I219-V. I can consider running Windows Server 2012 with my NUC6i5SYH if the I219-V driver can install properly.

Thanks.

Hi Sam,

Thank you for the additional information. Let me further check on this.

rgds,

wb

Hi wb,

I need to dispute your most recent statement above. I just completed an installation of Windows Server 2012 into my NUC6i5SYH with I219-V Ethernet, and the latest 21.1 LAN driver does NOT install against I219-V.

After this installer failed, I tried the INF driver installation method and got this:

The I219-V Ethernet of the NUC6i5SYH was not auto-detected and did not show up anywhere within this network adapter list.

This is basically proof that I219-V Ethernet is not supported with Windows Server 2012, in the same way Windows Server 2012 R2 and Windows Server 2016 are not supported for I219-V by the same driver package. Also, in studying the contents of the e1d63x64.inf, e1d64x64.inf and e1d65x64.inf files within the 21.1 driver package, it has become clear that I217-V/I218-V/I219-V are categorically excluded for Windows Server OS editions (2012, 2012 R2 and 2016), but I217-LM/I218-LM/I219-LM remain supported.

I would advice Intel to be more careful in stating which Windows OS edition is supported for which Intel LAN solution. There is obviously at least one case where the driver support matrix is incorrect, with the error not detected or corrected by Intel due to lack of verification of whether the driver can actually install or not.

Regards,

scan80269

HI Sam,

Thank you for bringing this matter to our attention. We will further look into this.

rgds,

wb

Hi,

I’ve had the same issues as you. Tried getting an ASUS B150i Pro motherboard with I219-V to work with Windows Server 2012R2 and 2016 as well. I started out with the Hyper-V Server editions, and tried to load drivers from Intel and Asus via the pnputil -i -a command, but this didn’t work.

After that i installed a Server 2012 R2 (with GUI). The only way I found to enable the Ethernet was to:

• Open Device Manager
• Open the unknown Network controller properties
• Driver — Update Driver
• Browse
• Let me pick from of list of device drivers on my computer
• Select the Intel i219-LM under Intel and use that instead.

This did work, but I have not been able to do the same for the Hyper-V Server edition (since it doesn’t have the Device Manager gui).

Kind regards,

Hi wb,

Thanks for answering. I have tried the drivers supplied by Asus (pnputil -i -a from the NDIS65 folder) and also from the latest 21.1 Intel drivers. I’ve tried running the supplied SETUPBD.exe application also.

As rspeak mentions, I believe this comes down to Windows Server 2016 and my hardware ID (15B8) not being in the .inf file.

rspeak, your procedure is for a different hardware ID than mine. How would you go about modifying e1d65x64.inf to support this HID: 15B8

As of now, when I do:

pnputil -i -a e1d65x64.inf

it gives me an driver installed correctly message. But sconfig still comes up with «No active network adapters»

This is extracted from device manager when my machine were running Windows Server 2012 R2 in GUI mode:

PCIVEN_8086&DEV_15B8&SUBSYS_86721043&REV_31

PCIVEN_8086&DEV_15B8&SUBSYS_86721043

PCIVEN_8086&DEV_15B8&CC_020000

PCIVEN_8086&DEV_15B8&CC_0200

Kind regards,

Hi Macvader,

Thank you for sharing the useful information. Glad to know you manage to made it work.

rgds,

wb

Macvader, well done! You solved it before I could give you the detailed procedures.&# 8232;I as well got it to work for my Hyper-V 2016, on the 6-gen i5 NUC. Also, some blogs show you copy and paste a whole bunch of Device IDs. Not necessary! Just do the ones that pertain to your LAN interface for your NUC, which in my case is 1570 ID. And bingo-bango, yer in biz!

Intel users ROCK!!