Epic Games Launcher is unable to complete EOS installation.
The EOS MSI fails with error 1603 during the InitializeComponents custom action. Investigation of the MSI logs shows that EpicOnlineServicesUserHelper.exe is launched by the installer but times out and is terminated.
The EpicOnlineServices Windows service is created successfully.
Starting the service causes EpicOnlineServicesHost.exe to launch EpicOnlineServicesUserHelper.exe as the updater process.
The updater immediately exits with service exit code 77.
The updater log contains the error:
“LogUpdaterService: Error: No updater mode specified”
Windows version: 10.0.19045
EOS version: 5.3.0
Launcher repeatedly attempts EOS installation because the service never starts successfully.
Ive already gone down the provided help list for this error and none of that worked. I dont want any suggestions regarding reinstalling the Launcher or going to Microsoft support. There is nothing wrong with my MSI service as other MSI installers worked just fine. THe problem lies withing the EOS executables.
I cannot properly use the engine anymore for my job. Is there some way to disable EOS entirely so I can work.
Checking around the community, this could be a corrupted state for EOS in your system. It’s worth checking under registry, if the proper ImagePath is set. Go to HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\EpicOnlineServices and check if the string looks like the screen below:
If the entry is missing, then EOS won’t work as intended. You can test by killing any active instance of it’s service, then going to the following directories, and clearing these folders’ content:
After that, you can try to install it again. Still, if you prefer to bypass EOS altogether, you can open the engine directly from your install folder (for example, C:\Program Files\Epic Games\UE_5.8\Engine\Binaries\Win64), by clicking on the UnrealEditor.exe file, then picking your .uproject from it’s launcher.
So I had perviously gone through regedit and manually did those changes but it didnt work.
After another few hours of trying different things I gave up and let GPT Codex just sort it out. Within 15min it was solved.
The reasoning it gave was that MSI was timing out because the EOS installer helper was hanging for just a bit too long causing it to rollback. The only way around it was increasing the timeout length and grabbing those folder files before the rollback to apply some edits before re-running the installer. - Among a few other issues.
If anybody else is struggling with this problem I can only say dont waste your time like me and just go through something like codex that can run commands on your local machine
