The Epic Games Launcher Setup Wizard Ended Prematurely

Development Getting Started & Setup
, , , ,
21

you could also try going in c:/programfiles(x86)/ and delete the original folder ‘Epic Games’ and rerun the installer.

1 Like
22

Thanks this did it for me too. Ridiculous how simple this was, spent 10 minutes playing around with cmd prompt.

1 Like
23

Deleting the folder helped me!

1 Like
24

how do i delete the folder

25

I ended up turning off all the dot Net windows features and then Epic Games Launcher installed just fine
After it installed I turned the dot Net windows features back on
I had tried signing in as Admin and turning UAC completely off which had not worked (I turned the UAC back on after the attempt)
I figured it out after checking my install logs and saw there was a dot Net fatal exception
So if all else fails check your install logs :smiley:

26

IT WORKED!

So I was going through all of the suggestions all throughout epics site and google and youtube even and nothing was working. I tried the command prompts, back-rolling my drivers, reupdating my drivers, turning off antivirus and firewalls; nothing was working. Then I came across this thread. The SIMPLEST solution worked for me! All I had to do was create a new destination folder in the C root (local disk) and I don’t know if deleting the original in program files helped or not but I did that too. When I opened up the installer setup wizard I just chose the new folder I just created and it worked seamlessly.

EVERYONE EXPERIENCING THIS ISSUE GIVE THIS A TRY!

27

Removing the old Launcher folder did the trick for me.

28

i kept messing around in my files and found out that windows installer is saying that " file epicgamesfortnite349235325 (random numbers i don’t remember so i just wrote random numbers here). I couldn’t find that file anywhere on my computer. The keyword is fortnite, because i remember previously downlaoding epic games as well as fornite with it, but i don’t remember what happened to the fornite file and now i need to find it or something. Please help.

29

I forgot to mention that my current epic installer, the one I’m having this problem with, is titled “epicgamesinstaller120302949” somethin’ like that.

30

Im not sure why but for me what fixed this was deleting everything from epic that was previously on my computer. Then when i started to download the launcher, when it asked me for a place to download it to in my explorer, I went up a level. So instead of goin into local C drive, program files (x86). I just went straight into the C drive. It downloaded fine after that.

31

Taken from Reddit, it helped me so I post it here:
download advanced uninstalled pro make sure html has the padlock :unlock: logo to make sure it’s the legit version run it then delete the epic games launcher from there then download it again and replace the file already in downloads then it should download

32

I worked on this issue for 2 days!! here is the reason and how to solve it

The Problem

  • The new EpicInstaller.msi doesn’t register or unpack correctly on Windows 11 24H2.

  • The MSI calls a Windows Installer script that fails mid-way when it tries to install DirectX runtime components (XINPUT1_3.dll).

  • Because of that, the installer exits “prematurely,” and you can’t launch Epic at all.

  • Antivirus or ESET isn’t the real cause — it’s the DirectX dependency + MSI bug.

1-Install DirectX manually

2-Copy Epic Launcher from a working machine (or old install) I did from my laptop

  • On another PC where Epic works, zip this folder: C:\Program Files (x86)\Epic Games\Launcher

  • Move the zip to the affected PC → extract it to C:\EpicGamesLauncher

  • 3 - Launch Manually

  • Run :C:\EpicGamesLauncher\Launcher\Portal\Binaries\Win64\EpicGamesLauncher.exe

  • It’ll self-update and run normally.

  • 4-(Optional) Create a desktop shortcut:
    Right-click → Send to → Desktop (create shortcut)

  • Epic Launcher runs perfectly and auto-updates, no reinstall needed.
    The MSI issue is purely on Epic’s side — not user error, not permissions.
    It happens because Windows 11 24H2 changed how the built-in Windows Installer handles DirectX runtimes.