Troubleshooting

Service Not Running

 

Error: Service Not Running

You may experience a situation where their Killer Control Center says "Service Not Running" instead of operating normally. 

service not running

 

 

This can often be resolved by simply restarting the machine by clicking Start > Power > Restart, especially if the Killer Control Center has recently been updated. 

In Windows, services start before anything else, including other programs. If the service does not start automatically when the machine starts, then there is likely another service that is preventing it from starting, or the service is not set to start automatically

You can check to make sure that the service is set to run automatically by following these steps:

  1. Click Start, type services.msc and press Enter.
  2. Scroll until you find the Killer Network Service and double-click it.
  3. Make sure the "Startup Type" is set to Automatic. You can also manually start it from here by clicking Start button, which will clear the error until you next restart your machine.

If it was already set to automatic, make sure you are using the latest Killer Control Center, found here - http://www.killernetworking.com/driver-downloads/item/killer-control-center-x64. For most users, this should fix the issue. If you have any issues installing the latest Killer Control Center, please refer to our installation troubleshooting KB here - http://www.killernetworking.com/driver-downloads/kb/cat/7-installing-and-updating#anchor1.

Some users may still encounter the issue after updating to the latest version of the Killer Control Center. We are aware of the issue, and we are currently working on an update to address it. In the meantime, you have a few options:

  • Ignore the Killer Control Center, for the time being. The error will disable all functions of the Killer Control Center, including all bandwidth optimization, but this may or may not be an inconvenience to you, depending on your usage. The network adapter(s) will otherwise continue to operate normally.
  • Start the service manually. This will only need to be done when the computer is rebooted, not when it is slept. 
  • Contact us here - http://www.killernetworking.com/about/contact - for a batch file that you can place in your startup folder that will start the service after Windows has completed booting. Depending on your security settings, this may require confirmation, so the process may not be entirely automated. 

We apologize for this temporary inconvenience. 

 

 

Fall Creator's Update Breaks Network Adapter

 

