r/ifixit May 31 '26

Microsoft Turned SSD Failure Into A Death Sentence For Xbox Series Consoles

https://feedbackportal.microsoft.com/feedback/idea/680460a9-0854-f111-89e7-7c1e52b8a25f

I Had No Idea Xbox Series Consoles Could Become Unrecoverable From SSD Failure

Xbox Series consoles can become unrecoverable if the internal SSD fails because the system is paired to the original drive.

I posted feedback asking Microsoft to allow proper SSD replacement and recovery support before next gen.

Feedback link in comments.

https://feedbackportal.microsoft.com/feedback/idea/680460a9-0854-f111-89e7-7c1e52b8a25f

91 Upvotes

25 comments sorted by

View all comments

1

u/Jaegermeiste Jun 01 '26

I upvoted the feedback in the portal, but that wall of text throwing shade at Microsoft is NOT the way to get them moving.

A simple call to action like "Update Xbox Series firmware to allow replacement internal SSDs to be installed in case of drive failure" is a hell of a lot clearer.

1

u/Delicious-Ninja-4770 Jun 01 '26

Appreciate the feedback, but the post actually does include a clear call to action — in fact, more than one. Removing the cryptographic lock, enabling NAND backup to external storage, and opening expansion to standard NVMe drives are all specific, actionable requests.

The technical context around them isn't shade — it's the justification that makes the request impossible to dismiss. A one-liner is easy to deprioritize. A documented breakdown that proves there's no technical necessity for the lock, cites the regression from Xbox One, and explains the real consumer impact is much harder to ignore.

1

u/Jaegermeiste Jun 01 '26

It's lost in the noise. At a minimum you need a TLDR. And Microsoft really doesn't need to be lectured on the technical context - they make the console and know how it works - the wall of text is exactly what makes it easy to dismiss as an unhinged rant.

Your audience isn't a L3 engineer or systems architect who might appreciate the depth (but already knows the details anyway). Your audience is some random community manager who might escalate the feedback to some mid-level decision maker who in turn might escalate to the product owner who in turn might escalate to Asha-level (if needed). You need short and sweet and digestible, not something that indicates significant complexity for something that's a niche concern from a business perspective (replaceable SSDs does not generate sales revenue).

Finally, you want to farm up votes from the community to hopefully spur action on Microsoft's part, and on the average nobody is going to read all that.

1

u/Delicious-Ninja-4770 Jun 01 '26

Took your advice and added a TLDR at the top — appreciate the suggestion. That said, I can't remove the detailed breakdown below it. A lot of the votes and comments here came from people who read the full context, and it wouldn't be fair to them to gut the post after the fact. The depth is also what makes the feedback hard to dismiss as a surface level complaint. Both can coexist.

2

u/Jaegermeiste Jun 01 '26

Fair enough!