HWID Spoofing Guides
Anti-Cheat Comparison: EAC vs BattlEye
Anti-cheat comparison for 2026: EAC vs BattlEye vs Vanguard vs RICOCHET and 8 more engines, with developer, kernel access, ban type and cross-game reach
TraceX rewrites supported hardware identifiers once for FragPunk. It does not reverse an account sanction or guarantee access.
FragPunk uses Phanuel. TraceX supports a one-time identifier rewrite for this route; current compatibility remains version-specific.
Free diagnostic
Hardware-ban symptoms in FragPunk are more consistent with device linkage when the same PC is blocked across separate accounts; an account sanction follows the account. Bad Guitar Studio's documented launch failures are the "Phanuel Anti-Cheat" bar reaching 100% before Steam returns to "Launch" and the "Please enable Secure Boot before playing" pop-up; neither proves an HWID ban without a separate enforcement notice or repeated device-linked penalty.
Hardware Coverage
For FragPunk, this reference separates identifiers associated with Phanuel from the fields TraceX supports. Only rows marked “Yes” in the TraceX column are claimed as rewritten. Read the Phanuel hardware guide.
| Hardware Identifier | FragPunk Tracks | TraceX Rewrites |
|---|---|---|
| CPU / Platform Identifier | Yes | Yes |
| SMBIOS Baseboard / System UUID | Yes | Yes |
| GPU Adapter Identifier | Yes | Yes |
| Physical Disk / Volume Serial | Yes | Yes |
| NIC MAC Address | Yes | Yes |
| Windows MachineGuid | Yes | Yes |
Reality Check
FragPunk 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.
“All bans are backed by conclusive evidence and strictly enforced under the User Agreement.”
Bad Guitar Studio, FragPunk Banned Players List (March 10, 2026)
Why You Need This
TraceX for FragPunk changes supported machine identifiers before launch; it does not remove publisher records or restore a sanctioned account.
You queue Ranked Shard Clash through Steam, but FragPunk never reaches Lancer select: the "Phanuel Anti-Cheat" bar hits 100%, the client closes, and Steam flips back to "Launch." Or the launcher stops on "Please enable Secure Boot before playing." Bad Guitar Studio documents both as startup checks, so neither message alone proves your PC is banned. The stronger HWID pattern is a separate enforcement notice that follows another FragPunk account on the same machine after a reinstall. At that point, the surviving device profile matters more than the game files.
Phanuel is the name players see in the FragPunk launcher. Installed components are associated with NEAC naming, but Bad Guitar Studio does not publish a complete component map or an HWID field list. Its official launch FAQ confirms the Phanuel progress bar and Secure Boot requirement; its Banned Players Lists confirm permanent account enforcement after system monitoring and manual review. Those facts do not make every failed launch a hardware ban. First separate a Secure Boot or service error from a separate ban notice, then look for the same enforcement state returning on the same PC. A Steam-to-Epic switch or client reinstall still presents the same Windows machine, so it is weak evidence of a clean device.
At the hardware layer, the useful identifiers are concrete even though Phanuel's weighting remains private: the SMBIOS Type 2 baseboard serial, the motherboard/system UUID, physical disk serials exposed through storage IOCTLs such as `IOCTL_STORAGE_QUERY_PROPERTY`, OS volume serials, physical NIC MAC addresses, and `MachineGuid` under `HKLM\SOFTWARE\Microsoft\Cryptography`. Windows also exposes a TPM 2.0 endorsement key, while Secure Boot reports whether the trusted startup chain is enabled. FragPunk confirms the Secure Boot check; it does not confirm that Phanuel stores the raw TPM endorsement key. These values do not share one lifetime. A Windows reinstall can replace `MachineGuid` and volume data, but it does not rewrite a retained board serial, motherboard UUID, disk firmware serial, or MAC address. Replacing only an SSD leaves the rest of a composite profile available for correlation.
Phanuel is a FragPunk-specific consumer label, and there is no public evidence that a FragPunk penalty automatically bans every NetEase title that uses NEAC-labelled components. The practical blast radius is accounts returning to FragPunk from the same actioned PC; do not turn shared vendor naming into a cross-game ban guarantee. A temporary session spoofer changes selected reports only while its driver or process is active, so rebooting can expose the old profile again. TraceX Spoofer uses a permanent rewrite for supported board, storage, Windows, and network identifiers. Complete the one-time setup, run it once, then delete the tool. TraceX does not disable Secure Boot, patch Phanuel, or load alongside Shard Clash. It changes the supported device-side values before the game starts; it cannot restore the FragPunk account that received the original penalty.
Verified
Bad Guitar Studio's June 25, 2024 "Launching Issues FAQ" names the "Phanuel Anti-Cheat" progress bar and documents the prompt "Please enable Secure Boot before playing." The page treats both as launch prerequisites, not ban messages. (Source: FragPunk official website, "Launching Issues FAQ," June 25, 2024.)
Why TraceX
For FragPunk, TraceX rewrites the supported identifiers once, so the product does not need to remain running during the game.
Run TraceX once before opening FragPunk through Steam / Epic Games Store. The rewrite persists, so you can delete the tool before Phanuel starts.
For FragPunk, TraceX's supported identifier changes persist across reboots without a resident daemon. Publisher sanctions remain separate.
For FragPunk, the documented Phanuel coverage includes CPU / Platform Identifier, SMBIOS Baseboard / System UUID, GPU Adapter Identifier. TraceX rewrites the supported fields in one pass.
FragPunk launches from Steam / Epic Games Store after the rewrite is complete. No TraceX process remains during Phanuel gameplay to consume resources.
For FragPunk, hardware ban (hwid), phanuel / neac-backed pc enforcement details stay separate from the current Phanuel status, so a game update is never treated as unchanged by default.
TraceX presents rewritten values for its supported fields when Phanuel checks FragPunk; current compatibility remains version-specific.
Setup Guide
FragPunk 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 FragPunk — free, no card required.
Run TraceX once before launching FragPunk. TraceX rewrites the supported identifiers listed on this page in one pass, then the tool can be removed.
Open FragPunk via the Steam / Epic Games Store with the FragPunk account via Steam or Epic Games Store required by the publisher. TraceX does not remove account sanctions, change publisher records, or guarantee access.
Review the current Phanuel status before opening FragPunk. Supported identifier changes persist without a TraceX daemon, but game and anti-cheat compatibility can change.
Free download
For FragPunk, TraceX issues a free license and setup guide after email registration. Run the supported identifier rewrite once, then check the current Phanuel status and follow the guide. TraceX does not reverse an account sanction or guarantee access.
Detection Analysis
Phanuel can combine identifiers from your PC into a hardware profile for FragPunk. TraceX rewrites the supported fields shown below before the game runs.
Phanuel 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 FragPunk account history or guarantee that Phanuel accepts a session.
Ban Reference
FragPunk uses Phanuel. This reference records the ban type, stated duration, and known triggers supplied for this page.
Similar Games
FragPunk players can compare these related titles, but each game keeps separate anti-cheat policies and enforcement.
FAQ
FragPunk HWID ban FAQs explain Phanuel enforcement and the supported TraceX workflow.
Phanuel is the anti-cheat name shown in FragPunk's launcher and official troubleshooting. NEAC naming is associated with installed components, but Bad Guitar Studio does not publish a full architecture or ownership map. Treat it as FragPunk's Phanuel stack with NEAC-labelled components. Calling the two names perfectly interchangeable, or importing claims from another NEAC-protected title, goes beyond the public evidence.
Bad Guitar Studio publicly confirms permanent account bans, but it does not publish an HWID schema or label every penalty as a device ban. A hardware action becomes plausible when a separate enforcement notice repeats on another FragPunk account used on the same PC after a client reinstall. That pattern is stronger than one failed launch, but only the publisher can confirm what signal decided an individual case.
No. Bad Guitar Studio's official FAQ documents a case where the "Phanuel Anti-Cheat" bar reaches 100%, FragPunk does not open, and Steam returns to "Launch." It also documents the "Please enable Secure Boot before playing" pop-up. Those are startup or platform-check failures. An HWID-ban diagnosis needs a separate enforcement notice and evidence that the penalty follows the device rather than the launcher error alone.
Bad Guitar Studio's October 11, 2024 policy says cheating can receive an indefinite ban, and its later Banned Players Lists describe severe-violation account bans as permanent. The publisher does not provide a separate public expiry table for hardware actions. Treat claims of an automatic reset after a fixed number of days as unverified, and do not confuse a community-reported multi-year account timer with a documented HWID duration.
A FragPunk reinstall changes game files, not the physical device. Reinstalling Windows can regenerate `MachineGuid` and an OS volume serial, but it does not replace the SMBIOS Type 2 baseboard serial, motherboard UUID, retained drive firmware serial, physical NIC MAC address, or TPM hardware. Because Phanuel's matching weights are private, neither a format nor one new SSD can be promised as a complete reset.
Changing storefronts changes the launcher and account linkage, not the Windows device beneath them. Steam and Epic still present the same baseboard, disks, network adapters, Windows identifiers, and boot state to FragPunk's PC stack. If the penalty is account-only, the proper route is a publisher review. If the PC is actioned, using another valuable account as a test can expose that account to the same device association.
Bad Guitar Studio does not publish a field list. Real Windows collection surfaces include the SMBIOS Type 2 baseboard serial and system UUID, physical disk serials through storage IOCTLs, volume serials, NIC MAC addresses, and `MachineGuid` under `HKLM\SOFTWARE\Microsoft\Cryptography`. TPM 2.0 also exposes an endorsement key. These are possible fingerprint inputs, not a leaked Phanuel schema or proof that every field is weighted equally.
No. FragPunk's official FAQ tells affected players to enable Secure Boot, and the literal "Please enable Secure Boot before playing" prompt is a prerequisite failure rather than a ban notice. Secure Boot state can be checked without proving that Phanuel stores the TPM 2.0 endorsement key. Disabling either security feature can stop the game from launching; it does not erase a publisher-side enforcement record.
Use FragPunk's official support channel and provide a short timeline, the exact notice, launcher, account identifier, and any legitimate used-hardware or account-compromise evidence. Bad Guitar Studio publishes reporting instructions for cheats, but it does not publish a dedicated HWID appeal form or response-time promise. A review may correct a false action; it does not guarantee restoration, and the public policy describes confirmed severe bans as permanent.
A temporary session spoofer changes selected reports only while its driver or process is active. After reboot, the original profile can return 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 stays open with Phanuel or Shard Clash. The rewrite changes supported device-side values; it does not reinstate the account that received the original ban.
Learn More
HWID Spoofing Guides
Anti-cheat comparison for 2026: EAC vs BattlEye vs Vanguard vs RICOCHET and 8 more engines, with developer, kernel access, ban type and cross-game reach
HWID Spoofing Guides
HWID ban duration compared across 24 games: which bans expire, which are permanent, and why your ban notice says the year 2226 when nothing is counting down
HWID Spoofing Guides
Permanent vs temporary HWID spoofer, settled: a session spoof substitutes values while it runs, a permanent rewrite changes them once and survives reboot
Next Steps
The notice shown in FragPunk 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 Phanuel 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.