This bug is annoying as hell, and its been on the launcher for so long without fixing that i feel more than frustrated.

How its taking so long to fix it, cant be that dificult when every other launcher out there works fine, i reported this years ago (and already was reported by other people).

Many people like me use remote desktop from their laptop to install or manage games on their desktop. We can play in our laptop using streaming services (being Steam streaming, Nvidia GeForce Now or whatever) and its great because u dont need to upgrade a laptop to play new games or buy a gaming laptop just to play games.

I like GoG overall, and support them every time i can, but this particular thing is the only thing holding me back to buying more games in this platform. Its a sad thing but its annoying to manage games when the GOG launcher crashes every time you remote desktop to your desktop computer.

And now with GoG Galaxy 2.0 trying to be the universal launcher this should be fixed ASAP. Otherwise people like me will be just too annoyed to even invite people to the GoG client just because of this issue and continue to use other clients or discord chats to communicate instead :/.

Bumping this, as it's still an issue for me in the latest build.

I frequently manage my gaming PC remotely. Steam, Epic, Battle.Net and Origin launchers all allow remote management over RDP without any problems. GoG fails every time.

I'd rather spend my time sitting at my gaming PC gaming, not waiting for game updates to load.

AnyDesk works though. Of course you can't really play through it, but managing the collection (tagging etc) when you are bored and elsewhere works like a charm.

This is still an issue. Launching in an RDP session appears to start successfully but soon exits with the error "Connection to Communication Service was lost and could not be restored".

This issue is long standing in the GOG Galaxy client and is not new to 2.0. It's happened in every version of Galaxy I've ever used.

It is still a bug in a recent setup (latest GOG-Galaxy und Win 10 1909 x64). I also miss the fuctionality, e.g. for starting downloads or getting offline installers. As the GOG-Downloader seems to be discontinued, this would be really helpful. I also tried VNC but it is the same problem using this protocol.

Yes ... this is so annoying.. It's been there since the original Gog Galaxy Client, and GoG's explanation was that it was too hard to fix, but yet it is still here in Galaxy 2.0 ..

Often I need to start a very big download while I am at work and need it to be ready by the time I am home, and I cannot do that because of that bug. Please GOG.. Fix this at last. Every other single storefront client works perfectly with Remote Desktop, it's just Galaxy that does not.

To anyone asking why would someone want to use RDP with the Galaxy client, My gaming PC is hooked up to my TV as its only monitor. I use RDP to install games and run driver updates so I don't have to mess around with UI/UX I know is not designed for display on a TV. This issue will make me seriously consider not using the Galaxy client as Steam and the other major store fronts let manage them over RDP.

I happen to have a 28 Xeon Core server with 386 GB of RAM and a GPU Card in it but it's too loud to keep in my home office. But the main reason I use RDP is so I can play games on my work computer from the comfort of my home office without having to install games on the company system.

Any updates on the issue?

I will say this, it appears to work fine if you just ignore the pop up.

Please fix this.

I got the same issues. I really would like to manage some of my stuff remotely.

Okey.
GOG Galaxy is now working for me via RDP I think enabling "interactive services" may help.

\HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Windows

DWORD: NoInteractiveServices

Change from 1 to 0

either that or GOG updated something.

Yes, please fix this already... :)