Swapping one or two components usually doesn't beat a hardware ban — and it can make things worse by tripping evasion detection. A modern HWID ban isn't a single value an anti-cheat checks for an exact match. It's a composite of many identifiers, compared with tolerance, so a profile that's mostly the same still resolves to "this is the banned machine."
If you changed a part and got flagged anyway, this is why. This article explains how composite matching works, why partial changes are read as ban evasion, and what that means honestly — including the limits of any software that touches your identifiers.
Quick reference: why partial changes fail
| What you change | Why it often isn't enough |
|---|---|
| Motherboard only | Disk, MAC, and other IDs still match |
| Disk only | Motherboard and SMBIOS still anchor the profile |
| MAC address | Low-weight signal; trivially changed, lightly trusted |
| Reinstall Windows | Firmware identifiers are unchanged |
| Registry cleanup | Artifacts and firmware values can still link you |
A HWID is a composite, not a single key
Anti-cheats build a hardware fingerprint from many sources at once — motherboard serial and SMBIOS UUID, disk serials, MAC addresses, and more. Crucially, the comparison doesn't demand that every value match. These systems use weighted, tolerant matching: if enough high-confidence identifiers still line up with a banned profile, the machine is flagged even though some values changed. That's the whole point of a composite — it's resilient to swapping a single part.
This is why which upgrades change your HWID matters so much: the motherboard and firmware-anchored values carry far more weight than a MAC address or a reinstalled OS. Change a light signal and the heavy anchors still betray you.
Why a partial change reads as evasion
Here's the part people underestimate. When a known-banned profile suddenly shows a few altered identifiers but still matches on the rest, that pattern looks exactly like someone trying to dodge a ban — because usually it is. Anti-cheats treat "mostly-matching profile with a couple of fresh values" as an evasion signal in its own right, not as a clean new machine. So a half-measure can confirm to the system that the banned user is back, rather than letting them slip through.
Vanguard's behavior shows the direction of travel: Riot has publicly described closing a motherboard pre-boot gap so the board is identified earlier and more reliably, narrowing the room for partial spoofing. The Vanguard deep dive covers how early and deep that identification runs.
Residual artifacts you don't think about
Even aggressive cleanup leaves traces. The Windows registry stores hardware and installation history, and identifiers like the registry MachineGuid persist across sessions. A clean reinstall removes software but not firmware-bound values, which is why reinstalling Windows doesn't change your HWID. These leftover links are part of why partial resets so often fail.
The honest limits
Be clear-eyed about software, too. Tools that change Windows-level identifiers operate in user mode — they can change registry IDs like the MachineGuid, NTFS volume serials, and MAC addresses, but they do not rewrite firmware-resident values such as the SMBIOS UUID, motherboard serial, or CPU data. Because a composite ban leans on exactly those firmware anchors, no honest tool can promise a guaranteed unban, and any approach carries some re-detection risk in an ongoing back-and-forth between anti-cheat and evasion.
FAQ
If I change my motherboard, am I unbanned?
Not reliably. The motherboard is the heaviest single identifier, but disk, SMBIOS, and other values still contribute to the composite that flags you.
Can changing parts actually make my ban worse?
It can confirm evasion. A mostly-matching profile with a few new values is a recognizable evasion pattern, not a clean machine.
Does fuzzy matching mean exact hardware doesn't matter?
It means an exact match isn't required. Enough high-weight identifiers matching is sufficient to flag the profile.
Will a registry clean remove the ban?
No. Firmware identifiers and residual artifacts can still link your system to the banned profile.
The takeaway
A hardware ban is a composite judged with tolerance, so changing a part or two rarely clears it and can read as evasion instead. The values that matter most are firmware-anchored, the ones no user-mode software rewrites — which is exactly why these bans are hard to escape and why no honest tool guarantees an unban. Understanding the composite is the real lesson: anti-cheats stopped checking single keys a long time ago.