Why am I unable to update from 4.0.1?

I am unable to update from 4.0.1. I am running Windows 7 and have Unreal Engine installed on my secondary hard drive. As soon as I click the update button it flashes “In Queue” and returns to being an update button. Content Examples shows “Not Ready”.

Update: Tried to uninstall once again and use the latest installer and experienced the same problem. It downloaded “ContentExamples_4.0Production-Windows[2014.04.02-17.08.21]” and stored it in the Backup folder. It appears to be the same data as yesterday.

Update: Still having this problem. Any ideas?

You should be able to run 4.0.1 directly from C:\Program Files\Unreal Engine\4.0\Engine\Binaries\Win64\UE4Editor-Cmd.exe

Or

It’s a 4 Gig download for the update and 7 for the full download. I would hope that if you delete the installation, it will download 4.0.2 instead of 4.0.1.

I have it installed on my secondary D drive but following that filepath for my install drive allows me to access the editor. Uninstalling the program and reinstalling causes 4.0.1 to be installed once again with the same problems updating.

No problem. It seems like I might already have the update but the client for some reason doesn’t detect it, since my install directory is 12.7 GB. 4 GB is stored in the Backup folder under ContentExamples.

OK, at least you can launch the old version. Someone else will have to look into the other problem, sorry. That kind of ‘isn’t good’ a 7 GB download followed by a 4 GB update.

Hi Cardern, Sorry you’re having issues, and sorry it’s been a while! I have only just found this post. Could you zip up the Logs folder and attach it please?

C:\Users\USER.NAME\AppData\Local\UnrealEngineLauncher\Saved\Logs

You can delete the backup folder if you like. It gets created when something was installed but there was already files in the destination directory that we didnt recognise - a safety measure to stop us from overwriting somebody’s work :slight_smile:

Ah I didn’t know that these existed. I realized in looking that the admin flag was false, so I tried running the launcher as administrator and it worked. Thanks!

Ah ok well I’m glad you’re up and running now. We should still be able to work properly without admin rights though, so if it’s ok with you, it’d be great to see all the logs anyway to find out why this may be happening. It’s odd that you were OK to install 4.0.1 originally but not the patch :), must be a bug somewhere

Thank you :slight_smile:

The solution to my problem was to run the launcher as administrator as I indicated in my response to Swifty above.

Log File
Good point, here is my most recent log file from before I updated. They all seem to be relatively identical and I pulled out personal information.