jimmytheboarhunter

I'm having the same problem and have been for a long time with numerous builds, currently on 14366 and it's not working. I believe the issue is to do with the way their anti hack works and enforcing driver verification. The reason I say that is because if your on a build that does work and disable driver verification within Windows you will get the same error, which goes away once you re enable driver verification. Not sure if it's a windows issue or BattlEye one, but I'm leaning towards BattlEye being the culprit.

Got the error after updating to Windows 10 Insider Preview Build 14366 and cannot launch the game with BattlEye running. Really surprised there isn't more discussion about this, am I the only one on the Windows Insider program who plays Arma?? Since BattlEye don't seem to care, has anyone managed to do their job for them and found a fix?

Just a quick post for anyone who encounters the "Failed to initialize BattlEye Service: Driver Load Error (577)". I got this error this afternoon after updating to the latest slow ring Windows 10 Insider Preview Build 14271. Battleye fails to launch and no amount of tweaking will fix it. I rolled back to build 14267 to fix the issue. Hopefully this helps anyone else trying to work out why Arma suddenly doesn't launch!

Same issue here, just updated BattleEye and the issue started (played 20 hours ago and all was fine). Try to launch game and get the "Failed to initialize BattlEye Service: Windows Test-Signing Mode not supported." On Windows 10 Tech Preview latest Build 9926. Any update or ETA?