Install Intel I218-V NIC Driver for Windows Server 2012

I recently procured the MSI H97M ECO for my Windows Server 2012 R2 Essentials. At first I was pleased to notice that it comes with an Intel NIC instead of a Realtek, since a lot of people on the internet favor the Intel over the Realtek for whatever reasons. At first I was amazed that I needed to to manually install a driver for an Intel NIC in Windows Server 2012. Ok, maybe the NIC is too new since the board just came out, was my first thought. After I found out that Intel just doesn’t allow the driver to be installed on Server 2012 I was left speechless. I will show you how to modify the driver to get it working, although it still leaves me a bit concerned.

If you used Google, you probably found the Blogpost on how to Enable the Intel I217-V NIC in Windows Server 2012 and found out that it doesn’t work for the I218-V under Server 2012. You need to modify it a little. Follow these steps to get it to work.

  1. Start cmd with Administrator Rights and type in the following two commands
    bcdedit -set loadoptions DISABLE_INTEGRITY_CHECKS 
    bcdedit -set TESTSIGNING ON
  2. Reboot
  3. Extract the downloaded Intel Driver.zip (get it at the MSI Website)
  4. Edit the PRO1000\Winx64\NDIS64\e1d64x64.inf
  5. Remove all 3 Lines of the Section [ControlFlags]
  6. In Section [Intel.NTamd64.6.3.1] copy the last 6 lines and add them to the bottom of Section [Intel.NTamd64.6.3]
  7. Your .inf File should look similar to this one
[Manufacturer]
%Intel% = Intel, NTamd64.6.3, NTamd64.6.3.1

[ControlFlags]

[Intel]

