Helldivers 2 no longer uses GameGuard on PC. Arrowhead switched the game to Easy Anti-Cheat (EAC) in its October 20, 2026 update, and the studio’s version 7.2.0 notes confirm the change. GameGuard’s kernel-level access and privacy claims are therefore historical context—not a description of the game’s current anti-cheat. If GameGuard files remain after the update, Arrowhead’s post-switch cleanup instructions are the relevant guide.
What changed, and which anti-cheat does Helldivers 2 use now?
As of Arrowhead’s October 20, 2026 update, the PC version of Helldivers 2 uses EAC instead of nProtect GameGuard. The studio confirmed the implementation in its version 7.2.0 release notes and transition announcements. That date matters: older guides and support pages may still describe GameGuard because they were written before the switch.
| Question | GameGuard | EAC |
|---|---|---|
| Role in Helldivers 2 | Previous PC anti-cheat, used before the October 20, 2026 update | Current PC anti-cheat after the update |
| What the cited Arrowhead material establishes | Developer statements about its historical permissions, operation, and data collection | Implementation in version 7.2.0 and transition details; not an equivalent privacy inventory |
| What to do about old files | Use Arrowhead’s targeted post-switch instructions if remnants are present | Keep the current game installation intact and verify its files after cleanup |
This is not a privacy or security head-to-head: the available Arrowhead statements do not provide equivalent telemetry inventories or driver-lifecycle details for both products. The fact that the game now uses EAC does not mean EAC behaves like GameGuard, nor does GameGuard’s historical permission profile describe EAC.
Was GameGuard a rootkit?
GameGuard had kernel-level access on Windows, according to Helldivers 2 technical director Peter Lindgren in 2024. “Rootkit” is often used loosely to mean software with deep system privileges, but that label alone does not establish that GameGuard concealed itself, acted maliciously, or compromised a PC.
Lindgren described GameGuard as an anti-cheat that examined running processes for software attempting to manipulate the game client. Kernel-level privilege is significant because it gives software access below ordinary applications; that is a legitimate trust and security consideration even when the software’s purpose is anti-cheat. But capability and reported behavior are different questions: privilege does not prove that a product read a particular file, stole a password, or performed another specific act.
In the same 2024 Steam discussion, Lindgren said GameGuard was active only while the game was running and did not change firewall settings. These are statements from the developer’s technical director about the game’s implementation, not an independent audit of every configuration or a guarantee that vulnerabilities were impossible.
Did GameGuard scan a PC or collect personal information?
Arrowhead’s account was that GameGuard checked running processes for software that could manipulate Helldivers 2. Lindgren also said that it did not collect personally identifiable information (PII), and described communication with a few servers for patching and reporting. Those claims explain the studio’s stated operation; they are not a public, field-by-field list of every data element the software could handle.
Lindgren’s exact assurance was: “No, GameGuard does not collect any personally identifiable information (PII).” That should be attributed to him rather than presented as a proven forensic conclusion. The reviewed first-party material does not provide a full telemetry inventory or an independent GameGuard-specific audit, so it cannot establish either that every imaginable collection was impossible or that private documents or passwords were collected.
It helps to separate three ideas that are often collapsed into one:
- Permission: GameGuard’s kernel-level access gave it a privileged position on Windows.
- Stated purpose and behavior: Arrowhead said it monitored running processes for game manipulation and used server connections for patching and reporting.
- Independent verification: The cited developer statements are assurances, not an external audit or complete technical inventory.
Arrowhead’s rationale for using anti-cheat in a cooperative game was that cheating can affect other players’ progression and the shared Galactic War. Lindgren cited Helldivers 1 players receiving 9,999 research samples through a cheat as an illustration of how one player’s actions could affect cooperative rewards; that is his anecdote, not a measure of how common cheating was. The studio also pointed to Helldivers 2’s peer-to-peer play and shared metagame as reasons to protect progression. Players can understand that rationale while still deciding that kernel-level access was not a trade-off they wanted.
Did GameGuard keep running after Helldivers 2 closed?
For Helldivers 2’s historical GameGuard implementation, Lindgren said it was active only while the game was running. That statement concerns the anti-cheat’s reported operation, not whether every related service or file vanished when the game closed or was uninstalled.
Arrowhead’s 2024 FAQ distinguished the administrator-level service from update files that could remain in the game directory. The GameGuard publisher likewise says service or driver files may remain if another installed game also uses GameGuard. A leftover file is not, by itself, proof that a service is currently running; conversely, deleting a visible game folder is not a reliable way to determine the state of system-level components.
If you need to check a specific PC’s current driver or service state, the cited material does not provide a universal diagnostic command or establish that every player has the same remnants. Avoid treating an old file path as proof of active monitoring, and do not manually delete unrelated Windows driver or registry entries based on a generic online guide.
How do I remove GameGuard leftovers after the EAC update?
If you have updated to EAC and are troubleshooting a launch problem or visible GameGuard remnants, use Arrowhead’s October 29, 2026 support sequence. It targets the game’s own files and asks you to restart and verify them; it is not a reason to remove unrelated system components.
- Open the game’s installation folder. In Steam, open your Library, right-click Helldivers 2, and choose Manage → Browse local files. The exact installation path depends on which Steam library contains the game.
- Run the included uninstaller. Open the game’s
EasyAntiCheatfolder and runGGuninst.exe. - Remove the old game-folder directory if it remains. Check
SteamsteamappscommonHelldivers 2inGameGuardunder the game’s installation location. If thatGameGuarddirectory is present, delete that directory—not similarly named files elsewhere on the PC. - Restart Windows. Use Windows’ Restart command rather than treating closing and reopening the game as the same step.
- Verify the game files in Steam. Open the game’s Properties → Installed Files → Verify integrity of game files. Let Steam complete the check before launching again.
These steps follow Arrowhead’s post-switch crashing article. If the problem involves mod remnants, follow the support article’s mod-specific guidance rather than assuming that every player should reset local data. In particular, deleting %appdata%ArrowheadHelldivers2 can remove local settings, so it is a consequential troubleshooting option—not a required GameGuard cleanup step for everyone.
Does uninstalling the game remove every GameGuard component?
Not necessarily, and the answer depends on what is installed and what “remove” means. Arrowhead said the administrator-level service was removed when Helldivers 2 was uninstalled or when gguninst.exe was run, while acknowledging that update files could remain in the game directory. The GameGuard publisher says service or driver files may persist if another installed game uses GameGuard and provides a separate uninstaller.
If the game is already gone but you have reason to investigate a remaining GameGuard component, consult the GameGuard publisher’s official support and uninstaller guidance rather than deleting system-driver or registry entries by hand. The available statements do not establish that every PC will retain a component, or that every remaining file represents an active service. A targeted uninstaller is a safer route than a third-party cleanup utility or manual system-file removal.
Why does an Arrowhead support page still tell me to reinstall GameGuard?
Some older support material has not kept pace with the EAC switch. Arrowhead’s Error 114 article, updated October 26, 2026, still describes removing and reinstalling GameGuard and suggests antivirus or firewall exceptions. That advice conflicts with the version 7.2.0 transition and Arrowhead’s newer October 29 post-switch troubleshooting article.
For a problem after the EAC update, prioritize the newer post-switch instructions over the older Error 114 page. Do not reinstall GameGuard just because an older page says to, and do not make broad antivirus or firewall exceptions a routine cleanup step. If the EAC-specific procedure does not resolve a current error, contact Arrowhead support with the error details instead of applying instructions written for the previous anti-cheat.
Why did Arrowhead replace GameGuard with EAC?
Arrowhead said its GameGuard implementation “wasn’t as effective as it could have been” and that the transition to EAC included additional security measures intended to address cheating and unfair modifications. The studio did not provide a measured detection-rate comparison in the cited announcement, so the explanation should be read as its stated reason for the change, not as a published benchmark.
Arrowhead warned that some gameplay-impacting mods—and even some cosmetic mods—might need updates or stop working after the transition. Its transition FAQ said the change added no hardware requirements and did not alter Steam Deck or Linux compatibility. Those statements describe the announced transition; they do not establish that every individual mod will work or that the two anti-cheat products share privacy practices, permissions, or removal procedures.
The practical conclusion is specific: GameGuard’s old Windows permissions are relevant when assessing the historical version of Helldivers 2, but the game switched to EAC on October 20, 2026. For cleanup, use the post-switch game-folder steps and avoid turning an old support instruction or an unexplained leftover file into a claim that GameGuard is still actively running.
Frequently Asked Questions
Can I play Helldivers 2 without installing an anti-cheat?
Arrowhead’s transition notes describe EAC as the replacement anti-cheat for the PC game, not an optional component. The cited material does not document an official anti-cheat-free launch mode.
Will deleting the GameGuard folder break the new anti-cheat?
Arrowhead’s cleanup sequence specifically targets the old binGameGuard directory if it remains, then asks players to restart and verify game files through Steam. Steam’s file verification is the recovery step if the installed game files need repair.
Are GameGuard and EAC made by the same company?
The cited sources identify GameGuard as nProtect GameGuard and describe EAC as the replacement selected by Arrowhead. Arrowhead’s announcement says its transition FAQ listed over 200 games using EAC, a studio-stated figure rather than an independently verified current count.
Does the EAC switch mean all mods are banned?
No blanket ban is established in Arrowhead’s transition notice. The studio warned that some mods affecting gameplay, and even some cosmetic mods, might need changes or stop working, so compatibility depends on the particular mod.