CADO SCRIPTVanguard HWID Ban & VAN 152: How to Get Back Into League
Quick verdict: VAN 152 means Vanguard has flagged your hardware, not just your account. Fresh accounts won't help because the ban follows your machine's identifiers. A reliable HWID spoofer resets those identifiers so you can play League again on the same PC.
You launch League of Legends, the client loads, and then VAN 152 hits you in the face. No lobby, no queue, just a hard stop. That error means Vanguard has linked your hardware to a banned account, not just the account itself. A new Riot account won't fix it because the ban lives on your machine's identifiers. Here's how Vanguard HWID bans actually work, which hardware gets flagged, and how a HWID spoofer gets you back into the game.
What VAN 152 Actually Means
VAN 152 is Vanguard's hardware ban code. It's not a network error, not a client bug, and not something a reinstall fixes. When Riot bans an account for scripting or other serious violations, Vanguard can escalate to a hardware ID (HWID) ban. That means the anti-cheat takes a fingerprint of your PC and stores it on the ban list. Any account launched from that machine hits the same wall.
The fingerprint isn't one single number. It's a combination of hardware and firmware identifiers that Vanguard collects at boot and while the game runs. Change one or two and you're still flagged. That's why swapping your account or reformatting Windows often does nothing. The ban is tied to the machine, not the software install.
If you're seeing VAN 152, your first move is to confirm it's a hardware flag and not a temporary Vanguard hiccup. Restart your PC, check the Vanguard tray icon, and try a different account. If every account fails with VAN 152, you're hardware banned. At that point, an HWID spoofer is the practical route back into League of Legends.
Which Hardware Identifiers Vanguard Flags
Vanguard doesn't publish its full list, but from community testing and the patterns players report after a VAN 152, these are the identifiers that matter. You don't need to change all of them manually. A good spoofer handles the set in one pass. But knowing what's on the list helps you understand why a single tweak won't cut it.
- Motherboard and BIOS identifiers: SMBIOS UUID, board serial, and firmware strings. These are heavily weighted because they're stable across Windows reinstalls.
- Disk serials: the physical drive's serial number, not the volume label. Swapping drives or spoofing the serial both work, but formatting does not.
- MAC addresses: network adapter hardware addresses. Vanguard sees these at boot and during play. Spoofers rotate them per adapter.
- GPU identifiers: device ID and subsystem ID strings. Less unique than the board, but still part of the fingerprint when combined with other data.
- Windows machine GUID and product ID: stored in the registry and tied to the install. A clean Windows install changes some of these but not the firmware-level ones.
- TPM and secure boot state: Vanguard reads TPM presence and related firmware data on Windows 11. Spoofers need to handle this layer too.
The key takeaway: Vanguard combines multiple identifiers into a single fingerprint. Changing your MAC address alone won't clear a VAN 152 if your motherboard UUID is still on the list. This is why half-measures fail and why a proper spoofer that covers the full stack is the only reliable fix.
Why a New Account Doesn't Fix VAN 152
This is the part that catches most players. You get banned, you make a fresh Riot account, you log in, and VAN 152 slaps you down before you even see the home screen. The account is new. The hardware isn't. Vanguard checks the machine fingerprint on launch and matches it to the ban database. New account, same PC, same ban.
Some players try a full Windows reinstall, a new drive, or a VPN. None of those touch the firmware-level identifiers Vanguard reads. A VPN changes your IP, not your hardware. A new drive changes one serial but leaves the motherboard and TPM data intact. You might get a few minutes further, but the flag catches up.
The only clean fix is to change the identifiers themselves. That's what a HWID spoofer does. It presents a new, clean set of hardware IDs to Vanguard so your machine looks like a different PC. Then you create a fresh account and play normally. If you want to understand the broader anti-cheat picture, our Vanguard and LoL scripts guide breaks down how the system behaves in 2026.
How a HWID Spoofer Gets You Back Into League
A HWID spoofer sits between your hardware and the operating system. Before Vanguard loads, it swaps the identifiers Vanguard would normally read: SMBIOS strings, disk serials, MAC addresses, machine GUID, and related firmware data. From Vanguard's perspective, your PC is a new machine with no ban history.
The process is straightforward. You run the spoofer, let it apply the new IDs, and reboot. Then you launch League of Legends with a fresh Riot account. Vanguard reads the spoofed identifiers, sees no match on the ban list, and lets you in. The whole cycle takes a few minutes once you have the tool.
Not all spoofers are equal. Some only change the MAC address or the disk serial, which isn't enough for VAN 152. You need one that covers the full stack, including SMBIOS and TPM data, and that stays updated as Vanguard evolves. Cado's HWID spoofer is built for exactly this scenario and works alongside the League of Legends script for gameplay features like orbwalker and prediction.
One important detail: run the spoofer before Vanguard starts. If Vanguard is already loaded, it may cache the original IDs. Reboot after spoofing to make sure the new identifiers are active at the firmware level. Most spoofer guides include a reboot step for this reason.
Step-by-Step: Clearing VAN 152 and Playing Again
Here's the practical sequence I'd use if I were hardware banned today. It's the same process our testing team runs when validating a spoofer against a new Vanguard build.
- Close League of Legends, the Riot Client, and Vanguard completely. Check Task Manager for vgtray.exe and end it if needed.
- Run the HWID spoofer and apply all available identifier changes. Don't skip the SMBIOS or TPM options if your spoofer offers them.
- Reboot your PC. This ensures the new hardware IDs are active before Vanguard loads at startup.
- Create a fresh Riot account using a new email. Don't reuse anything linked to the banned account.
- Launch League of Legends and log in. If VAN 152 is gone, you're clear. If it persists, your spoofer missed a layer and you need a more complete tool.
- Play a few normal games first to confirm stability, then move to ranked when you're comfortable.
If you're also using gameplay scripts, keep your setup clean. Don't pile on sketchy free tools that might reintroduce flags. Stick to one trusted source for both the spoofer and the script. Our guide to using LoL scripts safely covers the habits that keep your account healthy long term.
Common Mistakes After a VAN 152
Most players who stay stuck on VAN 152 make the same errors. Here's what to avoid.
- Reinstalling Windows without spoofing: changes software IDs but leaves motherboard and TPM data intact. Vanguard still sees the ban.
- Using a VPN or proxy: changes your IP, not your hardware. VAN 152 doesn't care about your IP.
- Swapping one drive: changes one serial but not the full fingerprint. You need all layers covered.
- Running the spoofer after Vanguard loads: Vanguard may have already cached the original IDs. Always spoof before launch.
- Reusing an old email or phone number: Riot can link accounts through shared contact info. Start fresh.
The pattern is clear: partial fixes don't work because Vanguard uses a composite fingerprint. You need a complete spoof and a clean account. Once you have both, VAN 152 stops being a problem.
Staying Clear After the Spoof
Getting back in is step one. Staying in is step two. After a spoof, treat your setup like a fresh start. Use a clean account, avoid the behavior that got you banned in the first place, and keep your tools updated. Vanguard pushes updates regularly, and a spoofer that worked last month may need a patch to stay effective.
For gameplay, a well-configured script can help you climb without drawing attention. Humanized orbwalking, realistic prediction, and sensible evade settings keep your play looking natural. If you're coming back after a ban, spend a few games in normals to recalibrate your settings and make sure everything feels smooth before you queue ranked.
VAN 152 is a hard stop, but it's not the end of your League career. Understand what Vanguard flags, use a complete HWID spoofer, and start fresh. That's the path back to the Rift. If you're ready to play again, Cado's HWID spoofer and script package give you a clean slate and the tools to climb.
If you want these settings already tuned for you, Cado is a League of Legends script built around exactly this kind of play.
FAQ
Can I fix VAN 152 without a HWID spoofer?
Not reliably. VAN 152 is a hardware ban, so you need to change the identifiers Vanguard reads. A spoofer is the only practical way to do that without replacing your motherboard and drive.
Will a new account alone bypass VAN 152?
No. Vanguard checks your hardware fingerprint on launch. A new account on the same machine will hit the same ban.
Which hardware IDs does Vanguard use for HWID bans?
Motherboard SMBIOS UUID, disk serials, MAC addresses, GPU IDs, Windows machine GUID, and TPM data are the main ones. Vanguard combines them into a single fingerprint.
How often should I run the spoofer?
Once per ban or when you want a clean slate. Run it before Vanguard loads, then reboot. If Vanguard updates and the flag returns, reapply the spoofer.
Does Cado's HWID spoofer work with the LoL script?
Yes. The spoofer and script are designed to work together. Spoof first, reboot, then launch League with the script loaded as usual.