HWID Spoofing Guides
TPM 2.0 and Secure Boot Anti-Cheat (2026)
TPM anti cheat and Secure Boot checks now gate Black Ops 7, Battlefield 6 and Fortnite tournaments. Here is what they measure and what they cannot rewrite
TraceX rewrites supported hardware identifiers once for Valorant. It does not reverse an account sanction or guarantee access.
Valorant uses Vanguard. TraceX supports a one-time identifier rewrite for this route; current compatibility remains version-specific.
Free diagnostic
Hardware-ban symptoms in Valorant are more consistent with device linkage when the same PC is blocked across separate accounts; an account sanction follows the account. Seeing "Error code: VAN 152" when the Riot Client returns you to login is Riot's published indicator of an HWID ban rather than an ordinary Competitive queue restriction.
Hardware Coverage
For Valorant, this reference separates identifiers associated with Vanguard from the fields TraceX supports. Only rows marked “Yes” in the TraceX column are claimed as rewritten. Read the Vanguard hardware guide.
| Hardware Identifier | Valorant Tracks | TraceX Rewrites |
|---|---|---|
| CPU / Platform Identifier | Yes | Yes |
| SMBIOS Board / System UUID | Yes | Yes |
| GPU Device Identifier | Yes | Yes |
| Disk / Volume Serials | Yes | Yes |
| Physical NIC MAC Address | Yes | Yes |
| Windows MachineGuid | Yes | Yes |
Reality Check
Valorant appeal outcomes depend on publisher policy and the evidence submitted. An appeal can correct an enforcement error, but it does not change device identifiers or guarantee reinstatement.
“Cheating in game by using auto-clickers, aimbots, and other unauthorized hardware or software that gives players an unfair advantage in game will get that player's account permanently banned. Queuing with cheaters will get those players banned for 180 days.”
Riot Games — VALORANT Support, "Addressing Cheating in VALORANT"
Why You Need This
TraceX for Valorant changes supported machine identifiers before launch; it does not remove publisher records or restore a sanctioned account.
You open the Riot Client for one more Competitive game on Bind, hit Play, and get thrown back to login with "Error code: VAN 152" before agent select. Unrated and Deathmatch never get a chance to load. A clean Valorant reinstall changes nothing, and the fresh Riot account you made for a quick test meets the same device restriction. That pattern is the giveaway: Riot is not rejecting a queue choice or only one account. Vanguard is recognizing the PC. The useful question is which hardware-rooted values survived your reinstall, and whether the penalty is account-only or a true HWID action.
VAN 152 survives a Valorant reinstall because the Riot Client package is not the identity Vanguard is actioning. Riot describes hardware bans as a separate enforcement layer, and its anti-cheat team says hardware actioning targets repeat offenders who return on the same machine. Older explainers add that vgk.sys always starts with Windows. That became incomplete on June 24, 2026: a secured Windows 11 25H2 PC can opt into Vanguard On-Demand, where the driver starts with the Riot title instead. PCs that do not pass or enable Vanguard Pre-Check can keep the original system-start model. Either path still presents a hardware-backed device identity when Valorant launches.
Riot does not publish a complete identifier weighting sheet, so any page claiming an exact recipe is guessing. The real collection surfaces behind a Windows hardware fingerprint include the SMBIOS Type 2 baseboard serial and Type 1 system UUID, physical disk serials exposed through storage IOCTLs, logical volume serials, physical NIC MAC addresses, and MachineGuid under HKLM\SOFTWARE\Microsoft\Cryptography. Hardware-rooted checks can also use the TPM 2.0 Endorsement Key and Secure Boot state. Riot now confirms the TPM Endorsement Key is factory-burned and can serve as non-fungible hardware identity. A Windows reinstall may regenerate MachineGuid and volume data, but it does not replace the baseboard serial, disk firmware serial, or TPM identity. That is why a wipe or one new SSD is not a complete answer.
Vanguard protects both Valorant and League of Legends, which creates a cross-game risk without making every Riot penalty identical. An account-only Valorant suspension is not proof that League is blocked. A true engine-level Vanguard hardware action is broader because both titles present the same PC to Riot's anti-cheat stack, so logging a valuable Riot account into the device is a poor diagnostic. Temporary session spoofers only change reported values while their driver or process is active, then expose the old profile after a reboot. TraceX Spoofer takes the permanent route for supported identifiers: complete the one-time setup, run the rewrite once, then delete the tool. TraceX leaves no session process or daemon to restart before Competitive.
Verified
On June 24, 2026, Riot Games introduced optional Vanguard On-Demand. Windows 11 25H2 systems that pass Vanguard Pre-Check can run the driver only while a Riot title is open instead of starting it with Windows. Riot's same technical post explains that the TPM 2.0 Endorsement Key is factory-burned and can serve as non-fungible hardware identity. (Source: Riot Games, "Incoming: Vanguard On-Demand," June 24, 2026.)
Why TraceX
For Valorant, TraceX rewrites the supported identifiers once, so the product does not need to remain running during the game.
Run TraceX once before opening Valorant through Riot Client. The rewrite persists, so you can delete the tool before Vanguard starts.
For Valorant, TraceX's supported identifier changes persist across reboots without a resident daemon. Publisher sanctions remain separate.
For Valorant, the documented Vanguard coverage includes CPU / Platform Identifier, SMBIOS Board / System UUID, GPU Device Identifier. TraceX rewrites the supported fields in one pass.
Valorant launches from Riot Client after the rewrite is complete. No TraceX process remains during Vanguard gameplay to consume resources.
For Valorant, hardware ban (hwid) — riot vanguard kernel driver (vgk.sys) details stay separate from the current Vanguard status, so a game update is never treated as unchanged by default.
TraceX presents rewritten values for its supported fields when Vanguard checks Valorant; current compatibility remains version-specific.
Setup Guide
Valorant setup has four steps: get the guide, run the supported identifier rewrite once, follow the publisher's account and launcher requirements, and check current compatibility before play.
Submit your email through the TraceX Spoofer homepage form to receive setup instructions for Valorant — free, no card required.
Run TraceX once before launching Valorant. TraceX rewrites the supported identifiers listed on this page in one pass, then the tool can be removed.
Open Valorant via the Riot Client with the Riot account required by the publisher. TraceX does not remove account sanctions, change publisher records, or guarantee access.
Review the current Vanguard status before opening Valorant. Supported identifier changes persist without a TraceX daemon, but game and anti-cheat compatibility can change.
Free download
For Valorant, TraceX issues a free license and setup guide after email registration. Run the supported identifier rewrite once, then check the current Vanguard status and follow the guide. TraceX does not reverse an account sanction or guarantee access.
Detection Analysis
Vanguard can combine identifiers from your PC into a hardware profile for Valorant. TraceX rewrites the supported fields shown below before the game runs.
Vanguard can compare the listed identifiers with enforcement records. A match can contribute to repeat-account detection, but the publisher does not disclose a universal decision rule.
TraceX presents rewritten values for supported fields. It does not erase Valorant account history or guarantee that Vanguard accepts a session.
Ban Reference
Valorant uses Vanguard. This reference records the ban type, stated duration, and known triggers supplied for this page.
All Vanguard Games
Vanguard also protects these TraceX-listed games; each publisher controls its own policies and enforcement.
FAQ
Valorant HWID ban FAQs explain Vanguard enforcement and the supported TraceX workflow.
VAN 152 is the error Riot associates with a hardware-ID ban. An ordinary AFK, chat, or Competitive-queue restriction applies to account features; VAN 152 means the machine itself is part of the enforcement decision. Do not use another person's Riot account as a test. Riot's HWID policy warns that accounts used on a hardware-banned computer can also be restricted, while the original banned account remains banned.
Riot does not publish one universal 120-day or four-month timer for every Valorant hardware action. Its current HWID policy says the affected player must wait at least one year before asking Player Support to re-evaluate the hardware ban, and approval is not guaranteed. Treat VAN 152 as indefinite unless Riot confirms otherwise for your case. A hardware re-evaluation also does not restore the Riot account that received the original cheating ban.
A Valorant reinstall replaces game files, not the device identity. Reinstalling Windows can regenerate MachineGuid and a logical volume serial, but it does not replace the SMBIOS Type 2 baseboard serial, Type 1 system UUID, physical disk firmware serial, NIC hardware, or TPM 2.0 Endorsement Key. Vanguard correlates a hardware-backed profile rather than trusting one Windows value, so a format or one replacement SSD can leave the durable anchors unchanged.
A VAN 152 restriction may be inherited because persistent identifiers travel with the physical parts. A used motherboard can retain its SMBIOS baseboard serial, system UUID, and TPM identity; a used drive retains its firmware serial. Stop testing valuable Riot accounts on the machine and open a Player Support ticket describing the purchase. Include legitimate proof of ownership if requested. Only Riot can confirm whether the device is actioned or review an inherited-ban claim.
No. TPM 2.0 and Secure Boot are security requirements, not switches that erase Riot's ban record. Disabling them can create a VAN:RESTRICTION or stop Valorant from launching on configurations where Vanguard requires them. Riot's June 2026 technical update also identifies the TPM Endorsement Key as durable hardware identity. A restriction asking for a secure configuration is different from VAN 152, which is Riot's hardware-ban code.
Not on every supported PC. Riot introduced optional Vanguard On-Demand on June 24, 2026. A Windows 11 25H2 system that satisfies Vanguard Pre-Check can start the driver with a Riot game and stop it outside the session. Players who do nothing, or whose systems do not meet the requirements, can remain on the original system-start model. On-Demand changes when vgk runs; it does not make VAN 152 an account-only penalty or remove hardware identity checks.
Valorant and League both use Vanguard, so the same machine is visible to the same Riot anti-cheat stack. That creates cross-title risk for a true engine-level hardware action. It does not mean every Valorant account suspension automatically bans League; account penalties can be title-specific. If you have VAN 152, do not log a valuable League account into that PC just to test the boundary. Ask Riot which products the hardware action covers.
No. A VPN changes the public IP address seen by Riot's servers; it does not rewrite the SMBIOS baseboard serial, system UUID, physical disk serials, MAC hardware, MachineGuid, TPM identity, or Secure Boot state. That makes a VPN relevant to an IP or routing problem, not VAN 152. If the Riot Client shows the hardware-ban code, changing networks cannot turn the same device into a different hardware profile.
A temporary spoofer changes what selected checks report only while its driver or process is active, so the old profile can return after a reboot and the tool must run again. TraceX uses a permanent rewrite for supported identifiers. Complete the one-time setup, run it once, then delete the tool; no TraceX daemon remains during Valorant. This changes the supported device-side profile, but it does not reinstate the Riot account that received the original penalty.
Yes, through Riot Player Support, but a ticket is a review request rather than a guaranteed reversal. Give a concise timeline and mention a compromised account or recently purchased used hardware only when it is true. Do not keep cycling new accounts on the device, because Riot treats that pattern as circumvention. Riot's HWID policy allows the affected player to request re-evaluation after at least one year; previously banned accounts remain banned even if the hardware action is later lifted.
Learn More
HWID Spoofing Guides
TPM anti cheat and Secure Boot checks now gate Black Ops 7, Battlefield 6 and Fortnite tournaments. Here is what they measure and what they cannot rewrite
HWID Spoofing Guides
A HWID ban appeal is worth filing only for a documented false positive, an inherited ban on a used PC, or another person’s activity on a shared machine.
HWID Spoofing Guides
No. You do not need to reinstall Windows for a HWID spoofer, and reinstalling Windows alone does not remove an HWID ban.
Next Steps
The notice shown in Valorant cannot confirm a hardware ban by itself. Repeated restrictions across separate accounts on the same PC can be consistent with device linkage, while an account-only sanction follows the account. The ban-type checker walks through the symptoms, while the Vanguard ban-duration guide records the publisher policy available for comparison before you decide whether waiting is relevant.
You can also browse every game TraceX supports or read up on the anti-cheat engines behind these bans.