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

×
Community
GOG GALAXY 2.0 discussionOPEN LETTER TO GOG (and message to support).(97 posts)(97 posts)
(97 posts)
Pages:
1
2
3
4
5
6
7
This is my favourite topic
Posted May 07, 2020
avatar
Phoenix-co: Instead of just deleting the updater, just create a new .txt file somewhere [edit because my old brain forgot to type that part: rename it as GalaxyUpdater.exe] , replace the original GalaxyUpdater.exe (in \Galaxy\redists\) with it, and set it as read only to protect it

We did that with skype's mandatory updates in the old days, worked fine
You know that would result in you overwriting (essentially deleting anyway) the updater, right?

You don't NEED a file to be in its place. You don't need to KEEP deleting it repeatedly. Just remove the .exe file or rename it (change the .exe to .old or .txt or whatever else that isn't .exe, or change the name to GalaxyUpdater1 or GalaxyUpdaterNo or something). one time, and done. As long as that file isn't there and named GalaxyUpdater.exe and you have Galaxy launching with the /runWithoutUpdating command added to its shortcut, it won't be updating.
Posted May 07, 2020
Of course I know. That's what I want after all. not that there is any benefit to keep it since you can just install "real" updates manually instead of using this virus

Adding a dummy updater is unneded "for now". Looking at how forceful the "update" was, they could have a way to imitate skype's way to regenerate its updater.

And by doing this, I can re-enable the autostart, since adding the /runWithoutUpdating part in the registry doesn't disable the update.
Posted May 07, 2020
avatar
Phoenix-co: And by doing this, I can re-enable the autostart, since adding the /runWithoutUpdating part in the registry doesn't disable the update.
THAT is a point I hadn't been thinking about. Thanks for reminding me.

Also out of curiosity, does an entirely blank text file renamed as .exe cause an error message on your system? I haven't tried it in a long time but I remember it used to. And if GOG is persisting on trying to launch that file and generating an error multiple times a day, that's going to suck.
Posted May 07, 2020
avatar
obliviondoll: Also out of curiosity, does an entirely blank text file renamed as .exe cause an error message on your system? I haven't tried it in a long time but I remember it used to. And if GOG is persisting on trying to launch that file and generating an error multiple times a day, that's going to suck.
Neither on winxp nor win7, can't say about win10. If you want to check, just create one on your desktop ant launch it, if nothing happen then it should be ok

BTW, about the autostart... another way to re-enable it could be to keep it disabled from the setting but to add a copy of the modified shortcut inside the startup folder ( win7: Start Menu\Programs\Startup ; win10: run shell:startup )
Posted May 07, 2020
avatar
obliviondoll: Also out of curiosity, does an entirely blank text file renamed as .exe cause an error message on your system? I haven't tried it in a long time but I remember it used to. And if GOG is persisting on trying to launch that file and generating an error multiple times a day, that's going to suck.
avatar
Phoenix-co: Neither on winxp nor win7, can't say about win10. If you want to check, just create one on your desktop ant launch it, if nothing happen then it should be ok

BTW, about the autostart... another way to re-enable it could be to keep it disabled from the setting but to add a copy of the modified shortcut inside the startup folder ( win7: Start Menu\Programs\Startup ; win10: run shell:startup )
I'm using Win10 no issues here
Post edited May 07, 2020 by ibanezrg82
Posted May 09, 2020
high rated
As yet, GOG has replied only with automated "we have received your message" emails and no actual reply from a person. I have added the following to my support "Galaxy feedback" message:

---------------------------

I feel it's worth adding 2 points:

1. Having been reading the forums actively since the problems began (that being since 2.0 was forced onto users who are opted out of beta in spite of still being labelled as a beta), I've seen a problem which was actively being discussed as affecting a number of users prior to the terribly-timed launch of the still-beta client. There are a number of users losing access to their entire game library on Galaxy 2.0 - this fact alone has prompted me to revert in order to avoid the risk of a future update to the still-in-beta client spreading this problem onto my account. With the fact that you knew this bug existed before the launch, it is highly irresponsible to have forced it onto the community as a whole in such a way.

2. I have compared your decision to launch Galaxy 2.0 while it's still in beta to the launch of Steam's new library update 6 months ago. Even though your launch compares favourably to that, I am literally comparing you to a software update from a company who have spent at least 6 months knowingly causing medical harm to their customers. That you are doing poorly enough to even be compared to them at all reflects badly on this decision, even if the comparison is one where you look "better" than an alternative.
Post edited May 09, 2020 by obliviondoll
Posted May 09, 2020
high rated
avatar
obliviondoll: As yet, GOG has replied only with automated "we have received your message" emails and no actual reply from a person. I have added the following to my support "Galaxy feedback" message:

---------------------------

I feel it's worth adding 2 points:

1. Having been reading the forums actively since the problems began (that being since 2.0 was forced onto users who are opted out of beta in spite of still being labelled as a beta), I've seen a problem which was actively being discussed as affecting a number of users prior to the terribly-timed launch of the still-beta client. There are a number of users losing access to their entire game library on Galaxy 2.0 - this fact alone has prompted me to revert in order to avoid the risk of a future update to the still-in-beta client spreading this problem onto my account. With the fact that you knew this bug existed before the launch, it is highly irresponsible to have forced it onto the community as a whole in such a way.

2. I have compared your decision to launch Galaxy 2.0 while it's still in beta to the launch of Steam's new library update 6 months ago. Even though your launch compares favourably to that, I am literally comparing you to a software update from a company who have spent at least 6 months knowingly causing medical harm to their customers. That you are doing poorly enough to even be compared to them at all reflects badly on this decision, even if the comparison is one where you look "better" than an alternative.
Yes! Every game that ran on DOSBOX suddenly stopped working on 2.0 - for me anyway
I was going to install ALL of my games at some point, I have three drives, but I don't want to do that if they wont work in the future.
I received an automated message I'm assuming because of the steps I took to block Galaxy from updating, no the files aren't corrupt GOG, they're just not there
Until they fix these very serious issues with 2.0 I don't want anything to do with it.
Posted May 10, 2020
avatar
ibanezrg82: Until they fix these very serious issues with 2.0 I don't want anything to do with it.
Exactly my thoughts at this stage as well.
Posted May 10, 2020
high rated
adding my voice to this as well. Hoping they hear us.
Posted May 11, 2020
avatar
ibanezrg82: The real fun part of this was in reverting back to the original, all of my game settings got reset to default including mods and I had to reinstall all of those, complete cluster eff
I took some steps and now have to make sure my games do not auto update and added a command line to the shortcut not to update, as well as deleted some of the update files.
Yeah. That happens, when you import already installed games. Galaxy validates and "repairs" them for you. The only way to prevent having to reinstall them, is to create a copy of the folder, have Galaxy "repair" the install, then delete the contents of the folder and paste the stuff from the copy back into it. Super annoying, but if modding a game is particularly difficult and time consuming, preferable.
avatar
Phoenix-co: Instead of just deleting the updater, just create a new .txt file somewhere [ . . . ]
"Instead of deleting, just do"? Implying it's less work to do all of that stuff...?
That's entirely unnecessary. "Just deleting" is the easiest, quickest, and least error-prone way to go about this.

And since the version won't magically update itself (that's what the updater was for), it won't be able to gain the ability to update itself, since... you know, it can't update itself as is.
But if it doesn't throw any errors, you do you.

