Disconnect Rob Run External: setup & troubleshooting
Install the loader, inject Disconnect Rob Run External and fix common loader errors - based on the vendor's official setup and troubleshooting guide.
This guide follows the vendor's official setup and troubleshooting instructions. Stuck at any point? Open a ticket at support with your order number and a screenshot of the error.
Before you start
- Your license key - it is in your order confirmation email and under your orders.
- Windows 10 or 11 (64-bit).
- More than 8 GB of RAM - the vendor lists low memory as the cause of "Exhausted System Resources" errors.
- A stable internet connection.
Security software
The vendor requires antivirus software, Windows Defender real-time protection and always-running anti-cheat services (for example FACEIT or Vanguard) to be uninstalled or turned off before you use the loader. Only download files from the official links in this guide.
Setup
Шаг 1: Install the Visual C++ runtimes
Download Visual-C-Runtimes.zip and extract it.
Right-click install_all.bat and choose Run as administrator to install all required runtimes.
Шаг 2: Install the DirectX runtime
Download and install the Microsoft DirectX End-User Runtime.
Шаг 3: Turn off conflicting software
Uninstall or turn off your antivirus, Windows Defender real-time protection and anti-cheat services such as FACEIT or Vanguard.
Предупреждение:Kaspersky and Norton are named by the vendor as known causes of loader errors.
Шаг 4: Download your loader
Go to cheezit.life, enter your license key and click Download. Your personal loader build downloads automatically.
Совет:If the page doesn't load or asks for a VPN, connect to a VPN (the vendor suggests TunnelBear) and try again.
Шаг 5: Log in to the loader
Open the loader. Log in with your existing account, or create a new account with your license key.
Совет:Open the loader only once per session - several loaders at the same time invalidate your session (error 0x15).
Шаг 6: Inject
Go to the Products page inside the loader, select the Rob Run product and click Inject.
Menu not showing? Enable Discord's legacy overlay
The vendor's guide asks for Discord's legacy game overlay. If the menu doesn't appear in game, check these settings:
- Use the official Discord app from discord.com.
- Open User Settings → Game Overlay.
- Turn Enable Overlay off and Enable Legacy Overlay on.
- Start the game, open the same menu again and make sure the game is switched on under "Currently Playing".
- Go back to the game and wait a moment - the menu should appear.
Quick fixes
- Something failed? Log out of the loader, log back in and inject again - many issues are fixed by a retry.
- Still failing? Restart your PC and inject again.
- ESP lagging: lower the game's FPS limit and graphics settings, and turn on the cheat's optimized rendering options.
- ESP shaky or blurry: turn off Anti-Aliasing and NVIDIA DLSS in the game settings.
- Download page or loader won't load: connect to a VPN and try again.
Common problems
The menu never appears
Check the Discord legacy overlay settings above. Then verify the game files (Steam: right-click the game → Properties → Installed Files → Verify integrity), make sure the default game version is installed (Properties → Game Versions & Betas → Default) and reinstall the game if needed. Make sure no antivirus or system monitoring tool is running.
The menu is frozen or there is no ESP
Verify the game files, check the game version and reinstall the game if needed (see above). Right after a game update the cheat may need an update from the vendor first - check our status page.
The cheat crashes
Inject again a few times and restart your PC. Remove antivirus and system monitoring tools (Windows Defender included).
The loader crashes at login
Usually a wrong password - check every letter and number. Lost your password? Open a support ticket and we request a password reset from the vendor.
"Invalid HWID"
Open a support ticket with your order number and loader username - we request a HWID reset from the vendor.
Windows version not supported
Errors such as 0x4 : 0x13, 0x5 : 0x1 or 0x5 : 0x4 mean the vendor doesn't support your Windows build yet. Open a ticket with your Loader.log and the system file the vendor asks for; according to the vendor, support for a new build can take 24-48 hours after the files are submitted.
Error codes
| Error | Meaning | What to try |
|---|---|---|
| Initial 0x0, Build 0x0, 1192 | Connection blocked (ISP or firewall) | VPN in another region; turn off Windows Firewall and your ISP's protection |
| Initial 0x1 / 0x2, Build 0x1 | Authentication failed | Download a fresh loader from cheezit.life with your key; try a VPN |
| Initial 0x3 | Missing runtimes | Install the Visual C++ and DirectX runtimes; update Windows |
| Initial 0x4, Build 0x2 | Module setup failed | Remove antivirus / system monitoring tools (Defender included) |
| Bypass 0x0 : 0x0, Injection 0x0 | Authentication failed | Use a stable connection; try a VPN |
| Bypass 0x0 : 0x2, Injection 0x4 | Bypass / write failure | Restart your PC and inject again |
| Bypass 0x0 : 0x8 | Driver couldn't load | Uninstall FACEIT and other always-on anti-cheats; turn off the Vulnerable Driver Blocklist; remove antivirus |
| Bypass 0x1 : 0x0 - 0x1 : 0x4 | Bypass failure | Uninstall FACEIT; remove antivirus (Kaspersky and Norton are known causes) |
| Bypass 0x4 : 0x4 / 0x5 / 0x7 / 0x9 | Not enough system resources | More than 8 GB RAM; remove antivirus |
| Bypass 0x4 : 0x10 / 0x11, 0x5 : 0x0 / 0x3 | Bypass failure | Turn off Virtualization Based Security (VBS); remove antivirus |
| Injection 0x15 : 0x5 | Client mapping failure | Install the runtimes; update Windows |
| 0x15 (validation) | Session invalid | Open only one loader at a time |
Your code isn't listed? The vendor keeps the full list on its troubleshooting page. Codes marked "no known fixes" there (for example Bypass 0x0 : 0x1) need a support ticket.
Collect a log for support
- Open the loader and log in. Before choosing a product, open the Settings tab.
- Turn on all checkboxes there.
- Inject and wait for the error, then wait another 30-60 seconds.
- Open
C:\Users\Public\and attach the.logfiles (for example Loader.log) to your ticket.

