Dayz wont start in experimental

[Killawife 599]

I played experimental on tuesday night. Went to play yesterday and it wouldnt start. 0.60 starts no problem but not exp. What happens is that the small start-up box comes up and then closes. its says in steam thats dayz is running and then it just stops even trying to start. At first I thought, no big deal, and tried a number of things, reinstalling dayz, reinstalling steam, changing some minor stuff like admin rights, reinstalling divx and c++ and a lot of stuff like that but nothing worked. So today I reinstalled windows. Updated all drivers and shit and when I press that button to play experimental.....nothing. 

What the actual fuck?

I have a computer that gets a 7.8 score on windows index with no fualts and it played experimental fine on tuesday. I changed NOTHING and suddenly it does't work. And as I said, 0.60 starts and runs fine but not exp.

 

Help.

 

[xconkersx 0]

did u ever fix this?

[chambersenator 106]

I had this problem, and I was able to resolve it by doing the following:

Removed all Battleye files (IIRC, one in in programsx86/common, the other is in your hidden appdata/local folder in your user folder, and the one in the steam/steamapps/common/DayZ folder) then verify the game cache. If you dont see BE files in the appdata folder, don't worry. Don't start the program until you complete the rest of the steps.

Temporarily uninstalled my antivirus program (not just disable, but uninstall) I had Symantec Endpoint Protection (I know, it sucks, but it was leftover from my previous job that required it)

Uninstalled any remote access software, such as teamviewer.

Try running it - if there is still a problem, Complete reinstall of graphics drivers and associated apps (geforce experience, for example). since you already did an OS install, you may want to try using the previous driver release instead)

Somewhere during this process, I was able to start the game, but it would close when I tried to connect to the server. Doing all those things fixed it though.

Also, I should say that I was able to run ArmA 3 fine, so it seems like it is specifically related to the whatever DayZ specific BE files were sent out.

My guess is that the BE client doesn't like something it sees, and quits out rather than telling you about it. I think this bug happens when it finds files it doesn't like, but have been deactivated (services stopped, etc) and since there's no running app to tell you about, it gets confused and just closes the app.

Edited December 10, 2016 by chambersenator