- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
I have a NUC 11 TNH i5000
System Model NUC11TNHi5
Windows 11 identifies it as:
11th Gen Intel(R) Core(TM) i5-1135G7 @ 2.40GHz 2.42 GHz
BIOS TNTGL357.0062.2021.1203.1108
64.0 GB (63.6 GB usable)
The problematic driver loading is for its:
Intel(R) Ethernet Controller (3) I225-LM
Presently running driver version: 1.0.2.6
C:\WINDOWS\system32\e2f68.din
C:\WINDOWS\system32\DRIVERS\e2f68.sys
(Are these really 32-bit? This seems surprising.)
The Intel® Driver & Support Assistant (Intel® DSA) providing no response or change in status upon repeated attempts, I downloaded the driver installer and ran it directly.
The response was: “No Intel Network Connections Found on this computer. No Drivers were installed.”
I also downloaded LAN-Win10_Win11-1.0.2.14 which contains “e2f” files and offered them via the Device Manager. The Device Manager response was “The best drivers for your device are already installed”.
I presume that the upshifting value from 1.0.2.6 to 1.0.2.14 is minor, but still...
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
I have found that you don't need an EXE file. Do the following:
- Open Device Manager.
- Right-click on the entry for the LAN controller and select Uninstall Device.
- In the dialog displayed, select (checkmark) Attempt to remove the driver for this device and then select Uninstall.
- Exit Device Manager.
- Right-click on the INF file, select Show more options and then select Install.
There will be no feedback; it will simply install and initialize the driver.
Hope this helps,
...S
Link Copied
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
This method seems the best so far with information combined from @Ronny_G_Intel and @n_scott_pearson
a) use the Device Manager to Uninstall Device including checking to Delete the Driver file C:\WINDOWS\system32\DRIVERS\e2f68.sys
b) then reboot
c) when/if Windows Update reverts the driver to version 1.0.2.6 then use the Device Manager function "Roll Back Driver" to the previous version which was 1.0.2.14.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
After this procedure, Windows (11) Update will pull the old driver 1.0.2.6 just the same and overwrite 1.0.2.14.
Windows thinks the 1.0.2.6 is newer/higher version than 1.0.2.14 hence also why one cannot install through
device manager with the manual update option.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Step 14 is perhaps your solution.
Let's take it from the top.
1) download the driver.
2) unzip the driver folder so you can point Device Manager to the folder containing the driver.
3) Open Device Manager, Network Adapters, Ethernet Controller (3) I225-LM, and open the Driver tab.
4) If any version other than 1.0.2.14 is presented, choose Uninstall Device and check the box for attempting to remove the driver.
5) Close the Ethernet Controller (3) I225-LM dialog box.
6) Within the Device Manager, right-click on Network Adapters and select Scan for Hardware Changes.
7) Ethernet Controller (3) I225-LM should reappear in the list.
9) Within the dialog box, select Update Driver and Browse My Computer.
10) Locate the folder where you unzipped LAN-Win10_Win11-1.0.2.14 and select the folder as the driver source.
11) Driver version 1.0.2.14 should successfully install.
12) Reboot.
13) Run Microsoft Updates.
14) when/if Windows Update reverts the driver to version 1.0.2.6 then use the Device Manager function "Roll Back Driver" to the previously installed version which was 1.0.2.14.
(Note that the rollback function appears to be about the order in which drivers are loaded, not about version numbers or their dates.)
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Not a solution. It is a workaround. They are not the same things.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
We all know it's not an elegant solution, although twenty years ago it would have been considered perfectly normal.
The strength of a collective is portrayed not from how they respond when everything is going smoothly, but in how they respond when their weaknesses have been exposed. Intel exposed some workflow issues at every step involved including Community Support.
Some of us just feel motivated to put our oars in the water and help.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Work arounds enable. Enabling does not fit in my definition of helping.
Great to have but not a fix.
We've told Intel over and over the problem with the file is its a .zip file. Yet it remains as a zip file.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
I have done it on two different NUC11 model's now and it worked on both. I am unsure what you are doing wrong.
...S
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
I am curious about your success with the LAN driver update.
From my perspective, the issue remains, and I have confirmed this with three methods:
- reliance upon the IDSA
- right-clicking on the downloaded .INF and selecting Install
- Device Driver "Update Driver" pointing it to the downloaded folder, which provides the response shown in the graphic declining to load the new version.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
The problem is still happening for me on an 11TNKi7.
I also followed Scott Pearson's instructions for manually updating the driver. The update worked initially (yesterday I confirmed in device manager the new driver version 1.0.2.14 was installed) and ISDA said I did not need any driver updates, but when I checked today after a reboot, my LAN driver was back to version 1.0.2.6 and ISDA is saying I need to update the LAN driver again.
I ran IDSA and its the same garbage again ... driver downloads, I click Install and nothing.
Intel, you have a total mess on your hands, how about fixing this. Don't you see all the posts from customers. Think of the thousands of customers who don't post and are wasting countless hours trying to sort through why IDSA is not working with this LAN update
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Hello @calzon65, @ArtVB, @LeonWaksman, @LeonWaksman, @vannvanndamndamn
Thanks to assistance from @n_scott_pearson, we have made more progress than any of the other threads on this topic of the LAN driver update.
What we need is for this issue to be escalated within Intel. This is quite beyond the Driver Support Assistant IDSA technicians can manage.
@n_scott_pearson - do you know how we can ensure that this issue is escalated to those who have the capacity to resolve it?
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Hello,
I have had NUC11PHi7 for a month and every day I get a message about updating the Intel (R) Ethernet Controller (3) I225-LM network card, which unfortunately does not update the driver. After trying many different installation methods, I managed to update the driver in a similar way as described by Scott. However, I was very surprised when the update message reappeared the next day. I checked and my driver was old again. I have already lost my nerve to this problem and added the update information to the ignored ones, but unfortunately the update message appears from time to time. I would like to add that I have not been able to find a way to run WOL for a month - I have already done a lot of configurations and unfortunately it does not work, but only now I found this forum and I hope you will help me.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
@Alberto_R_Intel is the support engineer that appears to be assigned to this particular case and he should have escalated.
I would note that there are a whole slew of these cases, all slightly different, that I believe are caused by the same issue. Further, I think that it is going to take some time for them to resolve this issue. The issue is that the basic support that IDSA has for installing a raw driver is not going to cut it here because, with Win10 to Win11 upgrades, there are older driver packages in place that will need to be uninstalled before the raw driver can be installed. I conclude that an installation package will likely be necessary to support the upgrade process.
...S
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Hello @Ronny_G_Intel
Your method fully succeeded for my NUC11TNHi5.
Your pivotal additional information beyond @n_scott_pearson's suggestion was to delete the driver file.
a) use the Device Manager to Uninstall Device
b) use File Manager to delete the driver file C:\WINDOWS\system32\DRIVERS\e2f68.sys
c) then reboot
I rebooted twice and checked with Device Manager each time to confirm that the Intel(R) Ethernet Controller (3) I225-LM was running 1.0.2.14.
Obviously the using File Manager to delete C:\WINDOWS\system32\DRIVERS\e2f68.sys is not something everyone wants to do, so you still need a smooth solution, but this succeeded for me.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
THIS IS COMPLETE INSANITY!!!
I checked my 11TNKi7 this morning and my LAN driver is back AGAIN to version 1.0.2.6, and again, IDSA wants to upgrade my LAN driver to 1.0.2.14.
So I took @Garitaar advice and this time I ran Roll Back Driver in the Device Manager. I also told IDSA to ignore the upgrade to 1.0.2.14. Through the Roll Back Driver function, my LAN driver is back to 1.0.2.14, but I have no idea if it will remain there. I also have no idea why my LAN driver continues to revert back to 1.0.2.6 after so many forced updates using all the methods described in this forum.
Intel, you are completely failing on this issue!!!!
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Changing to an older driver is caused by updating Windows - after manual update to version 1.0.2.14, Intel-Net-1.0.2.6 appears on the first occasion of the update, which restores the old driver. I think Intel gave the wrong version number which causes this situation. As I wrote earlier, I bought NUC a month ago to have reliable equipment that will be stable because I had an HP whose graphics were still failing and the service was still returning the equipment as working. Now I have Intel and I waste my time on such stupid things. I am completely disappointed. The WOL that I need is also not working and I only found the information that it is fixed in the new BIOS version 0066 which, unfortunately, is not yet released and I have to wait. I am the head of production in a small Polish company that produces and programs electronics and I am completely surprised that companies such as Intel can make such mistakes. For this there are procedures, verifications and rules that protect against this type of errors, not to mention the fact that customers solve their problems themselves and there is still no official solution.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
I just came across this same issue after installing Windows 10 Pro 21H2 on a couple of NUC11TNBi5.
Using the steps provided by @n_scott_pearson I was able to install the 1.0.2.14 drivers, and after a couple of reboots the drivers remained.
But when running Windows Update on these machines the the older 1.0.2.6 drivers would be re-installed.
To stop Windows from updating/downgrading the drivers I've enabled the group policy setting "Do not include drivers with Windows Updates".
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
One Month pass, intel still not solve this problem, after manual update LAN drive to 1.0.2.14, and windows update will "update" the Lan drive to 1.0.2.6.
GOOD JOBS! INTEL & MS.
![$$CN@FQBA)]FJ7%F%0D1MVK.png](https://community.intel.com/t5/image/serverpage/image-id/27570i88438B5B7753DEBD/image-size/large/is-moderation-mode/true?v=v2&px=999 "$$CN@FQBA)]FJ7%F%0D1MVK.png")
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
@EGe00 Use the Microsoft ShowHide tool to hide 1.0.2.6. Not a good solution, but may ease the pain.
Doc (not an Intel employee or contractor)
[Waiting for Windows 12]
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
There is a good solution. Once the windows update installs the 1.0.2.6 driver, select the option restore driver in the device manager and we have it.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
There are several threads on this topic, and Intel unambiguously have more than one issue in their workflow that enabled the compounded challenge with this LAN update.
Intel have apparently not communicated with Microsoft so they can push 1.0.2.14.
This approach succeeded for me. If you are doing this and it is not succeeding, I would be curious to know more.
Let's take it from the top.
1) download the driver.
2) unzip the driver folder so you can point Device Manager to the folder containing the driver.
3) Open Device Manager, Network Adapters, Ethernet Controller (3) I225-LM, and open the Driver tab.
4) If any version other than 1.0.2.14 is presented, choose Uninstall Device and check the box for attempting to remove the driver.
5) Close the Ethernet Controller (3) I225-LM dialog box.
6) Within the Device Manager, right-click on Network Adapters and select Scan for Hardware Changes.
7) Ethernet Controller (3) I225-LM should reappear in the list.
9) Within the dialog box, select Update Driver and Browse My Computer.
10) Locate the folder where you unzipped LAN-Win10_Win11-1.0.2.14 and select the folder as the driver source.
11) Driver version 1.0.2.14 should successfully install.
12) Reboot.
13) Run Microsoft Updates.
14) when/if Windows Update reverts the driver to version 1.0.2.6 then use the Device Manager function "Roll Back Driver" to the previously installed version which was 1.0.2.14.
(Note that the rollback function appears to be about the order in which drivers are loaded, not about version numbers or their dates.)
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Installing the driver manually via device manager, or even removing the device and telling Device Manager to uninstall the current drivers, as the hardware is "refound" point to the folder with the now unzipped drivers is not the issue.
The issue is Intel can't get the driver update tool to work correctly.
Also don't need all that fooling around to manually install the driver. Run Windows update first. Download, unzip the network card driver file. Click on the Network Card, Driver Update, Search my Computer, have disk, point to the unzipped folder, boom, it installs.
Then don't run Windows update for awhile. Any time you do until Intel gets this sorted, you'll have to manually install, driver update, search my computer, point to the folder.....
- Subscribe to RSS Feed
- Mark Topic as New
- Mark Topic as Read
- Float this Topic for Current User
- Bookmark
- Subscribe
- Printer Friendly Page