Latest Intel Killer Ethernet and Wireless Drivers for Windows 11

Almighty1 · May 5, 2023

Intel® Killer™ Performance Suite v34.23.3101 has been released
Release Date: May 2, 2023

Intel® Killer™ Performance Suite

This download record installs Wi-Fi, Ethernet drivers and Killer Software for the Intel® Killer™ products.

www.intel.com

Release Notes: https://downloadmirror.intel.com/778012/KillerPerformanceSuite_34.23.3101.pdf

Purpose

The 34.23.3101 version of Intel® Killer™ Performance Suite package installs the Windows® 10 and Windows 11 Wi-Fi, Ethernet drivers and Killer Networking Software for the following Intel® Killer products:

22.220.0.4 for Intel® Killer™ 1550, AX1650, AX1675
1.1.4.38 (Windows 10), 2.1.3.3 (Windows 11) for Intel® Killer™ E3100
10.063.1014.2022 (Windows 10), 1125.011.1206.2022 (Windows 11) for Intel® Killer™ E3000, E3100G
10.063.1014.2022 (Windows 10), 1168.011.1206.2022 (Windows 11) for Intel® Killer™ E2500v2, E2600
3.1423.302.1 for Killer Networking Software

Note: This Software Release version does not include new drivers for the Killer E2200, Killer E2400, Killer, E2500, Killer 1525 Wireless, Killer 1535 Wireless, Killer 1435 Wireless, or the Killer AX500 Wireless adapters, but the Killer Networking Software can be installed on the systems with the above adapters.

Notes:

Some drivers from this package may not have been updated and are the same as the previous package. You need to install this package in order to update any version of the drive mentioned above.
Only Windows 10 and Windows 11 64-bit Operating systems are supported. Check if your Windows 10 is 32-bit or 64-bit.

What's new

See the release notes for what's new or fixed, known issues, and supported hardware.

Download:

https://downloadmirror.intel.com/778012/KillerPerformanceSuite_34.23.3101_Win10-11x64.exe

johnlgalt · May 5, 2023

Almighty1 said:
but the Killer Networking Software can be installed on the systems with the above adapters.

