Windows says that BattlEye has invalid signature

[gtmoraes 10]

Whenever I try to start ArmA 3 with BattlEye, it says it was unable to start due to driver error (577).

 

Checking eventvwr, Windows says that:
"The BEDaisy service failed to start due to the following error:
Windows cannot verify the digital signature for this file. A recent hardware or software change might have installed a file that is signed incorrectly or damaged, or that might be malicious software from an unknown source."

 

I am currently using Windows 10 Insider Build 14379 (latest update). Curiously, this happens sporadically in different builds (it isn't working on my current build 14379, it was working on build 14377, it wasn't working on build 14361, it was working on a build prior 14361). I'm not sure if the builds are part of the problem, or if it's just coincidental.

 

I've tried refreshing Windows, but the problem continues.

 

When trying to download the BEService_x64.exe from BattlEye Official Download Page, Microsoft Edge says that "the signature of BEService_x64.exe is corrupt or invalid".

I am able to recover the .exe from the Downloads folder, but it still doesn't work (Game says: "Failed to initialize BattlEye Service: Driver Load Error (577)", Windows says the same as above on Event Viewer.)

 

Is this behaviour expected for this current Insider build (or any at all), or is it a bug?

 

 

System:

- Windows 10 Pro Build 14379 x64. Refreshed one hour ago since this post. All updates are installed.

- i5 4690k, GTX970 with latest drivers, 12GB RAM

- Game is installed on an SSD. There are no partitions, there are no other drives.

 

Thanks.

[jimmytheboarhunter 11]

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.