It seems that you're using an outdated browser. Some things may not work as they should (or don't work at all).
We suggest you upgrade newer and better browser like: Chrome, Firefox, Internet Explorer or Opera

×
avatar
qoopyqoopy: I wonder if hardware is part of the issue.
avatar
Ice_Mage: Hardware is irrelevant. They introduced an autoupdate bug, which they fixed in version 2.0.60 (and the experimental version before that).
Since your GOG Galaxy updated to a bugged version that can't autoupdate, the only way to fix it is to launch the full 2.0.60.2 installer while GOG Galaxy isn't running. If you encounter any problems, perform a clean install instead.
Thank you! Was able to update successfully from the link you gave. Appreciate it!
avatar
qoopyqoopy: I wonder if hardware is part of the issue.
avatar
Ice_Mage: Hardware is irrelevant. They introduced an autoupdate bug, which they fixed in version 2.0.60 (and the experimental version before that).
Since your GOG Galaxy updated to a bugged version that can't autoupdate, the only way to fix it is to launch the full 2.0.60.2 installer while GOG Galaxy isn't running. If you encounter any problems, perform a clean install instead.
This worked for me too. Thanks!
Normal update worked like a charm for me now. Not mad anymore at GOG.
avatar
Oceanboy06: I have the Same Problem as Well!
avatar
RedcoatsLounge: I've tried downloading from the site page and it still get's the older version. No idea what is going on . I hope the GOG team can get it sorted. I really want GOG to be my hub for gaming.
I finally bit the bullet and have GOG. Promptly bought a ton of old school CRPGs. Loving it so far
Am getting am update notice... I've been ignoring it but maybe I'll try this approach
I installed 2.0.60.2 manually because the previous versions wouldn't update, and now my 2.0.60.2 won't update either due to a
Root Exception: Error Message: CreateProcessWithTokenW failed with code 1058.

Guess I need to find a 2.0.62 installer now...
Post edited April 24, 2023 by jamsatle
avatar
jamsatle: Guess I need to find a 2.0.62 installer now...
Bookmark this JSON file. It will point to the current full installers, as long as they don't bump the major version from 2.

I suggest performing a clean install (ignore the link for the full installer; that's an outdated version now).
Thanks for the link! Will just have to wait and see if my .62 can update to .63 next.
well, my version finally updated to the 2.0.62.26 beta
without issues that I can see.

took gog long enough to fix this update bug...

but better late than never....
avatar
qoopyqoopy: I wonder if hardware is part of the issue.
avatar
Ice_Mage: Hardware is irrelevant. They introduced an autoupdate bug, which they fixed in version 2.0.60 (and the experimental version before that).
Since your GOG Galaxy updated to a bugged version that can't autoupdate, the only way to fix it is to launch the full 2.0.60.2 installer while GOG Galaxy isn't running. If you encounter any problems, perform a clean install instead.
what a bunch of incompetent devs...this error was appearing for like months... every year things are getting worse with software...
avatar
qoopyqoopy: I wonder if hardware is part of the issue.
avatar
Ice_Mage: Hardware is irrelevant. They introduced an autoupdate bug, which they fixed in version 2.0.60 (and the experimental version before that).
Since your GOG Galaxy updated to a bugged version that can't autoupdate, the only way to fix it is to launch the full 2.0.60.2 installer while GOG Galaxy isn't running. If you encounter any problems, perform a clean install instead.
Thank you so much. My only question is why is the 2.0.58.xx still the file on the main website? I just tried it again 5 minutes before finding this thread.
avatar
Raizenmare: Thank you so much.
You're welcome, though the latest version is currently 2.0.67.2. Like I said in my previous post, this JSON file will always point to the latest full installers (unless they bump the major version from 2.x). It's readable in Firefox by default, but the same can be accomplished in other browsers with an add-on like JSON Viewer.
avatar
Raizenmare: My only question is why is the 2.0.58.xx still the file on the main website?
The website doesn't link to a specific version. It gives you a stub installer, which connects to the Internet to download the needed components. The idea is to save time and bandwidth for people who are upgrading by not downloading the full package. Some people can't use this installer — likely due to their firewall — so I link to the full installer in my posts.
I don't know why you'd end up with an outdated version after using the stub installer. Maybe the installation actually failed and it didn't upgrade your installation.
avatar
Raizenmare: Thank you so much.
avatar
Ice_Mage: You're welcome, though the latest version is currently 2.0.67.2. Like I said in my previous post, this JSON file will always point to the latest full installers (unless they bump the major version from 2.x). It's readable in Firefox by default, but the same can be accomplished in other browsers with an add-on like JSON Viewer.
avatar
Raizenmare: My only question is why is the 2.0.58.xx still the file on the main website?
avatar
Ice_Mage: The website doesn't link to a specific version. It gives you a stub installer, which connects to the Internet to download the needed components. The idea is to save time and bandwidth for people who are upgrading by not downloading the full package. Some people can't use this installer — likely due to their firewall — so I link to the full installer in my posts.
I don't know why you'd end up with an outdated version after using the stub installer. Maybe the installation actually failed and it didn't upgrade your installation.
Perfect, thank you for this - I didn't have a JSON viewer, but followed your link to install one, and now I can see the download links. I installed by right clicking Run As Administrator after I downloaded the file, and it seems to work just fine.
avatar
jamsatle: Guess I need to find a 2.0.62 installer now...
avatar
Ice_Mage: Bookmark this JSON file. It will point to the current full installers, as long as they don't bump the major version from 2.

I suggest performing a clean install (ignore the link for the full installer; that's an outdated version now).
Thank you so much for that JSON file, this problem just started for me which is insane since it seems like it's over a year old, I cannot understamd how that is possible, I wasn't really having any issues until recently, I also had a beta version too but it too was tellomg me ot couldn't update. It't must have been just before the fix. I thought I was the only one dealing with it, I am glad I was not.

Thank you!