@benbeck Yes, it would be interesting to know what the issue is if you do manage to fix it. Maybe worth comparing perms on the EA App and CnC Remastered folders between the two machines, plus any network differences, AD group memberships etc. It could end up being quite a hassle to find the problem though.
I can confirm that now the game is launching without issues by default. No workaround is needed anymore, so they fixed it probably. Just hit play and popup appears that you need admin account but then the game is launching and not giving error message anymore. Check if you can confirm that too. Btw online play still doesn't work, still giving account restricted message
@Gr1mlock7 I had previously edited my XML code to fix, rather than doing it through View Properties. I've just reverted the change I made, so that the XML is back to the state it was in when the game would not launch and the game still launches fine. So yes, it seems that EA have updated the app so that the rogue parameter in their XML no longer causes a problem.
Thanks for letting us know 🙂
Any idea when EA fixed it btw? It seems that as of earlier today, people are still having issues with the same error displaying but stemming from the different problem with the 1312 specified logon session does not exist being shown in the EA log file.
Oh and my online play is still working, I'd still raise it with EA if I were you as it's perhaps an account related issue.
@bleearghh no problem)
Yes I just tried a couple of hours ago, but haven't touched the game like for a couple of days and before there were the same problem because I didn't edit anything just wait for them to solve it and they did finally haha.
So I need to get to live chat with regular ea support yes, to solve my account issue? Or some special support
After reading this whole thread I'm wondering if you have any idea why the game will not launch on a normal user account, regardless of the individual privileges or settings. I have the game working fine on an admin account but I don't particularly want to be playing games on it. Have you found any way to run it on a user account? Any help would be much appreciated.
@Spiderwolfer What's your UAC set to?
It is set to "always notify". That shouldn't be a problem though as I have all the credentials for the admin account. If it asks for a password I'd be able to give it. The issue is that it doesn't ask for it when I launch the game.
@Spiderwolfer I wanted to check as some people seem to have had success with the UAC setting that you already have set but I suspect they were already logged in on an admin account rather than a standard user. Guess we're no further forward in trying to work out what the problem is but I suspect it's the EA app code itself and probably too hard to fix outside of EA fixing it themselves.
Yeah I'd agree. It seems like it's failing to gather the correct permissions. I'd be curious to know why only some games are failing to accomplish this. I'll let you know if I figure anything out or it gets fixed. Seems this comment section is beginning to have more IT guys working on this than EA lol. Until then let me tell you my discoveries:
- Trying to launch it in compatibility mode on a Standard User fails, this is due to it not being able to access the ssleay32.dll file in the core folder. No idea why it can't. I tried this again after running the game on an administrator side hoping to initialize the ssleay32.dll file again but nothing changed.
- On a Standard User setting the exe file to run as administrator changes nothing.
- Setting the EA app with admin privileges does nothing
- Clearing the cache does nothing
- Resetting the app does nothing
- Redownloading the app or game does nothing
- Downloading the game from the Standard User side barely even works and needs user assistance AND changes nothing.
I acknowledge that there are helper tools you can download that supposedly fix the problems but I will not download sketchy third-party tools. The fact that one of EA's suggestions is to disable antivirus and firewalls to help it out is pretty moronic as well and I will not be doing that. Thank goodness we have people like you trying to help. Hopefully this info can be useful.
@Spiderwolfer Thanks for the kind words. Wish I could be of more help but it's gonna require someone more technical than me to come up with a standard user account workaround (if such a workaround is possible). Otherwise, as I say, it's probably going to have to wait for EA to pull their finger out and fix it :/ They did eventually at least fix their flaky parameter handling when parsing their XML, so maybe they'll fix this issue too. On the other hand maybe I'm being too optimistic!
