Uploaded September 2025 | Updated September 2026, 2 weeks ago
Microsoft has released a statement basically saying they found no connection between the recent Windows update KB5063878 and SSDs reportedly failing. But there's several reasons why I'm not convinced which I go over in this video. For example, they say the telemetry doesn't suggest an increase in failures, but I don't think their telemetry could even alert them to the drives failing. They also said they didn't receive reports from customers, but I also explain why that doesn't mean much either. Most importantly, another YouTuber JayzTwoCents was able to reproduce the issue himself and demonstrated it on video. So I explain why his demonstration actually seems consistent with the other reports about being related to heavy writing, but also possibly simultaneous reading.
JayzTwoCents' Video: youtube.com/watch?v=TbFIUu_7LIc
Time Stamps:
0:00 - Intro
1:08 - JayzTwoCents Reproduces It
2:25 - It's Probably Still The Same Cause
4:28 - Power Cycling Brings It Back
5:05 - Theory: No SSDs Are Being 100% "Bricked"
5:21 - Should You Un-Pause Windows Updates?
5:55 - Theory: It Usually Requires Both Heavy Reading & Writing
7:59 - Microsoft’s Telemetry Is Probably Missing Everything
9:45 - You Might Be Having The Issue Without Knowing
10:13 - The "Slow Crash" Explained
10:53 - Why It Wouldn’t Show Up In Telemetry
12:03 - Theory: It Makes Sense Not Showing in Telemetry
12:30 - Why Microsoft Wouldn’t Get Customer Reports
16:04 - But Microsoft Can’t Reproduce It?
16:28 - Other Thoughts
Microsoft has released a statement basically saying they found no connection between the recent Windows update KB5063878 and SSDs reportedly failing. But there's several reasons why I'm not convinced which I go over in this video. For example, they say the telemetry doesn't suggest an increase in failures, but I don't think their telemetry could even alert them to the drives failing. They also said they didn't receive reports from customers, but I also explain why that doesn't mean much either. Most importantly, another YouTuber JayzTwoCents was able to reproduce the issue himself and demonstrated it on video. So I explain why his demonstration actually seems consistent with the other reports about being related to heavy writing, but also possibly simultaneous reading.
JayzTwoCents' Video: youtube.com/watch?v=TbFIUu_7LIc
Time Stamps:
0:00 - Intro
1:08 - JayzTwoCents Reproduces It
2:25 - It's Probably Still The Same Cause
4:28 - Power Cycling Brings It Back
5:05 - Theory: No SSDs Are Being 100% "Bricked"
5:21 - Should You Un-Pause Windows Updates?
5:55 - Theory: It Usually Requires Both Heavy Reading & Writing
7:59 - Microsoft’s Telemetry Is Probably Missing Everything
9:45 - You Might Be Having The Issue Without Knowing
10:13 - The "Slow Crash" Explained
10:53 - Why It Wouldn’t Show Up In Telemetry
12:03 - Theory: It Makes Sense Not Showing in Telemetry
12:30 - Why Microsoft Wouldn’t Get Customer Reports
16:04 - But Microsoft Can’t Reproduce It?
16:28 - Other Thoughts
