Home Terms of use Help

Problems & errors

Why the software may fail to start and what to do about specific loader errors.

The software will not start

Most often the file has already been removed by your antivirus or Windows Defender — they treat private software as a threat. Add the folder to the exclusions BEFORE unpacking the archive, then download it again and run it as administrator. If the folder disappears by itself, the protection is still active.

System components are missing. Install Visual C++, DirectX and .NET Framework — the links are collected above in the recommended drivers section — then restart the computer.

Vanguard, FACEIT and ESEA work at driver level and load together with the system — closing them in the tray is not enough, they have to be uninstalled and the computer restarted. Simply logging out of the client will not help.

Check two things: the game must be in borderless windowed mode (in fullscreen the overlay often is not drawn), and the menu opens with the assigned key — it is listed in the instructions for that specific product.

Usually the culprit is a conflict with third-party overlays: Discord, GeForce Experience, MSI Afterburner, RivaTuner. Turn their overlays off completely and try again.

A key is bound to a specific product and may already be activated on other hardware. Make sure you are running exactly the loader the key was bought for, and write to support — we check the binding against your order.

The binding goes to your hardware fingerprint (HWID), and after a hardware change it no longer matches. Support resets it manually; note that frequent resets are limited — the rules are described in the terms of use.

That means a game or anti-cheat update has shipped and the developer is adapting the software. It must not be launched meanwhile — wait for the status on the product card to change. We refresh statuses daily.

Specific loader errors

The system has no Visual C++ 2010 libraries. Remove the already installed Visual C++ packages via Programs and Features, install the full set of all versions again from the Software and drivers section, and restart. Installing only the newest version is useless — the older libraries are not included in it.

DirectX 9 libraries are missing. Even on Windows 11 with a fresh DirectX 12 the d3dx9 files do not appear on their own — you need the DirectX End-User Runtime installer from the Software and drivers section, then restart the computer.

The loader files are damaged or did not download completely. Delete the folder entirely, add a new folder to the antivirus exclusions BEFORE downloading, download the archive again, install DirectX, reinstall the graphics driver and restart.

The interface cannot be drawn: either the loader files are damaged or the graphics driver is outdated. Download the loader again into a clean folder, install DirectX, update the Nvidia or AMD driver and restart.

The software driver does not load — it is blocked by the antivirus or an installed anti-cheat. Uninstall (actually uninstall, not close) FACEIT, ESEA and Vanguard, turn off any third-party antivirus and restart the computer.

The same as ke drv err: the driver does not start because of protection. Check that no anti-cheats or antivirus software are left in the system and that the loader folder is in the Windows Defender exclusions.

A variant of the same error for the 64-bit driver. Remove anti-cheats and antivirus, add the folder to the exclusions, restart and run the loader as administrator.

The loader could not inject into the game process — the injection was intercepted by an antivirus or an anti-cheat. Remove them from startup, uninstall FACEIT and similar clients, then run the loader as administrator.

64-bit Windows is required. The software does not work on 32-bit systems. Check with Win + Pause, the System type line — it must say 64-bit. If it is 32-bit, only reinstalling Windows as x64 will help.

Your Windows version or architecture does not match the software requirements. Open the System requirements tab on the product page and compare the version and build — some products do not support every Windows build.

The launch is blocked by system protection. Turn off the antivirus, Windows Defender, the Windows firewall and SmartScreen, add the loader folder to the exclusions and try again. Instructions for each step are collected in the Software and drivers section.

The same cause as ep err: 49 — one of the Windows protections triggered. Turn off Defender, the firewall and SmartScreen, remove any third-party antivirus, then restart the loader.