BattlEye is BattlEye Innovations's anti-cheat system for 13 TraceX-listed games. This guide explains its hardware profile, supported games, and current TraceX compatibility.
BattlEye Innovations · 13 supported games · All anti-cheats
BattlEye is an independent anti-cheat used by publishers behind PUBG, DayZ, Rainbow Six Siege, Destiny 2, Arma 3, and other PC games. Its Windows stack includes the BattlEye service and the `BEDaisy.sys` kernel driver, giving it a different trust boundary from a user-mode scanner attached only to the game process.
BattlEye is also associated with delayed enforcement. A session can be recorded, reviewed, and actioned later as part of a ban wave, so the absence of an immediate kick is not proof that a machine profile was accepted. A global BattlEye ban and a publisher or community-server ban are different records, and their scope should not be collapsed into one claim.
The same PC values can reappear in every BattlEye-protected title, creating cross-game exposure without an automatic cross-publisher ban. TraceX Spoofer rewrites the supported identifier set once; after the one-time setup, TraceX can be deleted instead of running beside each game.
BattlEye does not publish a complete hardware-field schema for every protected game. Its kernel driver can compare WMI queries to `Win32_BaseBoard`, `Win32_DiskDrive`, or `Win32_PhysicalMemory` with lower-level data such as the SMBIOS Type 2 baseboard serial and `IOCTL_STORAGE_QUERY_PROPERTY` controller descriptors. A WMI-only change is weak if `BEDaisy.sys` can observe a different answer through the storage or firmware stack.
BattlEye can also build context from `MachineGuid` at `HKLM\SOFTWARE\Microsoft\Cryptography`, Windows installation values, volume identifiers, and MAC enumeration. Physical and virtual adapters are distinguishable by their interface and driver metadata. That makes a newly randomized MAC a poor stand-alone identity change when the board, disks, and OS relationship stay stable.
The TPM 2.0 endorsement key is reachable through the TBS API, and Secure Boot state can describe whether Windows followed a verified boot path. BattlEye does not publish a universal list confirming key collection across every protected game, so those should be described as available integrity or fingerprint surfaces rather than mandatory fields in every BattlEye profile.
A composite or fuzzy match lets BattlEye tolerate an SSD replacement or Windows reinstall while retaining confidence in the rest of the machine. The same values can be collected again in PUBG, DayZ, and Siege, but publishers still control title-level enforcement. Delayed waves further separate the time of collection from the time a player sees the ban.
TraceX lists 13 BattlEye-protected games. Open a game page below for its current compatibility, ban details, and setup guidance.
TraceX rewrites supported identifiers across the WMI, SMBIOS, storage, registry, and network surfaces as a consistent set. The goal is to avoid a profile where `Win32_DiskDrive` changes but `IOCTL_STORAGE_QUERY_PROPERTY` still returns the old disk identity, or where a new `MachineGuid` sits beside unchanged firmware values.
This is a permanent rewrite workflow, not a process injected into BattlEye. Run TraceX once after the one-time setup and delete the tool. No background service is required for each PUBG, DayZ, or Siege session, and TraceX does not modify BattlEye's driver or explain how to evade its runtime checks.
A delayed ban wave means compatibility cannot be inferred from one short session. Use the latest published status, including Unverified, and do not treat a clean launch as a test result for future BattlEye or publisher builds.
BattlEye can separate detection from enforcement and issue actions in delayed waves. That reduces the feedback available to cheat developers and means a normal-looking logout does not prove the session was cleared. The timestamped status page is the relevant TraceX compatibility signal; a single launch is not a reliable ban-wave test.
BattlEye does not publish a rule that a PUBG ban automatically applies to DayZ or Siege. The same board, disk, Windows, and network values can be collected across BattlEye titles, so the machine can be recognized again. Global BattlEye actions, publisher bans, and community-server bans have different scopes even when they concern the same computer.
`BEDaisy.sys` operates in the Windows kernel, where it can compare user-mode reports with lower-level firmware and device data. That matters for `IOCTL_STORAGE_QUERY_PROPERTY`, SMBIOS tables, and driver metadata. Rewriting one WMI result without changing its underlying source can leave an inconsistent machine profile.
A reinstall changes software-layer values such as `MachineGuid`, but SMBIOS Type 2 board data and physical-disk serials normally survive. BattlEye can evaluate those durable values together rather than trusting the new Windows identity by itself. TraceX rewrites its supported hardware and OS identifiers as one set.
TraceX publishes BattlEye compatibility on the detection-status page with its current status and as-of date, or shows a missing result as Unverified. BattlEye's kernel driver, in-session checks, game-specific builds, and delayed waves mean a published result does not predict future enforcement.
No. Complete the one-time setup, run TraceX once to rewrite the supported identifiers, and delete the tool afterward. The changes are designed to persist without a per-session mask or resident TraceX process. Check BattlEye's latest published status, which may be Unverified, because its driver and publisher integrations evolve.
The linked TraceX guides explain how BattlEye builds a hardware profile, what enforcement looks like afterwards, and which supported identifiers TraceX rewrites.
Kernel level anti cheat explained: what Ring 0 access really gives Vanguard, EAC and BattlEye, when their drivers load, and what it means after a ban
HWID ban duration compared across 24 games: which bans expire, which are permanent, and why your ban notice says the year 2226 when nothing is counting down
HWID ban vs IP ban vs account ban: what each one actually blocks, how to tell which you have, and why a VPN fixes exactly one of the three ban types
A HWID ban appeal is worth filing only for a documented false positive, an inherited ban on a used PC, or another person’s activity on a shared machine.
TraceX links Easy Anti-Cheat, Vanguard, RICOCHET as related anti-cheat guides for comparison.
The status below shows the current published BattlEye compatibility result. An unverified result remains Unverified.
As of (US Eastern)