Resolve EA AntiCheat Incompatible Driver on Windows 11: Quick Guide

The “EA AntiCheat has detected an incompatible driver” block is one of the most common hard-stops gamers see on Windows 11: the game launcher refuses to start, the anti-cheat refuses to load, and the only diagnosis shown is a driver filename or a terse popup. This is usually fixable without reinstalling the game, but it requires systematic cleanup of low-level drivers, removal of known conflict-causing utilities, and a few Windows-level checks to confirm kernel-mode protections aren’t being tripped. The steps below combine the practical field fixes used by technicians with vendor guidance and Windows kernel documentation so you can identify the offending component, remove or update it safely, and restore game access without permanently weakening system security.

Background / Overview​

EA’s anti-cheat (EA Javelin / Easy Anti-Cheat family, often abbreviated EAAC or EAC) runs kernel-mode components to detect cheats. When it finds a driver that is unsigned, obsolete, deny-listed, or incompatible with Windows kernel mitigations (for example Memory Integrity / HVCI or Secure Boot policies), EAAC will refuse to let the game launch. In practice the error is triggered by three classes of root cause:

• A low-level driver left behind by third-party system utilities (RGB suites, motherboard control apps, monitoring tools).
• A driver that is legitimately used by another application but is unsigned or mismatched (remnants from older game anti-cheats, or non-WHQL drivers).
• A Windows security setting or kernel mitigation that prevents a kernel driver from loading or flags it as unsafe (Test Mode, HVCI/Memory Integrity, or a Secure Boot policy).

EA’s official support guidance explains that the anti-cheat will show a denylist-style message and that you should update or disable the software associated with the driver name reported by the error. Many community guides and repair steps follow that same approach: identify the driver name, remove the offending tool, update drivers, reinstall EAAC, and only then move to advanced checks like driver signing or kernel isolation toggles.

---

How to diagnose the problem (fast path)​

These quick checks will tell you whether the issue is a known third-party driver or a Windows configuration issue.

1. Note the filename in the EAAC popup​

If the popup lists a driver filename (for example gdrv.sys, mhyprot2.sys, or glckio2.sys) write it down exactly—this is your primary clue. If a filename is given, search for that exact filename on your PC (C:\Windows\System32\drivers and Temp locations) and online to map it back to the owning software.

2. Check Windows Event Viewer for EAAC entries​

Open Event Viewer (Win + X → Event Viewer) → Windows Logs → System and look for entries around the time EAAC failed to start. EAAC or system-level driver load errors will often log more detail there.

3. Look for known culprits​

Many community and vendor lists show recurring problem drivers:

• gdrv.sys / Gigabyte App Center or RGB Fusion
• glckio2.sys / GIGABYTE RGB Fusion variants
• mhyprot2.sys / HoYoverse (Genshin Impact) anti-cheat remnants
• hwinfo64a.sys / HWiNFO monitoring driver
• drivers installed by MSI Afterburner / RivaTuner or any app that injects kernel hooks

EA’s support page and anti-cheat denylist are explicit about these types of tools and advise updating or removing them. Treat such drivers as the first suspects.

---

Step‑by‑step fixes — start here (safe, recommended order)​

Follow these steps in order. Each step is designed to fix the most common cases and avoid unnecessary risk.

1) Identify the driver owner (if the error lists a name)​

• Copy the exact filename shown in the popup (for example gdrv.sys).
• Use File Explorer to search C:\Windows\System32\drivers and C:\Windows\Temp for that filename.
• If found, check file properties → Details to see the product name and company.
• If the file is in a game or vendor folder (for example a temp folder under a vendor install), uninstall or update that vendor application first.

If you don’t see a driver name in the popup, use Event Viewer as described above to find logged details. The filename is the single most useful clue.

2) Uninstall common conflicting apps (RGB, overclocking, monitoring)​

Certain background utilities inject kernel or user-mode hooks that anti-cheat flags as incompatible. Uninstall these if present:

• GIGABYTE App Center / RGB Fusion / Xtreme Engine (gdrv.sys / glckio2.sys)
• MSI Afterburner + RivaTuner (monitoring/injection components)
• HWiNFO (hwinfo drivers)
• EVGA Precision / Galaxy RGB tools
• Voicemod, Process Explorer drivers, Samsung Magician kernel drivers
• Any GPU overlay or third-party kernel driver injected by OEM utilities

Steps:

• Press Win + R → appwiz.cpl → uninstall the named apps.
• Reboot.
• Relaunch the game to test.

Community and vendor guidance repeatedly name these exact utilities as causes; removing them often resolves the block.

3) Update or reinstall GPU and chipset drivers (clean reinstall if necessary)​

Outdated or mismatched GPU stacks commonly trigger anti‑cheat checks.

• Open Device Manager → Display adapters → right-click GPU → Update driver (or download the latest WHQL driver from NVIDIA/AMD/Intel).
• Also update System Devices (chipset) and Network Adapters via vendor downloads (use the OEM or chipset vendor site, not shady third-party driver aggregators).
• If you're switching vendors or the driver is showing inconsistent version strings, perform a clean driver removal with the vendor cleanup tool (AMD Cleanup Utility) or Display Driver Uninstaller (DDU) in Safe Mode, then install the latest WHQL release. Reboot.

