Launcher crash while updating

Development Platform & Builds
, , , ,
1

Hello!
I have a really odd problem.
I was using UE4 and nothing strange happened. So far!

Since the last update (4.0.2) my launcher crashes.
To be specific:
It downloads everything, takes a bit time, but works.
After that at 90% the text changes to “Verifying Installation”.
The launcher is working, I can stop and pause any time, but after like one hour of processing it crashes with this:

3346-error.png
3346-error.png1010×719 310 KB

I have no idea what could this mean.
This never happened before, everything was running smoothly (except when I opened Blueprint, It takes some time to load that up, but it works every time.)

I already tried reinstalling UE4, didn’t help.
I’m using Windows 8 Pro.

Thanks for any help!

2

Hi CREFFER,

We haven’t seen this issue before.

  • Can you confirm that your Launcher is version number 1.0.0-2039063? (found in the bottom-left corner)
  • Have you already tried restarting your computer?
  • Please upload the log, in a Zip file, from C:\Users\USER.NAME\AppData\Local\UnrealEngineLauncher\Saved\Logs

Thanks

3

Hello!

Yes, my launcher is version number 1.0.0-2039063.
I tried restarting my PC, didn’t help.

Today I gave it another try. Something strange happened:

3402-crash.png
3402-crash.png539×1000 202 KB

As you can see my version is correct.
I started the update;
Then it crashed with that error message.
I assumed Betrayer.exe belonged to a game called Betrayer. It was made in UDK, I played it in the last few days. It wasn’t running, it’s not intalled on my PC anymore.

My logs:
[link text][2]

4

After another reinstall, It gives me the error it did first time,
this is what happens:

3421-error+2.jpg
3421-error+2.jpg1010×2280 353 KB

My log this time:
[link text][2]

5

Hi Creffer! Just wanted to let you know I am looking into your issue now. In the meantime, it would be helpful to see a dxdiag from the system you are running on if that is ok?

6

Update: I’m still looking into the crash you are seeing, but I have noticed something I want to warn you about in advance. Some of your logs contain examples of output that suggest a device problem. I’d recommend - just in case - backing up any important data you have on your machine. The output suggests potential issues with drive E:. I’m not saying there’s definitely a problem, but I have not seen those in other peoples’ logs before and it would be a shame if you lost any data.

In more detail, there are some file copy issues that report Windows Error Code 1117 (ERROR_IO_DEVICE), and also some file read issue that report “Error=I/O eszközhiba miatt nem lehetett a kérést végrehajtani.”

7

Hi Swifty!

I think the easiest way might be to reinstall my whole Windows.
If there is no other way, I might do that on the weekend.
Oh yeah, here is my dxdiag.
Thanks for your time!
link text

8

Thanks for that. If you are not having problems with anything else, there’s probably no need to reinstall windows :). Especially if you were able to install and use Unreal Engine 4.0.1 just fine. I haven’t managed to find the root of the issue yet. But if you like one thing you could try is to make sure the Launcher tries to install the latest editor as a fresh copy:-

  1. Close the Launcher
  2. Delete the folder “E:/Program Files/Unreal Engine/Launcher/PatchStaging”
  3. Delete the folder “E:/Program Files/Unreal Engine/4.0”
  4. Delete the file “C:/ProgramData/Epic/UnrealEngineLauncher/Data/Manifests/40003.manifest”
  5. Run the Launcher again
  6. Press the Install button
9

Thanks for the answer.
I deleted PatchStaging, I still need to delete the 4.0 folder, but I can’t do that somehow. It starts up the deleting process, but when the window closes it’s still there. Oh well, I’ll figure out something!

10

Hmm that is odd! Can you rename it instead?

11

Yeah I can!

12

Ok, might be a workaround for now then! Don’t forget step 4… And then try the install!

It might be good to check TaskManager for any rogue exe from editor/launcher that is stuck running, probably unlikely though

13

Yay!
That solved it finally, thanks for your help! :slight_smile:

Edit:
Holly cow,
What else, It fixed the BluePrint loading time too! Many thanks!

14

Great news! Glad you’re up and running again. Remember to keep an eye on that E: drive of yours, it still concerns me a little that you were having so many device IO errors :slight_smile: