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

×
avatar
alkhadr: I fixed the problem for myself. I tried every solution here, but none worked.

My solution was to log on to my administrator account and install GOG. (Just to be safe, even while using my admin account I right-clicked the executable and selected "run as administrator.")

Before I found this fix, I had tried to install GOG Galaxy using "run as administrator" from my non-admin/regular account. For some reason that didn't work and I had to log into the administrator account and install GOG Galaxy from there.
Nothing listed in this thread worked for me, so I went to try things on my own. Went to bios and turned off AMD SVM (virtualization) and it worked. Now I can play game but lose access to my virtual machines lol.
avatar
alkhadr: I fixed the problem for myself. I tried every solution here, but none worked.

My solution was to log on to my administrator account and install GOG. (Just to be safe, even while using my admin account I right-clicked the executable and selected "run as administrator.")

Before I found this fix, I had tried to install GOG Galaxy using "run as administrator" from my non-admin/regular account. For some reason that didn't work and I had to log into the administrator account and install GOG Galaxy from there.
avatar
Fran-K: Nothing listed in this thread worked for me, so I went to try things on my own. Went to bios and turned off AMD SVM (virtualization) and it worked. Now I can play game but lose access to my virtual machines lol.
I'm having this issue as well and while I didn't test it with it off, I do have SVM on for my VMs as well.

UPDATE: Just realized this only happens when I RDP into my machine...what in the world. This is repeatable too.
Post edited October 17, 2022 by Mag_Flux
avatar
Fran-K: Nothing listed in this thread worked for me, so I went to try things on my own. Went to bios and turned off AMD SVM (virtualization) and it worked. Now I can play game but lose access to my virtual machines lol.
avatar
Mag_Flux: I'm having this issue as well and while I didn't test it with it off, I do have SVM on for my VMs as well.

UPDATE: Just realized this only happens when I RDP into my machine...what in the world. This is repeatable too.
I can't believe this, but this does help. Galaxy has this error with RDP, but Team Viewer works fine. What on earth is going on with the program that that would matter...
avatar
Mag_Flux: I'm having this issue as well and while I didn't test it with it off, I do have SVM on for my VMs as well.

UPDATE: Just realized this only happens when I RDP into my machine...what in the world. This is repeatable too.
avatar
sep332: I can't believe this, but this does help. Galaxy has this error with RDP, but Team Viewer works fine. What on earth is going on with the program that that would matter...
Wow was RDPed into my other machine (I use it as a server) and having this issue...RDP must be the problem.
Yep same here for me...connecting through RDP and i have same error. Using teamviewer , update is working normally
RDP still an issue 19 Dec 2022
Still an issue, not using RDP. Tried compatibility modes, elevation etc. This is shameful.
Same here with RDP. I have a dedicated gaming PC where all my games are installed, and I connect to it via RDP from my main working PC when I occasionally wish to play lite games. Very disappointed to find that the Galaxy client refuses to work and forces me to go to the website to manually download and to install my games in order to play them remotely. GOG please fix this. Thanks in advanced.
Post edited December 20, 2022 by goldeng
+1. I'm remotely updating my gaming PC via RDP over my OpenVPN server to my home network out of state, but I can't update any of my GOG games because I hit this stupid error every time I try to use GOG Galaxy. This is stupid, stupid, stupid, stupid, stupid, and incredibly unbelievably absurdly obnoxious. Please fix your broken app.
just started getting this error on the MacOS app. never had it before. can't play a single game now....
I'm having the same issue. When I open the GOG Galaxy app on Mac it says that same thing about the communication error. I can't even go onto that for 10 seconds before that happens.
avatar
bbasinger: I'm having the same issue. When I open the GOG Galaxy app on Mac it says that same thing about the communication error. I can't even go onto that for 10 seconds before that happens.
Same issue for me on Mac.

... Ugh.
avatar
bbasinger: I'm having the same issue. When I open the GOG Galaxy app on Mac it says that same thing about the communication error. I can't even go onto that for 10 seconds before that happens.
avatar
Aurshur: Same issue for me on Mac.

... Ugh.
Same for me. Ventura 13.1 / Macbook Pro M1
avatar
Aurshur: Same issue for me on Mac.

... Ugh.
avatar
kafjopo: Same for me. Ventura 13.1 / Macbook Pro M1
Same machine here. not sure how I got it working eventually. Try allowing Accessibility for GOG Galaxy in System Settings -> Privacy & Security. You may have to log out and/or restart.

As a last resort, you can run the GalaxyCommunication service manually from Terminal (just leave it running while you're using GOG, then Ctrl-C)

/Users/Shared/GOG.com/Galaxy/redists/GalaxyCommunication
Can report this issue happens on Win10 pro Version 22H2, OS Build 10.0.19045, with RDP version 10.0.19041.2075, GOG GalaxyClient Version 2.0.58.4, and GalaxyClientService 2.0.58.4

Always able to recreate this issue to a T with any win10x 64bit machine, running that version of RDP, which is the most current as of 2/7/2023.Unable to reproduce this identical issue on any build of RDP on win11 x64 pro.

If RDP on win10 is lower than the mentioned 10.0.19041.2075.on win10, i don't have this issue. Appears to be a firewalling issue with how RDP works all around. Unable to recreate this on other win10 machines with builds lower than the aforementioned version 10.0.19041.2075.

Anyone have some insight on how they resolved this on the mentioned RDP build i mentioned, and their win10 build being 22H2 ?
Post edited February 10, 2023 by supernet2ec