GameGuard is INCA Internet's anti-cheat system for 3 TraceX-listed games. This guide explains its hardware profile, supported games, and current TraceX compatibility.
INCA Internet · 3 supported games · All anti-cheats
nProtect GameGuard is INCA Internet's long-running client-security middleware. It is common in online games with roots in the Korean market and also appears in titles such as Helldivers 2, Summoners War, and AION 2. The publisher bundles and configures the GameGuard module with its own game.
GameGuard combines user-mode monitoring with privileged driver components. That kernel presence is the hub's defining story: it can validate process, driver, and system information below the ordinary game process. Public product material does not expose one universal HWID schema for every GameGuard customer.
TraceX Spoofer rewrites the supported Windows machine profile without modifying GameGuard. Complete the one-time setup, run TraceX once, and delete it; the tool does not remain resident during an MMO or Helldivers session.
INCA does not publish which hardware fields every GameGuard customer enables. A kernel-backed deployment can reconcile standard WMI with lower-level sources: `Win32_BaseBoard` maps to the SMBIOS Type 2 baseboard serial, `Win32_DiskDrive` exposes storage descriptors that can be checked through `IOCTL_STORAGE_QUERY_PROPERTY`, and `Win32_PhysicalMemory` can expose DIMM data. These are possible collection surfaces rather than a claimed fixed packet.
Windows adds `MachineGuid` at `HKLM\SOFTWARE\Microsoft\Cryptography`, volume and installation values, and MAC enumeration. A user-mode rewrite that changes only one of those answers can be compared with firmware, storage, adapter, or driver metadata observed by the kernel component.
The TPM 2.0 endorsement key is available through TBS and Secure Boot provides boot-state evidence, but GameGuard's public material does not confirm key collection across Helldivers 2, Summoners War, and AION 2. A publisher can choose its own security requirements, which is why a single GameGuard checklist should not be presented as universal.
Composite or fuzzy matching lets a deployment connect several stable inputs while tolerating ordinary component changes. The same GameGuard middleware can collect comparable values in different titles, but each publisher controls its backend and ban policy. There is no supportable claim that one GameGuard action instantly bans every GameGuard game.
TraceX lists 3 GameGuard-protected games. Open a game page below for its current compatibility, ban details, and setup guidance.
TraceX rewrites supported SMBIOS, disk, memory, network, and Windows values as a consistent set. The WMI view and the lower-level structures agree, reducing the mixed profile that appears when only a MAC or registry key changes.
Run TraceX once after the one-time setup and delete the tool. The documented changes persist without a background mask, and TraceX does not patch GameGuard's process, kernel driver, or game binaries.
GameGuard modules are publisher-specific. Check the latest published status, including Unverified, for the current title instead of assuming a Helldivers 2 result permanently covers AION 2, Summoners War, or a later INCA module.
Kernel access can compare values exposed by WMI or the registry with firmware, storage, and driver-level information. For example, `Win32_DiskDrive` can be checked against `IOCTL_STORAGE_QUERY_PROPERTY`, and `Win32_BaseBoard` against SMBIOS Type 2. A surface-only change can therefore leave contradictory answers.
Not necessarily. They share INCA's GameGuard middleware, but each publisher bundles a particular module and backend policy. The same Windows fingerprint surfaces are available across the roster, creating re-flagging exposure, while enforcement and exact telemetry remain game-specific.
A reinstall normally changes `MachineGuid` and installation values, not SMBIOS Type 2 or physical-disk descriptors. If a GameGuard deployment uses a composite, the unchanged firmware and storage signals can preserve the relationship. TraceX rewrites its supported hardware and OS-level identifiers together.
There is no public INCA field list proving that every deployment does. Windows exposes TPM 2.0 services through TBS and can report Secure Boot state, so those are available security surfaces. The responsible wording is that a publisher may use them, not that every GameGuard title stores the key.
TraceX publishes GameGuard compatibility on the detection-status page with its current status and as-of date, or shows a missing result as Unverified. Each publisher bundles its own nProtect module and configuration, so AION 2 and Helldivers 2 can change independently.
No. TraceX performs one permanent rewrite of the documented identifier set. Complete the one-time setup, run it once, and delete it. Check the latest published status, which may be Unverified, because a publisher can update its GameGuard module without changing the anti-cheat name shown on this hub.
The linked TraceX guides explain how GameGuard builds a hardware profile, what enforcement looks like afterwards, and which supported identifiers TraceX rewrites.
Kernel level anti cheat explained: what Ring 0 access really gives Vanguard, EAC and BattlEye, when their drivers load, and what it means after a ban
How does anti cheat detect hardware? It reads SMBIOS serials, disk and volume IDs, your MAC and MachineGuid, then matches them as one composite fingerprint
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
Eight HWID ban myths that keep costing banned players money, from Windows reinstalls to VPNs, with the identifier-level mechanism behind each one
TraceX links Xigncode3, ACE, Phanuel as related anti-cheat guides for comparison.
The status below shows the current published GameGuard compatibility result. An unverified result remains Unverified.
As of (US Eastern)