LABDEMO

Intel NUC D54250WYKH: Installing LAN Driver on Windows Hyper-V Server 2012 R2, Windows Server 2016 and Windows Server 2019

Updated: These steps still applies in installing NIC drivers on Windows Server 2016 and Windows Server 2019 The Intel NUC are very handy when you need a portable Windows lab environment (most geeks do need it) and recently I got an Intel NUC D54250WYKH  and installed Windows Hyper-V Server 2012 R2 but after the installation I got a…

Jay-R Barrios
2–3 minutes
, , , , , ,

Updated: These steps still applies in installing NIC drivers on Windows Server 2016 and Windows Server 2019

Intel® NUC Kit D54250WYKH

The Intel NUC are very handy when you need a portable Windows lab environment (most geeks do need it) and recently I got an Intel NUC D54250WYKH  and installed Windows Hyper-V Server 2012 R2 but after the installation I got a prompt that no network adapter present in my computer where it should be the Intel (R) Ethernet Controller I218. Windows Server simply doesn’t detect it, I install Windows 10 Technical Preview on my other NUC and it has no issues with the network device. So search over the net and found out that Intel is not supporting Windows Server 2012/R2s on NUC but there’s always a workaround. If found these links and followed the instruction and got it working.

Reference links:

Here are the steps I did:

  1. Download this driver https://downloadcenter.intel.com/Detail_Desc.aspx?DwnldID=24198&lang=eng&ProdId=3744

File name: LAN_Win8.1_64_PROWin_19.3.exe

