im getting this error “There is a problem with this Windows Installer package. A DLL required for this install to complete could not be run.” so…did i paid for nothing??
Hi Folks,
Can you run Dependence walker against the installer and tell me what it reports back?
Im getting this to (beta user here). Not sure what is causing it?
“Alternatively, can you try running the installer as an administrator and see if that resolves the issue?”
It wont let me do that actually, its not even an option to open as an administrator which is odd. I also have the option to repair, which ive never seen before. When i select repair, it just crashes the operation.
Im not sure I understand how you resolved the problem? From reading it sounds like it did not get fixed?
The issue occurs if you double click the MSI in Windows Explorer or some dependencies are not met. Alternatively use CMD to run the MSI via MSIEXEC.
Hi Medusa and Aesthetic,
Please try the workaround that is reported here: https://answers.unrealengine.com/questions/12462/unreal-engine-4-installer-doesnt-work.html
The suggested solution is to run Command Prompt as an Administrator, and then use Command Prompt to run the installer.
Let us know if this does or does not resolve the issue.
nah this isnt working…I think the program has too many bugs for me to deal with it… I guess i’ll come back later on,
I got it working using the CMD prompt. Thanks.
So, here is what I think is going wrong and why running the installer using an elevated command prompt may fix the issue for some users. I have not gotten any installer logs that confirm this yet because when users run via cmd prompt it installs successfully:
The installer extracts files to a temporary folder(usually something like this: c:\Users\{YOUR_USER_NAME}\AppData\Local\Temp). I suspect your user has read/write permissions for this folder but not ‘execute’ permissions. The problem is that the installer needs to execute some of the stuff it extracted before it ‘elevates’ itself. If it can not execute, you see the error you posted.
Running the the installer via a command prompt that was ‘Run as Administrator’ will cause it to use Admin privileges which probably include full permissions to the temp folder.
You could try checking the folder I mentioned above to see if you have full control over it.
Halfway down this page are super simple instructions to add “Run MSI as administrator from Command Prompt”.
This is by far the easiest workaround.