New Hardware Support:

- Intel Ethernet Network Adapter I710-T4L
- Intel Ethernet Network Adapter I710-T4L for OCP 3.0
- Intel Ethernet Controller I226-T1
- Intel Ethernet Controller I226-IT
- Killer E3100X 2.5 Gigabit Ethernet Controller (3)
- Intel Ethernet Controller I226-LM
- Intel Ethernet Controller I226-LMvP
- Intel Ethernet Controller I226-V
- Intel Ethernet Connection (22) I219-LM
- Intel Ethernet Connection (23) I219-LM
- Intel Ethernet Connection (22) I219-V
- Intel Ethernet Connection (23) I219-V

New Software Support:

- Support for FreeBSD 12.3. Drivers are no longer tested on FreeBSD 12.2.
- Support for Microsoft Azure Stack HCI, version 21H2
- SetupBD.exe now supports an l switch, which saves an installation log file.
- Support for Microsoft Windows 10 version 1809 for 1Gbps devices based on the following controllers: Intel Ethernet Controller I710
- Support for Microsoft Windows 10 version 1809 for 10Gbps devices based on the following controllers: Intel Ethernet Controller X710
- Microsoft Windows Server 2022 support for devices based on the following controllers: Intel Ethernet Controller I225, Intel I217 Gigabit Ethernet Controller, Intel I218 Gigabit Ethernet Controller, and Intel I219 Gigabit Ethernet Controller

Intel Ethernet 800 Series Fixed Issues:

- Linux Driver: Prior to irdma version 1.8.45, installing the OOT irdma driver on a system with RDMA-capable Intel Ethernet Connection X722/Intel Ethernet Network Adapter X722 ports and using an OS or kernel with an in-tree irdma driver could cause a system crash. To prevent a system crash when using OOT irdma drivers, either use irdma 1.8.45, or update i40e version (2.18.9 or greater) and load it before this new irdma is loaded.
- Linux Driver: AF_XDP based applications may cause system crash on packet receive with RHEL based 4.18 kernels.
- Linux Driver: During a long reboot cycle test (about 250-500 reboots) of the Intel Ethernet 800 Series adapters, the Intel ICE and iavf driver may experience kernel panics leading to an abnormal reboot of the server.
- Linux Driver: The commands ethtool -C [rx|tx]-frames are not supported by the iavf driver and will be ignored. Setting [tx|rx]-frames-irq using ethtool -C may not correctly save the intended setting and may reset the value back to the default value of 0.
- Linux Driver: Interrupt Moderation settings reset to default when the queue settings of a port are modified using the ethtool -L ethx combined XX command.
- Linux Driver: When a VM is running heavy traffic loads and is attached to a Virtual Switch with either SR-IOV enabled or VMQ offload enabled, repeatedly enabling and disabling the SR-IOV/VMQ setting on the vNIC in the VM may result in a BSOD. Linux RDMA Driver
- Linux Driver: In order to send or receive RDMA traffic, the network interface associated with the RDMA device must be up. If the network interface experiences a link down event (for example, a disconnected cable or ip link set <interface> down), the associated RDMA device is removed and no longer available to RDMA applications. When the network interface link is restored, the RDMA device is automatically re-added.
- Linux Driver: RHEL 8.5 only: Any usermode test that uses ibv_create_ah (For example, a RoCEv2 usermode test such as udaddy) will fail.
- Linux Driver: Due to a nondeterministic race condition, if the irdma driver is loaded in Linux by an Intel Ethernet 800 series device with non-standard MTU (i.e., non-1500B MTU), the system's network interfaces may fail to load after reboot. After failing to load, interactions with the networking stack may hang on the system. Multiple reboots may be required to avoid the condition.
- Linux Driver: The Devlink command devlink dev param show (DEVLINK_CMD_PARAM_GET) does not report MinSREV values for firmware (fw.mgmt.srev) and OROM (fw.undi.srev). This defect was also seen on the NVMUpdate tool, which caused an inventory error.
- Windows Driver: When a VM is running heavy traffic loads and is attached to a Virtual Switch with either SR-IOV enabled or VMQ offload enabled, repeatedly enabling and disabling the SR-IOV/VMQ setting on the vNIC in the VM, may result a VM freeze/hang.
- Linux RDMA Driver: iWARP mode requires a VLAN to be configured to fully enable PFC.
- Firmware: Following a firmware update and reboot/power cycle on the Intel Ethernet CQDA2 Adapter, Port 1 is displaying NO-CARRIER and is not functional.
- Firmware: Added a state machine to the thermal threshold activity so that when the switch page fails, it tries again from the same state.
- Firmware: FW not allow link if module not supported in lenient mode.
- Firmware: RDE Device is reporting a RevisionID property of PCIeFunctions schema as 0x00, instead 0x02.
- Firmware: The RDE device reports its status as Starting (with low power), even though it is in standby mode.
- Firmware: Wake On LAN flow is unexpectedly triggered by the E810 CQDA2 for OCP 3.0 adapter. The server unexpectedly wakes up automatically from S5 power state in few seconds after shut down from the OS, and it is impossible to shut down the server
- Firmware: Fixed an issue where the FW was reporting a module power value of module from an incorrect location.
- NVM: If the error message OS layer initialization failed is displayed, please update the Windows QV driver to the version included in this release. Note: If you are using Proset, an update of the QV driver may also require updating the Proset. 

About Network Adapter Drivers:

When connected, the operating system usually installs a generic driver that helps the computer to recognize the newly attached device.

However, proper software must be applied if you want to make use of all features that the network adapter has available. This task also allows computers to properly recognize all device characteristics such as manufacturer, chipset, technology, and others.

Updating the adapter's drivers and utilities version might improve overall performance and stability, increase transfer speeds, fix different compatibility problems and several network-related errors, as well as bring various other changes.

To install this release, simply get the package, extract it if necessary, run the setup, and follow the instructions displayed on-screen. When done, don't forget to perform a system restart and reconnect the network adapter to make sure that all changes take effect properly.

Without further ado, if you intend to apply this version, click the download button and install the package. Moreover, check with our website as often as possible so that you don't miss a single new release.

  It is highly recommended to always use the most recent driver version available.

Try to set a system restore point before installing a device driver. This will help if you installed an incorrect or mismatched driver. Problems can arise when your hardware device is too old or not supported any longer.