Can't install Intel NIC Drivers

[Circuit_Bored]

I've got a media server that is running on an Asus x79 Deluxe motherboard (http://bit.ly/2mxlC69). It was running Windows Server 2012, but I recently updated to Windows Server 2016. I'm now running into an issue where I'm not able to install the drivers for the integrated Intel Gigabit Network Adapter, specifically Intel® 82579V. I've downloaded the Windows 10 drivers direct from Asus, but when I try to install them it tells me it's not compatible with the OS:

 

 

I've also downloaded the Windows Server 2016 driver directly from Intel. But when I try to install that one, it says there's no Intel hardware installed:

 

I do vaguely remember having to use the second option to get the drivers installed when I set up the server on Windows Server 2012 before, but this issue is beyond me now. Any help that can be offered would be appreciated.

 

[zMeul]

try these:

21.1: https://downloadcenter.intel.com/download/26594/Intel-Network-Adapter-Driver-for-Windows-Server-2016-?product=47549

22.0.1: https://downloadcenter.intel.com/download/26092/Ethernet-Intel-Network-Adapter-Driver-for-Windows-Server-2016-

 

but I don't the see the 82579V listed 

Edited March 16, 2017 by zMeul

[bcguru9384]

for whatever reason the installer is not reading the correct firmware .ini file or file just missing

seen this with windows me years ago note winme was great os after dedefaulted system

auto programing 2 least used commands

store=active makes new settings be whats called/used

store=persistent saves settings to be used thru reboots

any time system changes setting

like in irq's dhcp or upnp like allocation irq address space new table needs the store=active

or autoconfig must go thru full test method used to make new timings

 

[Circuit_Bored]

7 minutes ago, zMeul said:

the 82579V is old enough that WS 2016 should have already support in the OS

Unfortunately it's not:

 

And I don't know why. If I tell Windows to search for a driver, it comes up with nothing...

[zMeul]

Just now, Circuit_Bored said:

Unfortunately it's not:

edited the previous post

also try to point the device manager to the driver directory manually

[Circuit_Bored]

8 minutes ago, zMeul said:

edited the previous post

also try to point the device manager to the driver directory manually

I got the same result with both of your suggested downloads...  And I forgot to mention in my original post that I've also tried to point device manager to the directory manually.

[zMeul]

2 minutes ago, Circuit_Bored said:

I got the same result with both of your suggested downloads...  And I forgot to mention in my original post that I've also tried to point device manager to the directory manually.

last resort you could try and pick manually from the list

[Circuit_Bored]

2 minutes ago, zMeul said:

last resort you could try and pick manually from the list

No dice there either: 

 

I don't think it likes the self-extracting archive that the driver comes as. I can using the same dialog box manually select a driver, but the specific device isn't listed:

 

Is it possible that one of these might work? Even though it's not the exact model?

[0x1e]

2 minutes ago, Circuit_Bored said:

<Snip>

Is it possible that one of these might work? Even though it's not the exact model?

It should, but you may not have full functionality. It's worth a shot.

[zMeul]

Just now, Circuit_Bored said:

Is it possible that one of these might work? Even though it's not the exact model?

you can try, but dunno what's the diff between V and LM versions

[Circuit_Bored]

Well, it shows up now and is getting an IP:

 

And it has allowed me to create the NIC team that I was wanting to make. Thanks for the help guys!