Easy Anti-Cheat Won't Open? Install and Repair Fixes

By LK Wood IV · Published 2026-06-28 · Updated 2026-11-05 · ~11 min read · St. Louis County, MO

Easy Anti-Cheat runs underneath a huge share of online PC games. Star Citizen, Apex Legends, Fortnite, Lords of the Fallen, Elden Ring, and dozens more. When it breaks, the game simply will not start.

The errors arrive in a few flavors. “Easy Anti-Cheat is not installed.” “Easy Anti-Cheat failed to start.” “Untrusted system file.” Sometimes a launcher that just bounces you back to the desktop. They share a small set of real causes.

If you have an exact message, jump to its fix: not installed, the setup file does nothing, untrusted system file, error 30004, error 30005, Game Security Violation Detected, error 20010, unknown file version, or boot validation failed. No match? Work the order below.

I ranked these fixes by how often they work. One of them — Windows 11 Smart App Control — I hit on my own machine.

Try the step for your error, then launch the game normally. Once it runs, stop. If it still fails, keep the exact message and time so you can distinguish the next failure from the original one.

What Easy Anti-Cheat is, and why it fails

EAC is a kernel-level anti-cheat service that each game installs alongside itself. Because it runs at a low level and has to trust the code around it, it is unusually sensitive. Four things matter. Whether its own service is registered correctly. Whether it has permission to run. Whether Windows’ platform-security features such as Secure Boot and TPM are on. And whether anything on the system is blocking it from loading.

A stopped service by itself is normal when no protected game is running. Easy Anti-Cheat’s service notes explain that it starts with a protected game and stops afterward. Check the error from a launch attempt before reinstalling it.

Choose the repair that matches your game

1. Follow your game’s official EAC repair route

Installers differ. Check the publisher’s instructions for the game that fails, then locate its bundled EAC installer through the launcher’s game-folder option.

• Legacy repair window: if the game’s supported installer opens a window with a game selector and Repair Service, use that route as directed. Do not expect every installer to show those controls.
• EOS installer: follow the game’s documented command and product ID. For example, Wildgate’s official instructions start with launcher file verification, then use EasyAntiCheat_EOS_Setup.exe with Wildgate’s own ID. Its command normally produces no text; the guide checks the exit code to confirm installation. Use that procedure only for Wildgate. Easy Anti-Cheat’s own generic version, which reads the ID from the game’s Settings.json, is further down.
• Fortnite: Epic’s official repair procedure uses the game’s bundled installer with a repair argument and administrator launch. Follow that procedure rather than waiting for a generic dropdown.

After the publisher’s success check, launch the game again. If it still fails, record the exact error and follow that game’s troubleshooting steps. Do not substitute another title’s installer or EOS product ID.

2. Use administrator rights for the installer when required

If the publisher’s procedure calls for an administrator Command Prompt or an elevated repair shortcut, use it for that step. After the installer finishes, close it and start the game normally. Epic’s EAC integration guide distinguishes service installation from later game launches. A successful install followed by a launch error calls for the new error and game logs, not permanent administrator access.

For Fortnite LS-0013, Epic’s error guide tells Fortnite users to clear the permanent Run this program as an administrator setting on the executables it lists. The same guide has a separate diagnostic that runs the Epic Games Launcher as administrator once. Follow the branch for your game and executable.

3. Verify the game files

A single corrupted EAC file will break the service. Use your launcher’s repair. On Steam that is right-click the game, Properties, Installed Files, then Verify integrity of game files. Other launchers have an equivalent “verify” or “scan.” This re-downloads only the broken files, leaving the rest alone.

4. Turn on Secure Boot and TPM if your game requires them

Easy Anti-Cheat offers Secure Boot and TPM 2.0 as “additional security requirements.” The switch belongs to the game rather than to EAC: “Games using EAC may impose additional security requirements on players which are controlled by the developer.” These requirements “might apply to specific game types only (like competitive), specific accounts only… or might apply to all players” (Easy Anti-Cheat additional security requirements, checked 2026-09-28). So this step is not universal. Where a title has turned it on, Easy Anti-Cheat’s own kick messages name the problem: “Boot validation failed” or “Unable to verify Secure Boot” (below).

