I217-lm Driver Windows 10

[Antionette Eastin]

Ihave a Z230 with a I217-LM onboard NIC running Win 10 Pro X86 which was upgraded from Win 7 Pro. A MS Win 10 update has rendered my NIC inoperable and i will not connect to the internet or even my home network. I have talked with my ISP and this is not the issue as i have many devices connected to the internet with no issue (one of the devices is another Z230 with the exact same build) I noticed on the machine that is running without issue has an updated driver compared to the one i am having issues with. I have tried downloading all Win 10 drivers available but nothing has worked. I have gone to the Intel site and downloaded all the Win 10 and 7 Dirvers available but the will not update the NIC and i receive the same error with every driver package " this package is not compatable with your version of windows". i have even tried rolling the updates back to no avail; and even a fresh image only fixed it until the machine did the update once again. Again, my other machine is fine. i have done all the MS diagnostics and the device manager and cmd prompt tell me that the NIC is working properly.

Thank you for the quick reply Paul. I followed your instructions and the latest drivers have been installed, but i still cannot connect. I check again with my other Z230 and i noticed that it has an older driver installed but is working fine:

I tried to add the Drivers to an offline WinPE Image but it seems, sometimes not all files were copied to the Destination. I removed the faulty Driver and readded it, then all files were copied and the NIC was recognized by WinPE.

We recently purchased some Dell Optiplex XE2's and we're having this same issue. As soon as the machine boots into WinPE, it loses its IP address. Sadly, none of the drivers included seem to be working when I load them with drvload while in WinPE. Any additional help or suggestions are appreciated. Thanks!

We recently purchased HP Z230 workstation and have same issue. I217-LM drivers will not load into WinPE. Have tried adding all drivers from PRO1000\Winx64\NDIS62 but none work. Checked driver on the computer I'm trying to take the image from and it is using e1d62x64.inf. Any other suggestions would be appreciated.

Amazingly not one single person has mentioned the version of WinPE they are using! Is the original thread referring to the problematic NDIS61 drivers in WinPE 2.1 or some other version? I'd like to help in testing a solution to the problem if it's the same one I've experienced but not one person can contribute with any certainty without details of the real issue here.

It might be just that since it's tagged with sccm2012 that a certain version of WinPE is implied so I apologise if I'm incorrect! For an observer with other products that use WinPE and this network chipset though it would be useful to specify the exact setup for them to assist.

I am having a similar issue. I have a Dell E6540 with the I27-LM and I am using Ghost Console. I have loaded the driver (version 19) from \\PROWin32\PRO1000\Win32\NDIS62 into my WinPE folder, but upon pulling the original stock image from the Dell I am getting a 127.0.0.1 IP address. I have seen this before with Ghost due to a driver that is not working. Ghost only likes Vista x86 drivers; however the I27-LM does not have a Vista driver. Any Ideas? I am trying other versions of this Intel driver (18.7 and 18.6) but it seriously takes 10 minutes to load each driver into Ghost, so I will be around.

What it does is use the intel i210 ethernet controller driver for the i217-LM device. I had to look up the device id in Windows, to make it match. So if you plan to use this method, check the device id of your network card first.

We just recently got some dell 7020 and 9020 units and that is why i started to look. Symmantec doesn't do support for stuff like this, as GHOST is a dead product, but they are willing to sell you a maintenance kit if you want to upgrade your WINPE 2.5 to 3.0 but that should be free.

Both machines use the i217-lm NIC and would not allow us to use the GHOST WINPE and of course talk to the ghost console to push and pull images from the ghost client workstation app. We couldn't get an IP.

But now I was able to make up a driver set to work for i217 LM network drivers and storage drivers for the dell 7020/9020 as well in GHOST WINPE and now able to push and pull images from the ghost console without any issues.

My issue is related to Intel Ethernet Connection 3 I218-LM device drivers for WinPE. The reason I am posting it on this thread is because it is almost similar to what is being discussed here. The NIC works fine within Win 7x64 and the hardware ID is listed as PCI\VEN_8086&DEV_15A2&SUBSYS_833810F7 in device manager. The laptop I am trying to troubleshoot is Panasonic Toughbook CF31-MK5 model. When I am trying to PXE boot and image through SCCM 2012 it is not able to get the network drivers installed and I get an error "Failed to find a valid network adapter". I have made sure the required drivers are part of the boot image for SCCM but still it does not work. Digging furthermore into the inf file that is part of the driver pack I found that the above Device ID is not at all listed...I have contacted Panasonic and they are saying it is working fine in their Labs...Any help from this forum will be much appreciated.

