Rivet Networks Killer Suite Driver/Utility 2.2.1430 for Windows 10 64-bit

Fixed Issues:

- Enabled KCC2.x for more network adapters. Update E3000 driver. Update 1550/1650 driver. 
- Killer Control Center: Refined KCC look and feel in multiple areas.
- Killer Control Center: Enabled Killer Control Center 2.x UI version on all current supported Killer network adapters.
- Killer E3000/E3100G driver: Updated to latest 10.039.0212.2020 WHQL driver.
- Killer E22/24/25 driver: Fix BSOD seen in fast startup cycling on particular platform.
- Killer E3100 driver: Update to version 1.0.0.12 WQHL driver
- Killer Network Component: Update string conversion in Killer Analytics Service which could lead to higher than expected CPU and power consumption (~0.20%)
- AX500 Driver: Updated to latest AX500 package, include in general release.
- Killer 1550/1650 Driver: AMT_WLAN response 255 after resume from S4 with SOL/KVM connected
- Killer 1550/1650 Driver: [CMLU42] [19H1] [BSoD_0x7e] [Netwtw08!wfdRemoveScanQNode] BSOD cause by "Netwtw08.sys"
- Killer 1550/1650 Driver: [ICL-U] [Netwtw08!goVifSetDeviceCapabilityApi+0x14]Occurs blue screen 0x7e when idle unit with wi-fi connected
- Killer 1550/1650 Driver: [ICL][19H1] CPU usage is very high due to Dynamic Tuning sometimes
- Killer 1550/1650 Driver: [CML][19H2] [ucode_assert_0x66]WLAN can not search any AP after resume from MS and Radio ON/OFF
- Killer 1550/1650 Driver: [ICL U][BSOD_7E][Netwtw08!mpdlCancelTimerObject] when run DRTU (21.50.0.5)
- Killer 1550/1650 Driver: [ICL U] [Netwtw08!txStreamGetTidQueue] BSoD occurred when idle unit with wi fi connected.
- Killer 1550/1650 Driver: [CML] [19H1][Netwtw08!dpPeerDbDecTotalNblsCount]BSOD 0x7e point to Netwtw08 when cold boot with 21.50.0.5
- Killer 1550/1650 Driver: WLAN failed to connect to hotspot/SoftAP of new Xiaomi Phone
- Killer 1550/1650 Driver: [GLK] Can not connect to the nearest AP
- Killer 1550/1650 Driver: Mobile hotspot cannot turn on and show "The selected network band isn't available" in Network&Internet after resume from Soi3/Hibernate/Shutdown
- Killer 1550/1650 Driver: When Mobile hotspot set to 5Ghz only and do a hibernate then resume will lost function.
- Killer 1550/1650 Driver: WLAN on 5Ghz does not work well
- Killer 1550/1650 Driver: NIC was lost after connecting to an 802.11ax AP
- Killer 1550/1650 Driver: Cannot connect to any WLAN AP in production line testing 0x20101208.
- Killer 1550/1650 Driver: [assert 0x1208]WIFI yellow bang during online video streaming
- Killer 1550/1650 Driver: The wireless AP list showed "No Wi Fi networks found" occasionally
- Killer 1550/1650 Driver: device shows Yellow Bang when running Reboot/Coldboot stress test
- Killer 1550/1650 Driver: [CML][19H1] [Assert_0x105e]Disconnect from AP after Resume from MS
- Killer 1550/1650 Driver: Occurred 0x7e BSOD when reconnecting the wireless AP then change AP channel/ password
- Killer 1550/1650 Driver: The following security issue is resolved in this release: see INTEL TA 00338 https://cdrdv2.intel.com/v1/dl/getContent/618472

Versions:

- E2X00 Ethernet: 9.0.0.49
- E2500V2 Ethernet: 10.038.1118.2019
- E3000 Ethernet: 10.039.0212.2020
- E3100G Ethernet: 10.039.0212.2020
- E3100 Ethernet: 1.0.0.12
- 1525 WLAN: 12.0.0.448
- 1435/1535 WLAN: 12.0.0.938
- 1550 WLAN: 21.80.0.4
- 1650 WLAN: 21.80.0.4
- Killer Extension: 2.2.3245.0
- Killer Component: 2.2.3245.0

About Ethernet Drivers:

Windows platforms generally apply a generic driver that allows motherboards to recognize the Ethernet component.

However, in order to make use of all network card (adapter) features, you must install a proper LAN driver that enables the hardware. This task enables systems to connect to a network, as well as collect all component characteristics such as manufacturer and chipset.

If you intend to update the driver version, know that this process can add support for new OSes, fix different compatibility problems, resolve related errors encountered during the product’s lifetime, as well as include various other changes.

About Wireless LAN Drivers:

Windows OSes usually apply a generic driver that allows systems to recognize the wireless component. However, in order to use all available features of this hardware, you must install the appropriate drivers.

Enabling the wireless card allows systems to read chipset information and manufacturer name, as well as connect to a network without using an Ethernet cable.

Updating the driver version can resolve different compatibility issues, fix related errors spotted throughout the product's usage, add support for new operating systems, improve transfer speed, as well as bring various other changes.

As for applying this release, the installation steps should not pose to much of a challenge since each producer intends to make the procedure as easy as possible: just download the package, run the setup, and follow the on-screen instructions.

Bear in mind that we do not recommend you install this release on OSes other than the specified ones even though other platforms might also be suitable. Also, when the update has finished, do perform a restart to ensure that all changes take effect properly.

Therefore, if you wish to apply this package, click the download button, and setup the wireless card on your system. Moreover, if you want to stay “updated one minute ago,” check with our website as often as possible.