Hey,
So about 5 hours ago i started downloading the latest update.
i download at around 2 - 3 megs a second so the download took about 40-50mins. but it’s been installing for more than 4 hours now? is there a reason it’s taking soo long?
Hey,
So about 5 hours ago i started downloading the latest update.
i download at around 2 - 3 megs a second so the download took about 40-50mins. but it’s been installing for more than 4 hours now? is there a reason it’s taking soo long?
When 4.7.4 was introduced i had the same, so i had to uninstall 4.7.3 and install 4.7.4. Now with 4.7.4 to 4.7.5 im stuck at 90% so this may be the same situation.
Same here, just finished
Hey! so I think it’s just a matter of waiting! As you can tell i’m inpatient haha.
Sorry if that doesn’t help you! ^^
It randomly jumped to like 98% after a ridiculous amount of waiting ha.
Good Luck to people updating!
I’m glad you guys got there in the end! It does sound unusual though. If you wouldn’t mind, I’d love to get the logs from you to see if there is anything in there to indicate what the holdup might have been. You can zip up the log folder and attach it, found here:
C:\Users\username\AppData\Local\EpicGamesLauncher\Saved\Logs
I had the same issue and looking thru the logs its due to some delete, copy, move process not working and the launcher giving 5 seconds per retry…
Attached is a log file where you can see I gave up around 90% lol.
I deleted the Source directory that is pointed out in the logs and after that the HDD ran like mad as it verified and it seems like it worked without the delay issue. This is from an install that was 4.7.3 → 4.7.4 → then trying to install 4.7.5. I might have interrupted the install at some point and came back the next day but darned if I can remember.
EDIT: Just to note, after deleting the files and telling it to resume install it downloaded the source files after it couldn’t find them and verified them at full speed without the previous error.
Hey thanks MathewW! This actually highlights what the issue is. There’s a bug in the file manager code where a Move() call ignores an option to handle read only flags.
The effect of this is that when the move operation initially fails in the file manager code, a half second delay is added to then retry and fail for the same reason. In the Launcher code, if the move fails we perform a copy instead, which does correctly handle read-only flags. So in theory after a long period of time the patch will eventually succeed, but with a cost of 0.5 seconds per source file - that’s a lot!
For anyone else visiting, the local fix would be to manually delete the Source folder from the installation. Your patch will then figure out by itself that it needs to get all of those files, and the move will not fail.