If Windows keeps overwriting the vendor driver with an automatic update, block driver delivery temporarily via Group Policy or the ExcludeWUDriversInQualityUpdate registry key (use carefully; blocking Windows-supplied drivers forces you to track security updates manually). Detailed vendor-clean reinstall guidance is widely recommended by support communities for driver mismatch cases.

4) Repair or reinstall EA AntiCheat​

EAAC installation can become corrupted or mis-permissioned. Reinstalling from the supplied installer is low risk and often fixes validation errors.
Steps:

• Open the EA/Epic/Origin game folder (example: C:\Program Files\EA\AC or inside the game directory).
• Run EAAntiCheat.Installer.exe as Administrator.
• Select the game in the installer → Uninstall → then Install.
• Reboot and try launching the game.

If the installer is missing, verify game files via the launcher (Steam/Epic/EA App) or re-download the EAAC installer from the publisher’s support package. Community reports show reinstalling EAAC removes a surprising number of driver-validation failures.

5) Disable Windows Test Mode (if enabled)​

Test Mode (testsigning) allows unsigned kernel drivers to load and will raise red flags in anti-cheat checks. Microsoft documents that TESTSIGNING can be turned off with bcdedit. Do not enable Test Mode except for controlled development testing.

• Open an elevated Command Prompt and run:
  bcdedit /set TESTSIGNING OFF
• Reboot.
• Confirm with bcdedit and ensure testsigning is not Yes.

Microsoft explicitly documents the TESTSIGNING option and cautions about Secure Boot/BitLocker interactions. Only toggle this with clear understanding—leaving Test Mode on will cause anti-cheat failures. (learn.microsoft.com, support.microsoft.com)

6) Run EA AntiCheat and your game with Administrator privileges​

Improper permissions can prevent EAAC from performing integrity checks.

• Right-click EAAntiCheat.Installer.exe and your game EXE → Properties → Compatibility → check “Run this program as an administrator”.
• Apply, restart, and test launch.

This is a simple, zero-risk permission check that resolves some launch-block scenarios.

7) Repair Windows system files (SFC / DISM)​

Corrupted system files can interfere with driver loading.

• Open elevated Command Prompt and run:
  sfc /scannow
• Then run:
  DISM /Online /Cleanup-Image /RestoreHealth
• Reboot and retest.

SFC and DISM are standard Windows tools to repair broken system components and are safe first-line steps.

---

Advanced checks (for persistent or obscure cases)​

These are for experienced users. Back up, create a restore point, and document what you change.

8) Check unsigned or hidden kernel drivers​

• Open an elevated PowerShell or Command Prompt and export the loaded drivers list:
  driverquery /v /fo list > %USERPROFILE%\Desktop\drivers.txt
• Open drivers.txt and scan for non-Microsoft drivers with suspicious names.
• Use Microsoft Sysinternals Autoruns to identify drivers and services that load at boot. Disable suspect entries one at a time and reboot to test.

If you identify a driver whose vendor you recognize (e.g., a vendor RGB driver), remove the parent application properly via Programs & Features, then manually remove the driver file from C:\Windows\System32\drivers only after uninstall and reboot. Deleting drivers arbitrarily can render hardware nonfunctional. Use driver cleanup utilities for a clean uninstall.

9) Check Memory Integrity / Core Isolation (HVCI)​

Windows 11’s Memory Integrity (Hypervisor-enforced Code Integrity or HVCI) is an advanced mitigation that prevents unsigned or older drivers from loading. If EAAC or a driver is incompatible with HVCI you may see driver load errors or black-screen/BSOD symptoms.

• Open Windows Security → Device security → Core isolation details → check Memory integrity status.
• If Memory integrity is enabled and you suspect a driver conflict, you can temporarily disable it for troubleshooting, reboot, and retest. Re-enable after testing.
• Be explicit: disabling Memory Integrity reduces kernel-level protections—only do this long enough to confirm the cause and then seek a signed, updated driver from the vendor.

Community and Microsoft guidance confirm that HVCI frequently causes driver incompatibility symptoms and that some anti-cheat drivers needed updates to function under newer Windows mitigations.

10) Kernel mitigations and Secure Boot interactions​

• If you attempted to enable Test Mode while Secure Boot is active, Windows may refuse the change or block driver loads. Microsoft’s docs cover the interplay between Secure Boot and test-signed code—if you see “The value is protected by Secure Boot policy” when running bcdedit commands, check Secure Boot/BitLocker status and proceed cautiously. (learn.microsoft.com, support.microsoft.com)

---

Practical clean-up checklist (ordered)​

