Fortnite loads both anti-cheats at once: Easy Anti-Cheat and BattlEye start through the Epic launcher, and there is no launch parameter that lets you pick one, the way some other games allow. For anyone running a Fortnite cheat in 2026 this does not mean double the difficulty, it means a different update cycle: the software has to be rebuilt for changes in either system.
We keep fourteen builds for this game and watch the rebuild statistics after every patch. Below is what actually starts alongside the client, where the server side of the checks lives, how tournament mode differs from normal play in hardware requirements, and how all of that affects your choice. Current options with prices and live status sit on the Fortnite cheats → page, all of it checked on patch v42.00.
Why Fortnite has two anti-cheats
The history here runs longer than people assume. At launch Fortnite ran on BattlEye. In 2019 Epic moved the game to Easy Anti-Cheat, and after buying the company behind EAC the developer could shape the system to its own needs. In 2023 EAC went to kernel level and gained access to processes and memory at the same privilege level as the operating system.
BattlEye was never removed. Epic still keeps a separate support page for BattlEye problems in Fortnite, and the service installs alongside the game. The practical point is that the two systems watch different things and back each other up: one catches interference with client memory, the other keeps its own integrity checks and its own list of known drivers.
What starts when the game launches
When Fortnite starts, the EAC service, a kernel-level driver and a client component inside the game process all come up. The BattlEye service runs in parallel. Launch errors usually belong to one of them, and the error text tells you which one is complaining: EAC codes look nothing like BattlEye messages, and Epic keeps separate help pages for each.
That gives a practical rule for anyone whose game will not start after installing software. Look first at who threw the error, because the fix differs. Most of the time the answer is launch order rather than a game reinstall: loader first, client second, not the other way round.
The second most common case has nothing to do with cheat software at all. The anti-cheat clashes with something already on the system: old virtual drive drivers, overclocking utilities with kernel access, capture programs that inject into the process. We regularly get tickets where the game refused to launch because of a third-party recording overlay, while the person was certain the loader was at fault. The check is cheap: close everything unnecessary and start a clean client with no software attached. If the error stays, the system is the problem, not the build.
The server side and ban waves
The most underrated part of the system does not sit on your computer. EAC is built as a hybrid: a kernel driver, a user-mode service and a server backend that correlates reports across the entire player base. That is why Fortnite bans arrive in waves rather than during the match.
The mechanism is simple. The server accumulates signals: reports from live players, behavioural metrics, matches on hardware and accounts. Once enough data piles up on a specific cheat build, a batch of bans goes out at once, sometimes hundreds of thousands of accounts over a weekend. For anyone on a public free build that means the moment of the ban has nothing to do with the moment of detection, and weeks can pass between them.
Private projects work on different logic. The smaller the client base and the faster the rebuild after a patch, the less material collects on the server side. That is why the catalogue holds projects with closed access rather than open distribution. Through August, three of fourteen listings went to updating status and came back after a rebuild.
Replays and manual review
On top of the automation, Epic looks at recordings by eye. Replays and reports get reviewed in ranked and especially in tournament modes, and at the top divisions that stops being rare. No software protects you from this, because what gets examined is player behaviour on a recording, not process memory.
This is exactly the part newcomers ignore. Settings along the lines of maximum capture radius and instant snap survive any automated check and do not survive one attentive viewer. Which is the whole point of the features decent builds carry: smoothing, a delay when switching targets, the aim point randomization in Vengeance, a narrow FOV instead of a wide one.
How this differs from other games in the catalogue
Comparison with the neighbours puts the scale in perspective. Rust runs Easy Anti-Cheat only, DayZ and Escape from Tarkov live on BattlEye, Valorant uses its own Vanguard that loads a driver at system boot. One protection system each, so a software developer tracks a single source of change.
Fortnite has two, and their updates are not synchronised. A game patch can leave EAC alone while arriving with a BattlEye update, or the reverse. By our own numbers over the summer, Fortnite produced the most ragged rebuild schedule of any game in the catalogue: in some weeks builds went into updating twice.
For a buyer that translates into a simple rule. If you are taking a monthly subscription for Fortnite, look past the price at how the developer behaves during a freeze. In our catalogue the downtime days come back and the build stays off sale until it has cleared the patch. Projects that keep selling access mid-update are not on the shelf.
Tournament mode requires different hardware
Here Fortnite has a fork that most kernel-protected games do not. Secure Boot, TPM 2.0 and IOMMU are mandatory in Fortnite only for tournament modes, in force since 19 February. Regular matches and ranked play work without any of those requirements.
Compare that with the neighbours: Battlefield 6 wants Secure Boot and TPM to enter the game at all, and so does Valorant with Vanguard. Fortnite placed the barrier surgically, only around the competitive circuit. Two things follow. First, you can play normal Battle Royale and Zero Build on a machine without Secure Boot enabled, and that is a legitimate mode rather than a workaround. Second, the tournament circuit is protected noticeably harder than ranked, and IOMMU is there for a reason: it closes off a class of attacks through direct hardware access to memory.
That is why we split the advice: what works fine in normal matches should not be brought into tournaments at all. The breakdown of tournament rules with account level and two-factor authentication is a separate blog article.
One more question comes up in nearly every ticket: what the anti-cheat actually collects about your machine. The kernel driver sees running processes, loaded drivers and access to the game client's memory, while hardware identifiers get used to link accounts together. That is why a fresh account on the same computer does not help after a ban, and why spoofers exist as their own product category. On a clean machine a spoofer is optional, but once a hardware ban lands there is no point logging in without one.
What this changes when picking software
A double anti-cheat shifts the priority from feature lists to how fast the developer reacts. A build with a gorgeous menu that updates once a fortnight is useless in Fortnite, because patches land more often than that.
- Read the status, not the description: every listing shows whether that build has cleared the latest patch. At the end of August three of fourteen listings were on updating status.
- Take daily access as a trial: Covcheg from 239 rubles and Mason from 299 rubles let you see how the software behaves on your specific system before you buy a month.
- Do not chase the biggest settings menu: what works against manual replay review is smoothing and a narrow FOV, not the number of checkboxes. Mason has a panic key for the moment you need everything off fast.
- Check compatibility with your Windows build: the whole catalogue targets Windows 10 and 11 with the Epic launcher, not third-party client builds.
Where to go from here
Choosing for a specific scenario is easier on the page itself: on cheats for Fortnite → every listing shows price, undetected status and its feature set, and the list gets corrected after each Fortnite patch. You can also see there which projects price in rubles and which in dollars.
If you want advice for a specific system, ask in our community: Telegram (200+ members) and Discord (637+ members). Launch errors tied to EAC and BattlEye usually get sorted there in a few messages.
Common questions about Fortnite anti-cheats
Can you choose which anti-cheat Fortnite launches?
No. Both services install with the game through the Epic launcher and start automatically. There is no launch parameter that switches Fortnite to a single anti-cheat, unlike some other games where that choice existed historically.
Do you need Secure Boot and TPM for regular Fortnite play?
Not for regular matches or ranked. Secure Boot, TPM 2.0 and IOMMU are mandatory only in tournament modes, a requirement in force since 19 February. That separates Fortnite from Battlefield 6 and Valorant, where similar requirements cover the whole game.
Why does a ban arrive weeks later instead of immediately?
The EAC server side accumulates signals across the whole player base and fires bans in waves. Time passes between detecting a build and sending out the bans, and that time is spent gathering material. Public free builds land in those waves first, because thousands of people download them at once.
Does a private cheat protect against manual replay review?
No, and no honest seller will tell you otherwise. A human watches the replay and judges behaviour, not process memory. What helps are settings that keep the game looking ordinary: smoothing, a narrow FOV, no instant snapping. You can pick a build with those settings on the private Fortnite cheats → page.
How long does a rebuild after a Fortnite patch take?
Usually a day to several, and the exact time depends on what changed in the client and in the protection systems themselves. During the work the build goes to updating status and comes off sale, while active subscriptions get their downtime days back. Through August three of the fourteen catalogue listings went through that cycle.
What do I do if the game will not start after installing software?
Look at whose error is on screen, since EAC and BattlEye use different codes and have different Epic help pages. In most cases it comes down to launch order: loader first, client second. If the error repeats, the build's developer usually has a specific instruction for their own protection setup.
