Tutorials

Fix common issues before they ruin your session

Runtime Errors
DirectX missing or outdated (d3d11.dll / dxgi.dll errors)

The most common crash on a fresh Windows install. The loader uses DirectX 11 for rendering — if the runtime is missing or outdated, it won't open.

  1. Download the DirectX End-User Runtime Web Installer from Microsoft directly — search "directx end user runtime" on microsoft.com.
  2. Run dxwebsetup.exe as administrator and let it install all components.
  3. Reboot, then try the loader again.
If you're on Windows 11 and it still fails, open PowerShell as admin and run: DISM /Online /Add-Capability /CapabilityName:DirectX~~~~0.0.1.0
VCRUNTIME140.dll / MSVCP140.dll not found

The loader is compiled with MSVC and requires the Visual C++ Redistributable. Missing DLL errors like VCRUNTIME140.dll or MSVCP140.dll mean it's not installed.

  1. Download Visual C++ Redistributable 2015–2022 — both x64 and x86 versions.
  2. Install both, reboot.
  3. If the error persists, also install the 2013 and 2012 versions — some dependencies chain back to them.
Fastest way: download "VisualCppRedist AIO" — it installs all versions in one click. Widely used in the community.
.NET Framework errors / application won't start

If the loader shows a .NET error dialog or silently exits, the required .NET version isn't present.

  1. Open Settings → Apps → Optional features → More Windows features.
  2. Enable .NET Framework 3.5 and .NET Framework 4.8 if not already checked.
  3. Alternatively, download .NET Desktop Runtime 6.0+ from dotnet.microsoft.com.
  4. Reboot after install.
Loader & Injection
Antivirus deletes or blocks the loader

The loader uses injection techniques that AV heuristics flag as malicious. It is a false positive — the file is clean. The AV doesn't know the difference between a cheat loader and malware using the same API calls.

  1. Open Windows Security → Virus & threat protection → Manage settings.
  2. Scroll to ExclusionsAdd or remove exclusions.
  3. Add the entire Velox folder as a folder exclusion.
  4. Re-download the loader inside that folder — if it was already quarantined, restore it from Protection history first.
Only add the exclusion for the Velox folder. Do not disable Windows Defender entirely — that's unnecessary and exposes your system.
Loader opens but injection fails / game crashes on inject

Injection timing is the most common cause here. The game needs to be fully loaded before you inject.

  1. Launch the game and wait until you're at the main menu, not mid-loading screen.
  2. Make sure the loader is running as Administrator.
  3. Disable any overlay software (Discord overlay, GeForce Experience, MSI Afterburner) — they compete for the same hooks.
  4. If you're on Windows 11, disable Memory Integrity: Settings → Privacy & Security → Windows Security → Device Security → Core isolation → turn off Memory integrity. Reboot.
Memory Integrity is a security feature. Turn it back on when you're not using the loader.
HWID mismatch / license invalid after hardware change

If you changed your GPU, motherboard, or reinstalled Windows, your HWID will no longer match the registered one. The loader will show a license error.

  1. Log into the member panel.
  2. Go to License → Reset HWID.
  3. Relaunch the loader — it will register the new HWID automatically on first run.
Lifetime plan has unlimited HWID resets. Basic plan resets are limited — contact support on Discord if you've run out.
Performance
FPS drops after injection

The menu adds some CPU/GPU overhead, but a significant FPS drop usually means something else is competing for resources.

  1. In the menu, set ESP refresh rate to a lower value — full-refresh ESP on every frame is expensive.
  2. Disable features you aren't using (radar, 3D bones) to reduce render calls.
  3. Make sure the game is running on your dedicated GPU, not integrated graphics. Check via Task Manager → Performance tab.
  4. Close Chrome, Discord streams, or anything else doing hardware-accelerated rendering simultaneously.
Game stutters / freezes for 1–2 seconds periodically

Periodic freezes are almost always caused by Windows doing something in the background during your session.

  1. Disable Xbox Game Bar: Settings → Gaming → Xbox Game Bar → off.
  2. Set your power plan to High Performance or Ultimate Performance: run powercfg /setactive 8c5e7fda-e8bf-4a96-9a85-a6e23a8c635c in an admin PowerShell.
  3. Disable Superfetch / SysMain: open Services (services.msc), find SysMain, set it to Disabled.
# Enable Ultimate Performance plan (run as admin)
powercfg /duplicatescheme e9a42b02-d5df-448d-aa00-03f14749eb61