Help
cancel
Turn on suggestions
Auto-suggest helps you quickly narrow down your search results by suggesting possible matches as you type.
Showing results for 
Search instead for 
Did you mean: 

Z170 Ranger VIII & Z270 Hero IX Windows forcing old Intel Ethernet I219-V driver

d5aqoep
Level 8

‎06-28-2016 10:29 PM - last edited on ‎03-05-2024 10:58 PM by Community Admin

Windows 10 Current Redstone 1 Preview builds have the latest 12.15.23.1 (Dated 10/05/2016) Intel Ethernet driver built-in. This driver is perfect and does not drop LAN packets while transferring files from my NAS back to my PC.
But as soon as I run Windows Update, Windows installs an old 12.13.17.7 (Dated 13/08/2015) driver which is known to cause network stability issues and has memory leaks.

Do whatever you want, Rollback, disable driver updates, use reg tweaks, change driver policy in gpedit.msc, the damn old driver just overrides any new driver and installs itself like some virus.
I tried everything on the internet. This driver is forced like some critical update.

What can be done to force Windows to use latest driver which is in-built instead of this ****ty Windows Update driver? All Windows 10 builds from TH2 to RS1 are affected.
I have sent feedback thousands of times, even abused them. Apparently you need to sue Microsoft to get things done. That's the only language they understand.
Labels:
0 Kudos
7,478 Views
8 REPLIES 8

Chino
Level 15

‎06-29-2016 03:17 PM

Reinstall the Windows with the driver that works for you and disable Windows updates.
Overclocking The Core i7-7700K With DIP5 |Overclocking the Strix GTX 1080 | OC Panel & OC Panel II Guide | Overclocking i7-6700K to 4.6GHz | R5E 128GB DDR4 Setup | Liquid Cooling GTX 980 Ti Poseidon | R5E M.2 FAQ
0 Kudos

FuryA
Level 8

‎07-01-2016 03:12 AM

Reinstall the Windows and DL the newest driver is the best way to solve
0 Kudos

d5aqoep
Level 8
In response to FuryA

‎07-02-2016 12:53 AM

FuryA wrote:
Reinstall the Windows and DL the newest driver is the best way to solve


Done that a million times. Doesn't work.
Only using WUMT tool hales to hide the driver update.
0 Kudos

d5aqoep
Level 8

‎11-03-2016 08:43 PM

Any update on this problem? Windows 10 installs this driver as some critical update. So all newer drivers get over written with this crappy old version.*

This happens even on latest Insider Preview.*
0 Kudos

hiong
Level 8

‎11-04-2016 12:23 AM

hmmm, I don't get this problem on my M8E nor my M8G, the latest Intel driver installed sticks. Have you tried downloading and installing from this page?

https://downloadcenter.intel.com/download/25016/Intel-Network-Adapter-Driver-for-Windows-10?product=...
0 Kudos

IMNdi
Level 7
In response to hiong

‎11-17-2016 07:41 AM

I have. Tried 20.7 from Asus, 21.0 from Intel, they mount and then are immediately shot and Windows restores version 15.

I even attempted a manual install from Windows, which is not recommended because of PROSet, but even so, on short notice Windows reverted to v12.

12.13.17.7
2015-08-13

Oh, also, I get this: Device PCI\VEN_8086&DEV_15B8&SUBSYS_86721043&REV_31\3&11583659&0&FE could not be migrated.

Last Device Instance Id: SWD\IP_TUNNEL_VBUS\6TO4_ADAPTER
Class Guid: {4D36E972-E325-11CE-BFC1-08002BE10318}
Location Path:
Migration Rank: 0xF000FFFFFFFFF112
Present: true
Status: 0xC0000719

and this:

Device PCI\VEN_8086&DEV_15B8&SUBSYS_86721043&REV_31\3&11583659&0&FE requires further installation.

Nobody seems to have an official answer about what "device not migrated" means, not do I know if the "6to4" has any bearing on the issue (likely not) nor do I know if it's just a notification the device requires further installation or if it's an error that triggered the revert.
0 Kudos

IMNdi
Level 7
In response to IMNdi

‎11-18-2016 11:10 AM

New data:

60402

OK, what am I watching here? Why is this naming scheme different from Intel and Asus'? Am I on the latest driver, and is this a display error?

Windows claims my currently loaded driver is in Windows\System32\drivers\e1d65x64.sys. File is signed by Intel and Microsoft, and is listed as:

12.13.17.7 Modified 2016-04-20, Signed by Intel on 2015-08-13 and by Microsoft on April 2016 AND Aug 2015.
0 Kudos

d5aqoep
Level 8

‎01-10-2017 08:35 PM

I was so fed up of this behavior that I upgraded to ASUS Z270 Maximux IX Hero. Stock Bios 0503 did not make Windows 10 to force install this old driver. But After updating to it's latest BIOS 0701, Windows is again shoving 12.13.17.7 down the updates even though I have 12.15.23.8 as latest version installed.
IMNdi wrote:
OK, what am I watching here?.......

Only two things work to make the new driver stick. Use either one of the methods.

  • Let Windows install the wrong old driver 12.13.17.7. Install 12.15.23.8 manually using update driver wizard. Then run Windows update and Windows will again override it with 12.13.17.7. Now from driver tab of device manager, click on Roll Back Driver and select the first or second option as reason of roll back.
  • Let Windows install the wrong old driver 12.13.17.7. Download and run RAPR from here. Make sure you run it as admin mode. Click on Enumerate and select the faulty driver and FORCE DELETE. Then download WUMT x64 or x86 from here. Run it as admin and search for updates. Now it will show you that Intel driver is available for update. Select it and click on H (Hide button)


Also
Make sure you disable this setting
0 Kudos