Or not. I refuse to install that PoS software (and I'm not referring to Point of Sale).

The drivers I will take, though.

HuntyFtw · May 7, 2023

johnlgalt said:
Or not. I refuse to install that PoS software (and I'm not referring to Point of Sale).

The drivers I will take, though.

Same here. Finally, my 5GHz bugs are gone with these new drivers (no software, though).

Almighty1 · May 7, 2023

HuntyFtw said:
Same here. Finally, my 5GHz bugs are gone with these new drivers (no software, though).

The Killer 1535 which is Qualcomm/Atheros based has the issues even with the Qualcomm/Atheros drivers without the Killer Software of sync no surf multiple times a day so I am leading to thinking it's the hardware and not the software in that case. Replacing it with the Intel AX210 WiFi6E and the problems are history. I actually still have the Killer Software v3.0.1564 installed even though I am using the Intel AX210 now so I manually kill the processes that contain the word Rivet after booting up just in case I sell the system or give it away, I can get it back to stock.

johnlgalt · May 8, 2023

My 1635 is rock solid, right up until I install the Killer Networking software. Then it goes to mush.

I've tried 3 different times over the couple of years I've had this build (I started planning it 3 years ago this month, and assembled it July 2020). Naturally, it's why I have such a jaded opinion of the software.

asturias7 · Jun 22, 2023

Intel® Killer™ Performance Suite v34.23.5134 now available:

Intel® Killer™ Performance Suite

This download record installs Wi-Fi, Ethernet drivers and Killer Software for the Intel® Killer™ products.

www.intel.ca

Detailed Description

Purpose
The 34.23.5134 version of Intel® Killer™ Performance Suite package installs the Windows® 10 and Windows 11* Wi-Fi, Ethernet drivers and Killer Networking Software for the following Intel® Killer products:

22.230.0.8 for Intel® Killer™ 1550, AX1650, AX1675
1.1.4.38 (Windows 10), 2.1.3.3 (Windows 11) for Intel® Killer™ E3100
10.064.0316.2023 (Windows 10), 1126.012.0320.2023 (Windows 11) for Intel® Killer™ E5000
10.064.0316.2023 (Windows 10), 1125.012.0320.2023 (Windows 11) for Intel® Killer™ E3000, E3100G
10.064.0316.2023 (Windows 10), 1168.012.0320.2023 (Windows 11) for Intel® Killer™ E2500v2, E2600
3.1423.511.4 for Killer Networking Software

Note: This Software Release version does not include new drivers for the Killer E2200, Killer E2400, Killer, E2500, Killer 1525 Wireless, Killer 1535 Wireless, Killer 1435 Wireless, or the Killer AX500 Wireless adapters, but the Killer Networking Software can be installed on the systems with the above adapters.
Notes:

Some drivers from this package may not have been updated and are the same as the previous package. You need to install this package in order to update any version of the drive mentioned above.
Only Windows 10 and Windows 11 64-bit Operating systems are supported. Check if your Windows 10 is 32-bit or 64-bit.

What's new
See the release notes for what's new or fixed, known issues, and supported hardware.

https://downloadmirror.intel.com/781426/KillerPerformanceSuite_34.23.5134.pdf

johnlgalt · Jun 23, 2023

I tried installing that package, using a custom install to avoid installing the Killer software.

It hosed my system pretty badly - upon logging in, within a couple of seconds to a couple of minutes, the system would freeze and then crash and restart.

I used a System Restore that the installation created to revert back to the older drivers.

Old drivers work great. I then manually removed the old driver package, and let it revert to using standard Windows drivers. Both the E2600 (Gigabit) and E3100 (2.5 GB) seem to be doing perfectly fine with the Windows drivers.

Since I've now got the old drivers cleaned out, I'm gonna try to install the latest again, using the Custom Setup option. This time, I'm also disabling the E3X00u drivers from the group because those are for the USB NICs, not for the built in ones. I'm also excluding the E3100 drivers, as I suspect that that is a different NIC than the E3100G (which I think gets installed by the E3X00 drivers).

Hope this works.

johnlgalt · Jun 23, 2023

I was adding to my previous reply after installing the drivers that the PDF lists known issues with Killer Software - the last one listed is one I've always had whenever I installed it, hence why I do not install it anymore.

But, as I was typing, the system locked up again - I had installed the drivers but not yet even rebooted lol.

Now, this is after the first reboot.

johnlgalt · Jun 23, 2023

It took about 10 minutes, but the system did lock up again.

I was going to troubleshoot it, like running Task Manager to see if I could see anything going overboard in terms of resource usage, but I decided that I would revert again and just wait it out.

I have no idea why those drivers are giving my system fits, but the fact remains that if I install this latest build, it goes stupid.

johnlgalt · Jun 23, 2023

I might have a better idea now. With the new drivers installed, Windows is reporting my 2.5 G NIC to be an E3100G, but with the old drivers installed, it shows up as a E3000 (2.5 G). Going back through my hardware manuals, it is, in fact, the E3000, as seen in the PCI info string.

PCI\VEN_10EC&DEV_3000&SUBSYS_7C341462&REV_03\6&66EA3FB&0&0028000A

Which, according to Find unknown device information and drivers | Device Hunt is a RealTek chip being reported as a Killer device (which is as should be).

Also, when I revert, the version of the drivers that was installed before I started down this rabbit hole earlier today are the same ones listed in the February package for the same Killer drivers.

Intel® Killer™ Performance Suite

This download record installs Wi-Fi, Ethernet drivers and Killer Software for the Intel® Killer™ products.

www.intel.ca

But the package I have lying around (I like to keep drivers handy) is actually named KillerPerformanceSuite_3.1222.614_Win10-11x64.exe, which is probably still using the older Killer naming convention, Intel changed it a bit. But the February package did nothing to change the actual drivers, those are the same as the older killer package (which I noted earlier in this thread, I think).

I'm going to try to manually extract the drivers only and see if I can update them myself, one at a time, to see which one is actually failing. Hopefully, I can also figure out why.

Actually, since I am a couple of builds behind, I'm going to try to install them in order, to see if it's failing simply because my drivers are that old. That should notbe the case, like ever, but stranger things have happened lol.

neves · Jun 23, 2023

This is the part that i dislike the most about GUI installers:

Stuck like that for over 10 minutes, no error no nothing. In theory (while acting out like that) - it's usually working but in practice - doesn't seem like it:

Wouldn't mind a GUI installer - if it came with "advanced details" - so i can see what's wrong (easy to spot in a terminal). But like this - i get nothing. And i suspect - it's cause i went for a Custom installed - and disabled the extra cards included (which i don't know).

PS.Yep, as suspected - closing the installer tasks and running it again - while letting install all the driver packages - minus the Control App) worked as it should - i could of seconds.

