League of Legends Vanguard privacy and PC checklist

League of Legends Vanguard privacy is a different question from whether League launches after a patch. Privacy asks what trust boundary the client creates on a shared Windows PC. Troubleshooting asks which supported setting is blocking launch. Account recovery asks whether the Riot account itself is accessible. Treating all three as an “HWID problem” wastes time and can damage a working Windows installation.

This guide focuses on shared-PC hygiene and supported diagnostics. It contains no bypass instructions. League of Legends is not present on the current SpoofHWID Status list, so the article does not claim product compatibility.

Vanguard is shared infrastructure, not a League setting

Riot uses Vanguard across League of Legends and VALORANT on Windows. That means a Vanguard update, service issue, or Windows security requirement can affect more than one Riot title installed on the same PC. It also means reinstalling only League may leave the actual problem untouched.

Riot’s Vanguard FAQ for third-party applications explains the supported developer boundaries for tools that interact with League. Riot’s newer Vanguard On-Demand option is available only to systems that meet Riot’s stated Windows security conditions; it is optional, and it is not a universal switch for every PC.

For privacy, document which mode your machine uses instead of assuming behavior from an older forum post. For support, include that mode and your Windows version when reporting a problem.

A shared-PC privacy model that makes sense

Many League PCs are genuinely shared: a family desktop, a gaming lounge, a university machine, or one Windows installation with several user profiles. Separate the data accordingly.

Per-account data

Riot ID, recovery email, two-factor authentication, purchases, chat history, penalties, and ranked progress belong to the Riot account. Each person should use their own account and recovery channel. Windows user profiles do not turn a shared Riot account into separate identities.

Per-Windows-user data

Client preferences, logs, overlays, and some cache files can differ by Windows profile. A clean Windows profile can help isolate a corrupted local setting, but it is not a new motherboard and it does not erase server-side account state.

Per-machine data

UEFI configuration, Secure Boot, TPM, virtualization features, installed kernel drivers, and physical device inventory belong to the PC. Read hardware fingerprinting explained for the difference between these machine signals and ordinary application storage.

This separation is useful even if you never use a privacy product. It tells you whether to contact Riot, Microsoft, the motherboard vendor, or the owner of a conflicting driver.

VAN 9002 is a configuration problem, not a serial problem

Riot’s official VAN 9002 support article says the error usually means Windows Exploit Protection is disabled. Riot instructs players to restore the system mitigations to their Windows defaults and remove Riot-specific overrides before restarting.

That is an important distinction. Exploit Protection controls process mitigations such as DEP, control-flow protection, and address-space randomization. It is not an SMBIOS UUID and it is not repaired by changing a disk serial.

If you see VAN 9002:

1. Record the exact error and when it appears.
2. Follow Riot’s current article, not a registry file from a video description.
3. Note any enterprise security baseline or program-specific override before changing it.
4. If the PC belongs to work or school, ask its administrator; managed settings may return automatically.
5. Restart when Riot’s documented process requests it, then test before making a second change.

One change per test preserves cause and effect. Ten simultaneous “fixes” produce a machine nobody can explain.

Reduce legitimate software conflicts

Start League with the smallest supported software surface you can reasonably use. Close overlays, monitoring tools, RGB utilities, macro software, and development debuggers that you do not need for that session. Do not disable security products casually; use the publisher’s supported exclusions only when Riot or that security vendor specifically recommends them.

For a repeatable support test, record:

• Windows edition, version, and build
• Riot Client and League update status
• exact VAN code
• whether VALORANT, if installed, shows the same problem
• recent driver, BIOS, virtualization, or security-policy changes
• whether a clean boot changes the result

The goal is not to hide software. It is to identify a conflict without creating a new one.

What privacy tools cannot solve

A hardware mask cannot repair a disabled Windows mitigation. It cannot move purchases between Riot accounts, restore a suspended account, approve a third-party overlay, or tell Vanguard that an unsupported driver is safe. Those are separate systems with separate owners.

Temporary identity controls also have a deliberate boundary. As temporary HWID masking explains, a reboot should restore factory identifiers. That model can be useful in authorized research, but it is not a reason to run an unlisted competitive title under an assumed profile. The Status page is the only current coverage statement.

Account recovery belongs on the normal machine

Perform Riot account recovery, two-factor setup, payment changes, and support-ticket submission from the stable configuration you normally recognize. Keep the recovery email current and do not share Riot credentials between Windows users.

If a security change makes the machine look different to an account system, do not keep changing more variables. Return to the known configuration, document the prompt, and complete recovery through Riot. Seeded identities are designed for repeatable authorized testing; they are not a replacement for account ownership.

A practical ownership map

• Login, recovery, suspension, or purchase: Riot Support.
• VAN error: Riot’s matching error-code article.
• Exploit Protection or Windows Security: Microsoft documentation or the machine administrator.
• UEFI, Secure Boot, TPM, or IOMMU: PC or motherboard manufacturer.
• Overlay or companion app: that app’s publisher and Riot’s third-party policy.
• SpoofHWID support question: current Status.

This map keeps privacy review honest. It also gives support a clean report instead of a mystery assembled from five unrelated tweaks.

Official references

• Riot Games: Vanguard FAQ for third-party applications
• Riot Games: Vanguard On-Demand
• League Support: Error VAN 9002

For a deeper map of device identifiers, read SMBIOS UUID privacy. For a product decision, use the live Status page rather than this guide.