Hyper-v Drivers Windows Server 2008

[Anita Damelio]

Ihave an Intel NUC6i5SYH with I219-V gigabit Ethernet and discovered that the Intel Ethernet driver installs and runs with Windows 10, but not with Windows Server 2012 R2 or Windows Server 2016 OS. In looking for Intel Ethernet drivers on the downloadcenter.intel.com website, I found driver package 21.0 that lists support for both I219-LM and I219-V, but actual driver installation testing indicates that for Windows Server 2012 R2 and Windows Server 2016 OS, the e1d65x64.sys driver only installs against I219-LM but not I219-V.

Will Intel please clarify the support position of your Ethernet drivers for I219-V and Windows Server 2012 R2 and Windows Server 2016. If the drivers have no support for this HW/OS combination then a correction is in order for the downloadcenter.intel.com website, as the information on it currently is misleading.

The list under "This download is valid for the product(s) listed below" shows both I219-LM and I219-V. Since Windows Server OS are not supported with I21x-V, the presence of I219-V on this list looks like a mistake.

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.

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.

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.

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.

Guys! All these "LAN driver not supported on server" issues are easily solved by "hacking" the corresponding code-base driver ie Windows 7 driver for 2008, Windows 8 driver for 2012, Windows 10 driver for 2016, respectively.

The procedure is for a 4-gen NUC and Hyper-V server, and running the BCD edit commands. But with Windows server, all you have to do is do all the same steps, then have Device Manager browse to the hacked driver and you're good to go.

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.

Intel does not verify all solutions, including but not limited to any file transfers that may appear in this community. Accordingly, Intel disclaims all express and implied warranties, including without limitation, the implied warranties of merchantability, fitness for a particular purpose, and non-infringement, as well as any warranty arising from course of performance, course of dealing, or usage in trade.

"Windows cannot verify the digital signature for the drivers required for this device. A recent hardware or software change might have installed a file that is signed incorrectly or damaged, or that might be malicious software from an unknown source. (Code 52)"

I can get it working by disabling driver signature verification, but I really don't want to do that as this is a security related server. I have multiple other VMs running extremely similar configurations, at the guest and OS level, in the cluster, all of which are fully patched, none of which have any issues.

I really don't want to have to reinstall and reconfigure, especially if this is caused by some particular configuration on the VM which will make this occur again. Reinstalling means I need to reconfigure not only the server, but a bunch of the clients that depend on it as its certificate will change.

I took a Snapshot of the VM, and replace that 7 files, which were not signed, from another VM with same IS version. The file version on the affected server was wrong, but if i try to update the IS, it told me that it'S up to date.

I recently needed to reproduce a customer issue in my lab environment. My lab is a Windows 10 workstation with the Hyper-V role installed. Part of reproducing the issue involved building out a Windows Server 2012 R2 Foundation virtual machine. I figured this would not be a problem as 2012 R2 runs fine as a virtual machine. This was not the case though. I ran into a major hurdle with the integration tools. I will describe the process I went through to get a Windows Server 2012 R2 Foundation virtual machine running smoothly.

Now before anyone goes out and tries the below procedure for a production system, please understand that running Foundation edition as a virtual machine is not supported by Microsoft. Also it will likely violate the EULA (End User License Agreement). Typically Foundation edition is only sold with an OEM license. That means it comes pre-installed on hardware and must remain on that hardware. So in order to do this, and not violate the EULA, a non-OEM license is required. I have a MSDN subscription and thus have a valid license. Additionally, I am not running the server for any type of production workload.

I started the process by creating a generation 2 VM (virtual machine). Unfortunately I found out this will not work as the VM bugchecked during setup. I deleted that VM and created a generation 1 VM. I was then able to get the Windows loaded. This is when I discovered the major hurdle I mentioned above. The VM responded very slowly to mouse and keyboard input. I also noticed severely degraded performance. This was to the point of the VM almost being unusable. The VM behaved as if none of the integration services drivers were installed. Unfortunately Windows 10/2016 do not have the option to insert the integration disk. I was able to get the vmguest.iso from a 2012 R2 hyper-v host. However when I tried to run the setup I was informed that the latest integration services were already installed.

At this point I realized this was not going to be easy, but I enjoy a challenge. I browsed the vmguest.iso inside the Foundation VM. I extracted the following file: D:\support\amd64\Windows6.2-HyperVIntegrationServices-x64.cab. I then went into device manager. I noticed quite a few, a dozen or so, unknown devices.

I then tried to manually load the drivers from the extracted cab file. While the driver was found, it was not signed. I figured no sweat, just disable driver signing requirement in the BCD (Boot Configuration Data). Yet another roadblock. It is no longer possible to permanently disable driver signature enforcement. I was able to boot into driver signature enforcement disabled mode. I then manually loaded drivers for all the Unknown devices. This corrected the input and performance issues, at least for that boot. Booting into normal mode caused all the issues to return.

Getting the drivers to load each time Windows booted was the final step in getting the virtual machine to run properly. I looked into the bcdedit command line options and was not able to find an option to boot to driver signing disabled mode. What I ended up doing was to add a dummy entry to the boot list and set the timeout to 30 seconds with the following commands.

With drivers loaded, I restarted the server (probably not necessary but I wanted to ensure that all services were running) and Hyper-V Server recognised the network card, allowing me to make configuration changes if required.

I built a couple hyper-v servers for experimentation using ASUS p5k pro motherboards with 8 gigs of ram and a quad core Q6600 processor. (Great bang for your buck/pound/euro/pickyourcurrency :-) ) Anyway, they have marvell 1-Gig network cards plus I have other PCI-e Marval NICs too. Now they all work like they should have.

A few months back, Microsoft apparently implemented a HyperV function called GPU-P (More a less an early release) into Windows 10 Pro/Enterprise (1903 - 20H1) and possibly Windows Server 2016, 2019, and 2022 (People reported errors on server OS versions. Check back on these when more major server platform updates hit). Windows 11 looks to be a Go for this as well for the Pro/Enterprise editions as well, I believe same setup process will work, Let me know if changes or additions need to be made for this edition of Windows.

This is a replacement to the Legacy GPU RemoteFX which allowed the ability to pass through GPU acceleration to HyperV VMS. With GPU-P, this will allow you to partition different functions of a physical GPU (can be an enterprise or consumer card). I do not believe that this is considered SR-IOV, it can at least give us a somewhat realistic expectation of what to expect if we partition a GPU from the GTX Series to the RTX series of GPUS. AMD Cards work as well.

From What I can tell (feel free to correct me cause my sources are limited) we are sharing a GPU driver from the Host computer to give the VM a driver to use to bypass the code 43 error for any GPU. Apparently, it works with Nvidia drivers that came out before the VM passthrough enablement. When setting up the drivers, you can enable different kinds of functions (Cuda, NVENC, etc) Currently, This should enable NVENC encoding and Cuda support for applications with the DLLs listed below. If the DLLs are missing for what you need, you will be able to search your System32 folder to locate the right DLLs.

3a8082e126