I fiddled a bit with repeatedly un/reinstalling a handful of games after encountering a similar issue with my Fallout 2 installation to that one guy's post (failed updates). The results were wonky enough I don't feel confident making any recommendation based on them. I don't want to try re-installing Galaxy for this, but if anyone would care to try experimentally un/re-installing and down/updating a game/games they had the "wont update" thing on, they'd be in a position to comment as to whether full reinstallation vs removing glx DB's will affect your workaround mileage here :P
Fallout 2 refused to update, and after uninstallation refused to reinstall, downloading the entire game but failing (spuriously IMO) in the final stages where I guess it's hooking the install into Galaxy nicely, with a kinda mysterious error that makes me suspect an issue on gog's end with however they uhh... redistribute the redistributables (heh), as the files noted in the error was present, signed properly, and worked fine when ran manually.
Decided to try and fiddle with some other games that had not encountered the issue after the client update. Down-versioned Battle Brothers and then updated it, failed with a completely different - also apparently spurious - error that seemed to refer to a particular file as having a null json, when it seemed to be present and have reasonable* contents that are in valid json format. Reinstallation failed on the same error, unplayable in galaxy, fine on disk.
*at a best guess for what these files are, anyway
Some other games had no issues, so I delete the db and run through it all again a couple more times. Wildly inconsistent results - with the same games and pretty much the same client install.
So I'd cautiously suggest working around the original failing-update issue, and if you have issues with games refusing to update - good luck to you :| FWIW in my short fiddling, it looks like the failures are related to metadata about the game installation and/or redists - the actual games themselves were properly installed on disk at the end of a failed installation and ran fine launched outside of galaxy. So you should still be able to play affected games, if without the convenience. A 50-foot-high YMMV here, please.
For games that just fail to update as opposed to something you can't even install, I think if you disable game auto-updates and abort the failed one that should bring the play button back in galaxy. I'm done with my fiddling though, perhaps someone can try that and confirm/deny.
Two small side notes:
Using the ~1mb webinstaller will fetch you the latest version, you're not getting any previous version from that.
This has been in "beta" for a very long time, 1.2 is long gone, and this is a significant failure in the most basic functionality. Why not debug what we can, helping eachother (and maybe indirectly some poor goglin who's probably pulling some OT on this one) in the process, rather than devolve into ages-old, never-to-be-resolved tribal slapfights? P.S. Linux client when
Post edited April 27, 2022 by BARONBONGHITS