GOG Galaxy 2.0.80 Beta Breaks Game installation (Error E2)

[Ryonez]

This is more a notice, you can work around it but users need to be aware not to update the client.

There's a link on GOG's forms with more info here, GOG Galaxy 2.0.80 Beta, but the jist is the new 2.0.80 Beta client results with games having E2 errors when installing. No game will work with the client atm.
Rolling back to version 2.0.77.22 of the client does work, but you need to make sure not to update for now.
For myself, I replaced the GOG client link in the plugin to one of this older version to install it.

[moraroy]

@Ryonez does steams Proton 9.0.3 help?

[HazedNapkin]

I was having this issue and changing to proton 9.0.3 worked for me, thanks

[LaiKash]

Tried with 9.0.4 and didn't work. I'll try uninstalling too

[razorblade446]

Followed @Ryonez advice and solved the issue temporarily. Maybe we need some way of providing the stable version for GoG (Because of it providing a BETA)

[moraroy]

@razorblade446 @Ryonez @LaiKash @HazedNapkin I've been using Proton GE 9-10 actually guys, seems to work very well, not sure if this is still a problem with the "updated version of gog" yet though

[jamiehall123]

I ended up following a gog help article which worked for me. When it's in the final install stages (don't close gog galaxy), in the gog program folder rename the Dependencies-Temp folder to Dependancies, minute or two later it finishes the install successfully.

https://support.gog.com/hc/en-us/articles/360013537357-GOG-GALAXY-Installation-failed-E2-Update-failed-E2-Failed-to-finalize-the-update?product=gog

[moraroy]

@jamiehall123 amazing..... could you do a pull request?

[jamiehall123]

Sorry I should have clarified, the folder rename has to happen every time you install/update/verify a game in gog galaxy to avoid the E2 error.

I would class this as a workaround as it seems the Dependancies aren't installing, or being detected properly in this latest version.

Presuming renaming the folder forces the gog client into thinking the Dependancies have installed.

[moraroy]

@jamiehall123 well that's annoying lol I'll see keep an eye on it thank you for finding this! <3

[Ryonez]

I was having trouble were the folder rename wasn't helping on the problematic version.

[jamiehall123]

I was having trouble were the folder rename wasn't helping on the problematic version.

Just checking, did you perform the rename while the client was running, and towards the end of the game installing/updating?

[Ryonez]

I was having trouble were the folder rename wasn't helping on the problematic version.

Just checking, did you perform the rename while the client was running, and towards the end of the game installing/updating?

Was after it failed and I closed the client and switched to desktop.
My goal was to have this all working while in gamemode, the only concreate way I could do this was reverting back to the prior working version, 2.0.77.22 in this case. The proton version at the time made no difference, I've not tried Proton GE 9-10 yet.

I'm guessing if the updated client is a problem, and if Proton GE 9-10 does work, then GOG changed some filesystem process somewhere, that the newer GE adds. I've no idea what atm though, I haven't touched it since I rolled the client version back.

[jbroberg]

If nothing has changed in the most recent release i think it's fair to say this still doesn't work out the box.

My fix was installing Proton GE 9-10 via protonup-qt manually and force running gog via this speific version after installing GoG via NSL.

Proton GE 9-10 wasn't an installed proton version option out of the box after plugin install - maybe it should be if it's currently required to install GoG games?

many thanks for the NSL work it's amazing.

[moraroy]

@jbroberg yeah I'm considering that, not sure if a new proton will fix it or should I wait for gog to fix this issue. I'll give it a little more time. In this new update alot of the UMU shortcuts for gog were broken so be sure to let NSL remake those shortcuts. Using proton ge 9-10 seems to still work

[rogerclotet]

I have the same issue, didn't try installing GOG Galaxy before yesterday, the client seems to work okay but I have the same install problems reported.
I tried renaming the Dependencies directory as a workaround at different times during the installation but it doesn't seem to make a difference.

[moraroy]

@rogerclotet what about GE Proton 9-10?

[rogerclotet]

Ok, you're right @moraroy, I only tried with the latest GE Proton (9-22). I just tried 9-10 and it works! Thank you!

[Karrq]

Can confirm, GE Proton 9-10 works :)

[ghost]

Can confirm, GE Proton 9-10 works :)

Dumb question - EVERY time I go to load GOG via game mode I have to manually change the compatibility to Proton 9-10. What am I missing here?

[moraroy]

@michaelb2225 not missing anything there is nothing in the script yet that sets it for gog yet, as usually it sets the latest ge proton.

[denny-dee]

Not sure if my points are relevant to this thread, but I'll add my 2 cents. It all happened sometime in November-December I think, didn't play much NSL games since then.
My GOG version turns out to be 2.0.80 (I don't remember signing up for beta).
I have issues for the past 2-3 months, where I can barely play any NSL games other than EGS.
I've had issues running Sniper Ghost Warrior 3 from GOG, until I reinstalled the GOG client (unsure if I started fresh or just uninstalled and reinstalled GOG). Also, I had to disable GOG cloud saves, as they lead to crash. Also, I believe I had some troubles with UMU links for some game (maybe this one), until I replaced those with pre-umu links (just copied from some older and working game, changed ID and file path).
I installed and played Just Cause 1 and 2 from GOG a couple of times, until the SteamOS and NSL update (unsure if it was December or November). After that, I had issue with cloud saves for these games, and disabling this feature didn't work for me, had to uninstall the games. Maybe some file permission issues prevented GOG from saving cloud saves locally?
Now I've installed Far Cry 2 from GOG, but the game does not start, probably because of the client version. UPD: changing link values to non-umu, or changing Proton GE to 9-10 didn't work for me
Also, maybe NSL shouldn't force compatibility through launch options? If we force Proton through Steam UI, I'm not sure if it's used for the game now.

Also, I installed EA App back in December. I've played NFS for a few hours, it ran perfectly. However, now EA needs an update. It restarts with no issues, downloads the update, and fails to apply the update. I've tried fixing it by updating through NSL (both script and Decky plugin), but it crashes during the update. Again, file permissions issue maybe?

[Karrq]

I also noticed the proton version being set, but I believe it could be just the default for newly added shortcuts. Didn't really check if, after changing it manually, the version was changed back

[moraroy]

@denny-dee 1. when running the gog launcher and its games use Proton GE 9-10, it shouldn't crash anymore. 2. There was an error in the umu shortcuts back then, please get rid of all umu shortcuts and have NSL remake them, you should be good to go. 3. With umu, as far as I can tell, I don't think I'm able to get rid of the proton path inside of the command, that's why for umu shortcuts there is no force compatability being set and its inside of the launch options instead. Umu launcher seems to need that command. 4. Use the "repair EA App" inside of your library, when you installed the EA App, another shortcut was given to you called "repair ea app" this will repair the app, when ea decides to boot loop.

[moraroy]

@Karrq yes I belive this happens on the desktop version only correct? I noticed this too, I may be able to fix.