Resolved: Steps for resolving issues with the Epic Games installer that prevents installation.
Resolved: Steps for resolving issues with the Epic Games installer that prevents installation.
MSI installation issues arose on a desktop Windows 7 system, but successfully completed on a laptop running the same version of Windows. A thorough comparison between the two machines—examining permissions, registry settings, and DirectX—revealed no discrepancies. The problem was resolved on the desktop by following these steps: generating a log file using `msiexec /i C:\Users\myusername\Downloads\somepackage.msi /L*v install.txt` and then executing the MSI file with `msiexec /i C:\EpicGamesLauncherInstaller.msi`. A video demonstrating the solution is available at: https://youtu.be/75Sz3PX28WE
2755, 1307, and one more I’ve misplaced, but it also involved the hard drive. Surprisingly, only the epic installer caused difficulties during installation. All other programs installed without issues. I attempted to relocate the installer to various drives and folders, but if you experiment with enabling registry modification logging, always back up the registry before removing the new entry. Similarly, if you enable Group Policy editing logging, remember to turn it off afterward, as both generate large log files that consume space rapidly. I discovered a highly effective method for diagnosing and recording MSI errors, which involved running this command: `msiexec /i C:\Users\myusername\Downloads\somepackage.msi /L*v install.txt`. I looked for a return value of 3 and then scanned upwards to locate the beginning of any errors; after a brief examination…
1307, and one more that escapes my memory, yet it also involved the hard drive. The only installer causing difficulties was the Epic Installer. Other installations proceeded without issue. I attempted relocating the installer to various drives and directories. If you modify the registry through enabling logging, always create a backup of the registry before removing the new entry. Similarly, when utilizing GPedit logging, remember to turn it off afterward. Both methods generate enormous log files that quickly consume storage space. To effectively diagnose and record MSI errors, I utilized the following command: `msiexec /i C:\Users\myusername\Downloads\somepackage.msi /L*v install.txt`. I then searched for a return value of 3, scrolling upwards to locate the beginning of the errors. Referencing this resource proved invaluable: `https://docs.microsoft.com/en-us/windows/win32/msi/windows-installer-error-messages`. It helped me understand the errors and their significance. Additionally, I explored these techniques: adding an Installer folder within the Windows directory, verifying if the setup file was encrypted, and incorporating the SYSTEM user into the installer. I also temporarily disabled any antivirus software while troubleshooting. Examining DX registry values was crucial, followed by executing the following command from a Command Prompt window with administrator privileges: `msiexec /i C:\EpicGamesInstaller-10.7.0.msi`. This resulted in a successful installation with no errors. Right-clicking on the .msi file did not reveal an administrator command option; instead, I initiated Command Prompt with administrative privileges from the Start Accessories menu, navigated to the installer’s folder, and then copied and pasted the command above. This method offers assistance to individuals encountering issues with game installers or any .msi file.