Slashdot Mirror
Rollout of Windows 10 April Update Halted For Devices With Intel and Toshiba SSDs (bleepingcomputer.com)
Catalin Cimpanu, writing for BleepingComputer: Microsoft has halted the deployment of the Windows 10 April 2018 Update for computers using certain types of Intel and Toshiba solid state drives (SSDs). The Redmond-based OS maker took this decision following multiple user reports about the Windows 10 April 2018 Update not working properly on devices using: Intel SSD 600p Series, Intel SSD Pro 6000p Series, Toshiba XG4 Series, Toshiba XG5 Series, and Toshiba BG3 Series.
The Intel and Toshiba issues appear to be different. More specifically, Windows PCs using Intel SSDs would often crash and enter a UEFI screen after reboot, while users of Toshiba SSDs reported lower battery life and SSD drives becoming very hot.
The Intel and Toshiba issues appear to be different. More specifically, Windows PCs using Intel SSDs would often crash and enter a UEFI screen after reboot, while users of Toshiba SSDs reported lower battery life and SSD drives becoming very hot.
Again, don't they have people check things like that before they release the update?
Of course they do. The Home and Pro users. They haven't rolled this out to Enterprise customers yet.
I love the vagueness of the messages ;-)
It looks like the SSDs that stuck to the standard drivers and interfaces did not run into any problems at all. Basically this only impacted drives that used custom drivers.
Microsoft has brainwashed you into doing their QA for them, and you even take pride in how much of your life they have wasted.
custom drivers = drivers.
They fired their QA department. It is your job now.
You realize you're posting to a conversation thread about Microsoft's failure to deliver a working driver for OEM hardware, right?
We need a new law to cover damage done by updates. Everything gets updates these days, from phones to cars. The potential for problems is high.
If an update made your car undriveable you would take it back to the dealer and drive a rental at their expense until it was fixed. Somehow Microsoft just gets away with it though.
const int one = 65536; (Silvermoon, Texture.cs)
SJW, n: "Someone I don't like, and by the way I'm a fuckwit" - AC
Security updates are already covered for the lifetime of the product under UK law. If the device becomes unfit for purpose because of unpatched vulnerabilities you can get a partial refund based on how long you have owned it.
const int one = 65536; (Silvermoon, Texture.cs)
SJW, n: "Someone I don't like, and by the way I'm a fuckwit" - AC
The incompetence Microsoft is showing at the moment really knows no bounds. It is one thing to offload your quality control to an insider program of free labour but then it's quite another to not to actually listen to any of the responses.
The problem that affected the Spring Creator's Update which caused it to be pulled in the last minute was identified in 4 separate reports months earlier by the insiders. After fixing it the insider release was so short basically any new bugs were unable to be reported.
And now this. A problem that affects a large group of SSDs including the 2017 Surface Pro. Microsoft's premier hardware product.
It's one thing to offload widespread testing onto customers. It's quite another to screw up your most premium of products. This is no longer lack of quality control, this is sheer and utter incompetence.