The takeaway: Microsoft forced pre-release firmware onto millions of computers.
How you read that article and came to that conclusion is beyond me. No, that’s not the takeaway lol. Microsoft didn’t force the pre-release firmware onto people SSD’s.
Psaldorn@lemmy.world 1 day ago
The takeaway: Microsoft forced pre-release firmware onto millions of computers.
They’re lucky only a small percentage were damaged tbf.
FreedomAdvocate@lemmy.net.au 1 day ago
KairuByte@lemmy.dbzer0.com 1 day ago
We don’t actually know that’s the case though.
Psaldorn@lemmy.world 1 day ago
What’s the other path for this firmware being related to the update?
Maybe I’m missing something
KairuByte@lemmy.dbzer0.com 1 day ago
There are a few ways I can think of, such as coming from the factory with en engineering firmware, or a third party (manufacturer) tool pushing the update.
There’s also the question of how M$ would have even got the engineering firmware to begin with. If it did indeed get released through windows update, was it the manufacturer that provided it? M$ can’t really be expected to vet every driver they are provided.
Droechai@piefed.blahaj.zone 10 hours ago
If MS cant be expected to vet every driver they push with their autoupdater they shouldnt push drivers with the same tool that autoupdates their OS. Make one or the other. I see a use for autoupdate only MS products and a triggered updater for drivers that only gets used by the error wizard with a user prompt(whtever they call it) if they want to be able to claim no responsibility