1. Reboot into your BIOS/UEFI (usually Del or F2 at boot).
2. Under Boot or Security, set Secure Boot to Enabled, and confirm TPM (often labeled PTT on Intel or fTPM on AMD) is on.
3. Save and reboot.
4. To check the TPM from Windows, Easy Anti-Cheat’s page has you run tpmtool getdeviceinformation in an administrator PowerShell. TPM Present should read true, TPM Version 2.0, and Ready For Attestation true.
5. If a game still complains, open Windows Security > Device security > Core isolation and try enabling Memory Integrity. It can cost a little performance on some systems; here is what it costs, and what to do if it won’t turn on. (Microsoft Q&A)

One caution. Enabling Secure Boot on a PC that was installed in Legacy/CSM mode can stop Windows from booting. If your install is older, confirm it is using UEFI/GPT before flipping Secure Boot on. The Secure Boot not enabled fix gives the safe order, from msinfo32 and mbr2gpt to the per-board key reset, and maps each game’s Secure Boot and TPM error to its cause.

5. Update Windows, GPU drivers, and the Visual C++ runtimes

EAC leans on current platform components. Install pending Windows Updates, update your GPU driver, and install the latest Microsoft Visual C++ Redistributables (x64 and x86). Outdated runtimes are a quiet cause of “failed to start.”

6. Check for a confirmed antivirus block

Check the antivirus protection history or quarantine for a block at the time of the failure. If it identifies the affected game’s legitimate bundled EAC file, follow the publisher’s guidance for that file and your antivirus’s restore or exception controls. Use the actual filename supplied with that game; an EOS installer may have a different name. A confirmed block is a reason to investigate that file, not to exclude the whole game folder by default.

7. Check Windows 11 Smart App Control

This is the one I hit personally, on a clean Windows 11 install on my own 7800X3D / RTX 5080 build. The game would not launch, no fix above changed anything, and there was no useful error – because the thing blocking it was a Windows security feature rather than the game.

For your own failed launch, open Windows Security > App & browser control > Smart App Control settings and check which mode is active:

• Evaluation or Off: Leave the setting alone. Microsoft distinguishes Evaluation from enforcement: Evaluation assesses software without blocking it. An audit event is not evidence that Smart App Control prevented the launch.
• On: Compare the Windows Security block notice, or the event in Event Viewer > Applications and Services Logs > Microsoft > Windows > CodeIntegrity > Operational, with the failure. Does it identify the same executable path, the same time and Smart App Control as the enforcing policy? An entry about a different file or policy does not explain this error. If nothing matches, leave the setting alone and check the publisher’s instructions for the original game error.
• Confirmed block: Keep protection on. Verify the game files, look for a supported update to the blocked launcher or component, and give the publisher the file path and time if it still fails. Start the game normally after the update. Microsoft’s Smart App Control FAQ explains why there is no bypass for a single app.

“Easy Anti-Cheat is not installed”

Easy Anti-Cheat’s support page says this means its service “has not been installed, which is a prerequisite for the EAC driver to load.” The usual culprits are a game install script that mishandled the service, or something that blocked it during install. Its generic fix, for games that ship the EOS installer:

1. Open the game’s install folder, then its EasyAntiCheat subfolder. It holds EasyAntiCheat_EOS_Setup.exe and Settings.json.
2. Open Settings.json and copy the value of productid.
3. Open Command Prompt as administrator and change into that EasyAntiCheat folder with cd /d, which also switches drives, for example cd /d "D:\Games\Your Game\EasyAntiCheat".
4. Run the install with that ID in place of <productid> (drop the angle brackets), then read the result:

EasyAntiCheat_EOS_Setup.exe install <productid>
echo %ERRORLEVEL%

