It seems that you're using an outdated browser. Some things may not work as they should (or don't work at all).
We suggest you upgrade newer and better browser like: Chrome, Firefox, Internet Explorer or Opera

×
windows 10 . After i press play from the galaxy app or just the exe, for a few moments i won't be able to launch again because an instance is already running. After that without any error messages it will shut down and mark that i played it in the galaxy app. Mirror's edge is the only game affected, although it is the most demanding game i have installed and i have a potato.

I have tried reinstalling DirectX , gog galaxy and mirror's edge and also following the troubleshooting by creating a new environmental variable .
This question / problem has been solved by mistycovenimage
Sorry, I didn't see you mentioned it crashes from the .exe directly. My bad.

You may wish to check Games does not launch on Windows 10 and Crash just after splash screen, courtesy of PC Gaming Wiki.

The Mirror's Edge subforum seems pretty dead, but you might find someone there who has experienced this issue.
Post edited June 06, 2023 by mistycoven
Something else you can do if you have difficulty getting a game to run is try compatibility mode.

When you right click on an exe file there should be an option to run the program in compatibility mode. When you click that, you should see some kind of window or menu that lets you choose which earlier version of windows you want windows to try and simulate so that the program runs.

It's not a perfect solution, but it's saved me a lot of headaches. If I have an issue running a game I usually try this first.
avatar
Space_Slither: Mirror's edge is the only game affected, although it is the most demanding game i have installed and i have a potato.
That may be the reason...

However: did you try to find a solution here: https://www.gog.com/forum/mirrors_edge ?
Always start with trying one of the compatibility modes that Windows offers.
Since it was released about 15 years ago, try XP SP3 or Windows 7 first.

Also check the windows event log what caused the error.

There is also a nice little tool called dependency walker that can help identifying missing runtime components.