Tutorials
Fix common issues before they ruin your session
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.
- Download the DirectX End-User Runtime Web Installer from Microsoft directly — search "directx end user runtime" on microsoft.com.
- Run dxwebsetup.exe as administrator and let it install all components.
- Reboot, then try the loader again.
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.
- Download Visual C++ Redistributable 2015–2022 — both x64 and x86 versions.
- Install both, reboot.
- If the error persists, also install the 2013 and 2012 versions — some dependencies chain back to them.
If the loader shows a .NET error dialog or silently exits, the required .NET version isn't present.
- Open Settings → Apps → Optional features → More Windows features.
- Enable .NET Framework 3.5 and .NET Framework 4.8 if not already checked.
- Alternatively, download .NET Desktop Runtime 6.0+ from dotnet.microsoft.com.
- Reboot after install.
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.
- Open Windows Security → Virus & threat protection → Manage settings.
- Scroll to Exclusions → Add or remove exclusions.
- Add the entire Velox folder as a folder exclusion.
- Re-download the loader inside that folder — if it was already quarantined, restore it from Protection history first.
Injection timing is the most common cause here. The game needs to be fully loaded before you inject.
- Launch the game and wait until you're at the main menu, not mid-loading screen.
- Make sure the loader is running as Administrator.
- Disable any overlay software (Discord overlay, GeForce Experience, MSI Afterburner) — they compete for the same hooks.
- If you're on Windows 11, disable Memory Integrity: Settings → Privacy & Security → Windows Security → Device Security → Core isolation → turn off Memory integrity. Reboot.
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.
- Log into the member panel.
- Go to License → Reset HWID.
- Relaunch the loader — it will register the new HWID automatically on first run.
The menu adds some CPU/GPU overhead, but a significant FPS drop usually means something else is competing for resources.
- In the menu, set ESP refresh rate to a lower value — full-refresh ESP on every frame is expensive.
- Disable features you aren't using (radar, 3D bones) to reduce render calls.
- Make sure the game is running on your dedicated GPU, not integrated graphics. Check via Task Manager → Performance tab.
- Close Chrome, Discord streams, or anything else doing hardware-accelerated rendering simultaneously.
Periodic freezes are almost always caused by Windows doing something in the background during your session.
- Disable Xbox Game Bar: Settings → Gaming → Xbox Game Bar → off.
- Set your power plan to High Performance or Ultimate Performance: run powercfg /setactive 8c5e7fda-e8bf-4a96-9a85-a6e23a8c635c in an admin PowerShell.
- Disable Superfetch / SysMain: open Services (services.msc), find SysMain, set it to Disabled.
powercfg /duplicatescheme e9a42b02-d5df-448d-aa00-03f14749eb61