[DRIVERS] Intel Ethernet/WiFi/Bluetooth

[MoKiChU]

Hi everyone,

- Intel Ethernet Drivers (Drivers Only) :

Drivers - I225/I226 - Windows 11 : 2.1.4.2 WHQL [03/10/2023]
Drivers - I225/I226 - Windows 10 : 1.1.4.42 WHQL [29/06/2023]

Drivers - I219 (≥ Rev. 18) - Windows 11 : 20.0.2.7 WHQL [14/01/2024]
Drivers - I217/I218/I219 - Windows 10/11 : 12.19.2.57 WHQL [25/11/2023]
Drivers - I210/I211 - Windows 11 : 14.0.2.0 WHQL [24/11/2023]
Drivers - I210/I211 - Windows 10 : 14.0.2.0 WHQL [25/09/2023]
Drivers - 82579 - Windows 10 : 12.15.31.4 WHQL [25/07/2016]
Download - I225/I226 - Windows 11 : Link
Download - I225/I226 - Windows 10 : Link
Download - I219 (≥ Rev. 18) - Windows 11 : Link
Download - I217/I218/I219 - Windows 10/11 : Link
Download - I210/I211 - Windows 11 : Link
Download - I210/I211 - Windows 10 : Link
Download - 82579 - Windows 10 : Link

Install/Update Process :

- Press Windows key + X > Device Manager > Right-click on your Intel Ethernet device > Update driver > Browse my computer for driver software
- Browse... > Select the extracted drivers folder (ETHERNET_Intel_v...) > Next

- Intel WiFi Drivers (Drivers Only) :

Drivers - 9xxx/AXxxx/BExxx : 23.40.0.4 WHQL [10/03/2024]

Drivers - 8xxx : 22.200.2.1 WHQL [09/03/2023]
Drivers - 3165/3168/7265D : 23.40.0.4 WHQL [10/03/2024]
Drivers - 3160/7260/7265C : 18.33.17.1 WHQL [29/04/2019]
Download - 9xxx/AXxxx/BExxx : Link
Download - 8xxx : Link
Download - 3165/3168/7265D : Link
Download - 3160/7260/7265C : Link

Install/Update Process :

- Press Windows key + X > Device Manager > Right-click on your Intel WiFi device > Update driver > Browse my computer for driver software
- Browse... > Select the extracted drivers folder (WiFi_Intel_v...) > Next

- Intel Bluetooth Drivers (Drivers Only) :

Drivers - 9xxx/AXxxx/BExxx : 23.40.0.2 WHQL [22/02/2024]
Drivers - 8xxx : 22.200.0.2 WHQL [15/12/2022]
Drivers - 3165/3168/7265D : 23.40.0.2 WHQL [22/02/2024]
Drivers - 3160/7260/7265C : 20.100.5.1 WHQL [17/04/2019]
Download - 9xxx/AXxxx/BExxx : Link
Download - 8xxx : Link
Download - 3165/3168/7265D : Link
Download - 3160/7260/7265C : Link

Install/Update Process :

- Press Windows key + X > Device Manager > Right-click on your Intel Bluetooth device > Update driver > Browse my computer for driver software
- Browse... > Select the extracted drivers folder (BT_Intel_v...) > Check the Include subfolders option > Next

OS requirements : Windows 10 64 bit or more recent.
Hardware requirements : Intel Ethernet/WiFi/Bluetooth controller.

TIPS :

If you want to manage the drivers (remove old/unused drivers for example) that you have in your Windows DriverStore
Use Driver Store Explorer (Right click on "Rapr.exe" > Run as administrator).

If you want better interrupts delivery latency
Enable MSI (Message Signaled-based Interrupts) mode on all your supported devices (see the column "supported modes") with
MSI Mode Utility (Right click on "MSI_Mode_Utility_v3.exe" > Run as administrator).

[Ataemonus]

I think people who are having issues with these drivers, which by the way, are official Intel drivers, actually have issues with their install of Windows. Not everybody should search the internet for drivers, some should stick to whatever Windows installs or whatever the system/motherboard manufacturer provides.

[funkyd]

Ataemonus wrote:
I think people who are having issues with these drivers, which by the way, are official Intel drivers, actually have issues with their install of Windows. Not everybody should search the internet for drivers, some should stick to whatever Windows installs or whatever the system/motherboard manufacturer provides.

