Long story short, I hate overlays and game launchers in general (there are many things about them I strongly dislike: telemetry, achievements, de facto DRM, "social" features, plain unnecessary bloat, etc), and I'd like to run the game without Galaxy.

Usually, when I want to play a GOG game, I install it (this is the only thing I use Galaxy for), then I look in the \GalaxyClient\Games\<Game> folder for the executable and create a shortcut elsewhere, which I use to run the game without the launcher. However, I haven't been able to do this with Tron 2.0: on one hand, the tron.exe file doesn't seem to do anything; on the other hand, if I try to download the game outside Galaxy, I get an installer bundled with Galaxy, and I get the same results: the game is installed in the same folder inside GalaxyClient; the files are the same and the problem persists; and there doesn't seem to be any option to install the game without Galaxy.

Is there a way to run this game without having to run Galaxy? Usually, I always find a working executable file inside the installed folder, but this time I haven't found anything.

Thank you very much.

EDIT: It seems that the bundling with Galaxy is not the problem. I've tried running the game with Galaxy and it won't run either. It looks like tron.exe WOULD run the game, but there is some unknown issue than prevents the game from actually launching.

I'm running Windows 7 x64. Running the game (either from Galaxy or manually running Tron.exe) makes a process called TRON.exe appear in the Task Manager, but it just stays idle, doing anything and consuming about 2Mb of memory, no matter how much time I wait. Rebooting didn't solve the issue either.

I tried some of the solutions from the thread you linked (unregistering the dlls, fiddling with the registry...) and it didn't work. However, from the information given there, I started looking and found a forum about other game, where people had the same problem. It seems that just renaming the executable file is enough for Windows Games to stop recognizing it, and finally it launches. The link in question is here.

So, thank you very much.

Interesting! I suggested renaming the executable in the thread I linked to, but the person with the issue claimed it didn't work.

Glad to hear the problem has been resolved. If renaming the executable does work, then that is indeed a very simple solution. (I couldn't test myself, because I don't have access to a system with Windows 7 installed, at the moment.)