Hello Here are my system specs: Windows 7 x64 and Asus X99-A II which has I218-V chipset and I’d like to install the lastest / most suitable drivers for it.
My mainboard’s webpage has Intel Gigabit Ethernet Driver in two versions: 20.5.51.0 for my Windows 7 and 20.5.150.0 for Windows 10.
I couldn’t find any of them on official Intel’s webpage to compare - closest numbers I’ve found were v20.4.1 and v20.7 and when I click on any of them they points to v22.7.1 as "the latest one": https://downloadcenter.intel.com/downloa…r-for-Windows-7-
Question 1: Is v22.7.1 right one for my system? Or should I install these v20.5.X.X from my mainboard webpage?
Question 2: Is v22.7.1 better or worse than previous one, v22.6? I noticed that latest versions aren’t always "the best one" as it was posted here:
@Lex : First of all you should not mix the versions of Intel’s All-in-One Ethernet Packages incl. installer named “Intel Ethernet Connection CD” (latest version: 22.7.1, relased in September 2017) and the version of the included Intel Ethernet drivers themselves (latest version: 12.15.25.6712 dated 07/12/2017).
Yes, but you don’t need the 343 MB sized complete “Intel Ethernet Connection CD” v22.7.1, but just the included 370 KB sized Win7 x64 driver v12.15.25.6712. To make it as easy as possible for you, I have attached it. By the way: I do not recommend to install the much older driver, which is still offered by your motherboard manufacturer. These Companies usually do not test all the latest drivers with older mainboards.
According to my own experiences with my Z170 system these latest Intel Ethernet drivers are the best for modern Intel chipset systems.
Ah, ok, I didn’t quite get it before but I understand now: v22.7.1 is the latest version for Intel’s package which includes driver v12.15.25.6712 for my LAN chipset. So a few latest packages can still have the same driver version inside?
But indeed, the package inside isn’t 343MB but still is "quite big": 57MB for Windows 7 x64 versions. Is it the smallest one I can get "officially" from Intel website?
Thank you very much for this! <3
My natural curiosity led me to "quite interesting" finding. I unpacked your rar file and PROWinx64.exe (which was downloaded from Intel website). There are similar filenames as yours in PROWinx64.exe\PRO1000\Winx64\NDIS62\ directory - but the content is "a little" different.
I found out that your e1d62x64.inf file has that text inside: "DriverVer = 07/12/2017,12.15.25.6712"
And e1d62x64.inf file from latest PROWinx64.exe package has this one, "older"?: "DriverVer = 03/21/2017,12.15.25.6"
Does that mean that latest 22.7.1 package does not include latest driver for my LAN chipset?
That’s the reason why I always try to find out if some more recent drivers exist and if they are "safe to install" for me. The main problem here for me is (sometimes) quite different version numbering.
But, I must say, the second “yes” was not expected one as it seems very strange to me that Intel does not want to distribute it on their webpage. Can I ask what’s the source of this newest driver so I could easier find it and update in future?
When I am searching for the latest drivers, my favorite target is our partner site Station-Drivers. By the way: Intel releaaes all their drivers to the mainboard manufacturers, but doesn’t offer all of them at their Download Center. Reason: Intel is not a mainboard manufacturer anymore.
Ah, I see, that explains a little. The problem is: these manufacturers do not update their sites as they should, so we, users, are not in the best situation.
@khanmein - I too found the strange driver file numbering, but it appears that in post #11 and #12 that for some reason (I have Windows 10) that if I install the driver automatically from the driver package the e1d62 always got installed. Then stumbled across some folks mentioning the e1d65 for Windows 10. In order to get that one installed one must manually drill down in to the driver package as what sound like what you did.
Again, not sure why, even my Windows 8.1 system had the e1d62 when researching it should be the e1d64. Just got to manually do.