My GOG Galaxy client keeps saying it's ready to update but when I try to it restarts and I get the message "There was a problem with updating the application. You can always download the latest version from:" and then it provides the link. But I have no intention of re-downloading the client. I already jumped through a million hoops to sync all my other accounts on steam/uplay/etc. It was a lot of work and I'm not taking the slightest risk of having to do that again. So is this issue being worked on? I'm sure it affected 100% of users.

Wonderful. The installation breaks with 2 internal errors.GOG has to fix this and has to make a version that can be installed though GALAXY.

I'd try a clean install at that point.

1. Back up the aforementioned folders while GOG Galaxy isn't running:
%ProgramData%\GOG.com\Galaxy\
%LocalAppData%\GOG.com\Galaxy\
2. Uninstall GOG Galaxy.
3. Install both vc_redist.x86 and vc_redist.x64
4. Restart your system.
5. Run the full installer 2.0.60.2 for Windows.
6. The less you restore from the backups, the better. At least avoid restoring the prefetch and redists folders under %ProgramData%\GOG.com\Galaxy\

If you still encounter problems at step 5, you probably have an antivirus that's interfering.

Thanks for the input. Although client 2.0.60.2 beta is installed, according to GALAXY "settings". Is this the correct version or is the update no beta anymore?

Thanks I'll give this a try at some point.

"Beta" is by now a meaningless descriptor, because that's all there is. You can go to the homepage at www.gogalaxy.com and read the text below the only download button.

There are also so-called experimental updates. You can enable these under cogwheel - Settings - General - "Be the first to try out new features..." (no such update is available at the moment)

Oh, I know and forgot, that all GOG 2.0 versions are always beta versions.
So, then I seem to have the recent version, although the update seemed not to finish properly, but I remember, not far ago, that on every update,the progress bar stopped before reaching 100 %, but the update was complete.
Seemed to be a bad cosmetic bug.