New Origin Bug:Could not start, please verify that you have the latest version..

[Randalmaker]

"Could not start, please verify that you have the latest version and can start the game from Origin." => Error when trying to join another BF4 Server in Battlelog.

Theres a fun "new" bug for me, keeping me from connecting to BF4 games at least 50% of the time. "New" because it was actually happening to me in the Beat Client of Origin, but I thought it would get fixed in the final release. Well, OF COURSE it hasn't. The old client was completely stable, only acting up once a week or something, but this new error is very consistent for me.

Only workaround: Close Origin completely, logout from Battlelog, restart Chrome, restart Origin, login to Battelog again and then it mostly works. Which if a lot of fun when all you wanna do is switch to another server.

Thanks @EA for this new and improved version of Origin!

[MrurieI]

Same thing im getting while trying to join any bf3 server. Bf4 works well for now.

[Carbonic]

Tried reinstalling the Origin client?

[renesweb74]

I do it - but same problem again. I think is a communication problem between Battlelog PLugin and Origin. I must restart Origin and close the browser and say "play" in Origin - Battlelog open and I can join servers again - but this workaround is really annoying. Please fix that

For information - I work with two accounts, but should not the problem

[Ludarcr1s]

I'm having the same problem. I cant even start the game from Origin.

Please someone help.

[Randalmaker]

The problem seems to be connected to the cloud saving function of Origin. At least in my case. After i deactivated it I have never seen this bug again since. But thats not a perfect solution, of course, because for some game cloud saves can be useful...but atm I'm just happy it runs reliably.

[EA_David]

@Randalmaker Thanks for the post. I wonder, if you temporarily disable your anti-virus as a test, then re-enable Cloud Storage, do you encounter the same issue?

[Randalmaker]

Sure, I will try that. I wonder if maybe this is one of those bugs that appears for a while and then just never happens again. Anyway, going to test it. =)

[Randalmaker]

OK, I've tested around a bit and it actually looks like the Antivirus makes the difference. I had much less problems when i switched it off (Avast Free up-to-date). And just when it reactivated the bug occured again...so it seems to be the root of the problems at the moment.

[EA_David]

Thanks for the confirmation and the extra information given, we're seeing some similar reports to this one.