-
-
Notifications
You must be signed in to change notification settings - Fork 58
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
GOG Galaxy 2.0.80 Beta Breaks Game installation (Error E2) #515
Comments
@Ryonez does steams Proton 9.0.3 help? |
I was having this issue and changing to proton 9.0.3 worked for me, thanks |
Tried with 9.0.4 and didn't work. I'll try uninstalling too |
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) |
@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 |
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. |
@jamiehall123 amazing..... could you do a pull request? |
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. |
@jamiehall123 well that's annoying lol I'll see keep an eye on it thank you for finding this! <3 |
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. 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. |
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. |
@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 |
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. |
@rogerclotet what about GE Proton 9-10? |
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! |
Can confirm, GE Proton 9-10 works :) |
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.
The text was updated successfully, but these errors were encountered: