Live fire.
Reference-build status is armed and undetected against the current Ricochet build. Channel 04 boot-tested at T+1h 47m from the MW4 beta drop on 21 August 2026. Last verified 22 August 2026 · 14:22 UTC.
What “undetected” means to us.
Any loader can say “undetected.” Most sites use the word until they get caught, then quietly stop saying it. Here’s the harder answer.
-
Undetected means: Zero detection events reported against the reference build in the current Ricochet cycle. If Ricochet flagged a session running our loader, the log above would show a
DETECTEDrow within hours. It doesn’t. That is the entirety of the claim. - Undetected does NOT mean: Ricochet will never catch this loader. It will, eventually, if we don’t move first. Every private loader on the market has been detected at some point. What separates a working ops-shop from a dead one is the repatch clock — ours is 2-hour target after each Ricochet push.
- Undetected right now: Reference build armed since T+1h 47m of the 21 August 2026 MW4 beta launch. Zero detection events across every session in the last 24hr window. Channel 04 holding.
Where the loader boots undetected.
Windows configurations the reference build is tested against, and known conflicts we’ve seen in the field. If your rig is on the wrong side of any row, the loader still refunds under the 24-hour window.
| Requirement | Status | Notes |
|---|---|---|
| Windows 10 22H2 | ✓ Undetected | Fully tested. Reference rig runs this build. |
| Windows 11 23H2 / 24H2 | ✓ Undetected | Fully tested. TPM 2.0 handshake stable across both semi-annual updates. |
| TPM 2.0 | ✓ Required | Ricochet enforces TPM 2.0 attestation at boot — loader boot-checks and refuses on TPM 1.2. |
| Secure Boot | ✓ Required | Must be ENABLED. Secure Boot disabled = Ricochet immediate flag before the loader even injects. |
| HVCI / Memory Integrity | ? Toggle off | Loader detects HVCI at first boot and prompts you to disable it. Root cause: driver-level module needs kernel access HVCI blocks. |
| Windows Defender (real-time) | ✓ One folder exclusion | Defender stays running. Exclusion is only the loader’s install directory. Never fully disable AV. |
| Third-party AV (Norton, Kaspersky, ESET, etc.) | ? Uninstall | Known conflicts with heuristic engines. Uninstall (not just disable) before running the loader. |
| Overlays (Discord, GeForce Experience, Steam) | ? Disable in-game | Ricochet fingerprints game-process overlays. Disable in each app’s game-specific settings. |
| Virtualization / VM guests | ✗ Not supported | Ricochet detects VM environment via CPUID and refuses launch entirely. Bare metal only. |
— Matrix updated with each Ricochet cycle. Log rows below.
Every push, logged.
The MW4 loader shipped alongside beta on 21 August 2026. The log below is short by design — it grows one row per Ricochet cycle. Undetected status stamps are auto-generated by the ops desk.
— Log auto-updates from the ops desk each cycle. Ricochet pushes since beta launch: 1. Reference-build detection events since launch: 0.
Get armed.
The loader is armed and undetected against today’s Ricochet build. Boot the console, drop in the next match.