johnlgalt · Jun 23, 2023

You did answer the UAC prompt when it started installing, right?

If so, chalk up yet another issue lol. I didn't have that, it definitely got through the install, and prompted me to reboot....

johnlgalt · Jun 24, 2023

Another update - No Intel package would work - all of them caused the same symptoms.

At this point, I suspect something in the OS itself, so I clean installed last night and will now test the latest package without having the previous Killer-developed package ever having been installed in this install.

I cannot find the killer uninstaller app anymore, but I suspect that to install the Intel package(s), I'd have needed to fully uninstall the Killer packages, including reg entries and such, which the little killer uninstall utility would do, and which I am dead positive I had somewherebut I seem to have misplaced.

Ah, well. It's been almost six months since my last clean install anyway. lol.

Almighty1 · Jun 24, 2023

@johnlgalt - Here you go, this is from my archives as I haven't used Killer since 2020 if not earlier.

KillerSoftwareUninstaller.1.0.2020.0212.zip

Download KillerSoftwareUninstaller.1.0.2020.0212.zip for free from KrakenFiles.com

krakenfiles.com

johnlgalt · Jun 24, 2023

Lol - that is the file I remember, but I could not find it. But, as I said, it was time for a clean install (of Windows) anyway, which I did last night. And I'm going to install the Intel package directly onto this system in a bit. Which means, going forward, I should not need that, but I'm still grabbing it lol.

HuntyFtw · Jun 24, 2023

@johnlgalt if you install Killer drivers normally without changing any settings, after successful installation, it will let you choose whether to let Killer software install or not. I always uncheck it at this step and so far, the newer drivers are working fine for me.

johnlgalt · Jun 25, 2023

Not the issue. Are you talking about the Killer App from the store? Because that is not what the custom setting stops, there is a lot of other stuff installed besides just the driver if you use a complete install.

Anyway, my issue is that I did it both ways, with all three packages from this year. Every single one makes my computer freeze and lock up.

I cleanly install Windows 11 (bare metal install) on Friday, 23 June, the other evil day this year, and set it up Saturday. I tried all three packages from this year. Same thing - computer froze and locked up every single time. Both Complete and Custom installs.

The only package I have that works is KillerPerformanceSuite_3.1222.614_Win10-11x64.exe from July of last year. The hardware all checks out fine, With that particular driver package, I have 0 issues, and I didn't have to do a complete install, did the custom install and didn't let the other software components get installed. And, again, no issues. Throughput is exactly where it was before.

I have no idea why this is failing, but I'm gonna contact their support for it. I suspect they have lumped two devices together to use a single driver and it b0rks on my hardware, but I cannot prove this yet.

johnlgalt · Jun 25, 2023

Almighty1 said:
@johnlgalt - Here you go, this is from my archives as I haven't used Killer since 2020 if not earlier.

KillerSoftwareUninstaller.1.0.2020.0212.zip

Download KillerSoftwareUninstaller.1.0.2020.0212.zip for free from KrakenFiles.com

krakenfiles.com

I found it - because I had apparently slapped it onto a thumb drive for some reason, and didn't copy it back to the new storage volume when I cleanly installed Win11 last year lol.

But, I still thank you for it. Running it also let me verify that, in fact, there were no killer components on here before I started testing the Intel packages on my new clean install.

neves · Jun 25, 2023

johnlgalt said:
You did answer the UAC prompt when it started installing, right?

If so, chalk up yet another issue lol. I didn't have that, it definitely got through the install, and prompted me to reboot....

Yes, did the UAC thingy. Tho, as usual - i tend to chose advanced option where i deselected - the additional drivers (besides the one necessary for my NWC) and the control panel. Didn't seem to like that, so on next try i deselected only the panel - while installing all the drivers from the package (no issue - following this path). Not that the extra drivers - would cause any issue (won't do anything without their designated NW hardware) - it's just slightly messier (and i prefer a clean approach).

johnlgalt · Jun 26, 2023

After the clean install, and it still not working, I gave it one more try - I used the Intel driver scanner and installer, and it found both this NIC package and the BT package.

Installed the BT package, created a manual system restore point, rebooted, created a second manual restore point, then let the Intel scanner install the NIC package.

At first it seemed to work, but this morning my system was locked up again. Restored to that second restore point and all was well again.

My system does not like any of the Intel 34.xxx.yyy.zzz packages. At all.

At least I have a lot of details I can feed back to them to find out why this is happening to me.