Problem: Easy Anti-Cheat (EAC) error 30005 / “StartService failed with 1275” suddenly blocks many PC gamers from launching multiplayer games (Windows 11)

Published: 2026-01-11 12:00 (local time)

Quick Summary

Many Windows 11 players can’t launch EAC-protected games due to error 30005 variants (often “StartService failed with 1275” or “CreateFile failed with 32”).
It appears tied to EAC’s kernel driver/service failing to start—sometimes after Windows security changes or updates.
There is no single universal fix; multiple causes produce the same symptom.
Most reliable workarounds involve: repairing/reinstalling EAC, reducing security-software interference, and (for some) toggling Windows “Memory integrity.”
Some fixes carry real security tradeoffs; you should treat them as temporary and revert where possible.

What’s happening

Across multiple EAC-protected PC games (examples frequently include titles launched from Steam, Epic Games Launcher, and the Microsoft Store ecosystem), players report the game refusing to start and immediately throwing an Easy Anti-Cheat error 30005 message. Common wordings include “CreateFile failed with 32,” “CreateService failed,” and “StartService failed with 1275.” Official EAC guidance frames 30005 as the EAC service being unable to access required resources (often because something else is holding a handle or blocking it). Players’ reports also point to Windows 11 security features and/or post-update changes correlating with the start of the problem, especially when EAC’s driver/service is blocked or can’t initialize.

Who is affected: primarily Windows 11 players on PC, especially those with modern security settings enabled and those running third-party antivirus/firewall or system “hardening” tools. The impact is severe: you can’t reach the main menu or you get kicked before connecting—meaning the game is effectively unplayable. This problem is “widespread” in the sense that it spans many different games that share EAC, and continues to appear in support threads and official troubleshooting pages rather than being a single-game bug.

Likely causes (what research suggests)

EAC service/driver blocked by security software: EAC’s own documentation for error 30005 (CreateService failed with 32) emphasizes antivirus interference and suggests a reboot if the issue is transient.
Windows 11 security features preventing a kernel driver from loading: Many “StartService failed with 1275” reports align with Windows blocking a driver. Community troubleshooting commonly connects this to Windows Security’s “Core isolation / Memory integrity,” with some users reporting success after disabling it (with clear security tradeoffs).
Corrupt/missing EAC components or game files: Epic’s Fortnite support article recommends reinstalling EAC and performing a clean boot/closing background apps; third-party troubleshooting guides also cite corrupted EAC .sys components as a trigger and recommend forcing regeneration.
Game-specific EAC packaging/version differences: Player reports indicate one EAC title may fail while others work, implying a per-game EAC deployment issue rather than a global EAC outage.

Solutions & Workarounds

1) Repair or reinstall Easy Anti-Cheat (per game)

Who it helps: Windows 11 PC players on Steam/Epic/other launchers where EAC files may be corrupted or out of sync.

Close the game and fully exit your launcher (Steam/Epic/etc.).
Browse to the game’s installation folder and find the EasyAntiCheat (or EasyAntiCheat_EOS) folder.
Run the EAC setup/installer inside that folder and choose “Repair” or reinstall if offered.
Reboot, then launch the game again.

Risks / tradeoffs: Low risk; may require admin privileges. Doesn’t fix cases where Windows/security tools block EAC.

Stop & contact support when: EAC repair succeeds but the same error persists across reboots—open a ticket with the game’s support and include logs/screenshots.

2) Reduce third-party security interference (Defender/antivirus/firewall allowlisting)

Who it helps: Players with antivirus suites, aggressive endpoint protection, or firewall rules that may block the EAC service.

Temporarily disable third-party antivirus real-time protection (only to test).
Try launching the game once.
If it works, re-enable protection and add allowlist/exclusions for: the game folder, the launcher folder, and EAC components.
Reboot and retest.

Risks / tradeoffs: Temporarily disabling protections increases exposure; do not browse/download while protections are off.

