Evadus Setup Guide
Everything you need to install, configure, and troubleshoot Evadus — back to the main page →
Set this up weeks before your exam, not the night before. You need time to test against your school's actual LDB build and get comfortable with the controls. Getting caught is an academic integrity violation — expulsion-tier, premeditated category.
The Gemini window is visible. If your exam is screen-recorded (Respondus Monitor) or proctor-reviewed, the AI window is in the recording. Know what your school records before you use this.
Download the installer
From the main Evadus page, hit Get Evadus and pick Official Site (evadus.net — always the latest version) or Direct Download (our Mediafire mirror of the same installer).
Your browser will warn that the file could be harmful. That's the standard warning for unsigned installers — keep the file.
Handle the antivirus flag
Expect a flag — it's a known false positive (full explanation in the troubleshooting section below). The clean fix: add an exclusion for the Evadus folder in Windows Security before running the installer, and leave your real-time protection fully on.
Windows 11: Smart App Control
If Smart App Control is enabled, it will block Evadus immediately — SAC has no exclusion system and blocks all unsigned binaries by design. Turn it off: Windows Security → App & browser control → Smart App Control settings → Off.
Run the installer
Double-click the installer. You'll hit a SmartScreen warning ("Windows protected your PC") — click More info → Run anyway. If UAC asks for permission, click Yes.
Follow the wizard — Next → Install → Finish. Nothing to configure during install.
Log in and check your settings
When the launcher appears, click Login to Evadus and create a free account. The core functionality is free — no paid tier required.
Before your first run, open Evadus's settings and make sure the renderer mode is set to Any Renderer — not Protected. See the troubleshooting section below if the window won't load.
Evadus is an injector — it opens a handle to another process, allocates memory inside it, and runs code there. That exact sequence of Windows calls (OpenProcess → VirtualAllocEx → WriteProcessMemory → CreateRemoteThread) is also how a large portion of real malware works. Antivirus engines can't easily tell "injector doing something the user asked for" from "injector installing a payload," so they flag the pattern, not the behavior.
That's why our scan result matters: 1 of 70 engines flagged it on VirusTotal, and the single flag is a low-confidence machine-learning heuristic — a statistical model saying "this looks sort of like injection software," not "this matches a known threat." A real rat or stealer scores 35-60+ detections with named malware families. One low-confidence ML heuristic on an injector is the textbook false-positive fingerprint. HitmanPro (behavioral second-opinion scanner) came back completely clean as well.
How to avoid the flag without disabling your AV: add an exclusion — Windows Security → Virus & threat protection → Manage settings → Exclusions → Add an exclusion → select the Evadus install folder. With the exclusion in place, real-time protection stays fully on and the file never gets quarantined. Only disable protection temporarily if the exclusion alone doesn't stop it, and re-enable immediately after. And remember: on Windows 11, Smart App Control blocks unsigned binaries regardless of exclusions — it has to be off while using Evadus.
Check the renderer mode in Evadus's settings. If it's set to Protected — or any setting other than standard — the window can fail to render on some setups. This is the most common cause of "installed but nothing appears."
Switch it to Any Renderer, then fully restart Evadus — quit it from the system tray and relaunch, don't just toggle the window. Test again.
If it still won't render after that, note your Windows version and GPU and report it in the Discord so we can document the cause.
Your antivirus quarantined it before it could execute, or Smart App Control is on. Check Windows Security → Protection History for the quarantine, add the exclusion (see the first item above), and turn SAC off on Windows 11. Re-download the installer if the file was deleted.
Most likely your school runs a different LDB version than the one we confirmed (2.1.5.01). Note your LDB version and report it in the Discord — if a build is broken, the status on the main page changes. Do not use it on a real exam untested.
Stop. Close it, finish the exam honestly or talk to your teacher about a technical issue. Pushing through a flagged session turns a technical problem into a documented one. Then report what happened in the Discord so everyone learns from it.
Click each item as you confirm it. If every box isn't checked, you're not ready.
Setup done? Report your result.
Your LDB version + whether it worked keeps the status honest for everyone. Takes 30 seconds in the Discord — and it's how a tool stays confirmed instead of silently going dead.
Report in the Discord