ok explain this.....heres the extremely screwed up way I eventually got this to work. I went into the actual beta folder and updated from the new patch's zip file. no joy. I updated through Dayz Commander, no joy. I deleted my arma II OA beta folder and repeated the first two steps. nothing. Mind you the entire time I had been launching arma from dayz commander. So i went back into the arma II oa beta folder and launched directly from the .exe there...lo and behold it said version 1.62.99515!!! what the hell? The server wouldnt come up using the filter so I thought, maybe if I leave this copy open, launch the to the server from dayz commander but say "no" when it asks me to close my current arma II that was running and guess what....friggin worked and I got into the server. So to test exactly what happened I repeated the process. Opened arma II oa beta from the .exe then launched a second copy through dayz commander. It worked I got in. I thought, what the hell, lets launch it from dayz commander by itself now. Worked. Wierdest damn thing!? Its like somehow originally dayz commander was launching off some other .exe and somehow I forced it back to the correct ARMA II OA Beta exe. So if anyone else has had this problem read my convoluted, half-ass, idiot savant work-around and you can fix the update glitch too!