Enable the Intel 82579V NIC in Windows Server 2012

After installing Windows Server 2012 on my homebrew server, the onboard Intel 82579V Gigabit NIC on the Asus P9X79 motherboard was not working. On the Asus site I found Windows 8 Intel drivers for the motherboard. After installing the drivers the NIC was still not working. To get the  Intel 82579V NIC working in Windows Server 2012, I used the this forum thread as reference for this blog post.

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
  • Download the Intel drivers. In my case I used the Intel drivers Asus has available for the Asus P9X79 motherboard
  • Save them to a map and extract them if needed
  • Open the folder PRO1000
  • Open the folder Winx64
  • Open the folder NDIS63
  • Open the e1c63x64.inf file, I used Notepad++  to edit the file
  • In the [ControlFlags] section delete the 3 lines (1)
  • Select and copy the five %E1503 lines (2)
  • Paste the 5 lines in the [Intel.NTamd64.6.2] section below the %1502NC lines


  • After the modifications the e1c63x64.inf file must look like this:


  • Save the file
  • Install the Intel drivers


  • After the installation the Intel 82579V Gigabit NIC is recognized and enabled


  • 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


Now you can use the Intel 82579V Gigabit NIC  in Windows Server 2012.

97 thoughts on “Enable the Intel 82579V NIC in Windows Server 2012”

  1. Thanks. It is also workable in Windows Server 2008 R2, only should edit “NDIS62” folder

  2. Excellent post. For Windows Server 2012 use the NDIS63 folder, for Windows Server 2012 R2 use the NDIS64 folder. For a Gigabyte GA-Z97X-UD5H the Intel chip is a I217-V where VEN=8086 DEV=153B so use the file e1d64x64.inf <= e1d not e1c.

    (In general, grep/findstr the *.inf files to find the dev that matches your device, and you can find that in device manager – the properties page for the device that needs a driver, the details tab, the hardware ids.)

  3. Good post, it works for me so I can have a working networkingcard on my Intel NUC D54250WYKH. Thanks Excellent.

    Download this LAN driver for Windows 8 x64 for the NUC
    Extract package and open \PRO1000\Winx64\NDIS64\e1d64x64.inf in notepad, edit it so it looks like below “e1d64x64.inf”
    Run as admin: bcdedit -set loadoptions DISABLE_INTEGRITY_CHECKS
    Run as admin: bcdedit -set TESTSIGNING ON
    Install driver by executing \APPS\PROSETDX\Winx64\DxSysChk.exe
    Run as admin: bcdedit -set loadoptions ENABLE_INTEGRITY_CHECKS
    Run as admin: bcdedit -set TESTSIGNING OFF
    Then the network card works and is has this Intel(R) Ethernet Connection I218-V

    e1d64x64.inf remake:
    Signature = “$Windows NT$”
    Class = Net
    ClassGUID = {4d36e972-e325-11ce-bfc1-08002be10318}
    Provider = %Intel%
    CatalogFile = e1d64x64.cat
    DriverVer = 03/14/2014,

    %Intel% = Intel, NTamd64.6.3, NTamd64.6.3.1



    ; DisplayName Section DeviceID
    ; ———– ——- ——–
    %E153ANC.DeviceDesc% = E153A.6.3.1, PCI\VEN_8086&DEV_153A
    %E153ANC.DeviceDesc% = E153A.6.3.1, PCI\VEN_8086&DEV_153A&SUBSYS_00008086
    %E153ANC.DeviceDesc% = E153A.6.3.1, PCI\VEN_8086&DEV_153A&SUBSYS_00011179
    %E153BNC.DeviceDesc% = E153B.6.3.1, PCI\VEN_8086&DEV_153B
    %E153BNC.DeviceDesc% = E153B.6.3.1, PCI\VEN_8086&DEV_153B&SUBSYS_00008086
    %E153BNC.DeviceDesc% = E153B.6.3.1, PCI\VEN_8086&DEV_153B&SUBSYS_00011179
    %E155ANC.DeviceDesc% = E155A.6.3.1, PCI\VEN_8086&DEV_155A
    %E155ANC.DeviceDesc% = E155A.6.3.1, PCI\VEN_8086&DEV_155A&SUBSYS_00008086
    %E155ANC.DeviceDesc% = E155A.6.3.1, PCI\VEN_8086&DEV_155A&SUBSYS_00011179
    %E155ANC.DeviceDesc% = E155A.6.3.1, PCI\VEN_8086&DEV_155A&SUBSYS_90BA104D
    %E1559NC.DeviceDesc% = E1559.6.3.1, PCI\VEN_8086&DEV_1559
    %E1559NC.DeviceDesc% = E1559.6.3.1, PCI\VEN_8086&DEV_1559&SUBSYS_00008086
    %E1559NC.DeviceDesc% = E1559.6.3.1, PCI\VEN_8086&DEV_1559&SUBSYS_00011179
    %E1559NC.DeviceDesc% = E1559.6.3.1, PCI\VEN_8086&DEV_1559&SUBSYS_90BA104D
    %E15A0NC.DeviceDesc% = E15A0.6.3.1, PCI\VEN_8086&DEV_15A0
    %E15A0NC.DeviceDesc% = E15A0.6.3.1, PCI\VEN_8086&DEV_15A0&SUBSYS_00008086
    %E15A1NC.DeviceDesc% = E15A1.6.3.1, PCI\VEN_8086&DEV_15A1
    %E15A1NC.DeviceDesc% = E15A1.6.3.1, PCI\VEN_8086&DEV_15A1&SUBSYS_00008086

    ; DisplayName Section DeviceID
    ; ———– ——- ——–
    %E153ANC.DeviceDesc% = E153A, PCI\VEN_8086&DEV_153A
    %E153ANC.DeviceDesc% = E153A, PCI\VEN_8086&DEV_153A&SUBSYS_00008086
    %E153ANC.DeviceDesc% = E153A, PCI\VEN_8086&DEV_153A&SUBSYS_00011179
    %E155ANC.DeviceDesc% = E155A, PCI\VEN_8086&DEV_155A
    %E155ANC.DeviceDesc% = E155A, PCI\VEN_8086&DEV_155A&SUBSYS_00008086
    %E155ANC.DeviceDesc% = E155A, PCI\VEN_8086&DEV_155A&SUBSYS_00011179
    %E15A0NC.DeviceDesc% = E15A0, PCI\VEN_8086&DEV_15A0
    %E15A0NC.DeviceDesc% = E15A0, PCI\VEN_8086&DEV_15A0&SUBSYS_00008086
    %E1559NC.DeviceDesc% = E1559.6.3.1, PCI\VEN_8086&DEV_1559
    %E1559NC.DeviceDesc% = E1559.6.3.1, PCI\VEN_8086&DEV_1559&SUBSYS_00008086
    %E1559NC.DeviceDesc% = E1559.6.3.1, PCI\VEN_8086&DEV_1559&SUBSYS_00011179
    %E1559NC.DeviceDesc% = E1559.6.3.1, PCI\VEN_8086&DEV_1559&SUBSYS_90BA104D
    %E15A0NC.DeviceDesc% = E15A0.6.3.1, PCI\VEN_8086&DEV_15A0
    %E15A0NC.DeviceDesc% = E15A0.6.3.1, PCI\VEN_8086&DEV_15A0&SUBSYS_00008086
    %E15A1NC.DeviceDesc% = E15A1.6.3.1, PCI\VEN_8086&DEV_15A1
    %E15A1NC.DeviceDesc% = E15A1.6.3.1, PCI\VEN_8086&DEV_15A1&SUBSYS_00008086

  4. Hello,

    I did everything but for me it ‘s not true , I can install the driver but in the Network Connection Details
    give it no records and I have no function what can I do ?

    Bye Jens

  5. Dear Sir
    Iinstalled windows server 2012 but i cnnot conncect lan connection
    i instlled all lan adapter drivers
    so problem is windows network adapter not presnt in your computer
    but inwindows7 normal os is working i cannt understant what is a reyal prolem so help me sent detils to gmail id
    sent link also
    very urgent

  6. Thanks… works for me too. With sites like this, who needs MS Technet.

    good knowledge got from you

    intel company dont have this type knowledge

    suggestion is you have to work in intel company

  7. For anyone looking for a 2016 update to this, I can verify it works. I had to do a little more research to really understand how to do this, but this is the process I used. I downloaded the latest driver from Asus’s website, and I found the PRO1000 folder which will give you the proper file structure to do the rest, EXCEPT the last folder which should be NSI64 like a comment earlier said . From there I followed the instructions, BUT I verified all the lines of text in the pictures (in the sections you are directed to copy and paste into) were in both sections. I just added what wasn’t there to copy and paste. Be very careful as there are very little differences between some of them.

    Following this, I didn’t just run the install nor did I right click and choose install from the edited file. I went to device manager, found the ethernet device that didn’t have a driver and right clicked it. I chose to update driver, and then navigated to the NSI64 folder and it found the driver.

    A note, be sure to run the two commands in the Command prompt as administrator, and be sure you reboot before you attempt to install the driver as it won’t install until you reboot. when installing you will be asked if you really want to install the driver, say yes, and then verify the NIC is working. Once you do that, enter the second set of command prompts, and reboot.

  8. Hi,

    Did someone get it working for an

    Intel® 82583V network card?

    Hardware ID PCI\VEN_8086&DEV_150C

    I’ve adapted the Pro1000\Winx64\NDIS63\e1q63x64.inf and followed the procedure, but it doesn’t add the network adapter.

    Please advice


  9. Another option, which doesn’t involve editing the INF file, is:
    1. Open Device manager
    2. Find the unrecognised Intel 82579V under Network Adapters
    3. Right click, Update Driver
    4. Select “Browser my Computer for Driver Software”
    5. Select “Let me pick from a list of available drivers on my computer”
    6. Un-tick “Show Compatible Hardware”
    7. Select “Intel” as manufacturer, and then “Intel(R) 82579LM Gigabit Network Connection” as the model
    8. Click Next to install the driver

    This works because both the 82579LM and 82579V share the exact same driver. However only the 82579LM is listed in the INF as supported on Windows Server OSes.

    This is working for me on an Acer Revo RL80 with Windows Server 2016. The other advantage is that, because you haven’t modified the INF file, Windows still recognises the driver as signed.

  10. Thank you Stuart McConnachie, that did it without the possibility of messing up the driver files

  11. Perfect.
    Also works for Server 2019.
    I was about to purchase a new network card as all attempts failed. Luckily I found your post. So much neater and nicer to use onboard nic.
    Great instructions.
    (crazy to think that these instructions are actually still needed)

  12. Thanks so much! This helped me install the Intel 82579V LAN driver for an Acer Veriton X2610 (2610-UG630W) for Windows Server 2012 R2. I downloaded the Windows 8 64bit driver version 17.2, 2017/01/16 from https://www.acer.com/ac/en/US/content/support-product/3936

    The folder and INF were exactly the same as in your post, but my driver had more lines to copy and paste. It worked great, and I thank you as I have been trying to fix this for days!

Leave a Comment