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

×
If you still have this issue, in a different thread a user reports running as administrator worked:
https://www.gog.com/forum/general_beta_gog_galaxy_2.0/gog_galaxy_cant_update_my_games/post4
for those that found this thread on google there is a solution. end gog galaxy in task manager and then run gog galaxy as an administrator. Now it should work fully.
high rated
This Error (E7) occured in Dec. 21 at my computer as well. Icouldn't run Grim Dawn. After hours of searching for a solution i recognised that the installer's properties (open windows explorer, go to the GOG installer exe, right click ,then open properties and then compatibility) were set to "compatibility mode Windows XP". Holy shit. that's totally bullshit. ...
I set it back to "compatibility mode off" and "run as administrator"
Now it works fine again finally.
Getting this issue with Ion Fury.
avatar
bernhard.bremen: This Error (E7) occured in Dec. 21 at my computer as well. Icouldn't run Grim Dawn. After hours of searching for a solution i recognised that the installer's properties (open windows explorer, go to the GOG installer exe, right click ,then open properties and then compatibility) were set to "compatibility mode Windows XP". Holy shit. that's totally bullshit. ...
I set it back to "compatibility mode off" and "run as administrator"
Now it works fine again finally.
This worked for me too. Thanks for the workaround!
Unsetting the windows XP compatibility mode solved the problem for me too.
Why was the executable set to this mode, I wonder.
What bernhard.bremen said seems to work. Thanks!
Thanks for the solution, it works.

avatar
Himmelsblume: The problem is introduced with GoG Galaxy Update to 2.0.44 and not fixed with update 2.0.45.
Since Galaxy 2.0 was introduced, GOG is a constant problem... All my money goes back to Steam.
avatar
ketyow: Thanks for the solution, it works.

avatar
Himmelsblume: The problem is introduced with GoG Galaxy Update to 2.0.44 and not fixed with update 2.0.45.
avatar
ketyow: Since Galaxy 2.0 was introduced, GOG is a constant problem... All my money goes back to Steam.
It's a damn shame, Galaxy 1.0 was absolutely fantastic and was probably my favorite storefront, but Galaxy 2.0 threw more or less all of my goodwill for the platform into the trash. It's one of the worst downgrades I can think of because of all of the unnecessary features and absurd issues.
avatar
Edenadab_Daefaer: Unsetting the windows XP compatibility mode solved the problem for me too.
Why was the executable set to this mode, I wonder.
This worked for me! Thanks so much. Was trying all of yesterday contacting GOG etc. with no luck.
avatar
bernhard.bremen: This Error (E7) occured in Dec. 21 at my computer as well. Icouldn't run Grim Dawn. After hours of searching for a solution i recognised that the installer's properties (open windows explorer, go to the GOG installer exe, right click ,then open properties and then compatibility) were set to "compatibility mode Windows XP". Holy shit. that's totally bullshit. ...
I set it back to "compatibility mode off" and "run as administrator"
Now it works fine again finally.
Thank you, this is the problem
Hello,
The compatability mode fix did not work for me sooooo... I exited Galaxy, went to task manager to see if a game was still running, Europa Universalis IV was running in the background... killed that and hey presto things worked!

which step it was I don't know, but give it a go?
avatar
bernhard.bremen: This Error (E7) occured in Dec. 21 at my computer as well. Icouldn't run Grim Dawn. After hours of searching for a solution i recognised that the installer's properties (open windows explorer, go to the GOG installer exe, right click ,then open properties and then compatibility) were set to "compatibility mode Windows XP". Holy shit. that's totally bullshit. ...
I set it back to "compatibility mode off" and "run as administrator"
Now it works fine again finally.
avatar
schlorius: Thank you, this is the problem
thanks, it worked well