This time I couldn’t upgrade the Epic Game Store to v18 within the launched app, so I decided to reinstall via the Lutrisinstaller, which installed everything without errors.
After starting the Epic Game Store, the message “Update is being checked” appears and the Epic Game Store is closed again without errors. Here is the debug file from the Epic Game Store: https://paste.ubuntu.com/p/MC8wMQ6h5C/
I have just noticed that the update has deleted all my games. Now I want to completely delete the präfix from the Epic Store and create a new one.
Does the Epic Game Store installer do this, or do I have to create a new präfix via wine?
I have now installed the Epic Game Store in a new prefix and it has installed 592MB and then exited just as it did in the old prefix. Here is the error.log again: https://paste.ubuntu.com/p/FVHTfskdZ4/
Hi, it would be very helpful for the rest of us if you describe what other steps have you done to solve this. Currently I cannot install epic games because every time starts it says “Verifying Update” and then close and after that do nothing.
Hi, thanks for the tip, but that has not work for me. What I have done is I went to Windows and updated there Epic Games.
Once that was done then I went to Debian and copy from the Windows Installation the folder Launcher. After that Epic Games has worked.
I just tried different Wine derivatives and at some point the Epic Game Starter started.
At the moment it runs stable on GE-Proton9-25 without the UE error that used to occur from time to time with (Lutris-GE-Proton8-15-X86_64).
I was able to fix the online service with German help (Redirecting).
Although I have been using the EGS for 5 years, I will now part with it for a while and use heroic.
The EGS is running again, but the online service is not working again.
So, I let myself be tempted to update to 18.1.3. Now I have the same crap as you again. At startup it always download an update (436.3 MB), then checks it and then stops.
The only thing left to do is to install the EGS in a new prefix
Hi guys.
I’m a Steam Deck user and I’ve experienced this recurring update window after having the bad idea to try to update EGS.
I tried deleting everything ( prefix and EGS folder ) and
installing via Lutris script;
executing the exe with lutris ( I can’t then start downloading the application )
…if I install EGS in a new prefix, the store works, but the Epic Online Service still won’t update.
Since I myself lose the game links to heroic, only if I pack EGS in a new prefix, I would first wait for new versions and install over them. Unfortunately you can’t install old versions of EGS over it (maybe there is a trick?).
…otherwise use an alternative like heroic.
I never entered anything in the Clous synchronization (because it’s still a beta anyway). The local paths found there are also empty for me. The game then uses the default paths that it would also use for Windows.
I have just read through the thread here again, and for me the solution is here. Works 1A and the Epic Store is working again for now. I haven’t checked the online service yet.
According to the launcher I copied earlier, I now have version 18.2.0.
However, when I download the latest version using this link, I still get version 18.1.3.
Perhaps the bug has been fixed in 18.2.0?
The Epic Online Service is still not working. I was offered the update 18.2.0 to 18.3.0 today.
Then I did the update on Windows and copied the launcher back to Linux Mint.
That works.
Just tried to install Epic Games Launcher and can confirm the follow:
LogSelfUpdateService: Error: No local manifest loaded in HandleLauncherManifestLoaded.
LogSelfUpdateService: Error: InstalledManifestWithDataFuture was not valid in HandleLauncherManifestLoaded.
LogInit: Warning: LaunchNonElevatedProcess: No desktop shell is present.
LaunchNonElevatedProcess: No desktop shell is present.
Slate User Destroyed. User Index 0, Is Virtual User: 0
Monitored process exited.
Initial process has exited (return code: 0)
Exit with return code 0
Installing the launcher will download and patch itself automatically and from what I am guessing it is making some kind of permission modifications. Once the patch is done, it will results in the error that I have showed above.
After searching for a while a stumble on this link Link which gave me the idea of doing the following steps:
Install epic game launcher normally
Let is update
Once you get the error rename the folder ~/Games/epic-games-store/drive_c/Program Files (x86) and rename Epic Games to something like Epic Games1
Change the Executable path to the renamed from ~/Games/epic-games-store/drive_c/Program Files (x86)/Epic Games/Launcher/Portal/Binaries/Win32/EpicGamesLauncher.exe
to ~/Games/epic-games-store/drive_c/Program Files (x86)/Epic Games1/Launcher/Portal/Binaries/Win32/EpicGamesLauncher.exe
Launch the launcher from Lutris
Once you can see the launcher opened you can close it and go back rename it how it was.
This actually solved the error.
I had EGS starting and then closing without doing anything when launched via Lutris.
I opened EGS folder and a console and launched the .exe with wine directly, it started properly and updated, for some reason. After that it simply runs fine in Lutris.
Hey there!
I’ve encountered this issue before and just recently solved it again—none of the methods in this thread worked for me this time, but I managed to find my own solution.
I tried everything: different Wine versions, MSI installer, renaming folders—nothing worked. But it turned out the fix was just adjusting file permissions. I don’t know which exact permission was the issue, but here’s what I did:
I allowed read/write/edit/delete access for all users. On Ubuntu, you can do this by right-clicking the folder → Properties → Permissions tab. By doing this, the lock icon on the folder should also be gone. (I gave about everything access, though some of it seemed to automatically revert. The key change should be your user.)
Once I did that, the Launcher completed the 570 MB update and works perfectly now.
Do note that I have installed the newest EpicInstaller-18.7.0.msi manually and I’m currently using Wine TKG 10.7.
Previously when encountering this problem a few months ago, switching Wine versions worked for me as well—like GE-Proton9-25, which @ Volker_S mentioned. It is recommended to use the wine-10.7-staging-tk-x86_64 if possible.
I hope this helps someone else out there! Let me know if you’d like me to share screenshots or specifics.