Issues right off the bat

[axle93 0]

I JUST got ArmA2 and OA from Steam and I download DayZ Commander shortly afterward. So I'm playing Origins, right? I find some nice gear and log out before work. Go to log in afterwards: "Wait for Host." Sit there for a hour and nothing happens. Okay, I'll just play some normal DayZ. I meet up with a guy and in return for blood bagging him, he gives me an AK-74 Kobra. As soon as I remove it from his backpack, BAM. Kicked by BattleEye for "SetPos Restriction #0." Now whenever I go to join any DayZ server, I sit at "Waiting for server to start authentication" until I am given the option to disconnect my character and go back to the teams list.

My general response: WTF

[Steak and Potatoes 13480]

What version of dayz are you currently running compared to the server? 1.7.7 was updated to 1.7.7.1 today which may cause this issue. If you are running 7.1 downgrade through commander to match the server you are playing that has not picked up the hotfix.

[Vicco 123]

It's possible Steam corrupted your Dayz downloading the hotfix. Both my partner and me had that issue.

Check in Dayz Commander in the install/update section to see if it reports as "Corrupt."

If so, turn off the Steam auto-update, and use Dayz Commander to reinstall whatever version you want to play. It's fast and won't hurt anything.

Worked for me. I was getting the same "Waiting for server to start authentication" error until I found that Steam had corrupted Dayz.

Steam will probably fix their mistake pretty fast, but you don't have to wait.