- cross-posted to:
- technology@lemmy.world
You must log in or register to comment.
Microsoft keeps layoffs QA teams to use part from insiders (so free testing) and part hiring in India that is cheaper. Now we are seeing the consequences of this.
Windows is the only OS that managed to go back in time and reach its alpha stage again. Fascinating.
Translated from Japanese by Grok AI
Wow, so neowin chose to use the Nazi AI?
That’ll be the last click they ever get from me then
Eh… Reading the article it’s clear what’s causing this are faulty SSD drives. Windows might stress their crappy firmware, but the fault lies on the hardware.
If these drivers are WHQL, then it’s absolutely on Microsoft too for not having proper tests in place with software updates for this hardware. They are a multi trillion dollar company raking in record profits with their own testing system. If they released an update, and drives started failing on drivers they approved, they are just as much at fault
Sorry, I made a typo, I meant drives, not drivers.
Firmware is software embedded in the SSDs, and Windows has no control over them. Microsoft can’t fix this and the SSD manufacturers here are at fault.
Do note that I escaped Windows in 2017, and wouldn’t like to go back to it because of how nauseatingly user-hostile it is.
Ah, understood, and in that case I agree with you, if an SSD fails trying to do a constant write of 60GB it’s a pretty shit SSD. But it does seem like something weird is happening if these failures are only occurring with this windows update. Like someone with a fiber connection, one of these SSDs, and a new steam game purchase needing 110GB of storage would also have encountered this failure, if it was purely the SSD, since it didn’t occur before the update, and isn’t occurring on linux
