How Do I Clean My PC After a Ban?
Run Raw Spoofer to randomize 16 hardware identifiers (SMBIOS UUID, motherboard serial, disk serials, MAC addresses, GPU UUID, MachineGuid, RAM SPD, monitor EDID). The spoof persists until reboot. Optionally do a clean Windows reinstall to clear non-firmware traces (game launcher caches, anti-cheat driver caches). Format reinstall alone does NOT fix HWID bans because identifiers live in firmware. New motherboard rarely fixes it because other identifiers carry over. The spoofer is the real fix.
Cleaning a PC after a ban means restoring the machine to a state where anti-cheats can't link your fresh accounts to the banned hardware. The wrong fixes — format reinstall, motherboard swap alone, registry cleaning — are folklore that don't address how modern HWID bans actually work. The right fix is hardware-identifier spoofing.
Why format reinstall doesn't fix HWID bans
Format and reinstall Windows clears the OS but leaves firmware untouched. The identifiers anti-cheats fingerprint live in:
- SMBIOS (firmware on the motherboard's BIOS chip)
- Motherboard serial number (firmware)
- Disk serials (firmware on the drive controller)
- MAC addresses (firmware on each NIC)
- GPU UUID (firmware on the GPU)
- TPM endorsement key (firmware on TPM chip)
- RAM SPD strings (firmware on each RAM stick)
- Monitor EDID (firmware on the monitor)
- BIOS strings (firmware)
A Windows reinstall touches none of these. The fresh Windows install reads the same identifiers and presents the same fingerprint to anti-cheats. Fresh account on freshly-formatted PC = same hardware fingerprint = re-banned immediately. See can format reinstall fix a hardware ban.
Why motherboard swap alone rarely works
A new motherboard changes:
- SMBIOS UUID (new firmware)
- Motherboard serial
- BIOS strings (sometimes)
It does NOT change:
- Disk serials (still your old drives)
- MAC addresses (still your old NICs or the new mobo's built-in NIC mixed with your old USB NICs)
- GPU UUID (still your old GPU)
- RAM SPD (still your old RAM)
- TPM EK (if you keep the same TPM chip)
- Monitor EDID (still your old monitor)
Anti-cheats fingerprint multiple identifiers; matching on any 3-4 of them flags the hardware. Single-component swap rarely flips enough identifiers. See will a new motherboard fix my HWID ban.
The real fix — Raw Spoofer
Raw Spoofer randomizes 16 hardware identifiers in user-mode without changing the firmware. Run on cold boot before launching any game. The spoof presents fresh identifiers to anti-cheats for that session, randomized to look like factory-default OEM values rather than obvious random hex. Fresh accounts on spoofed hardware register as different machines.
What the spoofer randomizes:
- SMBIOS UUID, manufacturer, product, BIOS strings
- Motherboard serial number
- All SATA and NVMe disk serials
- GPT/MBR partition layout signatures
- Every NIC's permanent MAC address
- GPU UUID
- MachineGuid (registry)
- Windows Product ID and install date
- RAM SPD
- USB controller IDs
- PCI device IDs
- Monitor EDID strings
What the spoofer doesn't fix
TPM 2.0 endorsement key, Microsoft Pluton, Ring-3 CPU ID, Microsoft Remote Attestation chains. These are firmware-rooted and unspoofable from user-mode. Most current anti-cheats use these as launch gates (TPM presence required for game to start) rather than fingerprint anchors. The realistic threat model means spoofer coverage is high.
Optional — clean Windows reinstall
A Windows clean install isn't strictly necessary but isn't harmful either. It removes:
- Anti-cheat driver caches that record your prior session
- Game launcher caches (Steam, Epic, Battle.net stored telemetry)
- Browser session data
- Registry forensic traces from previous gaming activity
If you have a high-value hardware setup and want maximum recovery confidence, a clean install + spoofer + fresh accounts is the gold standard. Most users skip the reinstall and rely on the spoofer alone — that's also effective.
What about VPN
VPN helps for the first 24-48 hours post-ban to bypass IP-correlation. After 48 hours, IP correlation typically expires. See should I use a VPN with my cheat.
What about a fresh account
Mandatory. Cheat accounts that landed bans should never log in again — they're permanently flagged regardless of spoofing. Register fresh accounts on Steam/Epic/Battle.net/Riot. For account separation see should I use a separate account for cheating.
Sequence
- Cold boot Windows
- Run Raw Spoofer as administrator — randomizes 16 identifiers
- Connect VPN to clean exit node
- Open game launcher, register fresh accounts
- Launch game on fresh account
- After 48 hours, disconnect VPN if performance suffers
- Continue normal cheat workflow with spoofer-per-session habit
What doesn't work
- Format reinstall alone
- Motherboard swap alone
- Registry cleaning tools (CCleaner, etc.)
- Changing your IP without spoofing hardware
- Modded BIOS that "wipes" identifiers (some are scams, some break Windows boot)
- "HWID cleaners" sold on shady forums (mostly malware delivery)
For the HWID context see the HWID spoofer pillar and what hardware identifiers do anti-cheats track.
Related Pages
Sources
- About Easy Anti-Cheat — Epic Games
- BattlEye Support FAQ — BattlEye Innovations
- TPM 2.0 Overview — Microsoft
Related Questions
No. A Windows format and reinstall clears the OS but leaves firmware-rooted hardware identifiers (SMBIOS UUID, motherboard serial, disk serials, MAC addresses, GPU UUID, TPM endorsement key) untouched. The anti-cheat reads these from the hardware, not from Windows. Fresh Windows install presents the exact same fingerprint to the anti-cheat. The real fix is an HWID spoofer (Raw Spoofer randomizes 16 identifiers in 4 seconds) or physical hardware replacement.
Run Raw Spoofer on cold boot before every cheat session to randomize 16 hardware identifiers (SMBIOS, motherboard serial, disk serials, MAC addresses, GPU UUID, MachineGuid, RAM SPD, monitor EDID). Use a paid cheat (free cheats trigger detections faster). Configure aimbot and ESP with humanizer settings — aggressive tuning gets accounts flagged which can escalate to hardware bans. Don''t run the cheat without the spoofer. The 4 seconds per session is the difference between recoverable and permanent damage.
Yes, every session if you have ever been hardware-flagged, and as cheap insurance even if you haven''t. Cold boot Windows, run Raw Spoofer as administrator before opening Steam, Epic, Battle.net, or NetEase. The spoof persists until reboot. Skipping the spoofer means one signature detection bans your hardware permanently across every account on that machine. The 4-second spoof time per session is the cheapest insurance in the cheat workflow.
Modern anti-cheats fingerprint a composite of 16+ identifiers: SMBIOS UUID, motherboard serial, all disk serials (SATA + NVMe), every NIC''s MAC address, GPU UUID, MachineGuid (Windows registry), Windows Product ID, Windows install date, RAM SPD strings, USB controller IDs, PCI device IDs, monitor EDID, BIOS strings, TPM 2.0 endorsement key (unspoofable from user-mode), CPU ID, and Microsoft Remote Attestation. Raw Spoofer randomizes 13 of these; TPM EK and Pluton are firmware-baked and out of reach.
Rarely on its own. A new motherboard changes SMBIOS UUID, motherboard serial, and BIOS strings — but disk serials, MAC addresses on USB and discrete NICs, GPU UUID, RAM SPD, monitor EDID, TPM EK, and MachineGuid all carry over. Anti-cheats fingerprint composite matching across 16+ identifiers, requiring 5-8 matches to flag — single-component swap usually leaves enough matching identifiers to re-ban. Full hardware swap or an HWID spoofer is needed.