The first line prints nothing. That is normal. 0 from the second means the service installed. Close the prompt and start the game normally to check whether the original failure is gone. Anything else means it failed; EAC says to make sure the Command Prompt is running as administrator and try again. The ID has to come from that game’s own Settings.json. Fortnite’s route adds a repair argument to a shortcut instead.

EasyAntiCheat_EOS_Setup.exe does nothing when opened

Easy Anti-Cheat’s instructions never double-click it. They run it from an administrator Command Prompt with a command, and a successful run prints nothing; the proof is 0 from echo %ERRORLEVEL%. EAC also says the file is the same as EasyAntiCheat_EOS.exe in C:\Program Files (x86)\EasyAntiCheat_EOS. It prefers that copy because it is “generally the most up to date.” If the setup file in the game folder seems dead, run the install command above. If the service was installed before, run the repair command further down.

“Untrusted system file”

Epic’s support page says this error “typically indicates system-level corruption” and sends you to Microsoft’s System File Checker. Microsoft’s steps, in an administrator Command Prompt:

DISM.exe /Online /Cleanup-image /Restorehealth
sfc /scannow

Run DISM first. Microsoft says it provides the files System File Checker needs for its repairs. Leave the window open until the scan reaches 100%, restart, and launch the game. If the game also requires Secure Boot or a TPM, step 4 covers those.

Error 30005

Easy Anti-Cheat says its service “was unable to start the game.” A more detailed line such as “CreateFile failed with 32” usually comes with it. The most common cause is an EAC file locked by another program. Reboot first. If it keeps coming back, EAC points at antivirus and suggests adding EasyAntiCheat_EOS.exe, in C:\Program Files (x86)\EasyAntiCheat_EOS, to the exclusions in Windows Security. That is EAC’s own service file, not your game folder (see step 6).

Error 30004 with WaitForSingleObject Failed: 2

Do not treat every 30004 as the same error. For the exact text “Unexpected Error (WaitForSingleObject Failed: 2),” Fatshark’s official support page says the Windows installation is in a corrupted state. Its order is to install current Windows updates, run System File Checker, scan for malware, and use System Restore if the first steps do not resolve it. Microsoft’s supported system-file commands are in Untrusted system file above. If your 30004 has another suffix, record the complete text and use that game’s support page rather than borrowing this branch.

Game Security Violation Detected

Epic’s official EAC support article says this message means the game process or system integrity was compromised, usually by outdated or insecure third-party software running in the background. Open Task Manager, find the process named by the violation, end it, then relaunch the game. If no process is named or the error returns, continue through the affected game’s official EAC troubleshooting. Do not disable Windows security broadly or substitute the 30005 antivirus exclusion: that is a different error with a different cause.

Error 20010: installation folder encrypted

Easy Anti-Cheat says Windows has encrypted the service’s install folder, which stops the service from starting. Open C:\Program Files (x86)\EasyAntiCheat_EOS (EAC says it may differ if your system files are on another drive), right-click the folder, choose Properties > Advanced, and untick Encrypt contents to secure data.

“Unknown file version”

Easy Anti-Cheat says a game file has been modified and no longer matches what it expects, typically by the player or by software on the PC. Verify the game’s files in Steam or the Epic Games Launcher (step 3). If verification passes and the error stays, EAC suggests running Prime95 to rule out faulty hardware.

“Boot validation failed” and “Unable to verify Secure Boot”

These are kicks from games that require Secure Boot and a TPM. Easy Anti-Cheat’s explanations:

• “Boot validation failed: Measured bootlog not found”: Windows has not generated the measured boot log, or it was removed after boot. EAC says to make sure both TPM and Secure Boot are properly enabled.
• “Boot validation failed: PCR mismatch”: the events in the boot log do not match what was measured into the TPM during boot. Something likely removed or changed events, or extended the TPM without logging it. EAC gives no single fix; I’d start with the Secure Boot and TPM checks in step 4.
• “Unable to verify Secure Boot. Event missing from measured bootlog”: the firmware did not record that Secure Boot is on. EAC says to run the latest BIOS for your system.

