MANUAL

FIRST LAUNCH TO FIRST RAID
1 — BEFORE YOU START
CHECKWHY
Windows 10/11 x64the loader is x64 only
VMware / VirtualBox / Hyper-V guestwill not run. a virtual machine is detected and the loader exits quietly rather than half-working
Antivirus exclusion for the loader folderav products quarantine the loader on sight; an exclusion avoids a false alarm and a broken install
Run as administratorrequested automatically; the prompt is expected
2 — LAUNCH
1.  Run WeepingAngel_Loader.exe  (accept the UAC prompt)
2.  Sign in with the email and password your licence was issued to
3.  Press LAUNCH once
4.  Start Escape from Tarkov whenever you like
You only press LAUNCH once. It arms an attachment that waits for Tarkov to appear — you do not need to re-launch it between raids, and raids are not separate processes, so the overlay survives entering, dying and extracting without being re-injected.
3 — IN GAME
INPUTACTION
INSERTopen or close the overlay menu
mousethe menu unclips the cursor while it is open and restores it when it closes
F1…every bind is listed, and rebindable, inside the menu

The menu is drawn by the loader, not injected into the game, so it is unaffected by game resolution changes.

4 — WHEN SOMETHING IS WRONG
SYMPTOMCAUSE AND FIX
Loader closes immediately, no windowyou are in a virtual machine, or a debugger is attached. Both are deliberate refusals
"invalid email or password"credentials, not the licence. Passwords are case-sensitive
"no active licence on this account"the licence expired or was revoked. Check store or the forum
"this machine does not match the licensed one"the licence is enrolled elsewhere. Open a forum thread with your HWID from the loader window
Menu does not appear in raidthe game launched before LAUNCH armed, or the overlay is bound to a key you have rebound. Restart the loader, then the game
Game update broke thingsit will. Check status; the loader refuses rather than running against offsets it has not verified
5 — HARDWARE CHANGES

Your licence is bound to a weighted set of machine identifiers, not a single hash, so real upgrades are tolerated: a new GPU, a re-cabled NIC or a moved drive keeps working. Changing the motherboard and the system disk together does not — that is a different machine, and it will be treated as one.