Free League of Legends HWID Spoofer
Free permanent HWID spoofer for League of Legends. Bypass Riot Vanguard hardware bans by rewriting your IDs once, then delete the tool.
Free diagnostic
Is It Really a League of Legends HWID Ban?
A LoL HWID ban shows up the moment you launch the Riot Client: instead of getting to champion select, the client throws the VAN 152 error with a brief Vanguard popup, and any account you log in on from that PC — your main, a brand-new Riot account, your roommate's, your sibling's — is immediately, manually banned by Riot on sight, with no champion selected, no Summoner's Rift loaded, and no LP to lose.
Can you still log into your game account?
Hardware Coverage
What League of Legends Tracks — and What TraceX Rewrites
League of Legends's anti-cheat silently reads dozens of hardware identifiers from your PC while it's running — long before you reach a match. Learn how League of Legends's anti-cheat works and why it's difficult to bypass without a spoofer. Below is a sample of the identifiers being tracked.
| Hardware Identifier | League of Legends Tracks | TraceX Rewrites |
|---|---|---|
| CPU Serial (CPUID) | Yes | Yes |
| Motherboard Serial | Yes | Yes |
| TPM 2.0 Endorsement Key | Yes | Yes |
| GPU Device LUID | Yes | Yes |
| HDD / SSD Serial | Yes | Yes |
| NIC MAC Address | Yes | Yes |
| Windows Machine GUID | Yes | Yes |
Reality Check
League of Legends Appeals Almost Never Work
And when they're denied — which is almost always for HWID bans — your hardware stays permanently blacklisted. No second chances.
“HWID bans are different—and more serious—than normal account permabans. A hardware ID ban is a rare, drastic step we take against players who've consistently chosen not to adhere to our Community Pact or to abide by our terms of service. … Game access will be restricted, and any login attempt will result in a VAN 152 error code. … Reinstalling a game or deleting the responsible account won't remove an HWID ban.”
Riot Games — League of Legends Support, "Understanding Hardware ID (HWID) Bans" (last updated 2026-01-16)
Why You Need This
Do You Really Need an HWID Spoofer for League of Legends?
You queue ranked on the Riot Client, watch the loading bar crawl past 20% on Summoner's Rift, and instead of locking in your Yasuo or Ahri pick you get punted back to the desktop with a Vanguard popup and the error code VAN 152. The account you just got to Diamond II spamming Zed in mid lane is gone, your friend's account that you "borrowed" to test a script for fifteen minutes is gone, and the brand-new Riot account you registered on your phone five seconds ago to push through your placements gets banned the moment you try to log in on the same PC. Vanguard's kernel-level fingerprint on this machine doesn't care that you reinstalled League, that you reformatted Windows, or that you're swapping summoner names — it knows the motherboard, the TPM chip, and the pre-Vanguard Packman-era shenanigans tied to your Riot account.
A League of Legends HWID ban is fundamentally different from the in-game suspensions scripters used to laugh at in the Packman era. From 2018 until April 2024, LoL ran on Packman — Riot's in-house anti-tamper that, by the company's own admission in the April 2024 dev blog, was "roughly 250 million 'cheat-years' old" and "beaten." Bans then meant a 14-day timeout, a permaban on the offending account, and a $1.99 fresh level 30 from a bot farm. Riot wrote that re-entry was "the cost of a fresh level 30, with a side of large fries." The entire scripting-and-smurfing economy of LoL was built around that economic loop: get banned, buy another account, re-climb to Diamond on auto-piloted Zeris and Cassiopeias, repeat.
Vanguard broke the loop by moving the ban to the hardware. Vanguard's kernel driver vgk.sys loads at Windows boot and reads the system before any cheat or rootkit gets to ring-0 — TPM 2.0 chip, motherboard, disk, GPU, NIC. Riot is explicit about why TPM is required: it "acts as an extremely non-fungible form of hardware ID." When a Riot account gets HWID-banned for repeated cheating, Riot writes that hardware constellation into a database tied to the offender. Reinstall LoL? The machine still fingerprints the same. Reformat Windows? The TPM persistent identifier is unchanged. Make a brand-new Riot account on your phone, then log in on the banned PC? Riot's own HWID-ban article says verbatim that the new account "will be banned for a set period, as the system assumes that the account is attempting to circumvent the original ban."
Vanguard's results came fast: within four months of going live on Patch 14.9, Riot reported 175,000+ ban-actions and a Ranked scripting rate that fell below 1% for the first time in nearly four years. The MOBA-cheating ecosystem (scripts that auto-dodge skillshots, frame-perfect Yasuo combos, pixel-perfect Cassiopeia dodges) is much harder to detect than FPS aimbots — there is no killcam in League — which is why Vanguard had to bring its full kernel-level fingerprinting toolkit to a non-FPS game in 2024.
Verified
Within four months of Vanguard rolling out to League of Legends on May 1, 2024 (Patch 14.9), Riot's August 22, 2024 retrospective reported the system "dropping total hours spent botting from north of 1 million a day to less than 5 thousand" — a >99.5% reduction in bot activity that single-handedly collapsed the LoL level-30-smurf farming economy. (Source: Riot, /dev: Vanguard x LoL Retrospective, August 22, 2024.)
Why TraceX
Built for League of Legends Players
You shouldn't need to replace your PC to play League of Legendsagain. That's why TraceX exists.
Run TraceX once before launching League of Legends. No daemon, no startup entry, no background service. When you're done, delete the binary.
Your new hardware identifiers don't reset on reboot or reinstall. Vanguard reads them as permanent — exactly like a fresh build.
Every hardware identifier Vanguard reads — CPU, board, drives, GPU, NIC, Machine GUID — rewritten in a single pass.
TraceX runs before League of Legends launches — not during. No FPS drops, no stutter, no driver hooks left running while you play.
TraceX updates ahead of League of Legends detection cycles. New versions ship before changes land in the game.
When you load League of Legends, Vanguard fingerprints what looks like a fresh system. Your real hardware is never exposed.
Setup Guide
How to Bypass a League of Legends HWID Ban
Getting around a League of Legends HWID ban used to take hours — reinstalling Windows, flashing BIOS, wiping drivers, re-downloading everything, and praying it worked. One wrong step meant starting over and burning another account. With TraceX, a single click does more than all of that combined.
Free download
Get the free League of Legends HWID spoofer.
Submit your email and receive your free TraceX HWID Spoofer license in a few minutes. Run it once on your PC to permanently rewrite the identifiers Vanguard fingerprints, then delete the binary and reinstall League of Legends.
Detection Analysis
How League of Legends Scans Your Hardware
League of Legends tracks dozens of unique identifiers from your PC and creates a unique hardware profile. It also leaves behind registry traces even after uninstalling — designed to detect you on return. TraceX takes care of everything.
When you launch League of Legends, your real hardware IDs are scanned and matched against ban records. Every new account on a flagged PC is blocked.
League of Legends sees a completely new machine with no ban history. New account, clean hardware — access granted.
Ban Reference
League of Legends Ban Details
All Vanguard Games
Other Games Using Vanguard
All of these games use Vanguard — the same anti-cheat that banned you in League of Legends. One TraceX license covers every one of them.
FAQ
League of Legends HWID Ban — Frequently Asked Questions
I got VAN 152 launching League. Is this a hardware ban and is it permanent?
Yes — VAN 152 is Riot's HWID-ban error code, used identically on League and Valorant. Per Riot's HWID-ban support article: "Game access will be restricted, and any login attempt will result in a VAN 152 error code." The ban is not framed as having a fixed duration. Riot says the affected player must wait at least one year before submitting a re-evaluation request, and re-evaluation is "never guaranteed" to succeed. In practice, players treat VAN 152 as permanent.
My friend got HWID-banned. If I log into my Riot account on his PC, will I get banned too?
Yes — and Riot is explicit about it. From Riot's HWID-ban article verbatim: "If another account (a friend's or family member's, for example) is used to log into a game on a computer that has a HWID ban … That account will be restricted from accessing Riot Games products on the hardware-banned device. That account will be banned for a set period, as the system assumes that the account is attempting to circumvent the original ban." Riot's recommendation: "If you suspect a computer has an HWID ban, it's best not to try to log in with any account."
I reinstalled Windows and made a brand-new Riot account. Why does it still get banned on my old PC?
Because the ban is on the machine, not the account. Vanguard fingerprints the TPM 2.0 chip, motherboard serials, disk, NIC MAC, and GPU IDs at kernel level — and per Riot's own dev blog, TPM 2.0 was specifically required because it "acts as an extremely non-fungible form of hardware ID." Reinstalling Windows wipes the OS but does nothing to the TPM, motherboard UEFI strings, or the rest of the hardware constellation Vanguard reads.
League ran fine on my PC for ten years. Why won't Vanguard let it launch now?
Vanguard adds environment-security checks LoL never had under Packman: TPM 2.0 enforcement on Windows 11, blocked vulnerable kernel drivers, and rejected stale/legacy driver certificates. Riot's Vanguard x LoL retrospective: "If your PC is found to be too vulnerable (e.g., because of outdated Windows or specific configurations that make it susceptible to unfair third-party applications), you may be restricted from playing League of Legends." The same rig that worked under Packman can be locked out by Vanguard if it's running an old Windows version, lacks TPM 2.0, has signed-but-vulnerable drivers, or has legacy hardware whose Option ROMs aren't UEFI-signed.
I tested a script on a smurf, then my main got banned even though I never cheated on it. How?
This is one of the false-ban categories Riot itself identifies, and the technical name from the dev blog is "whoopsie daisies": "They tested a cheat on a smurf, poisoning their main through hardware linking." Vanguard fingerprints the hardware your Riot accounts log in on. When the smurf gets caught running a script, the hardware-link bridges the ban back to the main on the same machine. Riot does not reverse this scenario. The takeaway: never test cheats on any account on any PC you also use for your main.
Was the May 2024 Vanguard rollout really as bad as people say?
Yes for some, no for most. RiotK3o said "fewer than 0.03% of players" reported issues with Vanguard in the first week after Patch 14.9. But on June 18, 2024, Riot's LoLDev account confirmed a backend networking issue had falsely kicked players mid-game with "no Vanguard detected" errors and saddled them with leaver penalties / LP losses. Riot lifted the suspension actions but never fully reimbursed the LP losses. If your VAN error came during that window, you were almost certainly caught in the false-positive wave.
I bought a used PC. Could it have a previous owner's Vanguard HWID ban on it?
Yes — Riot's August 2024 retrospective lists "an account that was locked due to borrowing or buying previously banned hardware" as one of three categories of legitimate ban-reversal. The hardware fingerprint travels with the physical components — motherboard, TPM, drive — and a previous owner's HWID flag will follow you onto your build until those components are replaced. With proof of recent purchase, this is one of the few reversal categories Riot will entertain via Player Support.
My Intel 13900K / 14900K blue-screens with vgk.sys errors. Is Vanguard bricking my CPU?
Almost certainly not. Riot's August 2024 retrospective addresses this directly: Intel 13th- and 14th-gen CPUs shipped with firmware-level instability that surfaces as random blue screens, often with vgk.sys named in the bug-check (because the kernel happened to be executing Vanguard code when the CPU faulted). Intel issued microcode updates to address it. Update your motherboard BIOS to the latest from your OEM and check Intel's microcode advisories before assuming Vanguard is the cause.
Vanguard runs at Windows boot all the time. Is it spying on me?
Per Riot, no. From the Vanguard x LoL dev blog verbatim: "Vanguard is not really 'running all the time.' The driver loads at boot, but nothing is making calls to it, and there's no network connectivity until you run one of Riot's games. It's literally just sitting there (menacingly), so that it can attest to the fact that nothing's happened between Windows loading and the game starting." When you do play LoL, Vanguard takes screenshots only of the game-client window for ESP-cheat detection — not the whole desktop or other monitors.
Will an HWID ban on League also lock me out of Valorant and TFT?
Yes. Riot Vanguard runs across League, Valorant, TFT, and 2XKO — they share the Vanguard runtime and the same banlist database. A VAN 152 from any one of those titles locks all four on the same hardware constellation, and any new Riot account logging in on the banned PC hits the same error.