When I start packaging my project for windows, it instantly shows “Packaging complete” but no game files are created at the specified location. Also, no output log is generated for attempting to start packaging. There is also no error displayed. I have the same problem on both my PC and laptop. I spent 4 days looking for solutions all over the internet but in vain. I tried changing default maps, different combinations of project settings, different package settings, disabling antivirus and firewall, installing Visual Studio 2017 and 2019 etc. Nothing seems to work. I tried packaging projects on my friend’s system and it works perfectly. It seems to be a rare problem. Please help.
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.
check RunUAT.bat in the “EngineVersion”\Engine\Build\BatchFiles and compare with from git
1 Like
From deepest corners of my heart - THANK YOU! my runUAT.bat had 0 bytes size, as it turned out. I guess it happened after unsuccessful plugin rebuild for my engine version. So I copied the github runUAT.bat code. Thanks:clinking_glasses:
1 Like