Serenity Cheat
Setup and troubleshooting for Serenity Cheat on Rust.
Runs beside Rust rather than inside it. Lighter touch, lower risk surface.
| Game | Rust |
| Type | External |
| Status at last import | Undetected |
| Supported OS | Windows 10, Windows 11 |
| CPU | Intel, AMD |
Status changes faster than this page does. spookycheats.io/status is the live one, and it is what your days are counted against.
Durations
| Duration | Price | |
|---|---|---|
| 1 day | $4.99 | In stock |
| 1 week | $24.99 | In stock |
| 1 month | $49.99 | In stock |
Requirements
Serenity is strict about the machine, and it checks before it will inject. Get these right first — most "the loader does nothing" reports are one of them.
| RAM | 16 GB |
| CPU | Intel or AMD, with the AES instruction set |
| BIOS — virtualisation | SVM (AMD) or VT-x (Intel), enabled |
| BIOS — Secure Boot | disabled |
| Hyper-V | enabled, on both Intel and AMD |
| Firmware | UEFI |
| Disk format | GPT |
| Windows | 10 or 11, versions 21H2 through 25H2 |
The AES requirement is the one you cannot work around. If your CPU does not support it, no setting changes that — the build will not run on that machine.
Note that Hyper-V is on for Rust. Our ARC Raiders build wants it off on AMD, so if you run both, that is a setting you change between them.
You will also need the Visual C++ runtimes and the DirectX end-user runtime installed, and your antivirus off. Windows Defender removes the loader on sight.
Download
Serenity loader
Hosted by Serenity. Your key from your account unlocks it.
- Updated
- 2026-10-28
Setup
Turn off antivirus first
Every loader of this kind looks like malware to a scanner, because the thing it does and the thing malware does are the same shape. Defender will quarantine it mid-download and the file simply will not be where you put it.
Install an overlay
The menu draws through someone else's overlay rather than its own. Pick one:
| Overlay | Fullscreen | Works with |
|---|---|---|
| SteelSeries GG | Yes | NVIDIA and AMD |
| NVIDIA App | No | NVIDIA only |
| Medal | No | Any |
| Discord | No | Any |
On an AMD card, SteelSeries is your only option. It is also the only one that survives fullscreen, so it is the one to pick unless you have a reason not to.
For SteelSeries: turn Sonar on under Settings → General, then under Sonar → Shortcuts bind Master – Volume Up to F7. Press that bind before you inject, every time. For the NVIDIA App, enable the in-game overlay under Settings → General. For Discord, enable the game overlay, turn off Legacy Overlay, and turn on Hardware Acceleration under Appearance → Advanced.
Using the spoofer too? Run the cheat first and the spoofer second. The other order is the most common way people get banned with both installed.
First run
- Antivirus off.
- Press your overlay bind, if you are on SteelSeries.
- Run the loader.
- Paste the key from your account.
- Press inject.
- Wait for the loader to close by itself. That is the signal it worked — do not start the game before it does.
- Start Rust.
- Press Insert in game to open the menu.
If the loader closes on its own and Insert brings up a menu, you are done.
Known problems
Loader hangs on the loading screen. Put it in a new, empty folder of its own — not Downloads, not beside anything else — and run it as administrator. This fixes it far more often than it has any right to.
No menu, or the loader shuts instantly. The Visual C++ x64 redistributable is missing. Install it and try again.
Menu flickers, or the screen goes black. In SteelSeries, go to Settings → Moments → Capture and sound and turn off capturing while gaming.
"No suitable overlay". Turn the overlay off and back on, then re-inject.
Overlay errors naming GeForce or Sonar. For GeForce, toggle the overlay off and on. For SteelSeries, you missed the F7 bind before injecting.
Error 0x296. Re-inject.
Bind does nothing. Re-inject first; if it still does nothing, run the overlay itself as administrator.
Dependency or memory errors. Turn off every protection program, clear your startup programs, and reboot. Keep the loader on a real disk — running it out of OneDrive or a cloud-synced folder causes this.
Virtualisation errors. Turn off Virtual Machine Platform and Hypervisor Platform under Windows Features, reboot, and check SVM or VT-x is on in BIOS.
Vanguard or FACEIT installed. They conflict. Uninstall them — disabling is not enough, both run a driver at boot.
Network errors. Check the connection and turn off any VPN.
This build has no spoofer in it. If you are banned, you are banned on hardware, and getting back in means the spoofer or new parts.
Anything not on this list belongs in Common problems, and if it is not there either, ask in Discord.