The splatvik loader: injection, HWID binding and fixing the five things that go wrong

Almost every support ticket we receive is about the loader, and almost all of them are one of five problems. This guide covers what the loader does, why, and how to fix each failure yourself in under two minutes.

What the loader actually does

The loader is a single executable, around 4MB, that performs four jobs in sequence:

1. Authenticate. Your key is sent to our API and validated against the licence database. The response includes your subscription state, expiry and the build you are entitled to.
2. Bind hardware. On first use, a hash of stable hardware identifiers (motherboard serial, disk serial, CPU id) is computed and stored against your key.
3. Fetch the build. The correct, current, per-user-signed build is downloaded. Nothing is stored on disk between sessions — the payload lives in memory only.
4. Map. The payload is manually mapped into the game process and started.

Between steps 1 and 4 there is a status gate. If the product status is anything other than Undetected, the loader refuses to continue. This is deliberate and cannot be overridden. It exists so that nobody can run a build during a detection window, including people who really want to.

Why your antivirus flags it

Because it does exactly what malware does.

The loader allocates executable memory in another process and writes code into it. That behaviour pattern is what heuristic antivirus is built to catch, and it cannot distinguish between a cheat loader and a genuine threat, because at the instruction level there is no difference.

This is not a sign of a problem, and it is also not something we can fix — signing the binary would require a code-signing certificate issued to a legal entity, and that certificate would be revoked within a week of a single report.

What to do: pause real-time protection for the duration of injection, or add the loader's folder to your exclusion list. Windows Defender is the most common case:

Windows Security → Virus & threat protection
  → Manage settings → Add or remove exclusions
  → Add an exclusion → Folder → (your loader folder)

If you are not comfortable doing that, that is a completely reasonable position and you should not buy cheat software.

HWID binding explained

Each key binds to one machine. The bind is a one-way hash of three hardware identifiers, so we never store anything that identifies your actual hardware — only whether a given machine matches the one that first used the key.

Why it exists: it is the only thing preventing one purchased key from being shared with fifty people, which would make the pricing model impossible.

When it becomes a problem: you upgrade a component, reinstall Windows, or move to a different PC.

How to fix it: open your dashboard, find the licence, and press Reset HWID. It is instant, it does not require a ticket, and you get one free reset every 14 days. If you need more than that — for example you genuinely test across several machines — open a ticket and explain; we approve reasonable requests.

The five failures, and how to fix them

1. "Secure Boot must be disabled"

Cause: Windows will not load an unsigned kernel driver while Secure Boot is enabled. Our kernel-mode builds need one.

Fix:

1. Restart and enter your BIOS/UEFI (usually Del, F2 or F12 during boot).
2. Find Secure Boot — it is under Boot, Security, or Authentication depending on vendor.
3. Set it to Disabled.
4. Save and exit.

Verify it worked by pressing Win+R, typing msinfo32, and checking that "Secure Boot State" reads Off.

Our Unity-based builds (Pro Soccer Online, Unturned) are user-mode only and do not require this at all.

2. "Injection failed — process not found"

Cause: the game was not running, or was launched after the loader in a way the loader could not see.

Fix: always launch in this order — loader first, authenticate, then launch the game, reach the main menu, then press Inject. Injecting during a loading screen is the second most common version of this failure.

3. "Key already bound to another machine"

Cause: HWID mismatch. Either you changed hardware or you are on a different PC.

Fix: dashboard → licence → Reset HWID. Instant, one free reset per 14 days.

4. "Status: updating — injection blocked"

Cause: the game patched and the build is being rebuilt. This is the safety gate working correctly.

Fix: wait. Watch the status page — it updates in real time from our dev channel, so the moment status returns to Undetected the loader works again. Your subscription is automatically credited for the downtime, so you lose nothing but the evening.

5. Loader opens and immediately closes

Cause: almost always antivirus deleting the executable between download and launch.

Fix: check your antivirus quarantine. Restore the file, add a folder exclusion, and re-download from your downloads page. If it still closes instantly, run it from a terminal so you can read the error before the window disappears:

cd C:\path\to\loader
.\splatvik-loader.exe

Reading the loader status panel

Once authenticated, the loader shows four values:

If Build does not match the latest changelog entry, close the loader and reopen it — it caches the build manifest for five minutes.

Injection order, in full

1. Pause antivirus real-time protection.
2. Run the loader as administrator (right click → Run as administrator).
3. Paste your key and press Authenticate.
4. Confirm Status reads undetected.
5. Launch the game.
6. Wait for the main menu — not the splash screen.
7. Press Inject in the loader.
8. In game, press Insert to open the menu.
9. Press End at any time to unload immediately (the panic key).

The panic key

End unloads everything instantly — overlay, hooks, mapped payload. It exists for the moment a friend walks into the room or you need to alt-tab into a screen share.

It is not a substitute for closing the game if you think something has gone wrong. If a status change happens mid-session, the loader will tell you and you should stop playing.

Frequently asked questions

Can I run the loader on a VM? No. VM detection is part of the anti-cheat surface and running inside one increases risk substantially.

Does the loader need to stay open? Yes, while you play. It maintains the session heartbeat.

Can I use one key on my desktop and laptop? Not simultaneously. Use the HWID reset to move between them, subject to the 14-day limit.

Is my key visible to anyone else? No. Keys are shown only in your own dashboard, over HTTPS, and are never logged in plaintext.

What happens when my subscription expires? The loader authenticates but refuses to inject, and tells you the expiry date. Renew from the dashboard and it works again immediately — no new key required.

Download the current loader from the download page, or follow the full setup guide if this is your first time.