BE Problems

[Lido 54]

So, I've been playing dayz for a while, yet somehow was unaware it had an official site all this time...

Anyway, for the past 4 days, my Arma II has been perpetually stuck on BE client version 1.182, as its the version that comes with the latest beta patch for OA.

Join a server, and it requires version 1.187. OK, battleye will update as I play.

NOPE

"BattlEye Client : Server requiring client version 1.187, Updating..."

"BattlEye Client Successfully completed, restarting."

"BattlEye Client Initialized (v1.182)"

Then I get kicked.

So, being at least slightly aware BattlEye tends to be a butt nugget, I went over to their main site, downloaded the client and server versions, and put them in:

.../ArmAOA/Expansions/BattlEye

.../AppData/Local/Arma2OA

Join a server, and instead of even pretending to try to update, I get "BattlEye Initialization Fail"

I tried moving everything around, updating Arma II, uninstalling the BE patch with the uninstall exec. in the battleye folder, re-downloading the latest beta patch, re-installing both Arma II and Arma II OA, etc.

Nothing worked.

So here I am. Any suggestions?

Edit : 1/19/13. Broke again. It went from 1.187 back down to 1.182. Avira has it in exceptions and it just stopped, and I'm getting initialization fail again.

Edit 2 : 1/19/13. Fixed it again. Avira's exception list doesn't really give the foldres an exception. So I had to disable it. Yep.

Edited January 19, 2013 by Lido

[tsandrey 379]

Do you use Avira? If you do, add all BE folders as exceptions

[Rage VG 4033]

This is normally caused by an antivirus program. Disable it and try again. If it works, then add them as exceptions.

[Lido 54]

I want you to know I love you guys so much, this whole time I was adding exceptions to windows security, turns out my brother installed avira on a whim. You two, I give you my beans.

[Lido 54]

Oh. Idk how to close thread, first sentence was I'm an idiot, so theres that...

[Rage VG 4033]

Just let the thread die on its own. ;D

If you need any other help, don't hesitate to shoot me a message. I'm here to help.

[boneboys 7988]

Fixed...

[OrLoK 16188]

I fixed your title for you to make it easier for folk to see you have an issue not just a pointless rant.

[Lido 54]

Er... so it broke again. For some reason after closing dayz and opening it again, it un-updated it self from 1.187 to 1.182. Requesting more help...

[AmberHelios 2071]

start the game as admin and it will install it again and should stay this time

[Lido 54]

I always run as admin by deafult. It didn't work, manual install into appdata and game install location, now I am getting the Initialization Failed again.

Sadness. :c

[AmberHelios 2071]

delete the one out of your appdata folder and make sure avira ignores the folder in realtime protection

[Lido 54]

Got it. Turns out aviras "Exception" list doesn't really change anything or make it a bloody exception, as it kept freaking blocking it the moment I restarted Dayz.

So to anyone with avira problems on dayz : I basically turned off my avira for the moments when I play dayz, but I keep windows security on. I mean, leave SOME kinda wall up, but apparently avira be hating on my beauty.

So yea, Avira was just being an ass twice in two days.

[AmberHelios 2071]

Got it. Turns out aviras "Exception" list doesn't really change anything or make it a bloody exception, as it kept freaking blocking it the moment I restarted Dayz.

So to anyone with avira problems on dayz : I basically turned off my avira for the moments when I play dayz, but I keep windows security on. I mean, leave SOME kinda wall up, but apparently avira be hating on my beauty.

So yea, Avira was just being an ass twice in two days.

or get one of the other av on the market that dont see it as a virus even after an update

[Dayzo 182]

The way Windows 7 security works, you do not make an exception for the BEClient.dll in your Arma installation.

Windows 7 makes a copy, and that is the dll you have to make the exception for:

C:\Users\[your windows name]\AppData\Local\ArmA 2 OA\BattlEye\BEClient.dll

You can double check which file is causing the problem: Straight after getting kicked from the game, open Avira and click 'real time protection' in the left menu. At the top it will say 'last file found' and give you a path that you can copy/paste into the exception dialogue.

Also ensure you are adding the exception to the correct section in Avira.

It is the Real Time Protection which is giving this false positive, so it is that section which needs the path added to it:

configuration -> expert mode -> Real-Time Protection -> scan -> exceptions -> 'file objects to be excluded...'

Note that this false positive has been reported to Avira. If I was the only one, then they've only known about it for 24 hours.

I've no idea how long it will take them to look at it, since they must get dozens of false positive reports per day.

Edited January 19, 2013 by Anti

[PsyGriff 1]

I have the same problem.

I just bought the game from Steam, like yesterday and I installed the mod from Steam. Tried then, wouldn't work. Replaced the DayZ files from steam with the new ones from the download page on this site. Didn't work. Replaced the BattlEye dll file with the one from their site (1.62), still dont work. Got DayZ Commander, doesn't work. I still get BattlEye initiation failed. And I dont have Avira or any virus program...

What am I doing wrong?

EDIT: I did the try to log onto a normal Arma 2 server to, to update BattlEye that way...didn't work

EDIT: Got it to work...a bit. Now it loads, but when I get into the game, just to spawn, I get stuck at a loadingscreen

EDIT: Now it works, but I wont get logged in. Says something went wrong, disconnect and try again. Requesting Authentication and then it freezes

LAST EDIT: Got it to work...

Edited March 11, 2013 by PsyGriff