@Anoneevee Yeh it's one thing if it's some rare problem but these issues seem to be affecting a lot of people and communications from EA are dire.
Couple of other questions:
Is your machine W10 Home? What build are you on?
Do you use a PIN to log-in?
@Anoneevee I can't think of anything else that would be a likely culprit. It's annoying and I'd love to know what is causing it. Beyond this EA issue, the 1312 error itself is fairly common but it usually crops up when trying to access network resources and can be caused by how windows stores credentials (amongst other things). That's why I was asking about a PIN, since that is one of the general fixes for this error. Since your issue is with trying to gain admin perms over an exe on a local drive though, it seems to be a different problem.
That leaves us in the realms of checking everything that could potentially be causing the problem. That would be a time consuming and potentially fruitless process.
Some further areas might be:
Network config - is your machine part of a workgroup or domain? (Maybe the app is trying to use a runas with <user name> but your network config requires <machine name or domain>/<user name>)
Windows build (mine is 19044 vs your 19045)
Firewall / AV
Try different combinations of run as admin settings on EA App and game exe's
@Anoneevee You could also try setting UAC to highest level
