Kernel Input Setup

Introduction

If enabled, Speeder's kernel input allows your mouse and keyboard input to come from a physical mouse and keyboard installed on your computer. This is relatively significant because there will be no difference between a key you physically press and a key simulated by Speeder, preventing the anticheat from seeing the input as simulated. In the vast majority of cases, it will just work, and you don't have to do anything. However, if you experience the "failed to initialize" message when starting Speeder, you may have to do some additional work.

Setup

In most situations, kernel input is ON by default. In config.txt, check the line related to kernel input (varies by game). If the line is set to 1, kernel input is ON. However, if it fails to initialize, it will be disabled, and you should check the section below for possible solutions.

Once kernel input is enabled, you should set up the devices (i.e., keyboard & mouse) you want Speeder to use. This is technically not necessary, but if you don't do this, Speeder will choose random devices, which may look suspicious, as you will have input coming from two different devices. Ideally, you want Speeder to use the devices you are physically using. This way, there is no difference between your input and Speeder's input.

To figure out the correct device names, use the RawInput Detector utility here. Run the program as admin, press a key on your keyboard, press a key on your mouse, and you will now have the device names. These names will be automatically copied to your clipboard. At this point, simply open config.txt, go to the kernel input line, delete anything there (make the line blank), and then paste. The line will be filled out for you and will look like
1|\?\hid#bladesysvirthid&col15#1&2e315aa9&0&0004#{814b36c3-57ea-12e1-ba8d-10a3c92415ed}|\?\hid#bladesysvirthid&col12#1&2e515cb7&0&0003#{178ee321-96ea-31d1-ac4c-01a0c93455de}

The syntax of the line is
[enable kernel input]|[keyboard device name]|[mouse device name]
without the brackets, but you don't need to remember this if you follow the directions above.

What Do I Do if It Isn't Working?

The easiest way to fix kernel input is to use Launcher's "Initialize Kernel Input" checkbox. Simply check the box, and click Load Driver. Even if your driver is already loaded, it will still work. When you see the message box appear, you will need to unplug your keyboard and plug it back in. Assuming you have a normal USB mouse and keyboard, this method should always work. You can now run Speeder normally. However, if you are still having issues, read on.

Speeder relies on HID devices to send mouse and keyboard input. If you do not have an HID device installed for either your mouse or keyboard, the initialization will fail, and you will not be able to use kernel input. Fortunately, HID devices are extremely common. Most (all?) USB mice and keyboards are HID devices and will work fine with Speeder.

To see the HID devices you have installed on your computer, go to Device Manager and look under "Keyboards" and "Mice and other pointing devices." If you see "HID Keyboard Device" and "HID-compliant mouse," you should be all set.

If you do not have an HID device for either your keyboard or mouse, try to find a USB keyboard or mouse lying around (depending on which you are missing) and plug it in. Chances are it is an HID device and will work fine. Really cheap USB mice and keyboards are almost always HID devices, so, worst case, if you don't have one, you can spend $5 to get one.

If you are unable to use an HID device for some reason, you can set the kernel input line in config.txt to 0, and Speeder will use the Windows API to send input. For some games, this is fine and won't raise any red flags, but for others, it can be dangerous. For FPS games or games with an aimbot, I do not allow kernel input to be disabled for safety reasons. Always check the [Safety] section for each game.

Other Problems

Having Interception installed will cause kernel input to fail. Either uninstall it or set the kernel input line in config.txt to 0.

Avast antivirus (and maybe others?) can cause kernel input to fail. If you are having issues, I recommend temporarily disabling your antivirus so you can narrow down the problem. Windows Defender works fine.

Razer Synapse (and maybe other mouse software) can prevent kernel input from working correctly. Simply disable or uninstall Razer Synapse, and you should be all set. Please note that Razer Synapse will often run in the background without you knowing, so be sure to check services.msc, scroll down to Razer, and make sure none of the Razer services are "Running."

Scroll to Top