Some users have experienced issues with their network adapters directly after the Windows 10 Fall Creator's Update. The errors vary, but most point to a hardware failure of some kind. We have received reports of "Network Cable Unplugged" and "Device Cannot Start," even though the adapters were working normally before the update. Unfortunately, in some cases, the only solution seems to be to uninstall and reinstall the Windows 10 Fall Creator's Update. However, one thing you can try is uninstalling all drivers for the device from the Windows driver store, then restarting the machine, and installing the latest drivers. Here are the steps: 

  1. Make sure you have the latest Killer Control Center installer handy on the machine (you may need to use a USB thumb drive or some other medium if you can't access the Internet with the machine). 
  2. Right-click Start, click Apps and Features, find all entries with "Killer" in the title, and uninstall them. This includes "Killer Drivers" or "Killer Suite" or any variations. You can hold off on restarting for now if an uninstaller says to do so.
    1. If you encounter any issues with uninstalling, such as the uninstaller hanging (give it at least ten minutes), or giving an error message, cancel the uninstallation, then right-click the taskbar and click Task Manager.
    2. Make sure the Processes tab is selected.
    3. Click Name at the top of the "Name" column to sort by name.
    4. Scroll down and find any "Killer" process under "Apps" and "Background Processes", click it, and click the End Task button.
    5. Click the Services tab. 
    6. Click Name to sort by name.
    7. Scroll down and find the "Killer Network Service". Right-click it and click Stop. 
    8. Close the Task Manager window and return to the Apps and Features menu, and continue uninstalling all "Killer Drivers" or "Killer Suite" entries.
  3. Close Apps and Features and right-click Start and click Device Manager
  4. Find the Ethernet adapter under the Network Adapters heading, right click it, and click Uninstall Device. If you cannot find it, you may need to click View > Show hidden devices at the top of Device Manager. It may also be listed somewhere other than under Network Adapters.
  5. Check the box for Delete the driver software for this device if it is present.
  6. Click Uninstall.
  7. Click the light blue Scan for hardware changes icon at the top of Device Manager. The adapter will probably reappear, and may or may not still show a Code 10, but I would suggest continuing with this guide either way.
  8. Repeat steps 4-7 until you no longer have the option to Delete the driver software for this device. Note that you could keep doing this indefinitely, as Windows will always install a default driver, but once you can no longer Delete the driver software for this device, you have accomplished the goal of clearing out all of the drivers that we were trying to clear out, and so you're done by that point.
  9. Restart the computer by clicking Start > Power > Restart. Do not rely on the machine's power button as many modern computers have that button set to sleep, not power off. 
  10. Once the machine has restarted, run the installer for the latest Killer Control Center. If everything doesn't look perfect, restart the machine after the installation, even if the installer did not say to do so. 

If that doesn't solve the issue, try uninstalling the Fall Creator's Update. Here are the steps to do that:

  1. Click ​Start
  2. Type ​Windows Update ​and click ​Windows Update Settings.
  3. Click ​Recovery​ on the left. 
  4. Under "Go back to the previous version of Windows 10" click ​the ​Get Started​ button.

Windows will invariably reinstall the update at some point. Hopefully, when it does, it won't break things. Unfortunately, it has proven common for Windows Feature updates to cause issues, which can be resolved by uninstalling and reinstalling the update.

Bluetooth or Wi-Fi Missing From Device Manager or Grayed Out

5.0 

Bluetooth or Wi-Fi Missing From Device Manager or Grayed Out

Note: This guide can be used in the event of any M.2 device vanishing from the Device Manager. The procedure lists Killer devices specifically, but the phenomenon is widespread among M.2 devices and Windows 10, and these same steps can be used to restore functionality when any M.2 device disappears from Device Manager.

When this occurs, it is an issue of the BIOS or the operating system not enumerating the device properly. In very rare situations, it can be cause by some kind of physical trauma causing the device to become dislodged, or the device failing, but more often than not, the hardware is just fine. It’s just a matter of getting Windows or, sometimes, the BIOS, to see it again. Sometimes the device will be missing altogether, or sometimes it will be grayed out - the difference is only in whether your Device Manager is set to show devices that are no longer present in the machine. Either way, the Device Manager thinks that the device is gone, and that is what needs to be addressed.

  • First off, make sure that you do not have any USB devices disabled. The internal Wi-Fi and Bluetooth adapter is actually USB device, so if there are any USB devices disabled in your Device Manager, for any reason, this can cause the Bluetooth device to vanish. If you are unable to enable the USB device, then you should resolve that issue first. This includes USB Hub devices, or any devices under the Universal Serial Bus controllers category in Device Manager that show any errors, for any reason. Once you no longer have any disabled USB devices, the Bluetooth device should show back up. On some platforms, this is the #1 cause of Wi-Fi and Bluetooth adapters mysteriously vanishing from the Device Manager. Once you have resolved the USB issue, restart your machine, and check to see if the missing device has reappeared in your Device Manager. 

USB Error

  • If you do not have any disabled USB devices, or any with errors, or if you have resolved that issue and the Wi-Fi or Bluetooth adapter has not reappeared in the Device Manager, then you will need to update your chipset drivers, and possibly your machine or mainboard’s BIOS. We have noted that some platforms have chipset drivers that are buggy enough that they absolutely will experience this issue if their chipset drivers are not updated. You will need to obtain these drivers from your mainboard or machine manufacturer’s support page. If you cannot tell which drivers are the chipset drivers, it is generally recommended that you simply update all of the offered drivers, except for the Killer Network card drivers, which you should get from us, as they are likely more recent. If there is a BIOS update available, then updating the BIOS is also recommended, especially if the BIOS update notes mention anything that might pertain to this situation. Make certain that you at least update the chipset and USB drivers, if applicable. Some platforms combine the USB drivers into the chipset drivers, so you may not see a separate download. Once you have done these updates, restart the machine, and see if the missing device reappears in the Device Manager. Depending on what is available, the best order in which to update is as follows:
    1. Update your BIOS from your machine or mainboard's support page.
    2. Update your chipset drivers from  your machine or mainboard's support page.
    3. Update the USB drivers from your machine or mainboard's support page. If none are listed, they are probably rolled into the chipset driver.
    4. Update all other drivers available from your machine or mainboard's support page, except Killer Networking and Bluetooth drivers, which you should get from us.
    5. Restart your machine by clicking Start > Power > Restart
  • Windows itself can also play a part in the disappearing device. The Anniversary Update saw many such devices vanish, so much so that the Creator’s Update added a Bluetooth troubleshooter to Windows 10. Make sure that your Windows installation is up to date by using Windows Search to search Windows Update

    windows update

    then press Enter, and click Check for Updates

  • Once it has downloaded and installed everything it finds, restart the machine, and repeat this process until Windows Update finds no updates directly after restarting. Once this happens, check to see if the device has reappeared in the Device Manager. If this doesn’t help, and the issue is Bluetooth related, you can try troubleshooting using Windows built-in troubleshooter. Microsoft has instructions here - https://support.microsoft.com/en-us/help/14169/windows-10-fix-bluetooth-problems-faq
  • If the device is still missing from the Device Manager, then that means that it isn’t the chipset drivers (or at least it isn’t only the chipset drivers) that is not properly enumerating the device, but rather the BIOS itself. In this case, you will need to discharge the machine to force the BIOS to re-enumerate all of its hardware. Before you do this, make sure that you have updated the BIOS to the latest version, from the mainboard or machine manufacturer’s website, so that you address the flaw that caused this issue in the first place. Once that BIOS update is in place, and you have confirmed that the machine has booted back up, but the device is still not appearing in Device Manager, shut the machine back down, and unplug it from the wall. You will now need to fully discharge the machine.
    • If this is a desktop, you will need to remove the side panel, discharge yourself of static electricity on something metal (your computer’s case might work, or possibly your desk) and look for the CMOS battery. It is a large coin-cell battery. Remove that battery. Sometimes it’s easier with a flathead screwdriver, but it should be fairly simple to remove. Once you have removed that battery, press the power button on the machine 2-3 times to completely discharge it, then replace the CMOS battery and the case. If you are not comfortable doing this on your own, please refer to your mainboard or machine's support. 
    • If this is a laptop, hopefully it is one where you can easily remove the battery. This will be specific to your model of laptop, so you may need to refer to your owner’s manual, or your laptop’s support website. Some MSI models are held in with a single screw. If you are able to remove the laptop battery, do so, and then press the laptop’s power button a few times to fully discharge it. If you are unable to remove the laptop’s battery, temporarily change the power plan to a setting that does not allow it to sleep when the battery is low, then run the laptop until it discharges itself. Once it has discharged itself, press the power button a few times to make sure it is fully discharged.
    • Once you have a fully discharged machine, put it back together, plug it back in, and let it boot in to Windows. You may see a message mentioning setting the BIOS to defaults, or something along those lines. This is nothing to be alarmed about – simply confirm that you want it set to defaults, unless you had set custom settings, in which case, you will need to re-set those custom settings. In the future, this message may be a warning that your CMOS or laptop battery is dead or on its last legs, but for now, we know that you discharged the machine on purpose, so we can safely ignore this warning. Once you are booted back in to Windows, check the Device Manager to make sure that the missing Wi-Fi or Bluetooth device is no longer missing.
  • In some very rare cases, the device may not show up because the machine was not fully discharged. We have had users report that they were able to repeat the steps to discharge their machines a second time, and have had success after that. Once the updates were in place, and the devices shows up, that is usually the end of the problem.

One final step that you can take, if you are willing and able to do so, is to physically reseat your Wi-Fi adapter. The Wi-Fi and Bluetooth device are on the same card, so there is only one adapter to reseat, and reseating this adapter only requires that you remove one screw, slide it out of the slot, then slide it back in and screw it back down, being careful not to dislodge or damage the attached antenna leads. However, the difficulty in getting to this adapter and performing this step will vary depending on your machine or mainboard, and your level of expertise. You may wish to consult with your mainboard or machine manufacturer’s support at this point. If you have followed all of the other steps, and the device still has not reappeared, the device, or the mainboard, may also be physically damaged, and in need of repair, which would also necessitate contacting your mainboard or machine manufacturer’s support for RMA or repair options.  

"This Device Cannot Start (Code 10)" in Device Manager

 

"This Device Cannot Start (Code 10)" in Device Manager

code 10 device cannot start

We have seen many Code 10 errors lately from machines where Windows 10 has automatically updated the drivers from older versions. These errors do not mean that your adapter has actually failed. This is an issue with Windows 10, and getting the proper drivers installed will correct the issue. 

First, try updating to the latest Killer Control Center, which contains the latest suite and drivers. You can find that download here - http://www.killernetworking.com/driver-downloads/item/killer-control-center-x64​. If you have any problems with the install, you can refer to our KB article on that subject here - http://www.killernetworking.com/driver-downloads/kb/faq/6-troubleshooting-killer-ethernet-wireless-drivers-software​.

If you have no way of getting drivers onto the machine (no USB thumb drive, no other means of connecting to the Internet with this machine) then click here to jump down to the alternate guide to fixing Code 10 errors.

If you have installed the latest Killer Control Center and restarted the machine, and that did not clear the Code 10 error, you can usually clear it by cleaning out the driver store. Here are the steps to clear out the driver store, and install the latest driver:

  1. Make sure you have the latest Killer Control Center installer handy on the machine (you may need to use a USB thumb drive or some other medium if you can't access the Internet with the machine). 
  2. Right-click Start, click Apps and Features, find all entries with "Killer" in the title, and uninstall them. This includes "Killer Drivers" or "Killer Suite" or any variations. You can hold off on restarting for now if an uninstaller says to do so.
  3. Close Apps and Features and right-click Start and click Device Manager
  4. Find the Ethernet adapter under the Network Adapters heading, right click it, and click Uninstall Device. If you cannot find it, you may need to click View > Show hidden devices at the top of Device Manager. It may also be listed somewhere other than under Network Adapters.
  5. Check the box for Delete the driver software for this device if it is present.
  6. Click Uninstall.
  7. Click the light blue Scan for hardware changes icon at the top of Device Manager. The adapter will probably reappear, and may or may not still show a Code 10, but I would suggest continuing with this guide either way.
  8. Repeat steps 4-7 until you no longer have the option to Delete the driver software for this device. Note that you could keep doing this indefinitely, as Windows will always install a default driver, but once you can no longer Delete the driver software for this device, you have accomplished the goal of clearing out all of the drivers that we were trying to clear out, and so you're done by that point.
  9. Restart the computer by clicking Start > Power > Restart. Do not rely on the machine's power button as many modern computers have that button set to sleep, not power off. 
  10. Once the machine has restarted, run the installer for the latest Killer Control Center. If everything doesn't look perfect, restart the machine after the installation, even if the installer did not say to do so. 

 

 

The Alternate Guide to Fixing Code 10 Errors

This guide is only intended for use when you cannot get drivers onto the machine using a USB drive or an alternate means of Internet access, such as an installed Wi-Fi adapter.

  1. Close all other applications, as you will need to allow restarts as they are requested. If you regain connectivity after a restart, click here to go to step one on the guide above and proceed to clear the rest of the drivers in the driver store, as guided, and install the latest driver. This is very important as, otherwise, the "bad" driver will remain in the Windows driver store, and may cause issues in the future. 
  2. Right-click Start, click Apps and Features, find all entries with "Killer" in the title, and uninstall them. This includes "Killer Drivers" or "Killer Suite" or any variations. If an installer requests a restart at any point, click to allow it to restart. 
  3. Once the machine has restarted, test to see if the issue is resolved. 
  4. If not, right-click Start, and click Device Manager.
  5. Find the Ethernet adapter under the Network Adapters heading, right click it, and click Uninstall Device. If you cannot find it, you may need to click View > Show hidden devices at the top of Device Manager. It may also be listed somewhere other than under Network Adapters.
  6. Click Uninstall.
  7. Check the box for Delete the driver software for this device if it is present.
  8. Restart the computer by clicking Start > Power > Restart. Do not rely on the machine's power button as many modern computers have that button set to sleep, not power off. Once the machine has restarted, check to see if the issue is resolved. 
  9. If not, repeat steps 4 - 8 until you regain Internet connectivity. Once you do, remember to go to step one on the guide above and proceed to clear the rest of the drivers in the driver store, as guided, and install the latest driver. This is very important as, otherwise, the "bad" driver will remain in the Windows driver store, and may cause issues in the future. 

If you have any further issues or questions, feel free to reach out to support at http://www.killernetworking.com/about/contact

Bandwidth Test Error in Killer Control Center

 

Bandwidth Test Error in Killer Control Center

Users may notice that the built-in bandwidth test no longer functions in some versions of the Killer Control Center. This is due to changes in the way that the Killer Control Center connected to the servers that are needed to perform these tests. The current version of the Killer Control Center should not experience this issue. To resolve this issue, please update your version of the Killer Control Center by downloading the latest package from here - http://www.killernetworking.com/driver-downloads/item/killer-control-center-x64. If the version on your system is old enough, the installer may give you an error, and you will need to manually uninstall the previous version before installing the latest package. 

Problems With The Killer Network Manager

 

The Killer Network Manager is our outgoing performance suite. It is no longer being updated, and does not contain the latest Ethernet or Wi-Fi drivers. We encourage all users of the Killer Wireless-AC 1525/1535/1435, Killer Wireless-N 1202/1103, Killer E2200, Killer E2400, and Killer E2500 to upgrade to the Killer Control Center, found here - http://www.killernetworking.com/driver-downloads/item/killer-control-center-x64. This includes users whose machines came with the Killer Network Manager preinstalled. There is no need to continue using the Killer Network Manager.

For a smooth installation, download the latest Killer Control Center installation package, then uninstall all Killer products from your Apps and Features menu, which is accessible by right-clicking Start, then restart your computer, and double-click the new installation package to install the new Killer Control Center.

The old Killer Network Manager suite is still available for download here - http://www.killernetworking.com/driver-downloads/item/e2200-e2400-wireless - but will no longer be updated, and may not be fully compatible with future Windows updates, antivirus suites, or other applications that manipulate network data.

Slow Network Speeds

 

Slow Network Speeds

If you are experiencing slow Internet or network speeds, you can follow this troubleshooting guide to address and correct the most common problems. 

If you haven't already, please try installing the latest Killer Control Center from our website, and only from our website. It includes many fixes and improvements that are not be included in other packages. If you are still using the Killer Network Manager, you'll want to download the Killer Control Center, and then manually uninstall the Killer Network Manager, as well as the "Killer Drivers" entry in your programs list. You can find the latest Killer Control Center here: http://www.killernetworking.com/driver-downloads/item/killer-control-center-x64. Please download and run this installer, which will also install the latest drivers. If you experience any problems installing the Killer Control Center, you can refer to this article for help - http://www.killernetworking.com/driver-downloads/kb/faq/6-troubleshooting-killer-ethernet-wireless-drivers-software 

Once you have successfully updated your drivers, you will want to restart your computer by clicking Start > Power > Restart. It is important to note that closing the lid or pressing the power button on many modern computers does not shut them down, but instead activates sleep mode. You must restart them by clicking Start > Power > Restart for them to restart.

If updating the drivers does not solve the issue, try resetting your networking equipment in this specific order, even if you have reset your some or all of your equipment previously. This order is proven to help your devices sync up properly, and will help to get a clean slate with further troubleshooting. Doing this can help even if only one device is experiencing problems. 

  1. Shut down your computer.
  2. Locate your modem and note the lights on your modem when it is normal and ready. There may be a "Ready" light.
  3. Unplug your modem, router, and any switches or hubs, between your computer and the modem, as well as any wireless boosters or access points, and leave them all unplugged for now.
  4. Plug in your modem.
  5. Wait until your modem's lights show normal operation again.
  6. Plug in your router, if you have one, and give it about five minutes to boot.
  7. Plug in anything else between your computer and the modem
  8. Power on your computer.
  9. Once your computer is booted and connected to the Internet, you will want to reset its network stack:
    1. In the search box on the taskbar, type Command prompt, right-click Command prompt, and then select Run as administrator > Yes.
    2. At the command prompt, run the following commands in the listed order, and then check to see if that fixes your connection problem:
      • Type netsh winsock reset and press Enter.
      • Type netsh int ip reset and press Enter.
      • Type ipconfig /release and press Enter.
      • Type ipconfig /renew and press Enter.
      • Type ipconfig /flushdns and press Enter.
  10. Now reboot your machine once more and test to see if the issue is resolved.

If not, the next step is to make sure that your Windows installation is completely up to date. Microsoft has been updating Windows more often than with any previous release, so it's important to keep things up to date. To do this, simply search Windows Updates, hit Enter, and then click Check for Updates. If your machine finds updates, check again once it finishes installing. Once your machine finds no updates, restart again, and then check for updates once more. Once your machine finds no updates upon a fresh reboot, your Windows installation should be fully up to date.

If you have performed the above, and you are still experiencing issues with slow network speeds, there are some other things to try:

  • Set a benchmark. Place the device in one place, if dealing with Wi-Fi, and run a test using one speed test. Turn off all other network usage while troubleshooting. Speedtest.net and Testmy.net are both good bandwidth tests. Run three tests in short succession and record an average as your starting point. Test after each change to see if there has been improvement. Record what you changed, and what the speeds the change produced. If the change seems dramatic, restart the machine and test again to be sure. 
  • Make sure your BIOS is up to date from your machine or mainboard manufacturer's support page.
  • Make sure your chipset drivers are up to date from your machine or mainboard manufacturer's support page.
  • Make sure all of the other drivers are up to date from your machine or mainboard manufacturer's support page. You can safely download and install all available driver packages. If the driver does not apply, it will either not install, or will not be used. If the only options in a driver installer package are "Repair" or "Uninstall", choosing "Repair" will update the driver, if there is a newer driver available.
  • Update the firmware on your router if you own the router.
  • Update the firmware on your modem if you own the modem, but only if your ISP accepts the firmware. Your ISP's support team can help you with this. Some ISPs also have this information listed somewhere, but they may need to do something on their end if you update the firmware, in order to re-authorize your modem. 
  • Have your ISP update the firmware on your modem or router if they own your modem or router.
  • If you are using Wi-Fi, minimize the number of solid objects between the access point's antenna and the device suffering from low speeds, using line-of-sight. Moving a device or antenna even an inch to one side could bypass multiple solid objects, making an enormous difference. 
  • If you are using Wi-Fi, use the Killer Control Center's Wi-Fi analyzer to make changes to your router's settings. 
    • 5 GHz routers should be set to channels 36-48, and/or 149-165 that are as far away from other channels as possible.
    • 2.4 GHz routers should be set to channels 1, 6, or 11, depending on which channels have the least powerful conflicting radios present.
    • Sideband, or side channel should be set to 20 MHz if there are many other Wi-Fi access points in your area, especially if you are forced to share a channel. Higher side channels are less powerful, but provide a wider band, allowing the signal to get around solid objects better, theoretically improving performance in situations where there are no interference concerns, but the Wi-Fi signal needs to "get around" solid objects. Many, however, report that, in real life testing, 20 MHz still provides the better signal, so your mileage may vary. 
  • If you are using Wi-Fi and your router has both a 5 GHz radio and a 2.4 GHz radio, name them something different. Although it might seem simpler to name them the same thing, many routers do not handle this very well, and you can see performance issues by having them named the same thing. Many people opt to simply add "5" to the end of the 5 GHz radio. 
  • If you are using Wi-Fi extenders, name each of your extenders something different, so that you know which access point you are connected to. Wi-Fi extenders have limited radio capacity, and will, always provide at least slightly slower speeds than connecting directly to the router, as they have to use the same radio to receive and transmit, at the same time. 
  • If it seems like other machines using the same access point are having no issues, try to verify this. Borrow their machine and run a speed test. Ask for permission first, of course. If you are experiencing issues on a public access point, you might just find that the public access point is just terrible, and that no one else is having a problem because you're the only one playing latency-intensive first person shooters. 
  • If you are using a Wireless-N router in a crowded Wi-Fi environment, you are very likely to encounter drops and speed issues no matter what settings you change. Unfortunately, the 2.4 GHz spectrum is very limited on how many channels are available, and conflicts arise quickly. Updating to a Wireless-AC router may be required to increase your speeds and reduce wireless drops. 
  • If you are using an antivirus or firewall application, try completely uninstalling it for testing purposes. Unfortunately, simply disabling these programs do not work for troubleshooting purposes, as they often continue to manipulate network traffic. They must be fully uninstalled. If you notice that your speeds increase dramatically with the antivirus or firewall application uninstalled, try installing a freshly downloaded version from their website. If that doesn't help, then the issue may be one with the antivirus application itself. In that case, you will want to contact the support team for the antivirus application. 

If you are unable to get your speed issues sorted out using the above tips, feel free to contact us directly using the information below! 

 

No Killer Network Interfaces Connected

 

A few things can cause the Killer Control Center to report error. Following are the most common, and how to correct the issue:

  • You are not connected to the Internet. Connecting to the Internet with your Killer network adapter should clear this error. 
  • You recently installed or updated the Killer Control Center and have not rebooted your computer. Rebooting should resolve the issue. Please note that, to restart, you should click Start > Power > Restart, as simply closing the lid, or pressing the power button on many modern computers activates sleep mode, and does not actually power down the machine. 
  • You are connecting to the Internet using a network adapter other than a Killer product. Our performance suites only work when connecting to the Internet with our products. Be sure that you are connecting to the Internet using the Killer network adapter. 
  • You are using an incorrect device driver. Updating to the latest suite should resolve that issue. You can find the latest Killer Control Center here - http://www.killernetworking.com/driver-downloads/item/killer-control-center-x64. If you have manually installed a device driver that was not provided by Killer Networking, you may need to manually uninstall that driver first, deleting it from your driver cache, before you install the latest suite. 

Please reach out to support, using the link below, if you are unable to solve the issue using the above information. 

Ethernet Link Speed Capped at 100 Mbps

5.0 

Ethernet Link Speed Capped at 100 Mbps

You may find that your Ethernet speed is capped at 100 Mbps when your Internet Service Provider, or your internal network connection, should be providing speeds greater than 100 Mbps. If this is the case, you may be encountering a link speed issue. To check for this, check the link speed on the machine in question by following these steps:

  • Search Control Panel with Windows Search and press Enter
  • Click Network and Internet
  • Click View network status and tasks which will be underneath Network and Sharing Center
  • Click the connection that represents the Ethernet connection to your router or modem. You should see a screen that looks something like this.

link speed

Notice that the link "Speed" here reads as 100 Mbps. This means that the negotiated connection speed between the Ethernet adapter and whatever device it is plugged into is 100 Mbps. When everything is working correctly, this speed will read as 1.0 Gbps.

The only setting that is of concern for a Gigabit connection is that the adapter is set to Auto-Negotiate. From the Device Manager, you can check to see that the Killer adapter is set on Auto-Negotiate. This option is under the Advanced tab of the adapter's properties, in Speed & Duplex - right-click the adapter and choose properties, click the Advanced tab, and click Speed & Duplex, and make sure it is set to Auto-Negotiate. This is the default setting. We have had reports of some ISP technicians telling their customers that a Gigabit option will appear in this setting if the network adapter is working correctly. This is incorrect. Auto-Negotiate is the correct setting for Gigabit speeds in Speed & Duplex for Killer Networking Adapters.

If this is set correctly and your link speed still reads as 100 Mbps, then the issue could be a few things, although it is important to note up front that this is almost always an issue with an Ethernet cable. Even if you firmly believe that your Ethernet cabling is perfectly fine, and even if this cabling worked fine before, swapping it out for another, proven cable, or a brand new Cat 6 cable, will almost certainly solve the issue with the minimum of troubleshooting and headache. This is a very, very common occurrence when troubleshooting Gigabit Ethernet, and it nearly always comes down to one cable being the culprit. Note that this includes all cabling between the machine and the router, including any cabling in before and after any switches, or on the other side of any wall jacks, and behind the wall. However, if you were getting Gigabit using a particular setup and suddenly, with no changes whatsoever, your link speed is now 100 Mbps, then it's probably only one cable that is now having issues, and it is likely one that is exposed.

The fastest way to rule out any problems with anything other than cabling is to connect your machine directly into your modem with a single, proven Cat 6 or better Ethernet cable, and preferably into a proven Gigabit capable port, then check the link speed. If the link speed shows as 1.0 Gbps, then you know that the problem is somewhere in what you have just bypassed. Using this method of troubleshooting can be a pain if you are not dealing with a laptop, but it might still be worth doing if you have to decide if you need to call a contractor out to look at wiring behind your walls. Note that very long Ethernet cords are available for purchase, with lengths of over 200 feet or 60 meters, are available, so if you are involved in a prolonged debate with a technician over link speeds, this might be the simplest way to provide a temporary, single cable connection from your machine to the modem. 

That said, all adapters are different and handle shorts or issues with cables or ports differently, but a Gigabit adapter reporting as 100 Mbps is almost certainly a physical issue with the networking equipment.

You can troubleshoot this by trying different combinations:

  • If you cannot connect your machine to the modem with a single, proven Cat 6 cable, maybe you can connect a machine whose link speed currently shows as 1 Gbps to the Ethernet cable that is currently plugged into the problem machine. If this second machine now shows a link speed of 100 Mbps, this also proves that the issue is somewhere in the cabling or equipment between the machine and the access point, not with the machine itself. 
  • Power cycle (unplug and plug back in) your access point (hub, switch, router) and any other device between your machine and the access point.
  • Cat 6 is preferred to Cat 5e as, although the latter is technically capable of gigabit connections, it lacks any redundancies in grounding, which is an extremely common point of failure in network cables. Cat 6 remedies this issue, and making sure that all of your cabling is Cat 6 or better is usually a surefire way to achieve a gigabit connection. 
  • A "failed" Cat 5e or Cat 6 cable will usually still work at 100 Mbps. It doesn't take much physical trauma for a Cat 5e cable to revert to 100 Mbps, and many of the cheaper ones don't support 1 Gbps out of the bag, even though they will be labeled as supported 1 Gbps connections. If you have only tried a Cat 5e cable, you owe it to yourself to try a Cat 6 cable. This is almost certainly the issue. If you are having issues achieving Gigabit speeds and you have Cat 5e cables in the mix then it is safe to assume that those specific Cat 5e cables are not Gigabit capable. This is common. Incidents such as rolling over the cable with an office chair, or stepping on it, or closing a door on it, can all cause a Cat 5e cable to revert to 100 Mbps link speeds when it was previously working at Gigabit speeds.
  • Try different ports on your access point (hub, switch, router). If possible, use a port that is proven capable of working at Gigabit speeds with another machine. 
  • If all of these fail, then likely the Ethernet connector on the mainboard has an issue and you would need to check with your PC manufacturer (or mainboard manufacturer, if you assembled the machine yourself) on what your warranty or RMA options are. You may want to perform a physical inspection on the Ethernet jack's pins to make sure that none of them are bent or otherwise damaged. It is worth stressing once more, though, that this issue is nearly always one with the cabling somewhere between the Ethernet jack on your machine, and the Ethernet jack for the modem.

Cannot See Certain Wi-Fi Networks

 

Some users may experience issues with their Killer Wi-Fi adapter not being able to detect certain specific Wi-Fi access points. Here are the things to check for:

  • If you are in Europe and the access point might be on the 2.4 GHz band, it may be using channels 12 or 13. If you have access to the settings on this access point, try changing the the channel to 1, 6, or 11. If not, try updating to the latest version of drivers, which should be able to make use of channels 12 and 13 in European countries - http://www.killernetworking.com/driver-downloads/item/killer-control-center-x64
  • Your router or modem may be using a DFS channel. DFS channels are 5 GHz channels that can be used by the public, but public devices receive a "leave the channel" command if official use is necessary. Although Killer Wi-Fi adapters ordinarily have no problem operating on DFS channels, if your laptop has been used in an area where the DFS channel was being used in an official capacity (such as an airport), it may have received the signal to stay off of that channel. For example, in the United States and some parts of Europe, DFS channels are 5 GHz channels 50-144. When troubleshooting a wireless network that does not appear for a specific device, these channels should be avoided in these areas. You can use the chart available on this Wiki page to quickly see which channels are available in your area of the world. We have also noted that some routers will automatically choose DFS channels even though they are not compatible with those same channels, and they must be manually set to a channel in order to not use them. 
  • Your router or modem may need to be power cycled. All routers and modems rely on a very small amount of physical resources and, eventually, those resources will hang, making it necessary to restart them from time to time. The fastest and simplest way to do this is to unplug the device for ten seconds, then plug it back in. This can help even if only one device is having problems with the access point.
  • Your computer may need to be restarted. Restart your computer by clicking Start > Power > Restart. Note that pressing the power button on most modern computers activates sleep mode - it does not shut them down. In order for your computer to reboot, you must either click Shut Down or Restart
  • You may be too far away from the wireless access point. Wireless signals rely on line of sight and, as such, each individual solid object between your device and the access point diminishes the signal. A single wall may contain multiple solid objects. A floor contains concrete subflooring, wood framing, piping, and various other solid objects. If at all possible, make sure you can connect with another device before assuming any one device is faulty. 
  • There may be interference. 2.4 GHz routers in crowded apartment complexes are especially susceptible to this. You can use the KIller Control Center's Wi-Fi Analyzer to see how many people are sharing your current channel. If too many people are on the same channel as you, it may not be possible to connect to your own access point from too far away. Setting your sideband, or side channel, to 20 MHz can help mitigate this, as the smaller ths sideband, the stronger the signal. 
  • Your wireless profile may have become corrupted. If you have connected to this access point before, but it is no longer visible, you may need to delete the connection's profile and reconnect. Here are the steps:
    • Click the rectangular "Connect" button, where you would normally click to connect to a wireless network, on the bottom, right-hand side of your screen.
    • Click Network and Internet Settings.
    • Click Wi-Fi on the left, if it is not already selected.
    • Click Manage Known Networks
    • Click the network that you are not able to detect.
    • Click the Forget button.
    • Close the Settings window, and connect like normal. If the access point still does not appear, try restarting your machine by clicking Start > Power > Restart.

If you are still unable to connect to a specific wireless access point, feel free to reach out to our support here - http://www.killernetworking.com/about/contact.

Wifi and Router or Modem Issues With Killer 1535

 

Router or Modem Issues With Killer 1535

This article is intended to cover all issues that affect any access point, be it a router or modem, that occur when the Killer Wireless-AC 1535 connects or is connected.

The 1535 is a cutting edge Wireless-AC device with MU-MIMO and Transmit Beamforming technology and, as such, not all access points have firmware already installed that is able to handle the connection. Problems that some of our users have reported include:

  • Access point restarts or crashes upon connection, requiring restart
  • Access point restarts or crashes after being connected for some time, requiring restart
  • Access point slows dramatically
  • Access point randomly disconnects all connected devices

The fix for this issue will depend on your personal situation.

 

 

You Own the Access Point

In this case, you are connecting to a device, such as a router, that you own, which is then connected to another device, such as a modem, which is owned by your Internet Service Provider (ISP). If the device in question is a modem, please be sure that, even if you own the device, your ISP supports any firmware that you flash onto the modem. Most ISPs maintain a list of accepted firmware versions for each device online.

In many such situations, you can update the firmware of your device to resolve this issue. You should first try to update the firmware through the router's interface, if possible. If that is not a feature of that router, or if that does not solve the issue, check for the latest firmware from the official support page of your router. If the problem is still not resolved, then see if your router is listed below. Listed below are the routers whose model numbers that we are aware of have issues, along with the location of the updated firmware that the router manufacturer has made available to address the issue:

If you own a different model than the one listed above, and updating to the latest firmware that is available from the support page of your router's manufacturer, we suggest contacting the support for your router, we suggest first updating to the latest Killer Control Center, found here - http://www.killernetworking.com/driver-downloads/item/killer-control-center-x64. If that does not solve the issue, the next step would be to contact the support for your device and advise them of the steps that you have taken, and ask if they have a beta firmware available. At the same time, please contact our support, as well, using this form - http://www.killernetworking.com/about/contact

 

 

The Access Point is Owned By Your ISP

In this case, it is very possible that the device is running a very old firmware version. Most ISPs only update the firmware at the customer's request, or when it is absolutely necessary in order for the device to continue working on their network, and many ISPs use very old equipment. If you are connecting directly to an ISP owned device, and you are experiencing these issues, then your best bet would be to contact your ISP's support, and request that they update the firmware on the modem. This is usually a simple thing for them to do. If you are unable to resolve this by asking your ISP to update the firmware on the device, please let us know by contacting us here - http://www.killernetworking.com/about/contact - so that we may document the model of the access point that is not fully compatible with our device. In most cases, however, it is due to the age of the device, and a bug in its firmware. If asked, your ISP may be willing to change you to a different model of access point. You might also be able to provide your own access point (sometimes saving a monthly rental fee in the process), or buy your own router to plug into their modem, then use your router as the access point. If you decide to buy your own modem, most ISPs maintain a list of modems that work with their service. If you use multiple devices at the same time on the same access point, there is a good chance that you will see a boost in performance on all devices by providing your own modem. 

 

 

Addressing the Isssue with Drivers

There are some discussion threads where we have commented, linking to specific drivers on our site, where those drivers have now been moved, causing 404 errors, or redirections to this page. Those drivers were links to .INF drivers that could be installed using the Device Manager, to address specific access points crashing when the 1535 would connect to them. These posts and links were created before we had driver-only installers hosted on our website, and were generally just the latest driver-only file that we had available at that moment, as the problem was believed to be cause by the performance suite at the time. You can now download the latest driver-only installer here - http://www.killernetworking.com/driver-downloads/category/other-downloads. However, this will not always solve the issue, as the issue is sometimes not the performance suite, but that of buggy firmware with the access point. If you wish to try and address the issue by using a driver-only install, you will need to download the driver-only installer, then uninstall all "Killer" entries in your Programs and Features menu, restart your machine, then install the driver-only package. This will remove all Killer network management capability.

We have had some reports of users who were only able to keep their routers stable with only one very specific driver version - usually some Windows 8.1 driver used on a Windows 10 machine. In those cases, we will do our best to locate a copy of that specific version for you but, unfortunately for those cases, Windows Update will often update those drivers anyway, and that is completely out of our control. There are some guides out there on how to prevent Windows Update from updating your device drivers, but we have neither tested nor endorse any particular method of doing so, and we cannot say what the repercussions may be. 

 

 

Wi-Fi Issues with Killer Wireless-AC 1535 on Certain Platforms

 

Wireless Issues with Killer Wireless-AC 1535 on Certain Platforms

We are aware that users, on some specific platforms, are encountering Wi-Fi drops, slowdowns, disconnects, and packet loss issues, which are related to certain machines containing the Killer Wireless-AC 1535.

We have been working closely with the manufacturer to root cause the issue, and the manufacturers of these machines have been releasing chipset updates to address the problem. In most cases, users are able to resolve this issue by doing the following:

  • Update the chipset drivers from the manufacturer’s website, which, in many cases, has been updated as recently as October 26, 2017.
  • Update the BIOS from the manufacturer’s website, which has also been updated as recently as October 25, 2017.
  • Ensure that the Windows OS is up to date by using Windows Search to search “Windows Update, then clicking Check for Updates, letting it download and install whatever updates it finds, then restarting the machine, and checking again until no updates are found upon a fresh restart.
  • If the issue persists, please be sure that you are using the most up-to-date version of the Killer Control Center, available here - http://www.killernetworking.com/driver-downloads/item/killer-control-center-x64. The installer should automatically detect your current version of the suite and update on its own, but if you encounter any error, make sure you have the latest installer downloaded, then remove any "Killer" application from your Apps & Features menu (accessible from right-clicking Start), restart your machine, and then double-click the downloaded installer file for the latest suite once your machine has booted back up. 

If you are unable to resolve the issue by following these steps, we encourage you to reach out to us here - http://www.killernetworking.com/about/contact - so that we may help you on a case by case basis.

Please be sure to mention what steps you have already taken to troubleshoot the issue so that we do not unknowingly ask you to repeat steps.

 

Network Column in Windows Task Manager Not Working

 

For our software to display bandwidth correctly, Windows NDU (Windows Network Data Usage Monitoring Driver) ends up getting stopped/disabled. This is because both services work by examining packets, and both doing so at the same time can cause conflicts.

If you force NDU to run while Killer Control Center or Killer Network Manager is installed, those two programs may not display bandwidth correctly.

If you would like to re-activate the Windows NDU to test for yourself, open a Command Prompt and enter the following:

sc config ndu start=auto

After you enter that command, reboot your Computer.

NDU should now be set to start automatically and the Task Manager Processes tab should show traffic in the Network column, but the Killer Control Center or Killer Network Manager might not work properly.

To disable it, enter the following into a Command Prompt:

sc config ndu start=disabled

After you enter that command, reboot your Computer.

No Killer Enabled Devices On Linksys WRT32X

 

Users with Killer Network Adapters and the Linksys WRT32X may see "No Killer Enabled Devices" or "0 Killer Enabled Devices" on the user interface page of their WRT32X. 

The Killer optimization on the WRT32X is compatible with all Killer adapters that work with the Killer Control Center, which includes the:E2500, E2400, E2200, E2201, and all of our Wireless-N and Wireless-AC adapters. 

You must also have a recent version of the Killer Control Center installed. You can find the latest version of the Killer Control Center here - http://www.killernetworking.com/driver-downloads/item/killer-control-center-x64. If you run into any problems updating your performance suite, you can refer to our installation troubleshooting KB here - http://www.killernetworking.com/driver-downloads/kb/faq/6-troubleshooting-killer-ethernet-wireless-drivers-software.

After you have installed the latest Killer Control Center, if the router still fails to detect the Killer adapters, you may need to unplug the router for ten seconds, then plug it back in. If it still does not recognize the adapters. you may need to restart your computer once more by clicking Start > Power > Restart

If you still experience issues, it is recommended that you contact Linksys Support unless you are having other issues with your Killer adapter, in which case you should reach out to us through the contact form below. 

 

Memory Leaks

 

Some users have reported memory leaks with some versions of our performance suite. The current version of the Killer Control Center has no known instance of memory leaks. Unfortunately, when a computer is assembled, the software that is installed on the computer will not necessarily be up to date when the user unboxes the machine. This means that the user will need to update the software. Various computer manufacturers test and provide various versions of our software on their own support pages at their discretion, so the version of our software that you might find elsewhere on the web may not be the most up to date. If you are experiencing memory leaks, we highly suggest downloading and running the latest Killer Control Center installation package direclty from us, from this location - http://www.killernetworking.com/driver-downloads/item/killer-control-center-x64. If you experience any memory leaks, or any other issues with the latest Killer Control Center, please reach out to us at the contact information below. 

Wi-Fi: No Access Points with 1525 Using Killer Control Center 1.4.1500

 

No Wi-Fi Access Points with 1525 Using Killer Control Center 1.4.1500

This issue only affects users who have installed Killer Control Center 1.4.1500, or who installed drivers from that same version number of driver installer. If you are using the Killer Control Center, you can check your driver number by clicking the Settings button in the Killer Control Center. Version 1.4.1503 has now been released as of October 12 2017, and fixes this issue. Users with this problem should be able to simply download the package from here - http://www.killernetworking.com/driver-downloads/item/killer-control-center-x64 - and install it. It will update the components automatically. If the installer asks to close the applications in order to update them, keep telling it to close the needed applications, and it will finish the install after a few tries, if necessary. If you are unable to fix the issue in this manner, feel free to contact support. 

Ethernet Adapter No Longer In Device Manager

 

When a device goes missing from the Device Manager, it means that either the BIOS or the operating system is not enumerating the device for some reason. Check for another device in Device Manager that may be the Ethernet controller, but not labeled as such. It may be called "Unknown Device" or "Network Controller." If such a device exists, you can usually simply right-click on that device and click Update Driver and the problem will resolve itself from there.

If there is nothing at all indicating the existence of the Ethernet device, then the device may have been disbled in the BIOS. If you have recently made changes in the BIOS, then this would be worth checking. It's usually a fairly obvious setting, such as "Enable onboard LAN" that has been unchecked. If you have not changed anything in the BIOS, check to with your machine or mainboard manufacturer to make sure that you are using the most up to date version of the BIOS available. 

If you have ruled out the above, you may be able to uninstall and reinstall the drivers for the device by following these steps:

  1. Download the latest Killer Control Center installer from here - http://www.killernetworking.com/driver-downloads/item/killer-control-center-x64. If you do not have another adapter on that machine, you may need to use a USB drive, or some other method of moving the file onto the machine.
  2. Right-click Start and click Apps and Features
  3. Find any "Killer" entry and uninstall it, including "Killer Drivers" or "Killer Performance Suite" or any variation.
  4. Restart the machine by clicking Start > Power > Restart
  5. Once the machine has booted back up, right-click start and click Device Manager
  6. Click View and click Show hidden devices
  7. Hopefully the missing adapter will show up, albeit grayed out. Right click on it, and click Uninstall Device.
  8. Check the box for Delete the driver software for this device , if it exists, then click Uninstall.
  9. Click the light blue Scan for hardware changes icon at the top of Device Manager.
  10. If the adapter reppears, close the Device Manager and run the installer for the latest Killer Control Center. If it does not, restart the computer.

If the adapter still does not appear, then try updating all of the drivers available from your mainboard or machine manufacturer. The chipset driver is especially important. Uninstalling the most recent Windows Updates may also help, especially if the issue was first noticed after a Windows Update. Sometimes, uninstalling and reinstalling the Windows Update in question will result in a more successful outcome, with a working Ethernet adapter. 

Bluetooth with Killer Wireless-N or Wireless-AC is Not Working

 

The Bluetooth with My Killer Wireless-N or Wireless-AC is Not Working

Note: If your Bluetooth device is missing from Device Manager entirely, please see this KB article: http://www.killernetworking.com/driver-downloads/kb/faq/31-bluetooth-missing-from-device-manager

Ensure that you have downloaded the proper version of Killer Bluetooth software for your Killer Wireless card.

  • Please note that the Killer Wireless-N 1202 has a single Bluetooth installer for Windows 7, 8.1, and 10.
  • For Killer Wireless-AC products, please ensure you have downloaded the appropriate version for your adapter and OS, as the Bluetooth software is not unified.

All Bluetooth driver downloads are available here:

http://www.killernetworking.com/driver-downloads/category/bluetooth

 

Error 1721 Upon Killer Network Manager Installation

 

Error 1721 Upon Killer Network Manager Installation

Please note that this KB article only pertains to legacy products. If you are encountering issues with a currently supported Killer Network Adapter (Killer E2200, E2400, E2500, and all Wireless adapters) you can find the latest suite (Killer Control Center) here - http://www.killernetworking.com/driver-downloads/item/killer-control-center-x64. Please download the Killer Control Center, uninstall the Killer Network Manager and any Killer Drivers listed in your Apps and Features or Add/Remove Programs menu, restart, then install the Killer Control Center.

PROBLEM: Upon installation of the 6.0 software suite, you receive this error:

*Bigfoot Networks Killer Network Manager Error

*Error 1721.There is a problem with this Windows Installer package. A program required for this install to complete could not be run. Contact your support personnel or package vendor. Action: RegisterLSP64, location: C:Program Files\Bigfoot Networks\Killer Network Manager\KillerTool.exe, command: -lsp-map

SOLUTION: Install Microsoft .NET Framework 3.5 Service Pack 1. This update is also part of the Windows Automatic Update.

The direct download for this pack can be found here.

 

LSP Not Mapped Correctly

 

LSP Not Mapped Correctly

If you are encountering this error while using a currently supported Killer Network Adapter, such as the Killer E2200 or any Killer Wireless Adapter, please download the latest Killer Control Center from here - http://www.killernetworking.com/driver-downloads/item/killer-control-center-x64 - uninstall all "Killer' applications from your Apps and Features or Add/Remove Programs menu, including "Killer Drivers" or "Killer Performance Suite", restart your machine, and then run the installer that you downloaded to install the latest Killer Control Center, along with the latest drivers for your network adapter.

If you are using a Legacy Killer product, please continue reading. 

The Killer 2100/Xeno Pro employed a LSP (Layered Service Provider). While this is beneficial in allowing the Killer software to enable offload and lower latency, it has been found to be incompatable with some games, thus creating instability or crashes. If you are experiencing any crashes while playing games, it is recommended that you 'unmap' the LSP. Prioritization and other Killer freatures will continue to function.

Note: The Killer Network Manager application will warn you on each startup that the LSP is unmapped. You should choose 'no' to remapping. There is not currently a workaround to prevent the Network Manager from throwing this message.

This is done with the following steps:

Start an administrative command prompt and type these commands:

cd "\Program Files\Bigfoot Networks\Killer Network Manager"
killertool -lsp-unmap

Legacy Products and iTunes

 

iTunes Will Not Connect

A software update is needed. The latest Legacy drivers can be found here:

https://www.visiontek.com/support/download-drivers.html

A successful update will remedy connectivity errors with iTunes and other Apple software.

  Please note that this KB article only pertains to legacy products. If you are encountering this issue with a currently supported Killer Network Adapter (Killer E2200, E2400, E2500, and all Wireless adapters), please make sure that you are running the latest Killer Control Center - http://www.killernetworking.com/driver-downloads/item/killer-control-center-x64 - and, if that does not solve the issue, please contact support so that we may help you further. 

Legacy Killer Network Manager Asking for Flash Installation

 

The Network Manager Repeatedly Asks for Flash to be Installed

This error can be corrected by installing Flash within Internet Explorer, which is where the Killer app performs its check. You do not need to use IE as your browser going forward, but simply open IE, install Flash, and it should resolve the issue.

  Please note that this KB article only pertains to legacy products. If you are encountering this issue with a currently supported Killer Network Adapter (Killer E2200, E2400, E2500, and all Wireless adapters), please make sure that you are running the latest Killer Control Center - http://www.killernetworking.com/driver-downloads/item/killer-control-center-x64 - and, if that does not solve the issue, please contact support so that we may help you further. 

Legacy Products and Connections With Online Games

 

Problems Connecting to Grand Theft Auto 5, or Another Online Game.

Please note that this KB article only pertains to legacy products. If you are encountering connectivity issues with a currently supported Killer Network Adapter (Killer E2200, E2400, E2500, and all Wireless adapters), please make sure that you are running the latest Killer Control Center - http://www.killernetworking.com/driver-downloads/item/killer-control-center-x64 - and, if that does not solve the issue, please contact support so that we may help you further. 

Some newer games are not compatible with the Killer Xeno Pro/Killer 2100's offload solution. If you are having issues connecting to a particular game, there is a workaround to tell the Killer software to not bypass the Windows network stack for that particular process/game. The game will still get the highest priority with this method.The solution is to add the particular processes (such as hl2.exe for TF2, or GTA5.exe), to the gamedetect file.

First, ensure you know the full exe name of the game/process with the issue.

Then, go to C:\ProgramData\Bigfoot Networks . This folder is hidden by default. If you cannot find this folder, you will either need to turn off hidden files and folders, or type the path in full into windows explorer.

Once in the Bigfoot Networks ProgramData folder, right-click the GameDetect.xml file and click "Edit".

From here, you'll see a section at the top that looks like this:

<GameDetectSettings>
     <ByPassSection>
     <ByPass>mozybackup.exe</ByPass>
     <ByPass>mozystat.exe</ByPass>
     <ByPass>mozyconfig.exe</ByPass>

All you need to do is add a new line right under the mozy stuff and replace it with your application .exe. So, it should look something like this:

<ByPass>GTA5.exe</ByPass>

Then save the file and exit, then you'll need to reboot. You should then be able to connect to your game.

 

Legacy Products and Instability With Online Games

 

Instability When Playing Certain Games on Killer 2100 / E2100 / Xeno Pro

Please note that this KB article only pertains to legacy products. If you are encountering a stability issue that you believe is connected to a currently supported Killer Network Adapter (Killer E2200, E2400, E2500, and all Wireless adapters), please make sure that you are running the latest Killer Control Center - http://www.killernetworking.com/driver-downloads/item/killer-control-center-x64 - and, if that does not solve the issue, please contact support so that we may help you further. 

The Killer 2100/Xeno Pro employed a LSP (Layered Service Provider). While this is beneficial in allowing the Killer software to enable offload and lower latency, it has been found to be incompatable with some games, thus creating instability or crashes. If you are experiencing any crashes while playing games, it is recommended that you 'unmap' the LSP. Prioritization and other Killer freatures will continue to function.

Note: The Killer Network Manager application will warn you on each startup that the LSP is unmapped. You should choose 'no' to remapping. There is not currently a workaround to prevent the Network Manager from throwing this message.

This is done with the following steps:

Start an administrative command prompt and type these commands:

cd "\Program Files\Bigfoot Networks\Killer Network Manager"
killertool -lsp-unmap

 

Devices in USB Port on the Killer Xeno Pro Do Not Function

 

USB Devices Plugged into the USB Port on the Killer Xeno Pro Do Not Function

This behavior is by design. The USB port on the Killer NIC is only accessible from FNApps that run on the card itself. The only physical connection accessible from Windows is the RJ-45 network port.

 

Legacy Products And Issues With The QQ Chat Application

 

Unable to Establish a Connection with the QQ Chat Application

After opening QQ Chat, from the “Applications” tab of the Killer Network Manager, click on the QQ Chat process. Switch the priority from 1 to either 2, 3, or 4. This will allow the application to connect as normal.

 Please note that this KB article only pertains to legacy products. If you are encountering this issue with a currently supported Killer Network Adapter (Killer E2200, E2400, E2500, and all Wireless adapters), please make sure that you are running the latest Killer Control Center - http://www.killernetworking.com/driver-downloads/item/killer-control-center-x64 - and, if that does not solve the issue, please contact support so that we may help you further. 

Have a question about your Killer product that isn't answered in our Knowledge Base?  Contact Us.