Posted August 12, 2017
I believe I am having the same issue here.
barrycswords
New User
Registered: Dec 2016
From Australia
Dedly
New User
Registered: Jan 2013
From United States
Posted December 02, 2017
This is still an issue, I've reported it, and nothing has been done about it, to my knowledge.
BUT I FOUND A WORKAROUND.
Easy workaround: Use Chrome Remote Desktop or some other RDP client instead.
Harder workaround, but works well...
On the machine you're remoting into where you want to start the Galaxy Client but can't, do the following:
1. Create a new text file somewhere. Doesn't matter where.
2. Open the text file.
3. Add the following:
C:\Windows\System32\tscon.exe 1 /dest:console
C:\Windows\System32\tscon.exe 2 /dest:console
timeout 3
"[path to your]GalaxyClient.exe"
4. Save changes to the text file and close it.
5. Rename the file extension from .txt to .bat (if file extensions are not visible, you'll have to make them visible first in Windows/File Explorer options).
6. Now run the .bat file you just created.
The first two lines will close your RDP session but leave the desktop open (tested in Win7, haven't tried it in Win10 yet). It might be session 1 or 2. It's varied for me in the past, but it's always been one of those two. Put both in there and you're sure to make it work.
The third line tells the script to wait 3 seconds. Might not need this, but I wanted to make sure the RDP session had completely closed before it tried to open the client, just to avoid it failing yet again.
The last line will look something like "C:\Program Files\GoG\GalaxyClient.exe" or wherever you installed the client.
I just tested this, it disconnected my session, and started the client successfully. I RDP'd back into the host machine a couple minutes later and the Galaxy Client was open and waiting for me on my desktop.
BUT I FOUND A WORKAROUND.
Easy workaround: Use Chrome Remote Desktop or some other RDP client instead.
Harder workaround, but works well...
On the machine you're remoting into where you want to start the Galaxy Client but can't, do the following:
1. Create a new text file somewhere. Doesn't matter where.
2. Open the text file.
3. Add the following:
C:\Windows\System32\tscon.exe 1 /dest:console
C:\Windows\System32\tscon.exe 2 /dest:console
timeout 3
"[path to your]GalaxyClient.exe"
4. Save changes to the text file and close it.
5. Rename the file extension from .txt to .bat (if file extensions are not visible, you'll have to make them visible first in Windows/File Explorer options).
6. Now run the .bat file you just created.
The first two lines will close your RDP session but leave the desktop open (tested in Win7, haven't tried it in Win10 yet). It might be session 1 or 2. It's varied for me in the past, but it's always been one of those two. Put both in there and you're sure to make it work.
The third line tells the script to wait 3 seconds. Might not need this, but I wanted to make sure the RDP session had completely closed before it tried to open the client, just to avoid it failing yet again.
The last line will look something like "C:\Program Files\GoG\GalaxyClient.exe" or wherever you installed the client.
I just tested this, it disconnected my session, and started the client successfully. I RDP'd back into the host machine a couple minutes later and the Galaxy Client was open and waiting for me on my desktop.
Post edited December 02, 2017 by Dedly
Waifu4Life
JPN Game Enthusiast
Registered: Oct 2015
From Canada
Posted March 29, 2019
Can't believe this has yet to be fixed in 2019. Being at work and logging from home is the best time to update games via Galaxy. If they really want to push people into using it, they should make it more convenient for things like this.
dnovraD
2023-08-14: Remember the Spaces!
Registered: Jul 2012
From United States
Posted March 30, 2019
And you're looking for a solution without a problem. There are various ways to accomplish what you want with some simple software scheduling. Tell GOG to start at an hour; tell the computer to shutdown after an hour has passed, that sort of thing. And you can even set up in your bios for your computer to power itself on.
paladin181
Cheese
Registered: Nov 2012
From United States
Posted March 30, 2019
Waifu4Life
JPN Game Enthusiast
Registered: Oct 2015
From Canada
Posted March 30, 2019
Arallu
New User
Registered: Apr 2012
From United States
Posted August 14, 2019
BUT I FOUND A WORKAROUND.
Easy workaround: Use Chrome Remote Desktop or some other RDP client instead.
Harder workaround, but works well...
On the machine you're remoting into where you want to start the Galaxy Client but can't, do the following:
1. Create a new text file somewhere. Doesn't matter where.
2. Open the text file.
3. Add the following:
C:\Windows\System32\tscon.exe 1 /dest:console
C:\Windows\System32\tscon.exe 2 /dest:console
timeout 3
"[path to your]GalaxyClient.exe"
4. Save changes to the text file and close it.
5. Rename the file extension from .txt to .bat (if file extensions are not visible, you'll have to make them visible first in Windows/File Explorer options).
6. Now run the .bat file you just created.
The first two lines will close your RDP session but leave the desktop open (tested in Win7, haven't tried it in Win10 yet). It might be session 1 or 2. It's varied for me in the past, but it's always been one of those two. Put both in there and you're sure to make it work.
The third line tells the script to wait 3 seconds. Might not need this, but I wanted to make sure the RDP session had completely closed before it tried to open the client, just to avoid it failing yet again.
The last line will look something like "C:\Program Files\GoG\GalaxyClient.exe" or wherever you installed the client.
I just tested this, it disconnected my session, and started the client successfully. I RDP'd back into the host machine a couple minutes later and the Galaxy Client was open and waiting for me on my desktop.
Sometimes I have to kill all Galaxy processes and retry, this is on Windows 10.
cyberpunksoldier
New User
Registered: Feb 2010
From Australia
Posted October 27, 2020
Hey CDPR, this bug is the only reason I'm considering buying CP2077 through Steam instead of directly from GOG. GOG Galaxy runs just fine in Windows Remote Desktop Connection as long as I launch it somehow outside of the remote desktop. Why does Galaxy fail to launch inside remote desktop? Please fix this!
bstrobl
New User
Registered: Dec 2009
From Germany
Posted November 27, 2020
This affects me too, and should be fixed.
Gutterboy
New User
Registered: Jan 2015
From United States
Posted June 15, 2021
I can't believe this is still an issue. If I need to reboot my PC remotely through Remote Desktop GOG throws this error. As a software developer, I wonder what GOG is doing that breaks when initialing through an RDP connection? The hack above works and I've used a similar hack the keep Hamachi running on one of my app servers after remoting into it.
SargonAelther
Pls add Offline Installers for My Rewards!
Registered: Dec 2013
From Other
Posted June 28, 2022
Oh man, I just want to backup my game installers using my storage server, instead of via my desktop. What's the point of this restriction?
There's no reason for me to keep several devices online at once, when I have one specifically set up for 24/7 use. naturally it would be managed via RDP.
There's no reason for me to keep several devices online at once, when I have one specifically set up for 24/7 use. naturally it would be managed via RDP.
binarymelon
New User
Registered: Dec 2012
From Canada
Hurricane0440
Tux in a Tuxedo
Registered: Jul 2023
From United States
Posted June 05, 2024
If achievements and play time isn't really something you need, you could try installing and updating those games via the Heroic Games Launcher instead of GOG Galaxy.
https://heroicgameslauncher.com/
https://heroicgameslauncher.com/
Post edited June 05, 2024 by Hurricane0440
Yechiel
New User
Registered: Mar 2017
From United States
Posted July 20, 2024
BUT I FOUND A WORKAROUND.
Easy workaround: Use Chrome Remote Desktop or some other RDP client instead.
Harder workaround, but works well...
On the machine you're remoting into where you want to start the Galaxy Client but can't, do the following:
1. Create a new text file somewhere. Doesn't matter where.
2. Open the text file.
3. Add the following:
C:\Windows\System32\tscon.exe 1 /dest:console
C:\Windows\System32\tscon.exe 2 /dest:console
timeout 3
"[path to your]GalaxyClient.exe"
4. Save changes to the text file and close it.
5. Rename the file extension from .txt to .bat (if file extensions are not visible, you'll have to make them visible first in Windows/File Explorer options).
6. Now run the .bat file you just created.
The first two lines will close your RDP session but leave the desktop open (tested in Win7, haven't tried it in Win10 yet). It might be session 1 or 2. It's varied for me in the past, but it's always been one of those two. Put both in there and you're sure to make it work.
The third line tells the script to wait 3 seconds. Might not need this, but I wanted to make sure the RDP session had completely closed before it tried to open the client, just to avoid it failing yet again.
The last line will look something like "C:\Program Files\GoG\GalaxyClient.exe" or wherever you installed the client.
I just tested this, it disconnected my session, and started the client successfully. I RDP'd back into the host machine a couple minutes later and the Galaxy Client was open and waiting for me on my desktop.
Sometimes I have to kill all Galaxy processes and retry, this is on Windows 10.
So many threads of people having this problem, this should be on gog's faq.
Thanks!
sailense
New User
Registered: Feb 2013
From American Samoa
Posted August 08, 2024
BUT I FOUND A WORKAROUND.
Easy workaround: Use Chrome Remote Desktop or some other RDP client instead.
Harder workaround, but works well...
On the machine you're remoting into where you want to start the Galaxy Client but can't, do the following:
1. Create a new text file somewhere. Doesn't matter where.
2. Open the text file.
3. Add the following:
C:\Windows\System32\tscon.exe 1 /dest:console
C:\Windows\System32\tscon.exe 2 /dest:console
timeout 3
"[path to your]GalaxyClient.exe"
4. Save changes to the text file and close it.
5. Rename the file extension from .txt to .bat (if file extensions are not visible, you'll have to make them visible first in Windows/File Explorer options).
6. Now run the .bat file you just created.
The first two lines will close your RDP session but leave the desktop open (tested in Win7, haven't tried it in Win10 yet). It might be session 1 or 2. It's varied for me in the past, but it's always been one of those two. Put both in there and you're sure to make it work.
The third line tells the script to wait 3 seconds. Might not need this, but I wanted to make sure the RDP session had completely closed before it tried to open the client, just to avoid it failing yet again.
The last line will look something like "C:\Program Files\GoG\GalaxyClient.exe" or wherever you installed the client.
I just tested this, it disconnected my session, and started the client successfully. I RDP'd back into the host machine a couple minutes later and the Galaxy Client was open and waiting for me on my desktop.