Windows 11 SSD issues blamed on reviewers using 'early versions of firmware' (theverge.com) 4 points by sipofwater 10mo ago ↗ HN
[–] sipofwater 10mo ago ↗ * Article Mirror: https://archive.is/FryrW* Copy the text from PCDIY! (cited in the article) at https://archive.is/sVCjC and use https://translate.google.com to translate it. [–] sipofwater 10mo ago ↗ * "The Right Solid-State Drive (SSD) Matters": https://www.kingston.com/en/blog/servers-and-data-centers/ss...* "Enterprise versus Client SSD": https://www.kingston.com/en/blog/pc-performance/enterprise-v...
[–] sipofwater 10mo ago ↗ * "The Right Solid-State Drive (SSD) Matters": https://www.kingston.com/en/blog/servers-and-data-centers/ss...* "Enterprise versus Client SSD": https://www.kingston.com/en/blog/pc-performance/enterprise-v...
[–] sipofwater 10mo ago ↗ "ButterBarTheGr8's Aug 15, 2025 comment in "Unsuitable SSD/NVMe hardware for ZFS"": https://news.ycombinator.com/item?id=45167024
[–] buzzin_ 10mo ago ↗ Well, we all know that when a library method crashes, we blame the caller. It can't be the library's fault, the user simply called it the wrong way.So, similarly, it is Windows fault that it sent some series of commands that caused the poor innocent SSDs to be invisible to BIOS until power cycle.Absolutely no fault of the SSD. None.
4 comments
[ 4.0 ms ] story [ 19.9 ms ] thread* Copy the text from PCDIY! (cited in the article) at https://archive.is/sVCjC and use https://translate.google.com to translate it.
* "Enterprise versus Client SSD": https://www.kingston.com/en/blog/pc-performance/enterprise-v...
So, similarly, it is Windows fault that it sent some series of commands that caused the poor innocent SSDs to be invisible to BIOS until power cycle.
Absolutely no fault of the SSD. None.