Original Post — Direct link
Hi all,
Ive seen a surge of complaints in forums (and am currently experiencing the issue) regarding launching Siege since the update of Shadow Legacy.
Unfortunately people on console (Xbox) are unable to launch Siege due to the error
Please try again
For some reason Tom Clancys Rainbow Six(R symbol for Registered Name)Siege took too long to start. (0x8027025a).
If this could be addressed it would be appreciated as it takes several attempts to actually launch Siege.
This does not appear to be an issue with my Console as I have been successfully playing Siege for months without issue, and this started 1 day after the launch of Operation Shadow Legacy.
This, as you can imagine is a very frustrating experience for the Client with having to take 10/15 minutes, and several attempts to just launch Siege.
Thank you!
Screenshot of error can be found on the below link.

https://mobile.twitter.com/Andpersan...93173482422272
about 4 years ago - UBI-Froggard - Direct link
Hey,

Thanks for the report. If anyone who has this error comes across this thread, please let us know if reinstalling the game resolves this.
about 4 years ago - Ubi-Viral - Direct link
Hey folks!

If you are yet to can we please ask that you try the steps from the link below:

https://support.ubisoft.com/en-US/Faqs/000026628/

If the issue persists please let us know.

Thank you.
about 4 years ago - Ubi-Viral - Direct link
Originally Posted by JayGuards
It’s still happening
Can you confirm if you have the game on an internal or external hard drive?

Originally Posted by vannsmackk
I was able to fix it by power cycling the Xbox and disconnecting my Ethernet cable and reconnecting.
Awesome to hear that you managed to get this sorted!

Originally Posted by rchiav
My son has had this issue as well. I had him do a lot of different troubleshooting, including reinstalling after a console reset, nothing worked.Lastly I had him move the game from the external HD to the internal HD. After one failed start, it's now started several times after that. All other games are on the external HD and we've never had any issues with any other games or with this game before the update. Seems to be some problem with the last update and being on an external HD.
Thank you so much for letting us know what worked for you. We will pass this on to the Siege team.
about 4 years ago - Ubi-Milky - Direct link
Thanks vannsmackk for this update and Im glad to hear this fixed the issue for you.

It would seem that this error code on Xbox One can be solved for the time being, by power cycling the console and moving the game to an internal hard drive.

I would like to know if the players that have this issue with the external hard rives are using mainly traditional portable disc hard drives or newer portable SSD ones?