• Note the exact driver filename shown by EAAC or Event Viewer.
• Uninstall known conflicting utilities (RGB suites, monitoring, overclock tools).
• Reboot and test.
• Update GPU and chipset drivers; if mismatched, run DDU/AMD Cleanup Utility in Safe Mode and reinstall WHQL drivers.
• Reinstall EA AntiCheat from the game folder as Administrator.
• Run sfc /scannow and DISM /RestoreHealth.
• If problem persists, export driver list and use Autoruns to find hidden kernel loads. Disable/uninstall identified tools one at a time.
• As a last diagnostic, check Memory Integrity and Test Mode, but do not permanently disable protections—seek vendor-signed drivers instead.

---

When it’s safe to remove leftover anti-cheat or vendor drivers (caution)​

• Some packages (for example HoYoverse’s mhyprot2.sys or older anti-cheat kernels) have been known to leave drivers behind after uninstalling the game. If you’ve uninstalled the game and confirmed the driver is not used by any installed software, you can remove the driver file from C:\Windows\System32\drivers and delete any related service entries—but do this only as a final cleanup and after creating a system restore point. Community reports confirm this works for many users, but manual removal without uninstall risks system instability. Flag any driver deletion as a manual-cleanup operation and keep backups.

---

Critical analysis — strengths and risks​

What EA AntiCheat’s strict checks achieve​

• Stronger cheat prevention: Kernel-mode verification prevents many advanced cheats that inject code at low levels. This protects fair play in competitive environments.
• Platform integrity: By denylisting known risky drivers, anti-cheat systems reduce the attack surface used by kernel-level malware.

The risks and user friction​

• False-positives and benign apps flagged: Many legitimate hardware control and monitoring tools use low-level drivers for valid reasons; these are often flagged because they expose the same kernel surfaces cheats exploit. That means gamers using legitimate vendor utilities can be blocked. EA’s denylist and vendor lists make this explicit but can produce customer frustration.
• Pressure to disable system protections: Community guidance sometimes suggests disabling Memory Integrity or driver signature enforcement as troubleshooting. Those are security-reducing actions that should never be used permanently. They are useful only for diagnosing compatibility and verifying whether a driver is the culprit. Microsoft documentation makes this clear. (learn.microsoft.com, support.microsoft.com)
• Legacy hardware and drivers: Older devices with abandoned drivers may never receive vendor-signed updates and will be effectively blocked from anti-cheat protected titles without replacing hardware.

Best-practice trade-offs​

• Prioritize obtaining vendor-signed drivers and modern software updates rather than permanently lowering kernel protections. When you must disable a protection for testing, keep the window small, document the change, and restore protections immediately after testing.

---

If nothing fixes it — escalation path​

• Collect logs: attach EAAC logs from the game install directory and the EAAC installer log.
• Include Event Viewer entries and a drivers.txt export from driverquery.
• Contact EA Help (or the game publisher’s support) and provide logs and your hardware/driver versions; they can confirm denylist matches or advise on specific driver names.
• For stubborn driver remnants, consult the vendor’s support (Gigabyte, MSI, HoYoverse) for signed driver updates or removal tools.

Providing complete logs speeds up vendor diagnosis — EA Help documentation asks customers to provide the exact driver filename and logs to investigate denylist decisions.

---

Quick FAQ (concise answers)​

• Why does EA AntiCheat block MSI Afterburner or RGB software?
  Many of these tools inject monitoring hooks or install kernel-mode components that anti-cheat flags as potential exploitation surfaces. Removing or updating the tool usually resolves the issue.
• Is it safe to delete mhyprot2.sys?
  Only after you’ve uninstalled the application that installed it (for example, if you removed HoYoverse games). Delete kernel drivers only as part of a controlled cleanup and after creating a restore point. Community reports show it resolves blocks when the related game is no longer installed, but manual deletion should be a last step.
• Does disabling Memory Integrity fix the problem permanently?
  It can allow the driver to load, but it reduces system security. Use it only to confirm the driver is incompatible; then seek a signed driver or an updated version from the vendor.

---

Final recommendations and prevention​

• Keep system drivers (GPU, chipset, network) updated with vendor WHQL releases. Clean reinstall when you swap major driver versions.
• Remove non-essential kernel-level utilities used only for monitoring or cosmetic changes (RGB/overclocking) if you play EAC-protected titles. Consider using vendor apps that rely only on user-mode features instead.
• Avoid leaving Windows in Test Mode or permanently disabling driver signature enforcement—these are troubleshooting tools, not fixes. Microsoft docs explain the risks and the proper commands to toggle these modes. (learn.microsoft.com, support.microsoft.com)
• When blocked, collect the EAAC popup filename, Event Viewer entries, and a drivers.txt export. These make vendor support far more effective.

EA AntiCheat’s compatibility checks can be frustrating, but they play a necessary role in multiplayer fairness. The fastest paths back to play are identification (driver filename), removal of known conflicting utilities, a clean driver stack, and reinstalling EAAC. Only after those steps should you consider toggling kernel mitigations—and if you do, treat them as temporary diagnostics while working with hardware vendors or EA to obtain a signed, supported driver.

---

Source: Windows Report How to Fix “EA AntiCheat Has Detected an Incompatible Driver” on Windows 11?