I'd uninstall EA anticheat using the Uninstall All option.
https://help.ea.com/en/help/pc/ea-anticheat/#uninstall
Then I'd uninstall Battlefield using the Steam app uninstall process. Then uninstall the EA app using Windows uninstaller.
Finally I'd go to Windows uninstaller and take a picture of all the Microsoft Visual C++ Redistributables and .NET Framework that are installed. Then uninstall all C++ and .Net Framework using Windows uninstaller.
After everything's uninstalled reboot the PC and install Battlefield using Steam installer. The Steam installer should install everything Battlefield 1 needs to run. Including EA app, EA anticheat, C++, and .Net Framework.
If Battlefield still fails to run then I'd backup all my important data and do a full Windows reinstall because I don't know what's causing the issue.
Write down your Windows Product key before reinstall.
Make sure to reinstall all the C++ and .Net Framework that Battlefield didn't install. Other Windows apps might depend on them.
tnx for ur help, ike I said before – I already tried that. It was one of the first things I did. So basic I didn even mention it. I dug so deep into my system I dont even remember how far I went.
And yeah – every time I ll say it again – I m sure the problem is with eaanticheatservice and that 1503 error when tryna start it.
Anyone got any idea what else in the system could be turned off or on that might mess with it? Cuz I m bout to lose my mind here.
The last solution I can recommend is doing a clean windows install with drivers only and then installing the EA app and BF 1. I do repeat windows and drivers only. This should pretty much solve the issue. If this works then you'll have the task of installing your programs one by one and checking when BF 1 stops working.
nah, that's out of the question at the moment. and stupid. i haven't updated the Wind since then and haven't installed anything additional like drivers or third party software.
I will put this in every post - someone help me solve the 1503 error in eaanticheatservice. Maybe something else needs to be enabled in the registry or in some other services? it can't just break down by itself.
