I found a solution to it (it worked for me).
In binaries directory:
Rename MassEffect2.exe as MassEffect2Launcher.exe
Rename ME2Game.exe as MassEffect2.exe
Now It Works fine and it can import Mass Effect 1 saves.
Hope work for everyone.
Thank you soooo much, I swear to god if I hear about issues with ME4 I'm not going to buy the **bleep** thing.
Hello Commander(s),
This happened to me a few minutes ago.
It is not necessary to completely uninstall ME2 and reinstall it. There is a quicker way to do the workaround (took me 5 minutes).
If you're experiencing this error, go into the game folder (by default on windows 7: C:/Program files (x86)/Origin Games/Mass Effect 2)
Enter the folder named "Binaries" and permanently delete the "MassEffect2Config.exe" file. Then go back to the original game folder and permanently delete the folder named "data" (make sure Origin is closed).
Afterwards, launch Origin, right-click on the Mass Effect 2 icon and select "Repair Install". Let the repair tool fullfill his task (should'nt be very long).
Then, proceed to manually copy the saves from ME1 as indicated in the previous message from pudsley.
(Copy the content of the folder "Documents/BioWare/Mass Effect/Save" into "Documents/BioWare/Mass Effect 2/Save/ME1")
When it's done, launch Mass Effect 2 (use local data when asked by Origin), hopefully this issue should be fixed. It worked on my end.
Happy Reaper hunt.
Your method worked flawlessly for me as well, eachems.
The only difference was that the save content for ME1 was still in the ME2 save folder after the repair. I went ahead and deleted it and replaced it just to be safe.
Thanks for posting!
I just had the same exact problem as everyone else.
I tried eachems' steps, but they did not work for me.
I tried the following steps, and they did work:
@Brutalistanbul wrote:I found a solution to it (it worked for me).
In binaries directory:
Rename MassEffect2.exe as MassEffect2Launcher.exe
Rename ME2Game.exe as MassEffect2.exe
Now It Works fine and it can import Mass Effect 1 saves.
Hope work for everyone.
For anyone else, I would simply try the solution by eachems or by brutalinstanbul...eachems' process took us about 12 minutes, but it didn't work....the process by brutalinstanbul took less than 5 minutes and it did work.
Thx for the help from everyone and good luck with your solution.
-Troy & Spike
Well, this worked.
Kind of.
Now it won't let me play the DLCs.
Well, I figured why Origin won't validate the DLCs.
Seems like all my purchases from last year, except for the trilogy itself, reverted to "Processing".
Breaking the laucher wasn't enough, you had to go and steal my DLCs, just in case I figured a way around the launcher thing.
Good show!
Worked flawlessly, much ablidged.
So, after 4-5 days of deleting, renaming, editing file names, repairing, and such...
I have come to the conclusion that the original sin was that the configurator, somehow damaged the instance of ME2 that ran after the config.exe was opened, and every saved game afterwards was likewise corrupted. I have thought to delete the saves from the successful repairs I have had, because of the possibly corrupted saves may be bringing "virus-like" code to the newest install, affecting the install and preventing the freshly installed ME2 from working more than once. That has happened at least 4 times to me after various patches, fixes, etc. All without any lasting success and with several wasted hours of work and game.
The only consistent thing in the event log is the MSVCE80.dll error. 80 instances of failure to launch, after various attempted remedies. All of which stem from a desire to have ME1 saves carry over.
You will notice this is 2017 and the problem has been ongoing since at least 2012, sorta like andromeda distracted everyone from this clusterf*ck or do I merely have to blog/research deeper, longer, harder?
Did you disabled cloud saves?
If not the corrupt save games will indeed be back in your "Save" folder.
If the Games run after a game repair, the save games are not the culprit, the game repair does not touch the save folder.
The procedure is so:
If the game runs after you removed the save files, you can copy them back one by one or in small groups, if you have many to see which save is corrupted.
If this happens regularly I also would consider to run "Chkdsk" on the drive with the save files.
Danke Sehr, that is exactly how I went about it this past time...
It is running and is "reliable" but I have yet to have it recognize files from 2015 0r 2016...the corruption hit about 1 March...
Thanks again for the guidance...
This method does not seem to work if you are playing the game through a Vault account as there is no option to right click and repair. Had to delete Mass Effect 2 and redownload, then copy files as this post instructs.
The Vault installation doesn't differ from an "normal" installation.
If there is no repair function, it means that the game has not been installed correctly.
Hi 🙂 I tried your methode but the repair game, isn't showing up.
The problem remains the same, I click the play button, button becomes unavailable for a few moments and then I can click it again without anything happening.
I just bought the game, managed to only play once before it got like this.
*sadness*
Please create a DxDiag in text file format and post it with your next reply.
If you use Windows 7 also go to your Reliability monitor > Press the Windows key and "R" at the same time and copy and paste or type "perfmon /rel" (without the quotes) in the new Window > hit “ENTER” and look if it has entries for the game you have trouble with.
If yes double click at the last entry for the game executable, copy the info to the clipboard, and save it to a text file.
You can attach the DxDiag text file you created (and the “Reliability monitor” text file as well) to your post in the “Reply” window with the “Choose File” button.
