After installing "Assassins Creed Origins" Uplay is trying to update the game. After fully downloading the update (the progress bar is all the way up to the right) Uplay says that the download couldn't start and the "Start" button doesn't appear.
There is no start button, I can only update the game again or chech system files so I can never even start the game...
I could once solve the issue by manually moving some readme files in the Uplay_download folder that are not moved to the support folder. But now I can't get Uplay to not downloading the update again and again.
So there is no one with the same problem? The strange thing is that updates for other Ubisoft games always worked.
I guess what might work is to first move all respective downloaded files (from Uplay_download) to their intended location. But there seem to be a file somewhere telling
the game the update has not worked and to redownload. Does anyone know where this information might be stored?
Maybe you should try to reinstall it all to another drive?
I had nearly the same experience when I tried to reinstall the game from disc after patch 1.05 totally messed up the smoothness of the game for me. I wasn't able to start the game until I downloaded another 2 GB of data and that obviously included update 1.05. There was no "play button" and only the "download button" was there, which was weird. So my mission to bring it back to 1.03 finally failed. Too bad, because I read in the corresponding steam forum that some folks were able to bring the game back to 1.03. Maybe somebody will find a solution for Uplay, OR the devs will hopefully come up with some sort of a new patch or hotfix to fix all the issues that came with 1.05. Fingers crossed.
Hi there!
If you are still having this issue, I recommend verifying your game files (Depending if you purchased the game through Steam or Uplay). This should check to see if you have any corrupted files. You can also try uninstalling and reinstalling the game. I also recommend these download troubleshooting steps. If none of that helps, please make a ticket with a screenshot of the error you receive. Please also attach a Dxdiag and MSINFO— these files will help us locate what could be causing the issue. You can find instructions on how to create and submit these files on our support site here. Thanks!