neumi5694: Well, 2.0.58 runs stable on my machine.
I installed the upgrade manually.
Maybe it would be in place to get some sytem specs to find the pattern what's causing it to crash on some machines.
starchaser777: Did you also check your PC's 'reliability history'? No recent Galaxy crashes like the rest of us?
You can find it by searching 'reliability' in the search via the taskbar.
Ah, now I got some. The service did crash about an hour ago. Well, I seem to be part of the club then.
It happened about 5 hours after I started the client. Maybe that's why I never saw it before.
Edit:
for PocoNet.dll Dependency Walker shows that a couple of VC dlls have missing dependencies, but that's nothing out of the ordinary.
This is what Galaxy's log says to that (ignore the numbers, they change anyway on every startup).
2023-02-13 13:44:11.710 [Error][ (0)] [TID 11856][galaxy_client]: NetException during GenericGogPbReader::readWholePacket: Connection reset by peer,
2023-02-13 13:44:11.710 [Warning][ (0)] [TID 11856][galaxy_client]: Unrecoverable error for request [Sequence Number: 3901253836]
2023-02-13 13:44:11.711 [Information][ (0)] [TID 11856][galaxy_client]: Starting service 'GalaxyClientService' asynchronously.
2023-02-13 13:44:11.766 [Warning][ (0)] [TID 11856][galaxy_client]: Exception during sending request to service: Error Message: Reading response for request [Sequence Number: 3901253836] failed!
[...]
2023-02-13 13:45:13.284 [Information][ (0)] [TID 11856][galaxy_client]: Starting service 'GalaxyClientService' asynchronously.
2023-02-13 13:45:13.346 [Information][ (0)] [TID 11856][galaxy_client]: GalaxyClientService started properly.
2023-02-13 13:45:13.346 [Warning][ (0)] [TID 11856][galaxy_client]: Exception during sending request to service: Timeout
2023-02-13 13:46:14.859 [Information][ (0)] [TID 11856][galaxy_client]: Starting service 'GalaxyClientService' asynchronously.
2023-02-13 13:46:14.920 [Information][ (0)] [TID 11856][galaxy_client]: GalaxyClientService started properly.
Interesting is that after restarting the service first there is a timeout and Galaxy tries to start the service again. There is no error entry in the windows event log for that however, so maybe they just have too short timeouts.
So a connection loss crashes the service ... nicely done, GOG programmers :). But at least it's restarted shortly after.