I'm running a clean install of Windows 11. Prime Z690-A motherboard. The only "official" drivers are the ones available on Asus's site, Intel's drivers are only officially supported for Intel ethernet cards, not integrated ethernet controllers.

Also, the fact the bluescreen is a kernel security check failure points more to a driver or hardware compatibility issue than a Windows install issue. Two people have reported BSOD's, and we're doing so here to warn others so they update with caution.

[bigjohns97]

funkyd wrote:
I'm running a clean install of Windows 11. Prime Z690-A motherboard. The only "official" drivers are the ones available on Asus's site, Intel's drivers are only officially supported for Intel ethernet cards, not integrated ethernet controllers.

Also, the fact the bluescreen is a kernel security check failure points more to a driver or hardware compatibility issue than a Windows install issue. Two people have reported BSOD's, and we're doing so here to warn others so they update with caution.

Just a quick google search suggests that this could be system file related, malware, memory overclocking, quite a few things.

[lerun]

funkyd wrote:
I'm running a clean install of Windows 11. Prime Z690-A motherboard. The only "official" drivers are the ones available on Asus's site, Intel's drivers are only officially supported for Intel ethernet cards, not integrated ethernet controllers.

Also, the fact the bluescreen is a kernel security check failure points more to a driver or hardware compatibility issue than a Windows install issue. Two people have reported BSOD's, and we're doing so here to warn others so they update with caution.

Was also getting BSOD on win11 with these drivers. Had to roll back to the last one. Same motherboard.

[Ataemonus]

You are wrong, the Intel official drivers are generic, for all solutions based on their controllers.

[funkyd]

Ataemonus wrote:
You are wrong, the Intel official drivers are generic, for all solutions based on their controllers.

Straight from Intel's website:

"This software may also apply to Intel® Ethernet Controllers. Support for built-in network connections is provided by the system or board manufacturer."

I'm glad there are people not having issues with these drivers, but the fact is some people are. The condescending responses do not contribute anything to this discussion. I've built dozens of PC's; don't assume someone with a low post count here doesn't know what they're doing.

[Ataemonus]

Post count is irrelevant, however, the issues faced are quite relevant and speak loads to somebody's experience and knowledge.
Also, if you can understand the difference between hardware IDs and specific vendor IDs, that would also help your case 😉
A funny fact is that you linked to the Windows 10 driver packages, admitedly, the same as the Windows 11 ones, but shows you're not even looking in the right place to begin with.

Do not get me wrong, it's quite possible that somebody is having legitimate issues with the drivers, but the greater chance is that the issues are user caused, a fact which you seem to completely ignore.

[funkyd]

If you think a BSOD on a clean install of Windows that happens with one set of drivers but not another is somehow "user caused" and not an issue with the driver or hardware combination, then I'm not sure what to tell you. I'm not here to argue, but you sure make a lot of assumptions about the experience and knowledge of people you don't know.

[MoKiChU]

Hi everyone,

@ Intel Ethernet I225 controller users :

Since Windows 11 drivers, Intel use (only for I225 to date) a NetAdapter miniport driver which is built around the Net-Adapter framework (unlike Windows 10 drivers which Intel use a NDIS miniport driver built around the NDIS framework), which allows more low-level access to the I225 controller :

NDIS :



Net-Adapter :




Therefore, some third party apps that use NDIS drivers/devices (like Avast and its Avast! Firewall NDIS Filter Miniport) and/or that use WFP (Windows Filtering Platform) can cause your NetAdapter miniport driver kernel to crash/BSoD.

[funkyd]

MoKiChU wrote:

Therefore, some third party apps that use NDIS drivers/devices (like Avast and its Avast! Firewall NDIS Filter Miniport) and/or that use WFP (Windows Filtering Platform) can cause your NetAdapter miniport driver kernel to crash/BSoD.

Thank you for this information! This helped me track down the cause on my system. I am still testing, but virtualization appears to break these drivers. This includes Windows Sandbox and Windows Subsystem for Linux. Removing these allows the drivers to install. Reinstalling either will cause a BSOD after the 2nd reboot (the 1st reboot completes the feature installation, and the system appears to be stable until the 2nd reboot).

Anyone else who experienced BSOD's, can you respond if you're using Windows Sandbox, WSL, Hyper-V, or any other type of virtualization such as Bluestacks, VirtualBox, etc? If someone with a stable system wants to test by installing one of these features, just be aware you'll need to enter Safe Mode and remove the ethernet driver if you end up in a boot loop.