But also, very crucial detail to mention: unhide / display file extentions, so you don't end up with a "GalaxyUpdater.exe.txt" file...

BTW, I did that for Skype back in the day, too. Because that was the only solution to control Skype...
Post edited May 11, 2020 by BlackSun
Posted May 11, 2020
avatar
BlackSun: But also, very crucial detail to mention: unhide display file extentions, so you don't end up with a "GalaxyUpdater.exe.txt" file...
Yeah, when they first added the "feature" of Windows autohiding extensions, I made that mistake quite a few times before I got used to how it worked.
Posted May 14, 2020
Count my signature please
Posted May 16, 2020
high rated
avatar
BlackSun: If you, dear reader, want to prevent the update from ever occurring, or roll back after it got you - here's a dedicated topic to explain how to do that (shameful self-plug):

HOW TO Keep Galaxy v1.2 client and avoid the forced v2.0 BETA update
Thank you so, SO MUCH!!!
Posted May 23, 2020
avatar
obliviondoll: As yet, GOG has replied only with automated "we have received your message" emails and no actual reply from a person. I have added the following to my support "Galaxy feedback" message:

---------------------------

I feel it's worth adding 2 points:

1. Having been reading the forums actively since the problems began (that being since 2.0 was forced onto users who are opted out of beta in spite of still being labelled as a beta), I've seen a problem which was actively being discussed as affecting a number of users prior to the terribly-timed launch of the still-beta client. There are a number of users losing access to their entire game library on Galaxy 2.0 - this fact alone has prompted me to revert in order to avoid the risk of a future update to the still-in-beta client spreading this problem onto my account. With the fact that you knew this bug existed before the launch, it is highly irresponsible to have forced it onto the community as a whole in such a way.

2. I have compared your decision to launch Galaxy 2.0 while it's still in beta to the launch of Steam's new library update 6 months ago. Even though your launch compares favourably to that, I am literally comparing you to a software update from a company who have spent at least 6 months knowingly causing medical harm to their customers. That you are doing poorly enough to even be compared to them at all reflects badly on this decision, even if the comparison is one where you look "better" than an alternative.
I have re-sent the email above, and added the following to it:

---------------------------

I am re-sending this, as it has been 2 weeks since it was sent, and more than 3 weeks since I originally contacted you. I am still yet to hear back regarding this issue, and it remains serious and service-impairing. You have forced me and a significant number of other users to revert to the Galaxy 1.2 client due to a combination of direct-impact problems and concerns about extremely severe inconsistent issues with the platform that have been known about since beta and remain unsolved.

This is NOT an acceptable situation to be in. Neither the problem itself lasting for such a period, nor the lack of response to support contacts regarding the issue. You need to be addressing customer concerns, and doing so on a much shorter timeframe than this, EVEN in light of the current situation being a justification for delays in support response. 3 days is the extreme end of a "normal" expected timeframe. A week would be reasonable to expect for a delayed response in the current situation. Less than 2 weeks is the MAXIMUM I'd consider an acceptable timeframe for response. You are well past that level of delay now.
Posted May 23, 2020
high rated
CDPR doesn't care for GOG Galaxy 2.0

The fact they ported Gwent on Steam says a lot. Mostly priorities.

I say to people, let's not use Galaxy 2.0 again till they get their shit together. It's unacceptable to see something like this from a respected publisher and developer like CDPR. Especially when they have surprassed Ubisoft as #1 European video game developer and publisher.
Pages:
1
2
3
4
5
6
7
This is my favourite topic
Community
GOG GALAXY 2.0 discussionOPEN LETTER TO GOG (and message to support).(97 posts)(97 posts)
(97 posts)