<div>
If you can find a Windows 8 x64 driver for any of the above NICs, they should function fine.
</div>


If you can find a Windows 8 x64 driver for any of the above NICs, they should function fine.

<div>
It's pointed me in the right direction. &nbsp;Thanks<br />
<br />
I did provide a detailed response but it seems to have disappeared into the ether.
</div>


It's pointed me in the right direction.  Thanks

I did provide a detailed response but it seems to have disappeared into the ether.

<div>
<div class="content wysiwyg-content">
I've loaded Windows Server 2012 R2 Update Standard onto a Gigabyte &quot;GA-X99-<br />
Gaming G1 WIFI&quot; motherboard based system for use as a light duty Hyper-V server. &nbsp;<br />
<br />
The O/S &amp;&nbsp;Hyper-V run ok except that the O/S doesn't recognise either of the two 1000 Mb on-board Ethernet chips; a Qualcomm Atheros Killer E2201 and an Intel GbE. &nbsp;<br />
Neither chip supports Windows Server 2012. &nbsp;<br />
Drivers downloaded from the chip manufacturers also fail with errors indicating &quot;unsupported operating system&quot; or similar.<br />
I installed a D-Link DWA-182 Wireless dongle that supports Windows 8.1 but it failed with a &quot;missing WLANAPI.DLL&quot; error. <br />
<br />
Is there a way to force connectivity in this system?<br />
Thanks
</div>
</div>


I've loaded Windows Server 2012 R2 Update Standard onto a Gigabyte "GA-X99-
Gaming G1 WIFI" motherboard based system for use as a light duty Hyper-V server.  

The O/S & Hyper-V run ok except that the O/S doesn't recognise either of the two 1000 Mb on-board Ethernet chips; a Qualcomm Atheros Killer E2201 and an Intel GbE.  
Neither chip supports Windows Server 2012.  
Drivers downloaded from the chip manufacturers also fail with errors indicating "unsupported operating system" or similar.
I installed a D-Link DWA-182 Wireless dongle that supports Windows 8.1 but it failed with a "missing WLANAPI.DLL" error. 

Is there a way to force connectivity in this system?
Thanks

Windows Server 2012 R2 Ethernet connectivity

The Windows operating systems have distinct methodologies for designing and implementing networks, and have specific systems to accomplish various networking processes, such as Exchange for email, Sharepoint for shared files and programs, and IIS for delivery of web pages. Microsoft also produces server technologies for networked database use, security and virtualization.

Windows Networking

Networking hardware includes the physical devices facilitating the use of a computer network. Typically, networking hardware includes gateways, routers, network bridges, modems, wireless access points, networking cables, line drivers, switches, hubs, and repeaters. But it also includes hybrid network devices such as multilayer switches, protocol converters, bridge routers, proxy servers, firewalls, network address translators, multiplexers, network interface controllers, wireless network interface controllers, ISDN terminal adapters and other related hardware.

Networking Hardware-Other

Servers are computing devices that are similar to desktop computers in that they have the same basic components, but are significantly different in size, configuration and purpose. Servers are usually accessed over a network, and many run unattended, without a computer monitor, input device, audio hardware or USB interfaces. Many servers do not have a graphical user interface (GUI), and are configured and managed remotely. Servers typically include hardware redundancy such as dual power supplies, RAID disk systems, and ECC memory, along with extensive pre-boot memory testing and verification. Critical components might be hot swappable, and to guard against overheating, servers might have more powerful fans or use water cooling.