The correct order of steps around a HWID ban
Identify what was banned, clean Windows if required, run the spoofer and verify it applied, then sign in with the right account. Learn which mistakes undo the sequence.
Short answer
Work out what was banned, clean Windows if the ban survives a spoof, then run the spoofer and verify it applied. Only then sign in with your intended account. Launching the game before spoofing, reusing the banned account or restoring a backup image undoes all of it.
On this page9
- Why does the order matter so much?
- What is the correct order?
- Why can't you skip the first step?
- When do you need a clean Windows install?
- Does a per-boot or permanent spoof change the order?
- Which mistakes undo the sequence?
- What to check before you run the spoofer
- Should you edit identifiers by hand?
- Common questions about the order of steps
Why does the order matter so much?
Most reports of a spoofer not working turn out to be steps done out of order. The identifiers that matter are read at particular moments, such as when a service starts, a client launches or an account signs in. So whether a change took effect depends on what had already run and what had already been recorded. A good tool used in the wrong order gives the same result as no tool at all.
What is the correct order?
There are five steps: do them in this order, and do not skip verification just because the tool said it succeeded.
- Identify what was actually banned: the account, the machine, the connection or matchmaking. The ban types guide covers this step, which decides whether the rest of the list applies to you at all
- Clean Windows if required, because a fresh install clears identifiers that live in the operating system rather than in firmware. It also removes files and registry state left behind by a previous session
- Run the spoofer on a freshly booted machine, before you start the game or its launcher and before you sign in anywhere
- Verify the result by reading the identifiers and comparing them with the values you recorded beforehand. A success dialog is not evidence that anything changed
- Only then create or sign in with the account you intend to use. Start the launcher and the game in the order your product's documentation describes
Why can't you skip the first step?
Skipping straight to the tool is how people spend money on the wrong layer. If the ban is on the account, or the restriction is matchmaking placement, a spoof changes nothing you care about. Spend ten minutes working out which one you have by asking what exactly stopped working, on which account and on which machine. Then check whether a different account on the same machine behaves differently. That test costs nothing, and it tells you more than any other test you can run.
When do you need a clean Windows install?
A clean install is worth doing when identifiers and state held by the operating system are part of what identifies the machine. It is also worth doing when a previous installation is known to be full of leftovers. It is not a magic step and not always required: a permanent hardware-level spoof with nothing to clean up behind it may not need one. A clean install also does not touch anything held in firmware, so it is no substitute for understanding which identifiers are involved. Base the decision on what you learned in step 1, not on habit.
Tip
Does a per-boot or permanent spoof change the order?
No, but it changes the routine. A per-boot spoof reverts when the machine restarts, so everything from step 3 onward becomes a per-session routine: boot, spoof, verify, then launch. A permanent spoof persists across reboots, so steps 3 and 4 happen once and only step 5 repeats. Getting this wrong is the most common cause of a build that worked yesterday and not today. In those cases the machine was simply rebooted and nobody re-ran anything.
Which mistakes undo the sequence?
Each of these has been the real answer in a support thread that started with a spoofer not working. The middle column explains what goes wrong mechanically.
| Mistake | What actually happens | What to do instead |
|---|---|---|
| Launching the game or its launcher before spoofing | The client and its anti-cheat service start while the old identifiers are still live and may have already read and reported them | Boot, spoof, verify, and only then start the launcher |
| Signing into the banned account again | The ban that follows the account is applied regardless of what the machine now reports | Decide in step 1 whether the account is usable at all before touching hardware identity |
| Restoring a system backup image after spoofing | The image contains the identifier state from when it was taken, so the old values come straight back | Do not restore images into a spoofed state. Rebuild rather than restore |
| Rebooting after a per-boot spoof and not re-running it | The machine comes back with its original identifiers and nothing warns you | Treat boot, spoof, verify as one unit and never launch anything between them |
| Trusting the success dialog and skipping verification | A partial spoof looks identical to a complete one from the tool's own output | Compare before and after values yourself, as the verification page shows |
| Reinstalling Windows after spoofing rather than before | The install resets operating-system-level state, so any spoof held at that level is discarded | Clean first, spoof second. Never the other way round |
What to check before you run the spoofer
- You know what was banned: the account, the machine, the connection or matchmaking
- You have recorded the current identifier values, so there is a before list to compare against
- The game, its launcher and any platform client are fully closed, not minimised to the tray
- The machine has been freshly booted, not resumed from sleep or Fast Startup
- You know whether your spoof is per-boot or permanent, and what that means for your routine
- You do not plan to restore a backup image after this point
- You have decided which account you will sign in with afterwards
Warning
Should you edit identifiers by hand?
No. Writing identifiers by hand into the registry or into a board's firmware is how people break a working machine. The machine may fail to boot, lose activation, or report values so inconsistent that they identify it more clearly than the originals did. Inspecting values is read-only and always safe, while modification belongs to the tool that was built for it.
Common questions about the order of steps
Do I need a clean Windows install every time?
No. It is a step you take when operating-system-level identifiers and leftovers are part of the problem. If a permanent spoof covers what is being read and there is nothing local to clean, it may not be required at all.
Can I spoof while the game is closed but Steam is open?
No, close the platform client as well, because any client with a running background service may already have read the identifiers. The point of the order is that nothing reads them before the change.
What if I reboot and forget to re-run a per-boot spoof?
Do not launch anything: reboot again if you are unsure, re-run the spoof, verify it, and only then start the launcher.
Is it safe to restore a disk image later?
It is safe for the machine, but it puts back the identifier state captured in that image. Treat a restore as undoing everything from step 2 onward.
Does the order guarantee a result?
No. The order removes the mistakes that reliably break a spoof, but it cannot promise an outcome. Detection and correlation are decided by the anti-cheat vendor, not by the sequence you followed.
Sources
This is the order the team works through with customers, and every mistake in the list came out of a real support thread.
Read next
Still stuck? Open a ticket on Discord
All guides