Steam now forces games to tell you when they run a kernel-level anti-cheat — and that label is really a heads-up about which titles can read your hardware at the deepest level. Valve's disclosure rule means a store page must state, before you buy, whether the game installs a driver that runs in kernel mode and whether it leaves files behind after you uninstall.
For anyone who cares about their hardware fingerprint, this is the most useful transparency change in years. Kernel-mode anti-cheats are exactly the ones capable of building a deep HWID profile of your PC. This guide explains what the label means, why it matters for your hardware, and how to read it before you click buy.
Quick reference: the Steam anti-cheat label
| Field on the store page | What it tells you |
|---|---|
| Kernel-level integration | The game loads a driver at Ring 0 / boot time |
| Residual files after uninstall | The driver may stay after you remove the game |
| Anti-cheat name | Which system it uses (EAC, BattlEye, Vanguard, etc.) |
| No disclosure shown | Anti-cheat is server-side or user-mode only |
What the disclosure actually requires
Valve added a dedicated field in the "Edit Store Page" tool. Developers tick whether their anti-cheat has kernel-level integration and whether users must remove residual files after uninstalling. The rule is retroactive — it applies to games already on Steam, not just new releases. Disclosure is not required when the anti-cheat runs only on the game's servers or never touches kernel-level files, which is the key line: the label specifically flags the software that operates below the level a normal program can reach.
That announcement, made in late 2024, followed years of player and developer pressure for transparency around drivers most people never knew they were installing.
Why kernel mode matters for your HWID
A user-mode program sees your PC the way any app does. A kernel-mode driver runs at Ring 0 with boot-time loading and has access to effectively everything on the system. That is the same level of access an anti-cheat needs to read firmware-bound identifiers — the SMBIOS UUID, motherboard serial, TPM data — that make up a stable hardware fingerprint.
In other words, the games carrying this label are the ones that can build the kind of HWID profile that survives a fresh Windows install. Our deep dive on kernel anti-cheat privacy covers the broader trade-offs of handing that access to a game.
The "residual files" checkbox is the one to watch
The second checkbox — residual files after uninstall — is easy to skim past and shouldn't be. It means the driver can remain on your system after the game is gone. A leftover kernel driver is both a security surface and a privacy question, and removing it usually takes more than dragging the game to the trash. If you have ever uninstalled a game and wondered why a service still loads at boot, this is why; our guide on fully removing an anti-cheat walks through it.
How to use the label before you buy
Treat the disclosure as a checklist. If a game declares kernel-level integration, assume it can fingerprint your hardware and that a ban from it is likely to be hardware-anchored rather than account-only. Decide whether you are comfortable with a boot-time driver, check the residual-files note, and know the uninstall path in advance. None of this means kernel anti-cheat is malware — most of it does exactly what it claims — but you are now able to make that call with the facts in front of you instead of after installation.
FAQ
Does the Steam label mean the game is spying on me?
No. The label states a technical fact — that a kernel-mode driver is present. Kernel access creates the capability to read deeply, but disclosure is about transparency, not an accusation of misuse.
Do all games have to show this label?
No. Only games whose anti-cheat modifies kernel-level files must disclose. Purely server-side or user-mode anti-cheats are exempt, though Valve encourages disclosure anyway.
Why does kernel anti-cheat relate to HWID bans?
Because reading firmware-level identifiers like the SMBIOS UUID and TPM requires kernel access. Those values are what make a hardware ban stick across reinstalls, which is why kernel-anchored games tend to issue HWID bans.
Can I remove a kernel anti-cheat driver after uninstalling?
Usually yes, but not always automatically. The residual-files checkbox warns you when manual cleanup is needed.
The takeaway
Steam's anti-cheat label turns a question you used to answer only after installing into one you can answer at the store page. The single most important reading of it is this: a kernel-level tag marks the games that can see your hardware deeply enough to build a fingerprint and issue a hardware-anchored ban. That is not a reason to panic, but it is a reason to read the label — and to know your uninstall path before you commit.