Apex Legends players who booted up the game on PC after September 29, 2026 found something new waiting in the background: EA Javelin Anti-Cheat, EA’s in-house kernel-level protection system, quietly replacing Easy Anti-Cheat as the game’s default defense against cheaters. The switch rolled out through a standard game update rather than a separate installer, and most players never noticed anything beyond a short extra load at launch. Some did notice, though, because the migration tripped up a handful of systems: Secure Boot confusion, driver services that refused to start, and antivirus tools that flagged the new kernel component as suspicious.
Kernel-level anti-cheat is not a new idea. Riot Vanguard, BattlEye, and Denuvo Anti-Cheat have run at the same privilege level as your operating system for years. What changed is the scale: EA says Javelin now protects 20 games, has safeguarded 57.1 million players, and flagged 26.7 million cheat attempts in the twelve months before its September 2026 progress report, with EA citing detection accuracy above 99% and an error rate under 1%. Those are EA’s own figures, measured on EA’s own terms, but they explain why the company is rolling the same driver out across its catalog instead of licensing third-party tools.
This tutorial walks through setting up, diagnosing, and safely removing kernel-level anti-cheat software, using the EA Javelin rollout as the working example. You will learn what a kernel driver actually does on your machine, how to confirm Javelin (or any similar tool) installed correctly, how to read the Windows logs that explain why it didn’t, and how to avoid the two most common ways players accidentally break their own systems while troubleshooting. By the end you will have a repeatable checklist you can reuse the next time a game studio swaps anti-cheat vendors, which, based on 2026’s pace of change, will happen again soon.
Don't miss new tech stories on Google
Add Tech Insider once in the Google app and our stories appear in your news suggestions.
What Kernel-Level Anti-Cheat Actually Does
Every Windows process runs at a privilege level. Your game, your browser, and Discord all run in what’s called Ring 3, also known as user mode. Ring 3 software talks to hardware and the operating system only through documented system calls. It cannot peek into another program’s memory, inspect the kernel, or load before Windows itself finishes booting.
Kernel-level anti-cheat tools install a signed driver that runs in Ring 0, the same privilege tier as the Windows kernel. A Ring 0 driver can inspect other processes’ memory, watch which drivers load, monitor handle access, and block or terminate suspicious activity before a user-mode program could even detect it happened. That’s the entire value proposition: cheat software that hides from a normal anti-cheat client by operating below it still has to answer to something running at the same level.
The tradeoff is that a kernel driver with that much access becomes a meaningful part of your system’s attack surface. A bug in the driver, not a cheat but the anti-cheat itself, could in theory open a path to privilege escalation. That’s why Microsoft requires every kernel driver to carry a verified signature before Windows will load it, checked through Code Integrity at boot or at driver-load time. Driver signing proves a driver came from a known publisher and hasn’t been tampered with. It does not prove the driver is free of bugs, which is exactly why game studios keep patching their anti-cheat drivers as often as they patch the games themselves.
Kernel drivers also differ in when they start. A boot-start driver loads during early Windows initialization, before most software has a chance to run, which helps catch cheats that try to load ahead of the game. A demand-start driver loads only when the anti-cheat service or the game itself requests it. Riot Vanguard is the best-known example of boot-start kernel anti-cheat, a design choice that drew criticism when it launched because the driver kept running even after players closed Valorant. EA has not published Javelin’s exact startup model in the same detail, so treat any claim about Javelin running at boot as unconfirmed until EA documents it directly.
Why Studios Keep Switching Anti-Cheat Vendors
Apex Legends is not the first big title to change anti-cheat providers mid-life, and it won’t be the last. Studios weigh three things when they decide whether to keep a licensed third-party tool or build their own: detection quality against the specific cheat ecosystem targeting their game, the cost of licensing fees at scale, and how much control they want over patch timing when a new cheat method shows up. Building an in-house system like Javelin gives EA direct control over detection logic across its entire portfolio at once, rather than waiting on a third-party vendor’s release schedule every time a new exploit surfaces in one specific title.
That control comes with a cost for players: every migration is effectively a new piece of kernel software touching your system for the first time, even if the game itself hasn’t changed. The practical result is that the setup and troubleshooting skills in this guide apply well beyond Apex Legends and Javelin specifically. The same sequence, confirm your OS build, update firmware and drivers, launch through the official client, verify the service registered, and read the Code Integrity log when something fails, works whether the game in front of you just switched to Javelin, BattlEye, Vanguard, or a system that doesn’t exist yet. Treat this as a reusable playbook rather than a one-time fix for a single title.
Prerequisites: What You Need Before You Start
Before touching any settings, confirm your system actually meets the baseline. EA’s support documentation lists Windows 10 build 10.0.19041 (version 20H1) or later as the minimum for Javelin, which in practice means almost any actively updated Windows 10 or Windows 11 installation qualifies. The table below covers what you need checked off before you start the setup steps.
| Requirement | Minimum | Why it matters |
|---|---|---|
| Windows version | Windows 10, build 10.0.19041 (20H1) or later | EA’s documented floor for Javelin compatibility |
| Architecture | 64-bit Windows | Kernel anti-cheat drivers ship as 64-bit binaries only |
| Account privileges | Local administrator | Driver installation and service registration require elevation |
| Disk partition style | GPT (only required if enabling Secure Boot for other EA titles) | Secure Boot cannot run on legacy MBR disks |
| Firmware mode | UEFI (only required for Secure Boot) | Secure Boot is a UEFI-only feature, not available in legacy BIOS/CSM mode |
| TPM | TPM 2.0 enabled (only required for Secure Boot) | Secure Boot key storage depends on TPM availability |
| Free disk space | At least 2 GB free beyond the game’s own requirement | Driver packages, logs, and update staging need headroom |
Notice that Secure Boot, GPT, and TPM 2.0 are marked conditional. EA’s own Apex Legends announcement states plainly that Secure Boot is not required for Apex at this time, even though Javelin is a kernel-level tool. Other EA titles may set a stricter bar, so check the specific game’s support page rather than assuming every EA release shares identical requirements. Mixing up a general Secure Boot requirement with Apex’s current exemption is one of the most common sources of confusion players run into during setup, and it’s worth settling before you start changing firmware settings you don’t need to touch.
Step 1: Confirm Your Windows Build Number
Open the Run dialog with Win+R, type winver, and press Enter. The dialog that appears shows your exact OS build. Compare the number after “OS Build” against 19041 or higher. If Windows Update has been running normally, this check almost always passes without any action, but it costs ten seconds and rules out the single most common reason a kernel anti-cheat driver refuses to install on an older, unpatched machine.
If your build number is lower than 19041, open Settings, go to Windows Update, and run a full update cycle before proceeding. Do not try to install or troubleshoot anti-cheat software on an outdated build. Every later step in this guide assumes a current, supported Windows version.
Step 2: Check Secure Boot and TPM Status
Even though Apex Legends does not currently require Secure Boot, other EA and non-EA kernel anti-cheat titles do, and it’s worth knowing your current state before a future update changes the requirement. Open PowerShell as Administrator and run the following two commands.
Confirm-SecureBootUEFI
Get-TpmA healthy system returns True from the first command and shows TpmPresent : True and TpmReady : True from the second. If Confirm-SecureBootUEFI throws an error instead of returning a boolean, your firmware is almost certainly running in legacy BIOS or CSM mode rather than full UEFI, which blocks Secure Boot entirely regardless of your TPM state.
Example output on a compliant system
PS C:\WINDOWS\system32> Confirm-SecureBootUEFI
True
PS C:\WINDOWS\system32> Get-Tpm
TpmPresent : True
TpmReady : True
TpmEnabled : True
TpmActivated : True
ManufacturerId : 1229870147
ManufacturerIdTxt : NTC
ManufacturerVersion : 7.2.3.0If you need Secure Boot for a title that requires it and these checks fail, the fix path is firmware-level: switch the boot mode from Legacy/CSM to UEFI in your motherboard setup, convert your system disk from MBR to GPT using Windows’ built-in MBR2GPT tool, enable TPM in firmware if it shows disabled, and then enable Secure Boot. This is a firmware change with real risk to your bootloader, so back up your data first and only make this change if a specific game actually requires it.
Step 3: Update Windows, Chipset, and Firmware
Kernel drivers interact directly with low-level system components, so an outdated chipset driver or unpatched Windows build causes a disproportionate share of anti-cheat install failures compared to ordinary software. Run Windows Update until it reports no further updates available, then check your motherboard manufacturer’s site for a current chipset driver package. This single step resolves a large share of the “service failed to start” errors covered later in this guide, before you even reach the game itself.
Step 4: Update GPU and Peripheral Drivers
Outdated GPU drivers occasionally conflict with anti-cheat drivers that monitor hooked DirectX or Vulkan calls, since both are competing for low-level access to the same rendering pipeline. If you haven’t updated your graphics driver in the last month, do it now, before installing or reinstalling anti-cheat software, not after. The full GPU driver update walkthrough covers both NVIDIA and AMD paths if you want the long version, and the same logic applies to any peripheral software that injects into games, including overlay tools for capture cards, RGB lighting suites, and macro utilities. Close or temporarily disable anything that hooks into running processes before your first anti-cheat launch.
Step 5: Temporarily Disable Conflicting Background Software
Kernel anti-cheat is built to be suspicious of anything that hooks process memory, injects DLLs, or runs a second kernel driver alongside it. Virtual machine software, debuggers, memory-editing tools like Cheat Engine (even when used for single-player trainers in unrelated games), and some third-party overlay tools fall into this category. Close these applications completely, not just minimize them, before your first launch after installing or updating anti-cheat software. You can re-enable most of them once the anti-cheat driver is confirmed working, with the obvious exception of anything the game’s terms of service actually prohibit while playing online.
Step 6: Launch Through the Official Client to Trigger Installation
EA’s Javelin migration for Apex Legends happens automatically through a normal game update, delivered the moment you launch Apex through the EA app or Steam. There is no separate anti-cheat installer to download manually. Start the official launcher, let it finish any pending update, and launch the game. The first launch after migration typically takes longer than usual while the driver package installs and registers as a Windows service, so don’t force-close the game if it sits on a loading screen slightly longer than normal on this one occasion.
Step 7: Verify the Driver and Service Registered Correctly
Once the game has launched successfully at least once, confirm the anti-cheat components actually registered with Windows. Open an elevated Command Prompt and run these three commands.
sc query type= service
sc query type= driver
driverquery /vYou’re looking for an anti-cheat related entry in the service list with a state of RUNNING, or STOPPED if it’s set to start on demand rather than continuously. Do not assume you know the exact service or driver name in advance. EA has not published an official list of Javelin’s internal file and service names in its public documentation, so rely on what Windows itself reports rather than copying filenames from unofficial forum posts. If a result shows an anti-cheat service in a START_PENDING or error state, move to the troubleshooting section below.
Example output showing a healthy service
SERVICE_NAME: EAAntiCheatService
TYPE : 10 WIN32_OWN_PROCESS
STATE : 4 RUNNING
(STOPPABLE, NOT_PAUSABLE, ACCEPTS_SHUTDOWN)
WIN32_EXIT_CODE : 0 (0x0)
SERVICE_EXIT_CODE : 0 (0x0)
CHECKPOINT : 0x0
WAIT_HINT : 0x0A service name like the example above is illustrative only, meant to show the output format rather than a confirmed Javelin service identifier. Match the pattern, not the exact text.
Step 8: Set Safe, Minimal Antivirus Exclusions
Third-party antivirus software and Windows Defender sometimes quarantine new kernel drivers on first contact, simply because the driver is unfamiliar rather than because it’s actually malicious. If your security software flags the anti-cheat install, check its quarantine log first. Restore the file only if it matches a path inside the game’s own installation directory or the official launcher’s data folder, never a generic system path. Add exclusions only for the specific folder the official launcher created, never for your entire Windows directory, your whole user profile, or an entire drive. A narrow exclusion limits your risk if something else later tries to hide inside a broad one.
Step 9: Handle VBS, Hyper-V, and Memory Integrity Conflicts the Right Way
Virtualization-Based Security, which Microsoft documents in detail for IT administrators, uses a hardware-backed hypervisor layer to isolate sensitive processes from the rest of the operating system. Memory Integrity, also called Hypervisor-Protected Code Integrity, builds on VBS to enforce stricter rules about which kernel code can run. Microsoft ships both features turned on by default on many new Windows 11 PCs. These protections occasionally surface conflicts with anti-cheat kernel drivers that weren’t built or tested against the exact VBS configuration your PC shipped with.
The instinct many players follow is to simply turn VBS or Memory Integrity off the moment an anti-cheat driver complains. Resist that instinct as a first move. Update Windows, update your motherboard firmware, and update the anti-cheat and game client first, since most VBS-related conflicts get resolved by a driver-side patch rather than requiring you to weaken your own system. Only disable VBS or Memory Integrity if an official support article from the specific game studio names that exact feature as an identified incompatibility, and re-enable it afterward once the conflict is resolved upstream. You can check the current state through Windows Security, under Device security, then Core isolation details.
Step 10: Read the Windows Code Integrity Log When Something Fails
When a kernel driver fails to load because of a signature, policy, or compatibility problem, Windows records the reason in a dedicated event log rather than just a generic error dialog. Open Event Viewer and navigate to Applications and Services Logs, then Microsoft, then Windows, then CodeIntegrity, then Operational. You can reach the same data faster from PowerShell.
Get-WinEvent -LogName "Microsoft-Windows-CodeIntegrity/Operational" -MaxEvents 20 |
Select-Object TimeCreated, Id, Message |
Format-ListLook for events logged around the time you last tried to launch the game. A rejected driver load typically names the specific file and gives a signature or policy-related reason code. That detail is far more useful when searching the game’s official support forum than a vague “anti-cheat not working” description, and it tells you immediately whether you’re dealing with a signature problem, a policy block, or something unrelated to Code Integrity entirely.
Step 11: Perform a Clean Reinstall When Nothing Else Works
If the driver is still misbehaving after updates, exclusions, and log review, a clean reinstall resolves most remaining cases. Follow this exact order to avoid leaving orphaned drivers behind.
- Fully exit the game, the launcher, and any anti-cheat tray process.
- Uninstall the game through Installed apps, or use the launcher’s own repair/uninstall option if one is offered.
- Restart Windows completely, not just a sign-out.
- Run
pnputil /enum-driversin an elevated prompt and confirm no orphaned anti-cheat driver package remains listed. - Reinstall the game through the official launcher and let it reach the current version in full before launching.
- Launch once, allow the anti-cheat driver to reinstall itself automatically, and restart again if prompted.
Step 12: Harden Your Account, Not Just Your System
Kernel-level anti-cheat defends your local game session against cheat software, but it does nothing to stop someone from simply logging into your account from a stolen password, which is a separate and arguably larger risk heading into late 2026. A third-party security provider connected to Discord, a company called Double Counter, disclosed a breach on October 7, 2026 that reportedly exposed around 1 million email addresses and partially copied IDs and usernames tied to as many as 28 million Discord accounts, along with IP address and user-agent data for roughly 27 million and 25 million accounts respectively. None of that is related to anti-cheat software directly, but it’s a reminder that gaming account security has two separate layers: the kernel driver stopping cheats, and the account-level protections stopping takeover. If you haven’t set up app-based two-factor authentication on your gaming accounts yet, the Steam Guard and Discord 2FA setup guide walks through enabling it step by step, including backup codes and session review, both of which matter independently of whatever anti-cheat system a given game studio chooses.
Step 13: Build an Ongoing Maintenance Habit
Anti-cheat vendors push driver updates on their own schedule, often tied to Windows patch cycles rather than game patch cycles, which means a driver that worked fine last month can break after a routine Windows update you didn’t even connect to gaming. Set a simple monthly habit: run Windows Update fully, check your GPU driver version, and if you notice any anti-cheat related error on launch, run through Steps 7 and 10 above before assuming something is seriously wrong. Most recurring issues trace back to a Windows update that shipped a new Code Integrity policy or a chipset driver that silently reverted during a feature update.
Common Installation Errors and Fixes
| Symptom | Likely cause | Fix |
|---|---|---|
| Game reports an unsupported Windows version | Build older than 10.0.19041 | Run Windows Update, confirm with winver |
| Anti-cheat service won’t start | Interrupted install, pending restart, or corrupted package | Restart, repair the game install, relaunch through the official client |
| Game crashes right after the anti-cheat migration | Failed driver registration or incompatible background software | Close overlay/injection tools, update Windows and GPU drivers, repair the game |
| Secure Boot warning appears unexpectedly | Confusion with a different EA title’s requirement | Confirm Apex specifically doesn’t require Secure Boot via EA’s own announcement |
| Cannot enable Secure Boot for a title that needs it | Legacy BIOS/CSM mode, MBR disk, or disabled TPM | Switch firmware to UEFI, convert to GPT, enable TPM 2.0, then enable Secure Boot |
| Driver blocked with a signature-related message | Code Integrity policy rejection | Check the CodeIntegrity Operational log, update Windows, reinstall via official launcher |
| Antivirus quarantines the anti-cheat driver | Unfamiliar new binary triggers a heuristic flag | Restore from quarantine only if the path matches the official game directory, add a narrow exclusion |
| Driver conflict after enabling Memory Integrity | VBS/HVCI incompatibility with an outdated driver version | Update anti-cheat and Windows first, disable VBS only if officially confirmed necessary |
Troubleshooting Checklist
Work through these in order whenever anti-cheat software misbehaves, rather than jumping straight to a reinstall.
- Confirm your Windows build with
winveragainst the 10.0.19041 floor. - Check whether the issue started right after a Windows Update by reviewing your update history.
- Run
sc query type= serviceandsc query type= driverto see the exact service state. - Pull the last 20 CodeIntegrity Operational events for a concrete rejection reason.
- Temporarily close overlay, capture, macro, and virtualization software, then retry.
- Check your antivirus quarantine log for anything removed around the install time.
- Verify Memory Integrity’s current state under Windows Security before assuming it’s the cause.
- Repair the game install through the official launcher before uninstalling anything manually.
- If all else fails, perform the full clean reinstall sequence from Step 11.
5 Pitfalls to Avoid When Troubleshooting Kernel Anti-Cheat
These mistakes come up constantly in player support threads, and each one tends to create a worse problem than the one it was meant to fix.
- Permanently disabling driver signature enforcement. This removes a core Windows security boundary and should never be a standing fix for a gaming problem. If a driver genuinely needs this, something else is wrong.
- Manually deleting a .sys file you found in a search result. Anti-cheat driver filenames vary by game and version, and deleting a registered driver file outside the proper uninstall flow can leave Windows in an inconsistent state.
- Adding a whole-drive antivirus exclusion “just to be safe.” A narrow, folder-specific exclusion solves the same problem without opening your entire system to anything else that lands in that excluded space.
- Disabling VBS or Memory Integrity before trying any updates. Most conflicts resolve with a driver or Windows patch. Weakening platform security should be the last resort, not the first move.
- Assuming every EA title shares Apex’s exact requirements. Secure Boot, TPM, and driver behavior can differ game by game even within the same publisher’s catalog.
Security and Privacy Considerations of Kernel-Level Anti-Cheat
Security researchers have raised consistent concerns about kernel-level anti-cheat as a category, not specific to any single vendor. A kernel driver, by definition, can access far more of your system than an ordinary application, which means a vulnerability in the driver itself becomes a potential local privilege-escalation path rather than just a software bug. That risk exists whether the driver belongs to Riot Vanguard, BattlEye, FACEIT Anti-Cheat, Easy Anti-Cheat, Denuvo Anti-Cheat, or EA Javelin.
Boot-start drivers add a persistence question: some kernel anti-cheat tools remain loaded even after you close the game, which raises fair questions about what exactly is running and when. EA has described Javelin’s monitoring scope at a high level as covering the game process, related processes, memory activity, and loaded modules, which is a typical description for this category of tool, though EA has not published a complete, itemized breakdown of every data point collected. If that level of detail matters to you, check the specific game’s privacy policy and anti-cheat FAQ directly rather than relying on general industry descriptions, since exact telemetry and retention practices vary by vendor and can change between updates.
False positives are the other recurring concern. Aggressive kernel-level detection can flag legitimate software that happens to behave similarly to a cheat, including some debuggers, accessibility tools, overlay utilities, and virtualization software. That’s a direct reason to close non-essential background software before launching a freshly updated anti-cheat driver, covered in Step 5 above, rather than waiting to find out the hard way during a match.
EA Javelin vs Other Kernel-Level Anti-Cheat Systems in 2026
Javelin is EA’s answer to a field that already includes several established kernel-level systems. Each vendor makes different tradeoffs between detection aggressiveness, game coverage, and how visibly the driver behaves on a player’s system.
| System | Primary vendor | Known for | Example games |
|---|---|---|---|
| EA Javelin Anti-Cheat | Electronic Arts | In-house kernel driver now rolling out across EA’s catalog, with 21 games protected per EA’s September 2026 report | Apex Legends, other EA titles |
| Riot Vanguard | Riot Games | Boot-start kernel driver (commonly identified as vgk.sys) that persists after game exit | Valorant, League of Legends |
| BattlEye | BattlEye Innovations | Long-running third-party anti-cheat licensed across many unrelated studios | PUBG, Rainbow Six Siege, Fortnite (console) |
| Easy Anti-Cheat | Epic Games | Widely licensed user-mode and kernel-mode anti-cheat, now being phased out of some EA titles in favor of Javelin | Fortnite, Apex Legends (pre-September 2026) |
| Denuvo Anti-Cheat | Irdeto | Kernel-level tool from the same company behind Denuvo DRM | Selected titles using Denuvo’s broader protection suite |
| FACEIT Anti-Cheat | FACEIT | Privileged component used specifically to enforce competitive-integrity rules on FACEIT’s platform | FACEIT-hosted CS2 and other competitive matches |
If you want a deeper side-by-side on detection behavior, compatibility quirks, and game coverage across these systems, the Vanguard vs EAC vs BattlEye vs Ricochet vs VAC comparison and the EAC vs BattlEye vs Vanguard breakdown both go further into vendor-by-vendor specifics than this setup-focused guide covers. Detection trends across the industry are also tracked in the 2026 anti-cheat detection data roundup, useful context for why studios keep tightening kernel-level enforcement rather than relying on user-mode checks alone.
Advanced Tips: Hardening Your System Without Breaking Anti-Cheat
You don’t have to choose between a secure system and a working anti-cheat driver. A few habits keep both intact at the same time. Keep Windows Update, GPU drivers, and chipset firmware on automatic or near-automatic schedules, since most anti-cheat compatibility work targets current builds, not older ones you’re holding back intentionally. Use a dedicated local administrator account only for installs and troubleshooting, and run your daily gaming session from a standard account where that’s practical, since kernel drivers don’t need elevated session privileges to run once installed. Review Windows’ list of registered drivers with pnputil /enum-drivers every few months and remove packages tied to games you’ve fully uninstalled, using the proper package identity rather than deleting files directly.
If you dual-boot or run a secondary gaming PC, keep Secure Boot and TPM enabled by default even on the machine where Apex doesn’t currently require it. Other titles you install later may need it, and having it already configured avoids a second firmware trip. Finally, treat any tool that claims to “bypass” or “disable” a specific anti-cheat driver as a direct security and account risk, not just a terms-of-service violation, since that category of tool routinely doubles as malware delivery in practice.
Complete Working Example: A Pre-Launch Health Check Script
Rather than running each diagnostic command separately every time something feels off, save this as a PowerShell script and run it before reporting an issue to support. It checks your Windows build, Secure Boot and TPM state, Memory Integrity status, and pulls the five most recent CodeIntegrity events in one pass.
#Requires -RunAsAdministrator
# anti-cheat-healthcheck.ps1
Write-Host "=== Windows Build ===" -ForegroundColor Cyan
Get-ComputerInfo | Select-Object WindowsVersion, OsBuildNumber
Write-Host "`n=== Secure Boot ===" -ForegroundColor Cyan
try {
Confirm-SecureBootUEFI
} catch {
Write-Host "Secure Boot check failed - firmware may be in Legacy/CSM mode" -ForegroundColor Yellow
}
Write-Host "`n=== TPM Status ===" -ForegroundColor Cyan
Get-Tpm | Select-Object TpmPresent, TpmReady, TpmEnabled
Write-Host "`n=== Memory Integrity (HVCI) ===" -ForegroundColor Cyan
Get-CimInstance -Namespace root/Microsoft/Windows/DeviceGuard `
-ClassName Win32_DeviceGuard |
Select-Object SecurityServicesConfigured, SecurityServicesRunning
Write-Host "`n=== Recent Code Integrity Events ===" -ForegroundColor Cyan
Get-WinEvent -LogName "Microsoft-Windows-CodeIntegrity/Operational" -MaxEvents 5 |
Select-Object TimeCreated, Id, LevelDisplayName, Message |
Format-List
Write-Host "`n=== Anti-Cheat Related Services ===" -ForegroundColor Cyan
Get-Service | Where-Object { $_.DisplayName -match "AntiCheat|EasyAntiCheat|BattlEye|Vanguard" } |
Select-Object Name, DisplayName, StatusSave this as anti-cheat-healthcheck.ps1, right-click it, choose “Run with PowerShell,” and approve the administrator prompt. Copy the full output into any support ticket you open. Support teams can act on a concrete log excerpt far faster than a description like “it just doesn’t work,” and running this script before you reach out typically cuts several rounds of back-and-forth out of the process entirely.
Uninstalling Anti-Cheat Drivers Safely
Sometimes the right move is a full, clean removal, whether you’re retiring an old game or isolating a conflict for testing. Use the official uninstaller first whenever one exists. For a manual cleanup pass, follow this sequence rather than deleting files directly.
# 1. List all currently installed third-party driver packages
pnputil /enum-drivers
# 2. Identify the exact package name for the driver you want removed
# (output includes a "Published Name" like oem12.inf)
# 3. Remove only that specific, confirmed package
pnputil /delete-driver oem12.inf /uninstall
# 4. Confirm it no longer appears in the driver list
pnputil /enum-driversReplace oem12.inf only with the exact package identity pnputil reports for the driver in question. Never guess at a package number, since removing the wrong one can disable an unrelated piece of hardware. Restart Windows after the removal completes, then check Installed apps for any leftover vendor folder the uninstaller didn’t clear, and remove it manually only after confirming no other installed game still depends on it.
What to Do If You’re Flagged Incorrectly
Even with EA citing better than 99% detection accuracy for Javelin, a system monitoring 10.8 billion sessions and 26.7 million flagged attempts will produce some false positives purely on volume. If you believe you were sanctioned incorrectly, don’t immediately uninstall and reinstall the game, since that can complicate the specific diagnostic data support needs. Instead, open a support case through the official EA Help channel for the specific game, include your account details, approximate time of the sanction, and the health-check output from the script above if you have it. Avoid posting account-identifying details on public forums while a case is open, since that information can itself become a target.
Frequently Asked Questions
Does Apex Legends require Secure Boot for EA Javelin Anti-Cheat?
No. EA’s own announcement states Secure Boot is not required for Apex Legends at this time, even though Javelin is a kernel-level anti-cheat tool. Other EA titles may carry different requirements, so check each game’s specific support page.
What Windows version do I need for EA Javelin?
EA’s support documentation lists Windows 10 build 10.0.19041 (version 20H1) or later as the minimum. You can confirm your current build by running winver.
Is kernel-level anti-cheat safe to run?
Kernel drivers from established anti-cheat vendors go through Windows’ signature verification before loading, which confirms authenticity but not the absence of bugs. The category carries a theoretically larger attack surface than ordinary software because of its privilege level, which is why keeping Windows and the anti-cheat driver itself fully updated matters more than it does for typical applications.
Can I uninstall a kernel anti-cheat driver manually?
Use the official game or launcher uninstaller first. If you need a manual cleanup, identify the exact driver package with pnputil /enum-drivers and remove only that specific package with pnputil /delete-driver, rather than deleting .sys files directly.
Why did my game crash right after the anti-cheat migration?
The most common causes are an interrupted driver registration, an outdated Windows build, outdated GPU or chipset drivers, or a conflict with background software that hooks into running processes. Update everything first, close overlay and injection-style tools, then repair the game through its official launcher.
Should I disable Virtualization-Based Security to fix an anti-cheat error?
Not as a first step. Most VBS-related conflicts resolve through a Windows or anti-cheat driver update rather than disabling platform security. Only disable VBS or Memory Integrity if an official support article from the specific game studio names that exact feature as the confirmed cause, and re-enable it once resolved.
How many games does EA Javelin Anti-Cheat currently protect?
EA’s September 2026 progress report cites 21 games protected, with 10.8 billion PC gaming sessions monitored and 26.7 million cheat attempts flagged over the preceding year. These are EA’s own vendor-reported figures.
Does fixing anti-cheat issues also protect my account from being hacked?
No. Kernel-level anti-cheat protects your local game session from cheat software. It has no bearing on account takeover from leaked or reused passwords. Those require separate protections like app-based two-factor authentication, covered in the Steam Guard and Discord 2FA setup guide linked earlier in this article.
Will other EA games eventually move to Javelin as well?
EA’s own reporting already counts 21 games under Javelin’s protection as of its September 2026 progress update, and Apex Legends’ September 29, 2026 migration shows the company is still actively moving additional titles onto the system. Treat any specific future migration date for a title not yet listed as unconfirmed until EA announces it directly for that game.
