@M0GY3SZ There's another fix on Steam, where the registry path to the game is faulty.
This is someone's thread on it.
https://steamcommunity.com/app/1238810/discussions/0/5188758291785352869/
Anyway thnks for your post. I had meant to come back and edit these posts to reflect what's happened. You prompted me.
I just saw another suggestion you could try.
Someone deleted the Battlefield V folder in Documents.
Presumably then launched the game and it replaced the folder in Documents, with a fresh version.
Of course keep a back of the existing folder you have 'just in case'.
No idea if this is a fix that does anything.
I happy that my EA App is finally fully working. I did the migration to the EA App in April, and was without eight games since then.
While the pause the VPN allows me to launch seven of those games. I also found a fix for Battlefield 3 that would not launch due to another issue.
Can't really blame EA for the VPN problem. Even Steam gets funny with the VPN. ... What is surprising though is that I have all my gaming platforms executables of all types, split-tunnelled in my VPN. That is supposed to clean bypass the VPN for the executables I want the VPN have no effect on.
I even had the Battlefield V .exe bypasses in VPN. However it still needs the VPN paused to launch. I also found that I need the VPN paused to cleanly close the game. The alternative is use Task Manager and end the Battlefield V.
I also notified EA about my findiong out the my VPN was blocking game launches. Maybe if they know they might know where to start looking for a fix. Or at least make a posting somewhere telling folk about VPNs.
