Re: [PC] Mass Effect 3 Won't Launch

Has anyone been able to get ME 3 to work? I tried re-downloading the game this week and it is asking me for activation but when I tried clicking the product key button it gives me an error. Talking to EA support is like talking to an AI that will just repeat whatever is common knowledge without no real help. I was just talking to support that suggested I reinstall the EA app which makes no sense to me because ME 3 isn't really tied to the app. But I gave it a shot anyways which required me to reboot my pc (not sure why EA app requires a full reboot when other apps like steam/epic don't) but I did it anyways. Now I can't even get back to live chat since the option isn't even there any more. This issue has been driving me insane for the past 3 days. I own the game I just aquired all the DLCs and wanted to replay it again but this one issue I can't resolve....

@MinusTee 

• Make sure EA app and Steam are closed.
• Press the Windows key and "R" at the same time.
• Type or copy and paste "%ProgramData%\Electronic Arts\EA Services" (without the quotes) into the new Window > ENTER
• Move the "License" folder to your desktop.
• Test.

I've tried this. I even tried this and the Revo uninstaller method and also deleted the file inside the license folder. Still the same issue. I tried uninstalling EA app and clearing cache. Redownloading the game and still the same. I even tried making a new admin account on my Windows 11 pc. Uninstalled EA app cleared cache. Redownload ME 3 moved the license to desktop on this new admin account and still the same issue. Do you have anymore bright ideas? I fully suspect this is a backend issue on the server side because it wont register my product key and gives me the error of me potentially being offline when I fully am able to use the sign in option to log in with my origin account.

Wow, after trying about a million things, moving the license folder worked.  Thank you!!!!!!

I just wanted to add that my game also didn't launch anymore and what fixed it was disabling MSI Afterburner. I hope this might help some people.

Yeah this fixed it for me, thanks!