Wardogs Cheats troubleshooting.

Symptom: Windows Security quarantines the executable, or the loader launches then immediately closes. Fix: re-check that the Defender folder exclusion covers the exact loader folder path, not just a parent folder. Re-download the loader after the exclusion is in place; the quarantined copy has already been altered by Defender. Full walkthrough in Install · Step 4.

Symptom: machine crashes with a stop code (usually KERNEL_SECURITY_CHECK_FAILURE or DRIVER_VERIFIER) when the loader tries to arm. Cause: Windows 11 Memory Integrity (Core Isolation) is on and blocking the loader’s driver setup. Fix: turn it off in Windows Security → Device Security → Core Isolation. Reboot after the toggle before running the loader again.

Two common causes. First: check the status page — if the build is paused, keys don’t authenticate until the pause lifts. Second: check the key you pasted has no leading/trailing whitespace (email clients sometimes wrap it). If both are clean and it still fails, ping Discord with your license email; the operator can force-re-issue.

Loader launches, task manager shows the process, no window. Two things to try: run as admin (right-click → Run as administrator) — needed once for driver setup; and check if another instance is already running (kill any hidden copies from Task Manager). If it still won’t appear, delete the config folder (%APPDATA%\wardogs-loader) and re-launch to force a fresh session.

Cause: something else is intercepting the key (Windows Sticky Keys, a game overlay like Xbox Game Bar, or a macro tool). Fix: rebind the menu key from Misc → Keybinds to a different key you know is free (F10 and Insert are safe choices). See menu overview → Misc keybinds.

The overlay draws on top of the game frame — it won’t appear if the game is in exclusive-fullscreen and refuses external overlays. Switch WARDOGS to Borderless Windowed in graphics settings. If that doesn’t fix it, Alt+Enter cycles fullscreen modes and can force a re-render of overlay layers.

Two common causes. Thermal: GPU pushed past its throttle point takes the loader with it — check GPU temp in HWMonitor or MSI Afterburner. Memory: 8 GB RAM is technically supported but tight; if you’re on 8 GB, close browser tabs before session start. If neither, turn on Verbose logging in Misc, reproduce the crash, and send the log to Discord.

If you have Riot Vanguard, FACEIT AC, or ESEA Client installed — even if not currently running — the boot-time drivers race the loader for memory-page access. Uninstall (not just close) the conflicting client, reboot, then run the loader. Vanguard uninstall specifically: right-click the tray icon → Exit, then use Programs & Features to remove Riot Vanguard. Full explainer in the EAC safety doc.

Three things to check, in order: is the tab enabled at the top? Are you in the right mode (hold-to-fire requires you to hold the bind, silent needs a trigger action)? Is the FOV cone too narrow — the default 40° works for most, but if you set it to 10° the assist only engages when the target is nearly centered. Also check the occluder gate isn’t filtering out targets you can visually see (rare but happens with certain map geometry).

Check the range slider — default 300 m works but if you set it too low, distant players won’t render. Then check the faction color filter isn’t set to a single team you’re not fighting. Then check Only if visible isn’t on when you’re expecting ESP for through-wall targets. Full switch reference in menu overview → ESP.

Capture-safe is on by default but only works against Game Capture or Display Capture using the same hooking layer the loader uses to hide. If you’re using Window Capture in OBS specifically, some versions capture the overlay because they screenshot at the composition layer. Switch to Game Capture and it hides cleanly. Discord Screen Share is Game Capture by default and works.

Almost always a permissions issue on the config folder (%APPDATA%\wardogs-loader\configs). If you launched the loader as admin once and now run as regular user, the folder may be admin-owned. Fix: right-click the folder → Properties → Security → give your user Full control. Or just delete the folder — the loader re-creates it on next run with your current user as owner.

Delivery ships to the email on your account. First place to check: your inbox (median delivery inside a minute of payment clearing). Second: spam folder — the delivery email sometimes gets flagged. Third: if the payment shows as pending on the processor’s side (crypto especially), delivery waits until on-chain confirmation. If it’s been over 15 minutes and nothing has landed, DM Discord with your payment receipt; the operator can push delivery manually.

Two self-serve resets per license cycle. Currently the reset routes through Discord — DM the operator with your license email + “HWID reset” and it’s a one-message turnaround. Third reset in the same cycle needs a short review; still Discord.

The toggle is a small JS script (currency.js). If your browser is blocking JS on the site (uBlock in strict mode, Brave Shields aggressive), the toggle stays on USD. Whitelist the site or trust the page and the toggle wakes up. The prices themselves are correct — the checkout page always shows the right amount in your card’s currency even if the on-page toggle didn’t update.