How to repair or uninstall Easy Anti-Cheat by hand

The service normally installs with a game and removes itself when you uninstall the last game that uses it. To repair it by hand, locate the installed shared-service folder, then open Command Prompt as administrator. The example uses the usual C: location; substitute the actual path if it differs:

cd /d "C:\Program Files (x86)\EasyAntiCheat_EOS"
EasyAntiCheat_EOS.exe repair
echo %ERRORLEVEL%

0 means the repair command succeeded. Launch the protected game normally to check whether the repair fixed the launch error. To uninstall instead, run EasyAntiCheat_EOS.exe qa-factory-reset in the same folder, check for 0, close the prompt and delete the EasyAntiCheat_EOS folder. Every game on the PC that uses this service shares it, so EAC warns you may have to reinstall the others to play them again.

How to close or disable Easy Anti-Cheat

To close EAC after playing, exit the protected game and its launcher. Do not use the qa-factory-reset command merely to end a session: EAC documents it as an uninstall, and other games on the PC can share that service.

There is no one supported switch that disables EAC while preserving online play in every protected game. Use an offline or no-anti-cheat launch choice only when that game’s publisher documents one. EAC’s current player-support index covers 30005, 20010, unknown file version and boot validation. Publisher support fills two narrower gaps above: Fatshark documents one exact 30004 signature, and Epic documents Game Security Violation Detected. An incomplete EasyAntiCheat*.sys message still does not identify a supported repair. Record the game and complete text rather than applying the 30005 fix to a different signature.

What not to do

• Do not download a third-party “EAC fixer” or “anti-cheat repair” tool. Use your game publisher’s support instructions and bundled installer. Confirm the installer name and repair method for that title before running it.
• Do not reinstall the whole game first. It is the slowest fix and rarely the right one; it only helps if file verification (step 3) finds damage it cannot repair.
• Keep Windows protection on while diagnosing a launch failure. An audit entry or unrelated notice is not an enforced block on the game.

Game-specific notes

EAC setup and security requirements vary across titles. If the error names BattlEye instead of Easy Anti-Cheat, it is a different service with its own fixes: BattlEye errors and what the number in brackets means. Star Citizen has its own log-first walkthrough in Star Citizen error 5007. VALORANT and League of Legends use Riot Vanguard instead of Easy Anti-Cheat; their VAN codes are in the Riot Vanguard error code table. Check your games’ documented requirements when planning a modern AM5 build. The GPU reviews cover the cards that carry these games.

The bottom line

Start with the affected game’s supported EAC repair and file verification. A successful installer exit code answers one question; restarting the game answers the next. If it still fails, record the new message, executable and time for the publisher. Leave system-wide protections enabled.

Sources

• Easy Anti-Cheat – additional security requirements (Secure Boot, TPM, IOMMU, boot-validation kicks)
• Easy Anti-Cheat – Error: Easy Anti-Cheat is not installed (EOS install command)
• Easy Anti-Cheat – Error 30005
• Easy Anti-Cheat – Error 20010: installation folder encrypted
• Easy Anti-Cheat – Error: Unknown file version
• Easy Anti-Cheat – EAC Windows service (manual repair and uninstall)
• Fatshark – PC: How to Resolve Easy Anti-Cheat Errors (30004 WaitForSingleObject Failed: 2)
• Epic Games – Easy Anti-Cheat error: Game Security Violation Detected
• Epic Games – Easy Anti-Cheat error: Untrusted system file
• Microsoft – Use the System File Checker tool (DISM, then sfc /scannow)
• Roberts Space Industries – Easy Anti-Cheat troubleshooting
• Microsoft Q&A – can’t play games that use anti-cheat (Secure Boot / Memory Integrity)
• Epic Games – Fortnite Easy Anti-Cheat repair procedure
• Dreamhaven – Wildgate EOS installation and success check
• Microsoft – Smart App Control overview