Microsoft's "fixed" 1809 update still has serious problems

Faced with the rapidly-escalating PR nightmare of their data-deleting 1809 update to Windows 10, Microsoft first halted the update's rollout, and then hastily patched it before continuing onward. It looks like they once again skipped crucial testing phases, though, because the updated update has issues of its own, including an apparent BSOD issue. That's right, years after Windows 7's stability had largely succeeded in relegating the Blue Screen of Death to Windows history, MSFT's cascading Windows-as-a-Service failures may now have resurrected it as a modern reality.

From Neowin:

Earlier this week, Microsoft pushed out its monthly set of updates to various versions of Windows 10, including version 1809. It seems, however, that this patch carries its own major problems. Users all over the internet are reporting that their devices are getting into a blue screen of death (BSOD) after the update, preventing them from booting.

[...] 

The problem doesn't seem to affect just the feature update released last week, but users on the April 2018 Update are apparently facing similar issues. While most people reporting the error are using HP devices, Neowin user Mike Steel heard from Microsoft's support that it actually affects other brands as well and that the patch has since been pulled from Windows Update.

The number of issues found in the latest release of Windows 10 seems to suggest that Microsoft needs to rethink the way it deploys its updates. It also may leave some wondering if the Insider program, which is meant to help shape the operating system, has lost its way over the past four years.

Yes, Microsoft, you've also earned a facepalm. Congratulations?

To say that the Insider program has "lost its way" seems to be overly generous; it's increasingly clear that the Insider program is simply not an adequate substitute for the sort of disciplined, rigorous testing that MSFT  simply doesn't do anymore, having laid off their product testers.

It's long past time for MSFT to simply admit that their Windows As A Service strategy simply doesn't work, and that using their WX 10 Home user base as involuntary guinea pigs, trouble-shooing the OS for the benefit of Microsoft's valued Enterprise customers with no choice or compensation, is not only unethical, but actively damaging. And that damage isn't limited to WX Home users; MSFT's brand and reputation deteriorate further with each new failure of their WaaS regime, and especially undermines their efforts to convince potential Enterprise customers that WX+WaaS is just fine.

WX+WaaS is not fine; it's broken, a fact which is becoming more evident as each new failure is triggered by MSFT's failure to recover from the last failure.