Support runs through Discord.
There is no ticket queue and no support inbox — every question about keys, setup or access is answered by a real person in our Discord.
Join the DiscordSupport articles
Work through these before opening a ticket — they cover almost every first-time setup problem.
Before you install
Install the C++ Redistributables and DirectXMissing DLL errors are runtime installs, not a broken loader. Do this once per Windows install.
- 1
Install both Visual C++ Redistributables.
- Run the x64 package first, then the x86 package — some games and overlay helpers still ship 32-bit binaries.
- Use the current supported release from Microsoft, never an “AIO” repack from a third-party site.
- 2
Install the DirectX End-User Runtime.
- Windows 10 and 11 ship DirectX 12 but not the legacy libraries — D3DX, XAudio2 and XInput are missing by default.
- The June 2010 web installer adds exactly those DLLs. Run it even though it looks dated.
- 3
Restart Windows.
- 4
Launch the loader again.
- If it still names a missing DLL, reinstall the package that owns it.
- msvcp140.dll / vcruntime140.dll → Visual C++ Redistributable.
- d3dx9_43.dll / XINPUT1_3.dll / xaudio2_7.dll → DirectX End-User Runtime.
If an installer reports that a newer version is already present, that is fine — skip it and move on. Nothing here needs to be repeated after a game update.
Turn Defender off with Defender Control (DControl)dControl.exe disables Microsoft Defender completely — Windows has no built-in option for that.
- 1
Download Defender Control from sordum.org and extract it.
- Only from the official page — do not take it from a mirror or a Discord upload.
- The archive is password-protected; the password is sordum.
- 2
Run dControl.exe as administrator.
- 3
Read the status indicator before changing anything.
- Green — Defender is running.
- Red — Defender is already off.
- Orange — Defender cannot start, or only real-time protection is off.
- 4
Press the disable button, then confirm the indicator turns red.
- If Tamper Protection is on, the tool has to route through TrustedInstaller — expect a 3–5 second pause per toggle.
- 5
Open the menu and choose “Add it to the Exclusion list”.
- This whitelists C:\Program Files (x86)\DefenderControl\dControl.exe so a later scan does not delete the tool.
- 6
Verify in Windows Security → Virus & threat protection.
- Protection should read as off or “managed by your administrator”.
Windows Update can switch Defender back on. Re-check the indicator before each session. To re-enable it, press the enable button, restart, and wait a few minutes — Defender restarts itself. If you only need the loader to survive a scan, a single folder exclusion is enough.
Disable Core Isolation (Memory Integrity / HVCI)Memory integrity and HVCI are the same feature. One toggle turns both off.
- 1
Open Windows Security → Device security → Core isolation details.
- 2
Set Memory integrity to Off, then restart when prompted.
- 3
If the toggle is greyed out, use the registry.
- Win + R → regedit → HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\DeviceGuard\Scenarios\HypervisorEnforcedCodeIntegrity
- Set Enabled (DWORD) to 0. Create it as a DWORD if it does not exist.
- Restart.
- 4
Confirm in msinfo32 — “Virtualization-based security Services Running” must be empty.
If Memory integrity does not appear at all, HVCI is not running and there is nothing to turn off here.
Disable VBS and the hypervisorVBS keeps memory integrity and the hypervisor alive even after the toggle is off.
- 1
Turn off the policy.
- Win + R → gpedit.msc → Computer Configuration → Administrative Templates → System → Device Guard.
- “Turn On Virtualization Based Security” → Disabled.
- On Windows Home, set HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\DeviceGuard → EnableVirtualizationBasedSecurity (DWORD) to 0 instead.
- 2
Stop the hypervisor from launching at boot.
- In an administrator terminal: bcdedit /set hypervisorlaunchtype off
- 3
Remove the features that switch VBS back on.
- Win + R → optionalfeatures → untick Hyper-V, Virtual Machine Platform and Windows Hypervisor Platform.
- WSL2 and Docker Desktop depend on these and will stop working until you re-enable them.
- 4
Restart and verify.
- msinfo32 → “Virtualization-based security” must read “Not enabled”.
Disable the TPMA TPM keeps a hardware-bound key that survives a spoofer. Turn it off in firmware, not in Windows.
- 1
Suspend BitLocker before touching firmware.
- Run this in an administrator terminal: manage-bde -protectors -disable C:
- 2
Reboot into UEFI/BIOS.
- Settings → System → Recovery → Advanced startup → Restart now.
- Then Troubleshoot → Advanced options → UEFI Firmware Settings → Restart.
- 3
Turn the TPM off. The switch is vendor-specific:
- ASUS — Advanced → PCH-FW Configuration → PTT (Intel) or AMD fTPM.
- MSI — Settings → Security → Trusted Computing → Security Device Support → Disabled.
- Gigabyte — Settings → Miscellaneous → Intel Platform Trust Technology (PTT) → Disabled.
- ASRock — Security → AMD fTPM Switch, or Intel PTT on Intel boards.
- 4
Save and exit (F10), then confirm in Windows.
- tpm.msc must now say “The TPM is not present”.
Disabling the TPM in Device Manager only hides the device — the firmware switch is what actually removes it. Keep your BitLocker recovery key: disabling the TPM can invalidate a Windows Hello PIN.
Disable Secure BootUsually a single firmware toggle — but some boards lock it behind key management.
- 1
Reboot into UEFI/BIOS as described above.
- 2
Find Secure Boot and set it to Disabled.
- Most boards: Security or Boot tab → Secure Boot → Disabled.
- Some ASUS boards only expose it after setting OS Type to “Other OS”.
- 3
If the toggle is locked, clear the keys.
- Key Management → “Restore Factory Keys” or “Delete all Secure Boot variables”.
- Save and exit, re-enter firmware, then the toggle becomes available.
- 4
Confirm in msinfo32 → “Secure Boot State: Off”.
If the Windows drive was BitLocker-protected, changing Secure Boot state can trigger a recovery prompt on the next boot — have the recovery key ready.
Confirm everything is offThree commands that prove the prerequisites are actually disabled.
- 1
Open System Information.
- Press Win + R, type msinfo32, press Enter.
- Find “Virtualization-based security”. It must read “Not enabled”.
- Find “Virtualization-based security Services Running”. It must be empty.
- 2
Check the TPM.
- Press Win + R, type tpm.msc, press Enter.
- “The TPM is not present” means it is already disabled.
- If a TPM version is listed, it is still on — see Disable the TPM above.
- 3
Check Secure Boot and your build.
- Still in msinfo32, “Secure Boot State” must read “Off”.
- Note the OS Name line — loaders ship one build per Windows version.
If any of the three still report enabled, go back to the matching article above before opening the loader.
Getting started
Register your license in the dashboardLinking a license to your account is what creates the loader login.
- 1
Sign in and open Dashboard → Register a new Key.
- 2
Pick the product the key belongs to.
- Self-registration is available for Arc Raiders and Rob Run.
- 3
Choose a password for the license account.
- At least 8 characters. Your Scrappy username is used automatically.
- This is the login the loader uses — it is not your website password.
- 4
Paste the license key and submit.
- The key is validated against the licensing service and appears under Your Keys.
Enable the Discord overlay and Legacy OverlayBoth toggles have to be on — the loader menu is drawn through Discord's overlay hook.
- 1
Open Discord → User Settings.
- Gear icon at the bottom left of the app.
- 2
Open the Game Overlay settings page.
- In current builds it sits under Game Activity in the left sidebar.
- 3
Turn on “Enable Discord Overlay”.
- If Discord asks to install the overlay, accept and let it finish.
- 4
Turn on “Enable Legacy Overlay” on the same page.
- This switches from the new overlay to the classic one the loader hooks into.
- 5
Add the game under Registered Games.
- If the game is missing from the list, use “Add it!” and select the game's .exe.
- 6
Open the game and test the overlay before loading.
- Press the overlay hotkey shown in Discord and confirm the overlay opens in game.
If the menu never appears in game, check both toggles first — a legacy overlay that is switched off is the most common cause of an invisible menu.
Open the loaderRun it as administrator, sign in with the license account, load at the main menu.
- 1
Get the loader from your key email or the Discord.
- Never run a build from a third party — it will not be ours.
- 2
Extract the whole archive to its own folder.
- Example: C:\Scrappy. Do not run it from inside the .zip or from Program Files.
- The folder must keep every file it shipped with — the driver and config files sit next to the executable.
- 3
Right-click the loader and choose Run as administrator.
- 4
Sign in with the license account you registered in the dashboard.
- Not your website login — the username and password you set when registering the key.
- 5
Start the game, wait for the main menu, then press Load in the loader.
- Loading mid-match or during a queue usually leaves the overlay half-injected.
- 6
Open the in-game menu with the key shown in the loader window.
- If the menu does not draw, switch the overlay renderer in the loader settings.
The loader window differs slightly between builds, so the exact button labels live in the Discord #setup channel. If it closes instantly or reports access denied, jump to the antivirus article below.
Troubleshooting
The loader closes instantly, or Defender deleted a fileAlmost always the antivirus quarantining the driver, not a broken build.
- 1
Check Protection history.
- Windows Security → Virus & threat protection → Protection history → restore the quarantined file.
- 2
Exclude the loader folder.
- Virus & threat protection → Manage settings → Exclusions → Add an exclusion → Folder.
- Choose the folder you extracted to (e.g. C:\Scrappy).
- 3
Re-extract the archive, then run the loader as administrator again.
- 4
Re-enable real-time protection once the loader is running.
One folder exclusion is enough — there is no reason to disable Defender permanently, and doing so leaves the rest of the machine exposed.
Still stuck? Post what you tried in the Discord — include your msinfo32 output and the loader log.