Hope the above information help. Please note also 3rd-party website which we provide for your convenience only. We do not endorse any of the contents within this site, and any issues that may arise from following the information, solution, and/or recommendation herewith is solely the responsibility of its provider.

Intel does not verify all solutions, including but not limited to any file transfers that may appear in this community. Accordingly, Intel disclaims all express and implied warranties, including without limitation, the implied warranties of merchantability, fitness for a particular purpose, and non-infringement, as well as any warranty arising from course of performance, course of dealing, or usage in trade.

I have a couple of older Dell desktops with this problem in the e1000e chip on the motherboard. tso off is all that is needed to avoid the "Hardware Unit Hang" crash. Install ethtool and add a line to /etc/rc.local: ethtool -K eth0 tso off

When you do this, can you download a big file, let's say 5Gb, in a stable way, without it being a roller coaster? This is not the case for me. it's not a workaround, it replaces a problem with another one.

with the I217-LM or I219-LM on the board, and my USB network adapter with the RTL8152, at 1 000/500Mbps during the speedtest, with HTOP runing, i can see no more than 10% cpu load with my I5 9400T. So if realtek chips are a solution, i'd prefer go with that instead of having to tinker some settings.

That is exactly the reason why I won't chime into the blind praise of Intel ethernet cards over Realtek. I've first experienced this issue in 2007 (EDIT: no, that must have been 2-3+ years earlier already, with a e1000 addon PCi card) with e1000 and PCI cards, but also much newer e1000e PCIe aren't immune to this issue either - and when it happens, it causes real data corruption and data loss (e.g. on servers). Given that Intel is writing the e1000/ e1000e drivers themselves, they don't get to blame inadequate linux drivers either - and I've never seen issues like those with Realtek network cards...

Over the years I've fixed this issues differently, either by adding r8168 cards or patching the on-card eeprom of the intel card to disable features permanently (powersaving), but this doesn't instill much confidence in the hardware.

under windows i didn't notice any problem, it works as expected with the default settings.

here is a nperf from windows 10 with the HP 600 G1 with the I217 NIC, that's what i'm having with all my PC runing windows behind my router :

From my point of view this problem is driver related. This e1000e driver has a problem, this is not normal to build a NIC with features that you have to disable in order to have it to work correctly.

And by the way, disabling the settings make things working, but not correctly, see the curves above in my comments.

(I've never ran nperf...and never ran a speedtest from a router...I won't say for obvious reasons because it seems a lot of people actually do it...good time to note the SpeeTest dot Net license doesn't permit running on a router).

No, not from the router. The problem can ben seen from your PC, when using a router with an intel NIC like I217 / I219.

so the graphics i posted are from my PC, connected to the router. And of course you must have at least a 1Gbit internet connexion.

We receive a lot of support requests from customers that have problems with getting Windows PE to work with new hardware from HP, Dell, and Lenovo. What they all have in common is the Intel I217, I218, and I219 network interface cards.

Depending on the client computer hardware, WDS will deliver Win-PE 32-bit to clients with Legacy BIOS, and Win-PE 64-bit to the UEFI clients. Thus, it is important to import both x86 and x64 NIC drivers to Specops Deploy. See this blog post for a good way of managing your Win-PE drivers: -a-winpe-boot-image-with-windows-10-drivers/

Back to the issue with the NIC drivers. The problem is that the computer vendor only ships drivers for Windows 10 and these drivers are not compatible with Windows PE, even though Windows PE is based on Windows 10.

I am trying to install windows 2012 r2 via MDT to NUC . However I am having problems with the network driver. Intel did not write support for windows server into the driver. I have found posts on the internet on how to modify the .inf file and to disable driver signing. But this is a manual process and defeats the object of mdt.this link on how to hack manually

Looking at the spec sheets, I'm guessing the I218-V (on the NUC) and I218-LM are the exact same hardware with a different device ID. The I218-V's SKU is specifically to disable Windows Server support.

3a8082e126