Enable the Intel I217-V NIC in Windows Server 2012

My new Gigabyte Z87-D3HP motherboard with support for 4th Generation Intel® Core™ processors (codename Haswell) has a onboard Intel I217-V NIC. The NIC is not recognized and supported in Windows Server 2012. As with the “Enable the Intel 82579V NIC in Windows Server 2012” blogpost it is possible to enable the NIC in Windows Server 2012. Here are the steps:

  • To be able to modify the drivers you need to run the the following commands:
bcdedit -set loadoptions DISABLE_INTEGRITY_CHECKS 
bcdedit -set TESTSIGNING ON
  • Reboot the system
  • Download the Intel drivers from the motherboard vendor or from Intel. In my case I used the Intel Windows 8 64-bit  drivers Gigabyte has available for the Z87-D3HP motherboard on there website.

image

  • Save the drivers  and extract them
  • Open the folder PRO1000
  • Open the folder Winx64
  • Open the folder NDIS63
  • Open the e1d63x64.inf file, I used Notepad++  to edit the file
  • In the [ControlFlags] section delete the 3 lines (see 1)

 

image

  • Select and copy the three E153B lines ((see 2)
  • Paste the 3 lines in the [Intel.NTamd64.6.2] section below the %E155ANC lines (see 3)
  • After the modifications the e1d63x64.inf file must look like this:

image

  • Save the file
  • Install the Intel driver
  • During the installation the you got a “Windows can’t verify the publisher of this driver software” warning, select “Install this driver software anyway”  and continue

image

  • After the installation the Intel I217-V Gigabit NIC is recognized and enabled.

image

  • Enable the driver integrity checks and disable test signing again by using the following commands:
bcdedit -set loadoptions ENABLE_INTEGRITY_CHECKS
bcdedit -set TESTSIGNING OFF
  • Reboot the system

57 thoughts on “Enable the Intel I217-V NIC in Windows Server 2012”

  1. It’s worked! Very helpful, The Gigabyte Tech support only reply me that the i217-V NIC not support in Windows 2012, Thank you very much.

  2. Genial Ivo, Yo lo usé en Windows Server 2008.
    Hay que hacer lo mismo pero en la carpeta NDIS62 y el archivo es e1d62x64.inf

  3. Will this same modification allow me to install Windows Home Server 2011 which is based on 2008R2? Or would that require different .inf edits?

    TIA.

  4. works for 2012r2 – change to the ndis64 folder and of course the file NDIS64. reboot using advanced options (f8 under startup) disable digital signature – install

  5. I’ve got an Asus gryphon with a Intel I217-V Gigabit NIC, and am trying to install WHS 2011. No luck on NIC recognition with that OS of course, and tried your solution by editing the Server 2008r2 version of the e1d63x64.inf file, still no luck. I’m either not editing the right lines, or not with the proper lines I’m guessing. Any advice?

  6. Great post. I used this info to get the NIC working on 2012 R2
    Just go to the NDIS64 folder and edit the e1d64x64.inf file
    And if you are trying to install the driver in core/hyper-v server use this command after editing: “pnputil.exe -i -a \PRO1000\Winx64\NDIS64”

  7. found this searching for a x86-xp-driver running the I217V-adapter. I don’t understand much about txtoem, .inf, plug&play etc., but would a workaround like this ie performed with a Windows 7 (32bit)-driver make I217V work with windows xp as well?
    Or is there another way?
    Thank you Ivo.

  8. Hi thx ROBJM and Ivo.

    It worked for me. It’s a little bit different in 2012 R2 but with the screenshots it worked out fine.

  9. Hi Ivo, thanks a lot! You saved a Server Installation Windows Server 2012 essential on a Z87 pro 4. It worked immediately.
    All the best from cologne
    Reinhard

  10. Ivo, hartstikke bedankt! Trying to install WHS 2011 on an ASUS H87I-Plus board, and ran up against this issue of the LAN drivers not installing. Thankfully your edits to the NDIS62 file worked a treat… Whoever in Intel thought this was a good idea should be taken outside and given a good talking to.

  11. Hello Ivo,

    If you could help with this one, I’m tying to install intel I217-V driver for Windows Server 2003 x86/Windows XP, but with no luck. I know that it is said that windows Xp/2003 is not supported but I found one driver that does support I271-V, in one russian forum there posts with confirmation of successful driver install. In this link http://txt.do/ta2c is the *.inf code, If you could help me modify the content.
    The Driver file is here: https://downloadcenter.intel.com/Detail_Desc.aspx?agr=Y&DwnldID=22928. In the DriverSelectionGuide.txt is is said that:
    For these devices use the e1d driver:
    By Device ID:
    153A, 153B, 155A, 1559
    By Product Name:
    Intel(R) Ethernet Connection I217-LM
    Intel(R) Ethernet Connection I217-V
    Intel(R) Ethernet Connection I218-LM
    Intel(R) Ethernet Connection I218-V
    Which is e1d5132.inf.

    Thank you in advance.

  12. Thank you so so so so so so much.I had that problem on 2008r2 and it is solved by u man.Thannnkkksss.

  13. I used this approach with Windows Server 2012 R2, to get drivers installed for a i218-V chip on an ASUS z97-A motherboard.

    To apply this approach, I first found the section for the i218-V which has an identifier of E1559 instead of the E153B identifier for the I217-V, then found the matching lines in the Intel.NTamd64.6.3.1 section for E1559 (4 lines instead of 3) and copied them to the Intel.NTamd64.6.3 block. I did remove the controlflags but don’t think I needed to because the 1559 id isn’t included.

    Working great–I’m using this box as a host for many test op systems with Hyper-V so am not worried if there is some loading problem on the LAN connection as it really is just a client.

  14. I used ASROCK Z97 with windows 2008 r2 but i can’t found driver intel lan 1218 V . when i am read this website i found code for fix it in Pro1000——->WIN64——->NDIS62 folder .In the line e1d62x64.inf .You can edit code for fix %E15A1NC.DeviceDesc% = E15A1.6.1.1, PCI\VEN_8086&DEV_15A1
    %E15A1NC.DeviceDesc% = E15A1.6.1.1, PCI\VEN_8086&DEV_15A1&SUBSYS_00008086
    to the [Intel.NTamd64.6.1] block

  15. This tip in combination with the tip för 2012 R2 and I218-V above worked perfectly. Many thanks.

  16. perfect!! had to adjust for server 2012 r2 essentials but the adjustments needed are already in the comments.

  17. If you have a B85 PRO4 and want to install the driver to Server2012, you have to do the same in \NDIS64\e1d64x64.inf file also, then it works.

  18. Using a Maximus VII Hero (Z97) Board for experimenting with Win XP right now.
    This Asus board has definatly a I218-V Chip on it.

    Also use ProEmbSw11.exe driver package from Intel

    For these devices use the e1d driver:
    By Device ID:
    153A, 153B, 155A, 1559
    By Product Name:
    Intel(R) Ethernet Connection I217-LM
    Intel(R) Ethernet Connection I217-V
    Intel(R) Ethernet Connection I218-LM
    Intel(R) Ethernet Connection I218-V
    Which is e1d5132.inf.

    Tried to install this driver did not recognize the NIC chip.
    checking HW IDs it come out my I218-V has 15A1 instead of that 1559 iD in the driver.
    Modified the ID’s and the Driver installs… unfortunatly it seems futher checks are in the package.

    I218-V NIC gives out a (Code10) “Device can t be started” Error.

    Since the EMB package is compiled for a native 32 bit system (win xp) the driver should work.
    Why the device don t start? Are there any further check routines?

    If anybody can give me some advice on this issue… that would be nice.

    Thank you in advance

  19. Pingback: Homework Part 2 | LE BLOG DE DAVID LANOIZELEY
  20. Step1:- Change the following entries in PRO1000\Winx64\NDIS62e1k62x64.inf

    Copied under win2008 R2 section (all from windows 7 section)

    %E10DENC.DeviceDesc% = E10DE, PCI\VEN_8086&DEV_10DE
    %E10DENC.DeviceDesc% = E10DE, PCI\VEN_8086&DEV_10DE&SUBSYS_10DE8086
    %E10DFNC.DeviceDesc% = E10DF, PCI\VEN_8086&DEV_10DF
    %E10DFNC.DeviceDesc% = E10DF, PCI\VEN_8086&DEV_10DF&SUBSYS_10DF8086
    %E1525NC.DeviceDesc% = E10DF, PCI\VEN_8086&DEV_1525
    %E10EANC.DeviceDesc% = E10EA, PCI\VEN_8086&DEV_10EA
    %E10EANC.DeviceDesc% = E10EA, PCI\VEN_8086&DEV_10EA&SUBSYS_00011179
    %E10EBNC.DeviceDesc% = E10EB, PCI\VEN_8086&DEV_10EB
    %E10EBNC.DeviceDesc% = E10EB, PCI\VEN_8086&DEV_10EB&SUBSYS_00011179
    %E10EFNC.DeviceDesc% = E10EF, PCI\VEN_8086&DEV_10EF
    %E10EFNC.DeviceDesc% = E10EF, PCI\VEN_8086&DEV_10EF&SUBSYS_305317AA
    %E10EFNC.DeviceDesc% = E10EF, PCI\VEN_8086&DEV_10EF&SUBSYS_305917AA
    %E10EFNC.DeviceDesc% = E10EF, PCI\VEN_8086&DEV_10EF&SUBSYS_306017AA
    %E10EFNC.DeviceDesc% = E10EF, PCI\VEN_8086&DEV_10EF&SUBSYS_306A17AA
    %E10F0NC.DeviceDesc% = E10F0, PCI\VEN_8086&DEV_10F0

    Step2:- Run following command:-

    bcdedit -set loadoptions DISABLE_INTEGRITY_CHECKS
    bcdedit -set TESTSIGNING ON

    and reboot the system.

    Step3:-Launch R2 Server Manager and go to the device manager node.

    1.Right mouse click the banged out Ethernet nic.
    2.Select Update driver.
    3.Select browse my computer.
    4.Click “Let me pick from a list of device drivers on my computer”
    5.Click the “Have a disk” button
    7.Click the browse button
    8.Go to PRO1000\Winx64\NDIS62
    9.Click e1k62x64.inf (modified at step1) then click the open button

    Now select Intel 82576NS Gigabit Ethernet Controller

    Once LAN will be enabled then reboot the system and run:-

    bcdedit -set loadoptions ENABLE_INTEGRITY_CHECKS
    bcdedit -set TESTSIGNING OFF

    Now again reboot the system… It worked like a charm. I have done this for DB85FL board which have Intel® I217V Gigabit Ethernet Controller

    Cheers.

  21. Please ignore my last comments and follow this….!!! I have corrected the file path in this…!!!

    Step1:- Change the following entries in PRO1000\Winx64\NDIS62\e1k62x64.inf

    Copied under win2008 R2 section (all from windows 7 section)

    %E10DENC.DeviceDesc% = E10DE, PCI\VEN_8086&DEV_10DE
    %E10DENC.DeviceDesc% = E10DE, PCI\VEN_8086&DEV_10DE&SUBSYS_10DE8086
    %E10DFNC.DeviceDesc% = E10DF, PCI\VEN_8086&DEV_10DF
    %E10DFNC.DeviceDesc% = E10DF, PCI\VEN_8086&DEV_10DF&SUBSYS_10DF8086
    %E1525NC.DeviceDesc% = E10DF, PCI\VEN_8086&DEV_1525
    %E10EANC.DeviceDesc% = E10EA, PCI\VEN_8086&DEV_10EA
    %E10EANC.DeviceDesc% = E10EA, PCI\VEN_8086&DEV_10EA&SUBSYS_00011179
    %E10EBNC.DeviceDesc% = E10EB, PCI\VEN_8086&DEV_10EB
    %E10EBNC.DeviceDesc% = E10EB, PCI\VEN_8086&DEV_10EB&SUBSYS_00011179
    %E10EFNC.DeviceDesc% = E10EF, PCI\VEN_8086&DEV_10EF
    %E10EFNC.DeviceDesc% = E10EF, PCI\VEN_8086&DEV_10EF&SUBSYS_305317AA
    %E10EFNC.DeviceDesc% = E10EF, PCI\VEN_8086&DEV_10EF&SUBSYS_305917AA
    %E10EFNC.DeviceDesc% = E10EF, PCI\VEN_8086&DEV_10EF&SUBSYS_306017AA
    %E10EFNC.DeviceDesc% = E10EF, PCI\VEN_8086&DEV_10EF&SUBSYS_306A17AA
    %E10F0NC.DeviceDesc% = E10F0, PCI\VEN_8086&DEV_10F0

    Step2:- Run following command:-

    bcdedit -set loadoptions DISABLE_INTEGRITY_CHECKS
    bcdedit -set TESTSIGNING ON

    and reboot the system.

    Step3:-Launch R2 Server Manager and go to the device manager node.

    1.Right mouse click the banged out Ethernet nic.
    2.Select Update driver.
    3.Select browse my computer.
    4.Click “Let me pick from a list of device drivers on my computer”
    5.Click the “Have a disk” button
    7.Click the browse button
    8.Go to PRO1000\Winx64\NDIS62
    9.Click e1k62x64.inf (modified at step1) then click the open button

    Now select Intel 82576NS Gigabit Ethernet Controller

    Once LAN will be enabled then reboot the system and run:-

    bcdedit -set loadoptions ENABLE_INTEGRITY_CHECKS
    bcdedit -set TESTSIGNING OFF

    Now again reboot the system… It worked like a charm. I have done this for DB85FL board which have Intel® I217V Gigabit Ethernet Controller

    Cheers.

  22. Hi, I try your method but failed. It said cannot install because there are errors occurred when installing. I can only install i218-LM which is not working on my H97i-plus mother board with Windows Server 2012 R2 Essentials. Any ideas? Thanks.

  23. Thanks, it worked on Windows Server 2012 R2 Datacenter! However, I needed to make some slight modifications:

    1. The folder for Server 2012 R2 is NDIS64, not NDIS63.
    2. Likewise, the file is called e1d64x64.inf instead of e1d63x64.inf.
    3. If you try to install after editing the file, the installer will still complain that there are no NIC’s. You need to run APPSSETUPSETUPBDWinx64SetupBD.exe afterwards to get it to work.
    (Thanks to nearlydeaf.com who got it from jayhopeishere for this third tip)

  24. Thanks! I managed to get it working on ASUS H97M-PLUS with Windows Server 2012 R2 Essentials. I did it slightly different. Even though the Intel Download Center says the I218-V NIC is not supported on Windows Server 2012 R2, there is still a section under the Windows Server configurations for this NIC ([E15A1]).

    First I had to find out what the Hardware ID was for my device. To do this, go to Properties on the Ethernet Controller in Device manager. Go to Details and select the Hardware Ids Property. For the ASUS H97M-PLUS, the ID Is PCI\VEN_8086&DEV_15A1&SUBSYS_85C41043. So, in the e1d64x64.inf file in the NDIS64 folder, under the [Intel.NTamd64.6.3] heading I added the following (the third line is important to get windows to recognize the card):

    %E15A1NC.DeviceDesc% = E15A1, PCI\VEN_8086&DEV_15A1
    %E15A1NC.DeviceDesc% = E15A1, PCI\VEN_8086&DEV_15A1&SUBSYS_00008086
    %E15A1NC.DeviceDesc% = E15A1, PCI\VEN_8086&DEV_15A1&SUBSYS_85C41043

    Then I followed the steps above to reboot Windows in Test mode and updated the driver from device manager pointing to the updated file. Rebooted back to normal mode and it worked perfectly!

  25. What a crazy thing! I just want to use Windows Server 2012 R2 with this NIC. And because it supported fine on Windows 8.1 and no difference with Windows Server 2012 R2 this is a really nasty thing from Intel… But we succeeded. Bedankt! 🙂

  26. Hell.. It looks like getting connection is really hard. DHCP etc. Sometimes it just doesn’t work. Sometimes a reboot works. Let’s see. It will need to run as a very low low load server for word and excel, but it should run stable 😛

  27. WTF. Intel really sucks! Once I do get a connection it is 10Mbps… Something is really screwed. Also I didn’t get it to work with NDIS63, used NDIS64 instead.

    I haven’t seen 10Mbps in the last 10 years! Anyone else experiencing this issue?

    Luckily there is also a Qualcomm Atheros Killer E2201 NIC on the motherboard. With that one NO problems! No driver issues, no connection issues, no speed issues. Greedy Intel, a real pity…

  28. Sorry.. Problem resolved. Very strange problem. After a couple of days I also couldn’t connect to it with the other NIC (Killer), some pings came through, but some don’t.

    Replaced the cable and the problem is gone. So sorry for that, the connection is now stable. Maybe Intel doesn’t make a connection when the cable is bad.

    The problem was because the kids had stepped on the cable, and it was tight from the ground to the motherboard… Ouch. Luckily the port on the motherboard (€ 190) isn’t damaged. 🙂

    Great to see this problem is resolved! Thanks!

  29. Works fine for Supermicro C7Z87 and Windows 2008R2 Server if patch is done in NDIS62 Folder.
    Everything else as described in the main tutorial.
    Thank you very much!!!

  30. Thank for your posting!

    My main board is B85M PRO4 made by ASRock.
    I installed Windows Server 2008 R2, and used driver for Windows 8 64bit.

    With e1d63x64.inf, I failed
    but with e1d62x64.inf in the NDIS62 directory, I succeed.

    Unfortunately, I found another problem. Set static IP address, Network Adapter does not work.
    So I decided to use it with DHCP setting.

    Thank you again.

Leave a Comment