Universal tools

Disk and volume serials, SMBIOS and baseboard strings, and MAC addresses are the common targets, because those are what most anti-cheats read. Better tools also sweep the residue: registry keys, log files, crash dumps and installer traces that carry the old identifiers even after the hardware values change.

Temporary mode applies the changes until reboot and is the sensible default while testing — nothing is written permanently, and a restart puts the machine back. Permanent mode writes the new values and should only be used with a restore point in place, because a bad write to firmware-adjacent values is a real way to break a Windows install.

Cleaners are the other half of the job. Changing a serial while leaving the old one in a dozen log files defeats the purpose, and most ban-evasion failures come from the cleanup step rather than the spoof itself.

Each anti-cheat reads a different set of identifiers, so a tool that lists presets per anti-cheat is doing something meaningful rather than marketing. Kernel-level systems read more, read earlier, and are more likely to notice that values changed between sessions.

The hardest case is an anti-cheat that loads at boot: it sees the machine before any user-mode tool runs, so spoofing has to happen at a lower level or not at all. Entries that claim to handle those cases are the expensive ones for exactly that reason.

Spoofers need administrator rights and often load a driver, which is a larger change to your system than any cheat loader. Run them from a restore point, and never from an archive you cannot verify — this category is a common malware vector precisely because people run it with full privileges.

Also, changing hardware identifiers can affect things that have nothing to do with games: Windows activation, licensed software bound to a machine, and saved network configurations. Temporary mode avoids most of that.