[Intel.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

[Intel.NTamd64.6.3]
; 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

Now you should be able to install the Driver using the Autorun.exe. Windows might warn you about unsigned drivers, which you can just accept. The NIC will work afterwards, although when I tried to change some device settings the Device Manager crashed. 🙁

Also Windows will show Test Mode in the lower right corner on your Desktop. To get rid of this, revert the settings you typed in at Step 1.

bcdedit -set loadoptions ENABLE_INTEGRITY_CHECKS 
bcdedit -set TESTSIGNING OFF

Let me know if it doesn’t work for you, because I first followed the steps for the I217-V. So I ended up modifying multiple .inf Files. I’m fairly the one I mentioned here should be enough still I can’t be 100% sure. At least it worked for me, kinda. Still have to figure out if I’m able to change at least some adapter settings or if the driver will always crash.

24 thoughts on “Install Intel I218-V NIC Driver for Windows Server 2012

    • This solution worked for me as well, on Windows Server 2012R2 AFTER reboot. Please be sure reboot for the driver settings to take effect.

      Cheers,
      G.

  1. Hi, I used this and it worked perfectly for Server 2012 R2. I now need it to work with Server 2008 R2.

    What file would I have to modify for Server 2008 R2? I see in that driver that “Intel.NTamd64.6.3.1” is equal to Windows 8/8.1 and that “Intel.NTamd64.6.3” is equal to Windows Server 2012. What would be the identities of Win 7 and Win Server 2008?

    • Hi,

      I’m sorry, I’m not sure how you can get it to work with Server 2008 since I only played around with the files on Server 2012. I guess the solution should be similar but maybe in a different sub-folder. If you find a solution please let me know though and I’ll share it here in the comments.

      • Hello, I figured it out. The instructions are basically the same as above. Except there is no need to enter the command prompt commands (at least I didnt have to). Windows does state that the drivers are not Microsoft tested and signed do you want to install them anyways. I selected YES and they installed fine.

        What I did was use the above but for Server 2008R2, the drivers are in the NDIS62 folder and the driver name is ‘e1d62x64.inf’. AFter that its pretty much the same. Delete everything under Control Flags. I copied the last four lines under the AMD64.6.1.1 section and place them in the AMD64.6.1 section. I only did the last four lines because the ‘Hardware ID’ for mine was E15A0 as shown in the device manager under Device Resources. I guess this portion will vary from user to user and what motherboard they have. If you want to be sure for all mobo’s just copy the entire contents of Intel.NTamd64.6.1.1 down to the Intel.NTamd64.6.1 section.

  2. Hi have had no luck with getting the 1218V driver to install on a ASRock H97M Pro board running Windows Server 2012 R2 Essentials.

    The device shows up as PCI\VEN_8086&DEV_15A1&SUBSYS_15A11849 so I copied the appropriate lines in the file PRO1000\Winx64\NDIS64\e1d64x64.inf, created a new line to reflect the correct SUBSYS and attempted the install… it went on and even mentioned that the Intel 1218V driver being installed but then popped up a dialog stating that no intel adapter was found on the PC. Installing directly from device manager does a similar thing but states that “Windows found driver software for your device but encountered an error…. the hash for the file is not present in the specified catalog file. The file is likely corrupt of the victim of tampering” (and I did disable the integrity checks).

    In addition to deleting the three lines in control set, this is the section I copied and modified in the inf file:
    [Intel.NTamd64.6.3]

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

    Any ideas?

    • That’s weird as it is the same network chip. It might be that Intel updated the driver since then and changed something else. Check the release date of the version you are using. Other people reported it working if they followed my instructions exactly. Personally I haven’t touched the driver since I installed my server.

  3. Thank you so much for this tip!! I could not never have imagined that Intel would do such a stupid thing as willingly sabotage a driver installation like that and try to prevent you from installing OS A or OS B..WTF?

    I installed Windows 2008 R2, just edit the file ‘e1d62x64.inf’ but needed more lines from the section above or else I would get an error.

  4. THANK YOU!!

    I was searching for the problem for several hours and suspected a HW problem at first. Really stupid limitation by Intel!!

    The .inf file showed, in my case, more entries, than you have above. My file in the changed section looks like that:


    [Intel.NTamd64.6.3]
    ; 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
    %E15A2NC.DeviceDesc% = E15A2, PCI\VEN_8086&DEV_15A2
    %E15A2NC.DeviceDesc% = E15A2, PCI\VEN_8086&DEV_15A2&SUBSYS_00008086
    %E15A2NC.DeviceDesc% = E15A2, PCI\VEN_8086&DEV_15A2&SUBSYS_00011179
    %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
    %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
    %E15A2NC.DeviceDesc% = E15A2.6.3.1, PCI\VEN_8086&DEV_15A2
    %E15A2NC.DeviceDesc% = E15A2.6.3.1, PCI\VEN_8086&DEV_15A2&SUBSYS_00008086
    %E15A2NC.DeviceDesc% = E15A2.6.3.1, PCI\VEN_8086&DEV_15A2&SUBSYS_00011179
    %E15A3NC.DeviceDesc% = E15A3.6.3.1, PCI\VEN_8086&DEV_15A3
    %E15A3NC.DeviceDesc% = E15A3.6.3.1, PCI\VEN_8086&DEV_15A3&SUBSYS_00008086
    %E15A3NC.DeviceDesc% = E15A3.6.3.1, PCI\VEN_8086&DEV_15A3&SUBSYS_00011179

  5. Editing the INF is a great idea. However I was able to get everything working on a MSI Z97 MPOWER MAX AC with the Intel I218-V on board Network Chip by forcing it to use the Intel I218-LM version #2. It is working so far and even the unmodified Intel utility software installs fine. It just sees the forced installed I218-LM driver and moves on. Howe I did it is by using Device Manager and updating driver but then manually selecting Intel and manually selecting the I218-LM driver. It will complain that the driver isn’t compatible but proceed anyway. It will copy files and then should work immediately. After the install completes you can rerun the Intel driver install utility and it will succeed.

    • That is good to know! Thanks for your input. Were you able to modify the WoL settings in the drivers option window? Mine always crashed, so I had to use the powershell in order to modify any settings.

  6. I can confirm what MichaelS says, working on Asus ASUS Z97M-PLUS
    No fumbling around with inf files and powershell and shit, nice and cleean
    Thank you MichaelS!!! Very very happy

  7. Easiest code edit ever. Ive seen various versions of this technique and several of them I believe would result in a registry train wreck but this is spot on, took less than two minutes. Do not try other posted methods as I tried one to test my theory and had I not prepared for the possibility I would have lost everything.

  8. Thanks. This worked like a charm, even for a neophyte like me. WHS 2008 is installing like a charm on the Ausus 97Z motherboard.

  9. The tip manually selecting the Intel I218-LM driver worked also well for an Asus H81 Gamer on Windows Server 2016.
    Thanks for that to Michael!
    Best greetings from Germany
    Olaf

  10. I can confirm this work for the Intel i219v aswell. Just check your hardwareID in the device manager. Mine was 15B7

    You can find it 4x within the line:
    PCI\VEN_8086&DEV_15B7&SUBSYS_805D103C

    After the DEV_ is your version. Delete control flags as described above. Then under Intel.NTamd64.6.1.1 search for your version and copy these lines. For me it was:

    %E15B7NC.DeviceDesc% = E15B7.6.1.1, PCI\VEN_8086&DEV_15B7
    %E15B7NC.DeviceDesc% = E15B7.6.1.1, PCI\VEN_8086&DEV_15B7&SUBSYS_00008086

    Paste them somewhere under Intel.NTamd64.6.1

    Regards,
    JohnDoe

  11. I have just installed Windows Server 2016 with my ASUS Z97 Pro. I had some trouble at first with your desciption because i just didn’t work.
    I solved it with not editing the NDIS64 Folder but insteed i changed the NDIS65 Folder. That was the solution. Now everything works fine.

    Thanks a lot for getting me started in the right direction

Leave a Reply

Your email address will not be published. Required fields are marked *