XSX and XB1 not reading (Seagate) external SSD after June 22 update?

Please do and let me know how it goes. Will be waiting for your feedback on this.

Hi Lucas,

Update: repair is still working on it but I found a reddit post with my exact issue , thought you might want to check it out. They say the issue was fixed, but it persists. Cheers.

https://www.reddit.com/r/xboxinside...r_a_recent_update_23rd_august_my_series_x_no/

yes, they read it right away when connected but only the one's with the update take a long time ( 20 mins) to read the SSD when not connected, if they do at all. The un updated XB1 reads it right away offline. I sent my XSX in a couple days ago , so I'll see if repair finds any issues.

Just so I can understand this right: When your consoles are connected to the internet they read your SSD right away, but if they're not connected it takes a long time for them to read it?

This is weird. And to be honest I would suggest you to format it if it was an easy step to do. But if you have 2.3TB of games, I think it would be better to not do it right now. And even because if this was a SSD issue, all your consoles would not read it or take too long to read it.

Hi Lucas,

Yes, my SSD has 78 games onboard , but it was detected by my XSX and XB!S with no problems before the June 22 update. My un-updated XB1 detects and reads it fine though. I tested my XB1S again and it took 20 minutes to read the contents of the SSD. I also sent my XSX for repair for the same reason. I'm conflicted as to whether or not I should format the drive though, but will If I have to. I tested it using "seatools" and it passed with no problems. I did notice that once I connected to the internet that the XB1s and XSX detected the SSD right away, like it used to do offline. The series S always has to be connected to the internet If I remember right, so I would guess the functionality is different and my issue would be unique to the series X and XB1s. I have about 700 gigs of free space left on the drive ( it's a 3 terabyte SSD by seagate ), so I don't think it's a lack of memory issue.

Thanks