Packaging immediately finishes, does nothing

I am trying to package my project for windows 64 bit, but when i do, i get the Package Complete! message straight away and no files are present in the set folder, and nothing shows up in the update log. This also happens for Zip Up Project.
I have tried reinstalling Unreal Engine but this has not worked. The project has been sucessfully packaged before.

i have tried this with multiple projects, including creating a brand new first person template and this has still occured. As you can see, the output log has outputted nothing

I have tried installing a previous version of unreal engine (4.17), still with no effect, even on template games

I’ve been having this same issue. I’ve tried a few things like adding Error Debug Symbols in the options panel to no avail. Hoping to have this resolved today, will post an answer when it’s fixed.

1 Like

Hey Hero,

I had the same exact issue and in my instance it was due to some native Windows settings. To save you some time on troubleshooting Windows, try the following.

  1. Create a new User in windows
  2. Load Epic Game Launcher from new user > Try packaging a project there.

Turns out, my Windows had issues accessing the CMD prompt and a few other essentials needed for packaging a project. After creating a new User, I was able to access CMD and packaging a project suddenly worked perfectly.

In a worse scenario it might be best for you to reformat your PC if it’s a virus messing with your system.

Hope this works for you too.

1 Like

Thank you, this has worked in packaging my project. However, I am unable to control my character at all. Not sure what this is.

I just woke up today and my project started doing the same thing with 0 changes.

So i had this problem too. I created an account just to hopefully help someone else out.

Spent about 5-6 hours just attempting to research this issue but nobody can seem to find the answer.

Here is the most likely cause to your problem.

The package manager uses CMD.exe to complete the package, if that connection to CMD.exe is not possible then it will show no output, and instant complete your package without writing any data.

So the first question you need to answer: If you open up cmd.exe in your search bar and run it, does it open up correctly? Or does it instantly close? If access to your cmd.exe is not working, than the package wont complete. CMD may be experience issues- resolve this by running the following commands in Powershell (since CMD isnt working) DISM /Online /Cleanup-Image /CheckHealth DISM /Online /Cleanup-Image /ScanHealth DISM /Online /Cleanup-Image /RestoreHealth

Another issue that needs to be resolved is CMD may have a registry edit to Auto close(my issue and most likely your issue too) Resolve this: Run regedit Go to HKLM\Software\Microsoft\Command Processor\ or HKEY_CURRENT_USER\Software\Microsoft\Command Processor\ or HKEY_LOCAL_MACHINE\Software\Microsoft\Command Processor\

For some reason there was AUTORUN key with “EXIT” inside.

Remove the AutoRun key and everything should went back to normal. CMD.exe should start to work again.

Second fix: Create a new local windows user with admin rights and no password, and run the packager there, that should work.

2 Likes

I solved this here

1 Like