DayZ "BattlEye: Client Not Responding" Kick? How to Fix It

"BattlEye: Client not responding" in DayZ means the server's BattlEye stopped hearing from the BattlEye service on your PC for long enough that it kicked you. It is not a ban. For one player, the cause is nearly always on that PC: BattlEye not running or blocked by a firewall, the game started without BattlEye, or a connection that drops packets. When every player on a server gets it at once, the server is freezing long enough for everyone to time out, and the fix is on the server side.

What the kick looks like

Players see one of these on the disconnect screen:

You were kicked from the game. (BattlEye: Client not responding)

BattlEye: Client not responding

On the server, the RCon log or the BattlEye log shows the player being kicked with the same reason. Similar BattlEye messages have different causes:

Signature errors are a separate topic, covered in the "Signature check timed out" fix.

Player fix 1: Start DayZ with BattlEye

DayZ must start through Steam or the DayZ Launcher, which runs DayZ_BE.exe and starts BattlEye before the game. Starting DayZ_x64.exe directly, or from an old shortcut, launches the game without BattlEye. You can connect, but the server kicks you within a minute with "Client not responding".

Check the launcher's Parameters tab too. Remove any custom executable paths or launch options copied from old guides.

Player fix 2: Reinstall the BattlEye service

1. Close DayZ and the launcher.
2. In Steam, right click DayZ > Manage > Browse local files.
3. Open the BattlEye folder and run Install_BattlEye.bat as administrator. It reinstalls the BattlEye service.
4. Restart the PC and join again.

If the folder or file is missing, verify the game files in Steam (Properties > Installed Files > Verify integrity of game files), then repeat.

Player fix 3: Firewall, antivirus and VPN

BattlEye talks to the server through its own service. If it is blocked, the game connection works but BattlEye goes silent.

• In Windows Defender Firewall or your security suite, allow DayZ_x64.exe, DayZ_BE.exe and the BattlEye service (BEService_x64.exe, installed in C:\Program Files (x86)\Common Files\BattlEye).
• Turn off VPNs and "gaming accelerators". They often drop the BattlEye traffic while keeping the game traffic alive.
• If your antivirus has a gaming or network inspection feature, add DayZ as an exception or test with it off.

Player fix 4: A connection that drops packets

Wi-Fi with interference, a busy upload (cloud backups, streaming) or a congested ISP route can drop the small packets BattlEye sends. Signs: the kick happens at random times rather than right after joining, and other online games also stutter.

• Use a wired connection for a test.
• Pause uploads and streaming.
• Join a different server in a similar region. If the kicks follow you everywhere, it is your connection or PC. If they happen on one server only, tell its owner.

When everyone gets kicked at once

If the whole server gets "Client not responding" at the same moment, the players are fine. The server stopped processing long enough for BattlEye to give up on every client. Common causes:

1. Server freezes. Heavy mods, a huge persistence file or a busy economy can freeze the server for several seconds, especially around restarts. Check the server's RPT log in the profiles folder for long gaps or errors at the time of the kick. The -freezecheck launch option helps you find the freeze in the logs.
2. Out of memory. A server short on RAM swaps or stalls. Modded maps and big mod lists need much more than vanilla, as shown in DayZ server requirements.
3. Mods with errors. A mod that throws script errors every frame slows the whole server. Look at the RPT log for repeated errors from one mod, and update or remove it.
4. Restarting while players are on. Players connected during a restart can be kicked with this reason before the server even says it is going down. Give players a warning before scheduled restarts.

Server side BattlEye setup

On a self hosted server, check that BattlEye is set up properly:

• BattlEye = 1; in serverDZ.cfg (BattlEye on, which is required for public servers).
• A battleye folder in the server profile with BEServer_x64.dll and beserver_x64.cfg.
• The server has write access to that folder. BattlEye renames the cfg to an _active_ copy while it runs and needs to write its logs there.
• Old beserver_x64_active_*.cfg files from crashed runs can be deleted with the server stopped.

The DayZ admin tools guide covers the beserver_x64.cfg file and RCon in more detail.

Running a server without the hassle

On a GamezServers DayZ server, BattlEye is set up for you, the server starts with -dologs -adminlog -freezecheck so freezes show up in the logs, the RCon password is generated in the panel for tools like BattleMetrics, and the file manager gives you the RPT and BattlEye logs. Mods download and update from Workshop IDs on every start, which keeps the server and players in step. If you want a server for your group, see DayZ server hosting.

FAQ

Is "BattlEye: Client not responding" a ban?

No. It is a kick because BattlEye on your PC stopped answering. Fix BattlEye or your connection and you can rejoin right away.

Why do I only get this on one DayZ server?

That server may be freezing, or the route to it drops packets. If other servers work, tell the owner and include the time of the kick so they can check their logs.

Does verifying game files fix BattlEye kicks?

It fixes a missing or damaged BattlEye install. Run Install_BattlEye.bat afterwards to reinstall the service.

Can a server owner turn BattlEye off?

BattlEye = 0; turns it off, but public servers should keep it on. Without it, there is no anti-cheat on the server.