So far nothing has helped and the download keeps starting and stopping constantly, and when it does run, its running obscenely slow. I let it run overnight last night and this is more or less how far it made it. Is there any other ways to fix this?
Hey there @Apollosyx! Welcome to the community! It seems like the write speed is incredibly low, which is stopping the download itself from continuing while it waits writes the last data. This could be related to writability issues more than reflecting on your download. What’s your hard drive’s regular write speeds for other applications in comparison?
Hello there.
The write speed is between 700 - 1000MB/s, attempting the install to an external SSD. Watching the task manager for this while its running and its barely scraping 1% on utilization.
Just double tested moving a large file to it manually and it moved it at approx 700MB/s.
Looks like the drive itself is good in that case. This slowdown is extreme, since nothing else is having this issue, the launcher could be having issues directly. You could enable the launcher logs, try the download again, then check the laws for possible errors.
Long shot question, do you have any Antivirus that scans every file downloaded from other applications? This could be stalling the process.
In the meantime I redirected my VaultCache to that same drive and was able to download a decent sized sample project to it at a decent speed.
I restarted the download of the original DevKit I was trying to install and its started out at a decent pace but is still getting those intermittent breaks and stop. Checking the log file seems to show the same error repeating.
[2025.02.19-07.34.08:291][160]LogHttp: Warning: 000001655F35A030: HTTP request timed out after 10.00 seconds URL=http://download.epicgames.com/Builds/Org/o-usvfbmlqdt678vrp36qvm2d5cz2cpr/985dc4d67ff142588b6393c46b1dff84/default/ChunksV4/54/7D74B72856986E1D_DF5361F4431D856949929582C9D0CE29.chunk
[2025.02.19-07.34.08:291][160]LogHttp: Warning: 000001655F35A030: request failed, libcurl error: 0 (No error)
[2025.02.19-07.34.08:291][160]LogHttp: Warning: 000001655F35A030: libcurl info message cache 0 (Found bundle for host download.epicgames.com: 0x165234476d0 [can pipeline])
[2025.02.19-07.34.08:291][160]LogHttp: Warning: 000001655F35A030: libcurl info message cache 1 (Re-using existing connection! (#665) with host download.epicgames.com)
[2025.02.19-07.34.08:291][160]LogHttp: Warning: 000001655F35A030: libcurl info message cache 2 (Connected to download.epicgames.com (18.160.60.38) port 80 (#665))
[2025.02.19-07.34.08:291][160]LogHttp: Warning: 000001655F35A030: libcurl info message cache 3 (Closing connection 665)
[2025.02.19-07.34.08:330][161]LogCloudChunkSource: FAILED: http://download.epicgames.com/Builds/Org/o-usvfbmlqdt678vrp36qvm2d5cz2cpr/985dc4d67ff142588b6393c46b1dff84/default/ChunksV4/54/7D74B72856986E1D_DF5361F4431D856949929582C9D0CE29.chunk
[2025.02.19-07.34.09:661][201]LogHttp: Warning: 000001655F35F6E0: HTTP request timed out after 10.00 seconds URL=http://download.epicgames.com/Builds/Org/o-usvfbmlqdt678vrp36qvm2d5cz2cpr/985dc4d67ff142588b6393c46b1dff84/default/ChunksV4/08/DD25DC32CBA2FE0C_3829369443B5F8D391359DB2A349CF8E.chunk
[2025.02.19-07.34.09:661][201]LogHttp: Warning: 000001655F35F6E0: request failed, libcurl error: 0 (No error)
[2025.02.19-07.34.09:661][201]LogHttp: Warning: 000001655F35F6E0: libcurl info message cache 0 (Found bundle for host download.epicgames.com: 0x165234476d0 [can pipeline])
[2025.02.19-07.34.09:661][201]LogHttp: Warning: 000001655F35F6E0: libcurl info message cache 1 (Re-using existing connection! (#677) with host download.epicgames.com)
[2025.02.19-07.34.09:661][201]LogHttp: Warning: 000001655F35F6E0: libcurl info message cache 2 (Connected to download.epicgames.com (18.160.60.38) port 80 (#677))
[2025.02.19-07.34.09:661][201]LogHttp: Warning: 000001655F35F6E0: libcurl info message cache 3 (Closing connection 677)
[2025.02.19-07.34.09:728][203]LogCloudChunkSource: FAILED: http://download.epicgames.com/Builds/Org/o-usvfbmlqdt678vrp36qvm2d5cz2cpr/985dc4d67ff142588b6393c46b1dff84/default/ChunksV4/08/DD25DC32CBA2FE0C_3829369443B5F8D391359DB2A349CF8E.chunk
I may have jinxed it and since posting that its back down to running in about the state it was in the original screenshot.
Only new error is :
[2025.02.19-07.47.14:971][499]LogEOSMessageService: Error: Unable to find port.
It seems the API requests were failing, then the connection failing possibly due to being unable to use the expected port (port 80 in this regard). What resource are you currently downloading? These errors make me think my initial appraisal that the write speed could be incorrect or clearly not the full picture.
Its attempting to download and install the Ark DevKit
Ahhh understood. I am going to try the resource on my side and see if there are any issues with the requests. In the meantime, does downloading a version of the Engine have the same disparity?
Not that I’ve noticed. The engine is already installed but I never saw any hangups on it. I tested downloading a few of the 50+ GB Fab projects to that drive and they also didn’t seem to have any hang-ups.
Even after restarting the devkit download it’s only progressed 28.6GB in the hour and a half or so.
Could be an issue with the chunk sizes, but I’ll have to verify when I install it. I didn’t have a drive on hand that could handle the 800gb check at the moment without doing some cleaning. Might have to dust off an HDD or spoof the requirement in the meantime to test it.
No worries. I am not in a huge rush to download it and am learning in the base engine in the meantime anyway. Just wanted to get ahead of it since it would take an actual week to download when it’s sputtering like that.
A few other error codes I was able to find in the log:
[2025.02.19-08.01.20:379][458]LogEpicConnectMessageRouter: Warning: FEpicConnectMessageRouter::GetMessageType(): Couldn't deserialize Epic Connect {"correlationId":"743f9e55-492c-4901-99dd-b42631895716","timestamp":1739952081856,"id":"ZWE1MzY5ZDkxN2MyNDRjZT","connectionId":"0242acfffe110002-00000001-03248e59-01ed7fc5609f4195-7870bf46","payload":{"accountId":"e61776579c7844299663cceb2a35f46a","status":"online","perNs":[{"status":"online","activity":{"value":"???? ????????????"},"ns":"Fortnite","props":{"X_NonEOS_ProductName":"Fortnite","X_NonEOS_IslandCode":"9862-4661-6699","X_NonEOS_IsPlaying":"false"},"conns":[{"id":"V2:Fortnite:PS5:792190429832791845:C1611ED23CC54226910C6B3269C4351C","props":{}}]},{"productId":"prod-fn","appId":"fghi4567FNFBKFz3E4TROb0bmPS8h1GW","status":"online","activity":{"value":""},"ns":"62a9473a2dca46b29ccf17577fcf42d7","props":{"EOS_ProductVersion":"++Fortnite+Release-33.30-CL-39768313","EOS_Platform":"PSN","EOS_IntegratedPlatform":"UNKNOWN","EOS_ProductName":"Fortnite","EOS_Lobby":"{"version":3}","EOS_OnlinePlatformType":"1000","EOS_Session":"{"version":3}"},"conns":[{"id":"0242acfffe110002-00000001-03271479-a5bb6efd7f6485f2-adbc95ce#sub-eas-1721718756","props":{}}]}]},"type":"presence.v1.UPDATE"}
[2025.02.19-08.01.20:379][458]LogEpicConnectMessageRouter: Warning: FEpicConnectMessageRouter::Route(): Message type empty or JsonMessage failed to parse: {"correlationId":"743f9e55-492c-4901-99dd-b42631895716","timestamp":1739952081856,"id":"ZWE1MzY5ZDkxN2MyNDRjZT","connectionId":"0242acfffe110002-00000001-03248e59-01ed7fc5609f4195-7870bf46","payload":{"accountId":"e61776579c7844299663cceb2a35f46a","status":"online","perNs":[{"status":"online","activity":{"value":"???? ????????????"},"ns":"Fortnite","props":{"X_NonEOS_ProductName":"Fortnite","X_NonEOS_IslandCode":"9862-4661-6699","X_NonEOS_IsPlaying":"false"},"conns":[{"id":"V2:Fortnite:PS5:792190429832791845:C1611ED23CC54226910C6B3269C4351C","props":{}}]},{"productId":"prod-fn","appId":"fghi4567FNFBKFz3E4TROb0bmPS8h1GW","status":"online","activity":{"value":""},"ns":"62a9473a2dca46b29ccf17577fcf42d7","props":{"EOS_ProductVersion":"++Fortnite+Release-33.30-CL-39768313","EOS_Platform":"PSN","EOS_IntegratedPlatform":"UNKNOWN","EOS_ProductName":"Fortnite","EOS_Lobby":"{"version":3}","EOS_OnlinePlatformType":"1000","EOS_Session":"{"version":3}"},"conns":[{"id":"0242acfffe110002-00000001-03271479-a5bb6efd7f6485f2-adbc95ce#sub-eas-1721718756","props":{}}]}]},"type":"presence.v1.UPDATE"}
[2025.02.19-08.37.44:408][967][MainRouter] Best Match: invalid - [83] states compared
[2025.02.19-08.37.44:408][967][MainRouter] Canceling in progress navigation. New command issued.
[2025.02.19-08.37.44:408][967][MainRouter] Navigation Canceled.
[2025.02.19-08.37.44:408][967][MainRouter] GoToUrl('/settings')
[2025.02.19-08.37.44:408][967][MainRouter] Resolved To: '/settings'
[2025.02.19-08.37.44:408][967][MainRouter] Best Match: invalid - [83] states compared
[2025.02.19-08.37.44:408][967][MainRouter] Navigation Canceled.
[2025.02.19-08.37.44:408][967]LogPortal: Warning: NavigationUriHandler: Invalid location /settings. Will attempt to go back to the previous location
[2025.02.19-08.37.44:408][967][MainRouter] GoToUrl('/ue/community')
[2025.02.19-08.37.44:408][967][MainRouter] Resolved To: '/ue/community'
[2025.02.19-08.37.44:410][967][MainRouter] Best Match: ue.community
[2025.02.19-08.37.44:410][967][MainRouter] Navigation Stopped. Already at location.
[2025.02.19-08.37.44:410][967][MainRouter] Navigation Canceled.
[2025.02.19-08.37.44:410][967]LogUriHandler: Started processing URI [com.epicgames.launcher://settings] with OnSignInUriHandler
[2025.02.19-08.37.44:411][967]LogUriHandler: Started processing URI [com.epicgames.launcher://settings] with SettingsUriHandler
[2025.02.19-08.37.44:411][967][MainRouter] Navigation Canceled.
The first message wasnt very present early on but seemed to have started occuring every few minutes after letting it run for about 5-6 hours.
Second one is pretty common as well but has slight variations in its messaging here and there.
Edit:
This may be a stretch but could the log file itself be the issue? The size of that file has grown absurd, something around almost 200mb with the install only at 12%. Would the constant writing to that explain the gradual decrease in speed? It’s definitely getting slower and slower installing as it goes. I cannot figure out how to disable the logging to test though, turning off debug logging doesnt actually do anything, it keeps writing regardless.
Interesting. I started the installation and watched it passively while working on other things until the end, and only once did it hitch, but without a corresponding error in the logs. There are some API failures on my side, but it kept chugging along at relatively good speed.
So let’s try a couple things.
Head over to C:\Users\YourUser\AppData\Local\EpicGamesLauncher\Saved\Config\Windows
Make a backup of the Engine.ini (it’s probably blank but might not be). Then in the active one, add these lines:
[HTTP]
HttpTimeout=10
HttpConnectionTimeout=10
HttpReceiveTimeout=10
HttpSendTimeout=10
[Portal.BuildPatch]
ChunkDownloads=3
ChunkRetries=20
RetryTime=0.5
These vars are from a thread about a different issue from 2016 so it might not be relevant, but worth a try in this case.
I put those in there before posting the original thread, I found the same thread mentioning that as you may have. There were a few others that suggested disabling windows defender, running as admin, and putting those same lines in defaultengine.ini as well and its the same.
I even tried reinstalling the whole launcher earlier and its the same. Having restarted it a few times I’ve definitely noticed its a progressive slowdown, it will crank it out earlier on but then gets slower and slower and slower.
Even resuming the download takes several hours, as the file verification starts grinding down in speed the longer it goes, which is why it started to seem like needing to constantly write to the ever growing log file actually may be an issue.
I did the reinstall of the launcher about 4 hours ago, and its still trying to “resume” the download, reading from the disk, bouncing between 20kb/s and 0kb/s, and the log file is up around 75mb now.
Did yours manage to download the entire install? A few of the total resets of the installation and it always seem to start dragging about 30-40gb in, which doesnt make any sense, since I was able to download larger files than that from FAB in just a few minutes with no issue.
I believe it completed the entire download, though didn’t test the kit as it didn’t seem pertinent before uninstalling it. I don’t believe the log writing could be causing these issues, even the writing itself is a significant amount.
After many days it did finally get finished downloading, but now it has ceased all activity and is sitting at 82%. No noticeable activity from the drive on task manager. It’s just sitting. I am at a loss for why this has become such a huge process to even get it to install.
[2025.02.22-14.59.17:647][795]LogBuildPatchServices: File construction complete
[2025.02.22-14.59.18:219][829]LogBuildPatchServices: Staged install complete
[2025.02.22-14.59.18:303][834]LogBuildPatchServices: Running backup and stage relocation
[2025.02.22-15.03.27:917][696]LogEOSMessageService: Error: Unable to find port.
[2025.02.22-15.08.27:919][556]LogEOSMessageService: Error: Unable to find port.
[2025.02.22-15.13.27:928][413]LogEOSMessageService: Error: Unable to find port.
[2025.02.22-15.18.27:934][275]LogEOSMessageService: Error: Unable to find port.
[2025.02.22-15.23.27:927][142]LogEOSMessageService: Error: Unable to find port.
[2025.02.22-15.28.27:929][ 9]LogEOSMessageService: Error: Unable to find port.
[2025.02.22-15.33.27:950][874]LogEOSMessageService: Error: Unable to find port.
[2025.02.22-15.38.27:942][744]LogEOSMessageService: Error: Unable to find port.
[2025.02.22-15.43.27:956][611]LogEOSMessageService: Error: Unable to find port.
[2025.02.22-15.48.27:965][480]LogEOSMessageService: Error: Unable to find port.
[2025.02.22-15.53.27:958][351]LogEOSMessageService: Error: Unable to find port.
[2025.02.22-15.58.27:982][226]LogEOSMessageService: Error: Unable to find port.
[2025.02.22-16.03.27:982][102]LogEOSMessageService: Error: Unable to find port.
[2025.02.22-16.08.27:992][979]LogEOSMessageService: Error: Unable to find port.
[2025.02.22-16.13.27:989][857]LogEOSMessageService: Error: Unable to find port.
[2025.02.22-16.18.27:998][738]LogEOSMessageService: Error: Unable to find port.
[2025.02.22-16.23.27:991][617]LogEOSMessageService: Error: Unable to find port.
[2025.02.22-16.28.27:998][496]LogEOSMessageService: Error: Unable to find port.
[2025.02.22-16.33.28:015][380]LogEOSMessageService: Error: Unable to find port.
[2025.02.22-16.38.28:041][494]LogEOSMessageService: Error: Unable to find port.
[2025.02.22-16.43.28:044][993]LogEOSMessageService: Error: Unable to find port.
[2025.02.22-16.48.28:037][981]LogEOSMessageService: Error: Unable to find port.
[2025.02.22-16.53.28:069][998]LogEOSMessageService: Error: Unable to find port.
[2025.02.22-16.58.28:086][ 9]LogEOSMessageService: Error: Unable to find port.
[2025.02.22-17.03.28:106][988]LogEOSMessageService: Error: Unable to find port.
[2025.02.22-17.08.28:115][ 76]LogEOSMessageService: Error: Unable to find port.
Starting to think at this point I should just accept I am not meant to use this thing. It’s been tying up my launcher and running for a week now. There’s nothing I can find wrong, every individual piece of this works, its just not working together for this download.
I too have been experiencing the graphics stopping at 82 percent. But after investigating the logs, I have learned that it is still running – but very, very slowly.
Try monitoring it from PowerShell using this:
Get-Content C:\Users,UserName>AppData\Local\EpicGamesLauncher\Saved\Logs\EpicGamesLauncher.log -Wait -Tail 10
Also, try adding an incoming firewall rule to account for EPICs requests: 80, 433, 443, 3478, 3479, 5060, 5062, 5222, 6250, and 12000-65000
Having same issue. Stalled at 82 percent. My other PC completed it all in one hour. Sadly, I can’t use that PC for development. This sucks bad.