Stop & contact support when: You confirm security software is the trigger and you can’t create a stable allowlist—contact your antivirus vendor and the game publisher.

3) Toggle Windows Security “Memory integrity” (Core isolation) to test driver blocking

Who it helps: Players seeing “StartService failed with 1275” and similar “driver/service can’t start” behavior on Windows 11.

Open Windows Security.
Go to Device security > Core isolation details.
Turn “Memory integrity” OFF.
Restart your PC.
Launch the game and check if EAC starts normally.
If you’re cautious, some users report a pattern of turning it back ON after confirming the game launches, then restarting again (results vary).

Risks / tradeoffs: This reduces system security (it’s designed to help block certain malicious drivers). Treat as a temporary diagnostic step, not a permanent fix.

Stop & contact support when: Disabling Memory integrity is the only thing that works—report it to the game/EAC support as a compatibility issue, because you shouldn’t have to weaken security to play.

4) Clean boot (eliminate background conflicts)

Who it helps: Players running overlays, injector-like utilities, RGB tools, monitoring apps, macro software, VPNs, or “optimizer” tools that may collide with anti-cheat.

Use Windows “clean boot” steps to start with minimal startup services/apps (Epic recommends this approach for persistent 30005-type issues).
Launch the game.
If it works, re-enable startup items in small batches to find the conflicting program.

Risks / tradeoffs: Inconvenient; may temporarily disable useful drivers/tools until you re-enable them.

Stop & contact support when: You find a specific conflicting app; contact that vendor and the game support with the conflict details.

5) Force regeneration of EAC driver file (advanced, only if you understand what you’re deleting)

Who it helps: Users whose EAC driver file is corrupted and won’t initialize correctly.

Exit the game and launcher completely.
In the game’s EasyAntiCheat/EasyAntiCheat_EOS folder, locate the EAC .sys driver file (name varies by game/version).
Delete the .sys file so EAC is forced to recreate it on next launch (some guides recommend this approach).
Verify game files in your launcher (Steam “Verify integrity” or equivalent) to restore anything missing.
Reboot and retest.

Risks / tradeoffs: If you delete the wrong file, you can break the install; always verify/repair afterward.

Stop & contact support when: File deletion/repair loops indefinitely—this suggests a deeper permission/security conflict or a game-side EAC packaging issue.

Prevention (so it doesn’t come back)

Keep Windows, GPU drivers, and the game updated (but be cautious with “tweaks” that harden driver loading without understanding the impact on anti-cheat).
Avoid running multiple overlays/injectors at once (FPS counters, reshade-like tools, aggressive macro software), especially when troubleshooting.
Use allowlists instead of permanently disabling antivirus/Defender protections.
After a successful fix, document what changed (security toggle, conflicting app) so you can quickly revert if the issue returns.

FAQ

Q: Is error 30005 always “my PC” and not the game?
A: Not always. The same EAC error can be triggered by your local security/configuration OR by how a specific game ships/updates its EAC components. Evidence: some players report only one EAC game fails while others run.

Q: Why does “StartService failed with 1275” matter?
A: It often indicates Windows blocked a driver/service from starting, which aligns with reports that Windows security settings (like Memory integrity) can be involved.

Q: Is disabling Memory integrity safe?
A: It’s a security reduction. Use it as a temporary diagnostic step and re-enable it if possible. If it’s the only fix, push the publisher/EAC for a compatibility update.

Q: Can a reboot really fix it?
A: Sometimes. EAC’s official guidance notes the issue can be transient, and a reboot may release locked handles/resources.

Q: Should I reinstall Windows?
A: It’s usually overkill. Try EAC repair, clean boot, and security/allowlisting steps first. Reinstalling Windows should be a last resort.

Q: When should I contact official support?
A: If you can reproduce the issue after EAC repair + reboot + clean boot, or if the only workaround requires weakening Windows security, contact the game publisher and include exact error text and what you tried.