Forum Discussion
I FOUND THE SOLUTION
https://www.youtube.com/watch?v=wE2I_jnCIGU
- 2 years ago
Also, you can get rid of that popup msg in Origin client by editing the local.xml file;
Stop origin client loading EA app message;
1. Open C:\ProgramData\Origin\local.xml in notepad
2. Add new key there:<Setting key="MigrationDisabled" type="1" value="true" />
This should go at bottom just above the last line which is "</Settings>."
Save the file and exit. Now launch Origin and that stupid notice will be gone.
Congrats...you can now play your games properly.Also, set Origin settings to not automatically update. You can manually update games from in the library if you think there's an update you need for it.
Everyone should be aware....with these fixes in here....it's just a matter of time before they delete this thread.....just like they did my last one.
- 2 years ago
this is the missing key to the puzzle
by blocking api1 you do no remove the setting* from the xml, but since I restored mine, it never shows!
I assume if the Api1 is not blocked and ea pushed a 'removal' of the migration, the xml will be updated.
the
api1.origin.com
is the domain it uses to check for updates, which also happens to be how it fetches data to write to the xml.
*-presumably another setting to show it or disabled set to false and hence, it shows it
@markomitic81 perhaps the latest origin version has something broken? and it's not the fix affecting it?
- 2 years ago
Good point @speedracer523 because even after editing the xml File, there is indeed scope for that to be later over-written with another version if the upgrade push does that.
I opened Origin and disabled all permissions that I could see, including Notifications and updates.
That may be enough, but if I get locked out again by the forced EA App upgrade pop up, then I'll know the XML has been put back to where it was.
So far, so good. But I am aware now that the XML may need to be re-edited, and other steps taken to stop that being re-edited back to where it started.
- 2 years ago@AYAYATOR1337
Thank god, but for some reason, fifa 20 wont apply mods via frosty mod manager - 2 years ago
Excellent, the solution proposed by @AYAYATOR1337 and @Mardoin69 works, or has for me.
Namely the editing of the local.xml fileI would advise making a copy of that File first, just in case, so it can be put back in case of issues, or in case EA get their act together and fix the broken EA App.
Now when I click on the Game's icon on my Desktop, I am taken straight to the Game.
Well done! - 2 years ago@AYAYATOR1337 God bless you my friend, this works even for fifa😃😃
- 2 years ago
This worked for me! THANK YOU!!!!!🥳
- 2 years ago
Hello Gamers! It seems unfortunately, as of March 14th, 2023 (At least where I am), EA updated Origin and seemed to change how local.xml is generated, now generating whenever you launch Origin. This pretty much impacts how this method is done, since before, Origin only generated/updated local.xml whenever you fully closed Origin. Even if you had the setting key inside local.xml and closed Origin, it would still be there. I'd have to assume that the setting key is either blacklisted or straight up deleted. This is some unfortunate news to hear, as we all pretty much stick with Origin because of EA App's poor optimization when it comes to older games, and lack of features that Origin holds. There may not be a fix for this, and we will unfortunately have to move on and stick with EA's new app. This will have a huge impact on us Origin users. Only time will tell if there will be a new method of using Origin again.
About EA app Technical Issues & Bugs
Recent Discussions
- 38 seconds ago
- 2 hours ago
- 2 hours ago
- 2 hours ago
- 2 hours ago