Forum Discussion
8 Replies
- @holger1405 That seemed to do the trick! Seems to be launching fine now from both Steam and EA app (tried it a couple times both ways to make sure it wasn't just a fluke). Thank you so much, I really appreciate you taking the time to help me out 🙂
Hello.
Sorry to re-open this thread. But Holger seemed very helpful.
I have a problem too, with starting up ME:A. My launcher just closes and reboots when trying to start the game.
Even tried online support, that didn't help, and now they won't help anymore apparently, because I've been shut off to the 24/7 chat support.I'm having the same problem mcswifty, I've found I've been able to launch it through frosty mod manager with platform launching disabled so maybe try that. More a work around rather than an actual fix but it's better than nothing ig. Also not sure if it matters but I run frosty as administrator. Hopefully this works for you too
Please create a DxDiag in text file format and post it with your next reply. You can do that with the "Choose file" button at the bottom right corner of the reply window.
OMG Thank you SO MUCH, @Metro_Unicorn
Now it works, launching via Frosty Mod Manger.
However pretty sad that you have to do that, and that the game won't work without that. EA really need to up their game.Yay glad to hear it worked!
@mcswifty97 It seems that this is issue with Windows' Security update. Try this (Windows 11):
1. Open Exploit protection.
2. Select the "Program settings" tab.
3. Click "Add Program to customise"
4. Type MassEffectAndromeda.exe
5. Turn off "Force randomisation for images (Mandatory ASLR) by enabling Override system settings and moving the slider to the off position (see the attached image).
6. Click Apply.
Hope this will help for you as well as for me. Launching via Frosty Mod Manager doesn't work for me, by the way.
Found solution here:
Леее, целую твои пальцы дорогой!!! хоть что-то помогло, спасибо!
About Mass Effect Franchise Discussion
Recent Discussions
- 10 hours ago
- 3 days ago