Version: 19.3 (Latest

Date: 08/15/2014

Size: 33.2 MB

Language: Multi language

Operating Systems: Windows 8.1, 64-bit*

  1. Extract the installer using winrar (I extracted it in C:\Temp)
  2. Once extracted, go to this directory C:\Temp\lan_win8.1_64_prowin_19.3\PRO1000\Winx64\NDIS64 and open e1d64x64.inf

Open and edit e1d64x64.inf

  1. Edit the e1d64x64.inf file

-remove the 3 lines under the [ControlFlags]

Edit e1d64x64.inf

copy the highlighted part and paste it under:

“%E15A2NC.DeviceDesc%            = E15A2,       PCI\VEN_8086&DEV_15A2&SUBSYS_00011179”

EditInf03

  1. Save the inf file.
  2. Copy the NDIS64 folder to your usb and plug it in your NUC

  1. In your hyper-v server run the following
  • bcdedit /set LOADOPTIONS DISABLE_INTEGRITY_CHECKS
  • bcdedit /set TESTSIGNING ON
  • bcdedit /set nointegritychecks ON

and Reboot the server shutdown /r /t 0

  1. install the driver using pnputil –i –a D:\NDIS64\ e1d64x64.inf

Installing Driver in Hyper-V

A Windows security warning will pop-up, click Install this driver software anyway.

You should see something like this in the command prompt:

Processing inf : e1d64x64.inf

Successfully installed the driver on a device on the system.

Driver package added successfully…..

  1. Switch the Driver Enforcement back on, run the following command
  • bcdedit /set LOADOPTIONS ENABLE_INTEGRITY_CHECKS
  • bcdedit /set TESTSIGNING OFF
  • bcdedit /set nointegritychecks OFF
  1. Reboot your NUC Hyper-V server and you’re all set.

This workaround can also be applied to Windows Server 2012 R2 Update.

If you’re keen in building a portable data center with Intel NUCs check this post: http://deploymentbunny.com/2014/09/28/building-next-gen-datacenter-the-pelicase-portable-datacenter/

71 responses to “Intel NUC D54250WYKH: Installing LAN Driver on Windows Hyper-V Server 2012 R2, Windows Server 2016 and Windows Server 2019”

  1. Miguel Angel Avatar
    Miguel Angel

    Check again. I can see a new driver for Windows Server 2012 “LAN_Server2012R2_64_19.5.exe”

    Reply
  2. Chris Avatar
    Chris

    Thanks for the writeup! Despite Intel releasing a driver for 2012 R-2, I was getting the same errors. I followed your instructions and now the NUC is on-line.

    Reply
  3. keithga Avatar
    keithga

    Some adjustments to your example above, turns out that you forgot one entry for my 153b.

    All you need to do is to copy the [Intel.NTamd64.6.3.1] section to notepad.exe and replace all instances of “.6.3.1,” with “,” then copy that section to [Intel.NTamd64.6.3] The advantage is that we use the correct DDInstall Section for server rather than for workstation.

    %E1559NC.DeviceDesc% = E1559.6.3.1, PCI\VEN_8086&DEV_1559
    should be:
    %E1559NC.DeviceDesc% = E1559, PCI\VEN_8086&DEV_1559

    Full example at: https://onedrive.live.com/redir?resid=5407B03614346A99%21124500

    Reply
    1. rickhantz Avatar
      rickhantz

      I’m installing 2012se, first edition (not R2). Followed all the steps. It says it installs successfully and driver package added.. Device Manager still shows no driver installed, even after reboot. I am using the D54250WYKH. It runs Win10Pro just fine, with inbox drivers, so I know the NIC is good. I did pull the drivers off the Win10 install using dism, but I’m betting they won’t work with Server 2012. I guess I’ll try.

      Reply
      1. rickhantz Avatar
        rickhantz

        Dam, on Win10, the net driver is Inbox, not oem, so its not exported.

      2. rickhantz Avatar
        rickhantz

        setupapi.dev shows success, no errors. Do I need to modify a different inf file for 2012se?

      3. rickhantz Avatar
        rickhantz

        Read further, and used NDIS63 for Server 2012. Still no errors, but no functioning NIC.

      4. rickhantz Avatar
        rickhantz

        Cut and paste error. Working now. Table below gave me a clue.

        Then the Network Driver Interface Specification (NDIS) that matches our OS, for reference:
        Version Desktop OS Server OS
        NDIS 6.0 Vista *
        NDIS 6.1 Vista SP 1 Server 2008
        NDIS 6.2 Windows 7 Server 2008 R2
        NDIS 6.3 Windows 8 Server 2012
        NDIS 6.4 Windows 8.1 Server 2012 R2

      5. jay Avatar
        jay

        Glad to here that! I’ve recently installed Server 2016 in my NUC. I had to use the Win 10 driver.

  4. Brad Avatar
    Brad

    I have the original Intel NUC (Celeron 847) I have been unable to find a write-up explaining how to do this for that particular NUC. I decided to try this. I will say that the intel lan driver for the Celeron NUC has the exact same files as listed in this example. I followed the directions to the letter, and the driver installed correctly, but still the same problem…..No active network adapters found.

    Any suggestion’s?

    thanks

    Reply
    1. keithga Avatar
      keithga

      Verify that the driver installed correctly by reviewing the c:\windows\inf\setupapi.*.log files. Either it will report it installed or not. Also verify that the device is running correctly in the device manager. Then it’s a matter of basic network troubleshooting: Is the lan cable plugged in, is your DHCP server up? etc…

      If you are still having problems, post logs and output showing your work.

      Reply
      1. Brad Avatar
        Brad

        Thanks for the quick response! I will do that and get back to you. Its 12:20am in my local…no more playing with hyper-v tonight, time for bed 🙁

      2. Brad Avatar
        Brad

        Well, I finally got back to working on this. I decided to re-install hyper-v server 2012 R2 and try again. This time, when I attempt to install the inf file, pnputil comes up with an error saying: adding the driver package failed : the system cannot find the file specified.

        I have made sure that I am pointing to the correct location, but no matter what, same error every time.
        Any ideas?

        Thanks
        Brad

      3. Brad Avatar
        Brad

        Ok, finally got it figured out! My NUC (intel Celeron 847) has a different nic than the newer nuc’s. Mine has a Intel 82579V. Basically, everything is the same, except the file you modify is e1c64x64.inf

  5. Stefan Avatar
    Stefan

    Does this also count for the intel nuc i3? D33217 series? I tried it but still no network card, i do it with a gui version of windows server 2012 r2

    Reply
    1. keithga Avatar
      keithga

      Sorry, has nothing to do with Server Core vs Server GUI, neither work with intel drivers.

      Reply
      1. Stefan Avatar
        Stefan

        So i have bad luck with this one 😔 well never asked never known! Thanks for replying.

    2. Chris Avatar
      Chris

      I got my i3 working (posted a comment below) the ID for me was E15A3 instead of E15A2, so I had to find the relevant sections from the “desktop” OS for A3 and copy them into the “server” section

      Reply
  6. Article: CAPS v4 Maroubra and Bundoran – Page 2

    […] WS2012 I recommend the micro ZUMA. Actually yes you can. Here is a like to the work around. Intel NUC D54250WYKH: Installing LAN Driver on Windows Hyper-V Server 2012 R2 | JDeployment Reply With […]

    Reply
  7. 2012R2 Core and Hyper-V on Intel Nuc | Some Downtime

    […] Ethernet Adapter (you will need to modify the driver to allow installation on Windows Server 2012 R2, follow these steps) […]

    Reply
  8. Alex Avatar
    Alex

    Excellent post! Thinking of purchasing a NUC 5i5 for Hyper-V hosting with Win2012R2. Does anyone know if this “procedure” works for the 5i5RYH? Don’t want to be limited to Wifi connection and could use the information before buying it.

    Reply
  9. Rick Manion Avatar
    Rick Manion

    Worked like a charm, thanks!

    Reply
  10. telexen Avatar
    telexen

    I couldn’t get this to work at all with the 5i5RYK. I know it’s a different generation, so it’s entirely possible it uses one of the other LAN controllers.Using bcdedit went fine, even popped up the driver warning, but the driver still wouldn’t install.

    Has anyone else with the current generation NUC managed to get this to work?

    Reply
  11. abud Avatar
    abud

    Hello.. This is a good Intel NUC.. and Good Article, as I also looking for this product. However, I want to ask whether the offering price from http://www.itosa.co.id/

    Is good enough or not ? please kindly advice me, Thank You

    Reply
  12. Harley Jensen Avatar
    Harley Jensen

    This is brilliant. I did it on my brand new NUC5i7RYH and it just worked. Thank you so much for sharing.

    Reply
  13. Shailesh M Avatar
    Shailesh M

    This is sweet, thanks for sharing!

    Reply
  14. Bret Miller Avatar
    Bret Miller

    Thanks for taking the time to publish this post. It worked perfectly for me. My NUC is online with 2012R2 🙂

    Reply
  15. schlivo Avatar
    schlivo

    Thanks,

    Worked with Hyper-V Core 2016 preview on NUC5i7RYH with Windows 10 x64 drivers
    Just follow the same steps but use e1d65x64.inf file located in NDIS65 folder

    Cheers

    Reply
  16. Alex Avatar
    Alex

    Thanks, for your excellent post:
    i just purchase a awesome NUC5i7RYH and I followed your directions.
    But after running pnputil -i -a D:\NDIS64\e1d64x64.inf. — CMD returns the error — “Adding the driver package failed: The hash for the file is not present in the specified catalog file. The file is likely corrupt or the victim of tampering” I plan on running the nuc/server at my house..
    Any assistance would be greatly appreciated..

    Reply
    1. jay Avatar
      jay

      Hi Alex, thanks for the comment, just want to check, have you run CMD as Administrator?

      Reply
      1. Alex Avatar
        Alex

        Thanks Jay, for your response, Yes. I did run CMD as Administrator.

  17. Peter Avatar
    Peter

    TY good post

    Reply
  18. Halloween, Allerhelgen og Intel NUC – IHD Blog

    […] kan læse en fin beskrivelse af hvordan du retter e1d64x64.inf filen eller også kan du hente den jeg har rettet til her og kopiere den ind […]

    Reply
  19. Rax Avatar
    Rax

    Hi I am trying to install the LAN drivers on NUC5I7RYH, I cannot find LAN_Win8.1_64_PROWin_19.3.exe drivers, only can get LAN_Win8.1_64_PROWin_19.1.exe. Tried to carry out the same steps but failed. Any ideas where I can get LAN_Win8.1_64_PROWin_19.3.exe or a work around for the current driver I have.

    Cheers

    Reply
    1. jay Avatar
      jay

      https://downloadcenter.intel.com/download/23071/Network-Adapter-Driver-for-Windows-8-1-

      Reply
  20. Running Windows Server 2016 CTP4 on an Intel NUC 5i5RYH – sqlbrander-nl

    […] blog post of Jay about running Windows Server 2012 R2 on an Intel NUC 54250WYKH and the problems with the […]

    Reply
  21. Tuomas Avatar
    Tuomas

    Thank you! I used your instructions and the driver installed..

    Reply
    1. jay Avatar
      jay

      Glad to hear that 🙂

      Reply
  22. Installing Windows 2012 R2 Datacenter on NUC5i3RYH | calmdownpony

    […] a […]

    Reply
  23. Hyper-V 2012 R2 on an Intel NUC (NUC5i7RYH) – Luke.Geek.NZ

    […] Thanks to an article written by Jay “Intel NUC D54250WYKH: Installing LAN Driver on Windows Hyper-V Server 2012 R2” for a lot of assistance in getting this going, was able to easily adapt it for the […]

    Reply
  24. Adewale Avatar
    Adewale

    Please am trying to install it on my desktop. and will also install on VHD later. Can i follow the same steps?

    Reply
  25. Chris Avatar
    Chris

    So this stumped me for a bit on my NUC5i3RYK (or NUC5i3RYH) with Server 2016 Tech Preview 4.

    The Intel NIC is E15A3 (not E15A2). I used NDIS 6.5 (NDIS65 folder)

    The key was undersanding that you need to copy the sections from the “desktop” OS to the “server” OS
    http://www.ivobeerens.nl/2012/08/08/enable-the-intel-82579v-nic-in-windows-server-2012/

    This (probably) is in addition to removing the blocks in the ControlFlags suggestion (I did this step)

    This way I took the Windows 10 lines, compared them to the Server 2016 lines and added the missing ~4-6 lines. After that BOOM it worked great!

    Thanks everyone!

    Reply
  26. Intel NUC: Installing LAN Driver on Windows Hyper-V Server 2012 R2 | ADMINISAURUS.COM

    […] Intel NUC D54250WYKH: Installing LAN Driver on Windows Hyper-V Server 2012 R2 […]

    Reply
  27. Mike Doherty Avatar
    Mike Doherty

    Simple work-around:

    I have had success by simply manually installing the Intel(R) 82580 Gigabit Network Connection driver… seems to work just fine.

    I am using the 82580 driver on Windows Server 2016 TP 5 on a NUC5i3RYK as I post…

    Hope that helps.

    Mikrodots, Inc.

    Reply
    1. Khismet Avatar
      Khismet

      Thanks for this post – that’s got my Server 2012 install on a D54250WYK communicating with the world

      Reply
  28. Jake Avatar
    Jake

    I can’t get this to work in Hyper-V server 2012r2. It works flawlessly in 2012R2 w/ GUI >_<
    I don't understand what the difference is

    Reply
  29. Daniel Avatar
    Daniel

    Probably a stupid question (as I don’t quite understand Hyper-V), but would these instructions still work if I’m just installing Windows Server 2012 R2 as a normal OS?

    I’ve ordered a NUC but only discovered after it was bought that Intel doesn’t support Server on it.

    Reply
    1. jay Avatar
      jay

      Yes this still works, but you will need the latest driver from Intel. Recently my friend bought NUC and installed Windows Server 2012 R2 and applied the same steps for the network adapter to work.

      Reply
  30. Installing the LAN Driver on Windows Hyper-V Server 2012 R2 on an Intel NUC 5i3RYH | PowerBiz Solutions

    […] well, but the LAN drivers would not install. Using information from the following two websites (https://jayrbarrios.com/2014/11/19/intel-nuc-d54250wykh-installing-lan-driver-on-windows-hyper-v-ser&#8230; and https://foxdeploy.com/2013/09/12/hacking-an-intel-network-card-to-work-on-server-2012-r2/), I […]

    Reply
  31. Graham Avatar
    Graham

    Do you know if in Hyper V 2012 there’s anyway to force a specific model of the network adaptor?
    In Server 2012 this method doesn’t seem to work for me however if I go through a manual driver selection, then choose disk, I’m able to select the correct item and install the card. Using pnputil -i -a won’t work for me in Hyper-V

    Thanks and appreciate the guide so far

    Reply
  32. rt Avatar
    rt

    Thank You for this article, it worked for Windows Server 2012 R2. My NUC5i5RYH now has network connectivity.

    Reply
    1. jay Avatar
      jay

      Great hear that 🙂 glad you found this blog helpful. Thank you, for your feed back.

      Reply
  33. Jessy Avatar
    Jessy

    +1
    Thank you for this article. It helps!
    It ‘s worked for me with NUC6I5SYH. But I had to add few lines in the copy from “4.” section above :

    %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
    %E156FNC.DeviceDesc% = E156F.6.3.1, PCI\VEN_8086&DEV_156F
    %E156FNC.DeviceDesc% = E156F.6.3.1, PCI\VEN_8086&DEV_156F&SUBSYS_00008086
    %E156FNC.DeviceDesc% = E156F.6.3.1, PCI\VEN_8086&DEV_156F&SUBSYS_00011179
    %E1570NC.DeviceDesc% = E1570.6.3.1, PCI\VEN_8086&DEV_1570
    %E1570NC.DeviceDesc% = E1570.6.3.1, PCI\VEN_8086&DEV_1570&SUBSYS_00008086
    %E1570NC.DeviceDesc% = E1570.6.3.1, PCI\VEN_8086&DEV_1570&SUBSYS_00011179

    instead of :

    %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

    Thanks again.

    Reply
    1. Goran Avatar
      Goran

      in which map and which folder did you make those changes? i have the same nuc but it doesnt work 🙁
      and which drivers did you use? tnx in advance 🙂

      Reply
      1. Jessy Avatar
        Jessy

        Hi,

        1. Install Win 2012 R2
        2. Follow the “Installing LAN Driver on Windows Hyper-V Server 2012 R2” above with :
        – LAN_Win8.1_64_21 driver
        – My modification in order to add DEV_1570 section
        ==> The network card appears in Network Connections window.
        3. Add Hyper-V role

      2. Goran Avatar
        Goran

        tnx working 🙂

  34. Philipp Avatar
    Philipp

    Has anyone gotten the network driver of an Intel NUC5PPYH to work in Windows Hyper-V Server 2016 (standalone)?
    It has a realtek NIC (RTL8168/8111), but the driver from the Intel website to work:-(

    Reply
  35. Stefan Avatar
    Stefan

    This also applies to Windows Hyper-V server 2016!

    Reply
    1. jay Avatar
      jay

      Cool! thanks for confirming 🙂

      Reply
  36. cosmao Avatar
    cosmao

    thank you very much for your solution. I’ve W2012 R with lan driver ON 🙂

    Reply
  37. Install the LAN driver and Wifi – Intel NUC 7th Gen Server 2012 R2 | Shin's Blog

    […] The steps are an enhancement to those documented here by Jay-R Barrios:http://jayrbarrios.com/2014/11/19/intel-nuc-d54250wykh-installing-lan-driver-on-windows-hyper-v-serv&#8230; […]

    Reply
  38. Mick Avatar
    Mick

    Hi! Trying to get this to work with a NUC W34010WYK but don’t know which the correct inf file is. Any help would be appreciated.

    Reply
  39. John Avatar
    John

    These instructions were helpful for getting the older driver to work. Although I did not understand exactly what the modifications were doing, I followed the instructions perfectly, and it worked successfully. Alternatively, it looks like the most recent networking driver for several NUC models, including mine, has support for Windows Server 2012/R2, even though the driver is labeled as if it is only for Windows 8.1. This is the one I mean: “Intel(R) Network Connections Software Version 22.6” dated Oct. 27, 2017. Take a look at the file with “Release Notes” and you’ll see plainly it was intended also for Windows Server 2012. I installed it on my NUC running Windows Server 2012 R2 without any problems, replacing the older driver from this example, and it appears to be working just fine.
    However, that brings me to another point, which is related to the problem created with the earlier driver. First of all, using an unsigned driver, especially a prominent networking driver, creates a security hole for malware to exploit. Also, the Secure Boot functionality enabled in the BIOS cannot work properly with unsigned drivers installed, if I am not mistaken.
    Additionally, having used the technique of this article originally, even though I have since replaced that driver with the newest one, there appears to be a remnant of that process affecting my machine. I am not technically savvy enough to know how to remove the problem at this point.
    When I look at the network adapter’s Properties page and Driver tab, it shows “Digital Signer: Not digitally signed.” Then, in Driver Details, I can see four files listed, one of which is “C:\Windows\system32\e1d64x64.din”. It shows Unknown for Provider, File version, and Copyright. Actually, I was expecting this new driver to completely replace that old one as well as the unsigned file condition. I am concerned about the security effects, but I do not know how to fix this issue. Any ideas would be welcome. Thanks.

    Reply
  40. mamafunny Avatar
    mamafunny

    Can this method use on windows server 2008 r2?

    Reply
  41. Chris Avatar
    Chris

    Thank you! Just made this work with Server 2016, you totally saved my a$$.

    Reply
    1. jay Avatar
      jay

      Hi Chris, good to know 🙂

      Reply
  42. John Avatar
    John

    THANK YOU!!!!

    Reply
  43. Deploying Windows Server 2012 R2 to Intel NUC devices using MDT 2013 – Deployment Research

    […] Modify the e1d64x64.inf file per Jay-R Barrios instructions in his post: Intel NUC D54250WYKH: Installing LAN Driver on Windows Hyper-V Server 2012 R2 […]

    Reply
  44. Anand Shah Avatar
    Anand Shah

    hi,

    This procedure also works for windows server 2019 (GUI)

    Yet to test on core (should work mostly, as pnputil runs on core too…)

    Reply
    1. Anand Shah Avatar
      Anand Shah

      The link to the intel software drivers for windows server 2019 is at

      https://downloadcenter.intel.com/download/28396/Intel-Network-Adapter-Driver-for-Windows-Server-2019-?product=71305

      Reply
  45. Installing Network Drivers on Hyper-V with Intel I211-AT Network Adapter | NotWeasel

    […] He didn’t seem to resolve it, but pointed me to this guy, who got Intel drivers working for a different unsupported network adapter:https://jayrbarrios.com/2014/11/19/intel-nuc-d54250wykh-installing-lan-driver-on-windows-hyper-v-ser&#8230; […]

    Reply

Leave a Reply to Hyper-V 2012 R2 on an Intel NUC (NUC5i7RYH) – Luke.Geek.NZCancel reply

Trending

Discover more from LABDEMO

Subscribe now to keep reading and get access to the full archive.

Continue reading