Newsletter Archives
-
Microsoft yanks buggy second monthly cumulative update for Win10 version 1803, KB 4467682
Remember the buggy Win10 version 1803 patch that bluescreens Surface Book 2 machines?
Microsoft urged Surface Book 2 owners to boot around the bluescreen and uninstall the patch. Which is just what you want to tell your boss about her brand new, expensive Surface Book 2, right?
Looks like MS has retracted completely and pulled the patch. The KB article now says:
After installing this optional update some users have reported getting a blue or black screen with error code, “System thread exception not handled.” As a precaution, we have removed this optional update from Windows Update and Microsoft Update Catalog to protect customers. Fixes and improvements will be available in the December 2018 security update release and will include a resolution for this issue.
One can only hope that Microsoft will test this patch, for a change, before it appears.
And that “optional” stuff. That’s just a fig leaf. The second monthly cumulative updates are “optional” in the sense that you have to click on Check for Updates. Which isn’t exactly optional, to my way of thinking.
Thx Günter Born, who promises to have a blog post tomorrow that describes a second bug in the same cumulative update.
-
Microsoft acknowledges Surface Book 2 blue screen bug in Win10 1803 second monthly cumulative update
Is there a German word for when a manufacturer’s flagship hardware product bluescreens after installing the latest update to its flagship operating system?
Computerworld Woody on Windows.
Thx @b, @abbodi86, @PKCano.
-
Last month’s second Tuesday cumulative update for Win10 1803 is bricking Surface Book 2
See what I mean about testing cumulative updates before they’re rolled out?
KB 4467682, last month’s second cumulative update for Win10 1803 (the “non-security only” patch from Nov. 27) is bricking many Surface Book 2 machines. I’ve been rallying for Microsoft to start testing its “C or D week” cumulative updates before they’re released. Here’s an excellent example of why that’s crucial.
Richard Speed at The Reg reports:
Blue Screens of Death (BSOD) first began occurring shortly after the update, KB4467682, was dropped on 27 November.
The BSOD headache manifests itself by throwing a
SYSTEM THREAD EXCEPTION NOT HANDLED
error and rebooting the computer. Some users reported seeing the error repeatedly, while others are luckier, losing their work only three times a day or so.Liam Tung at ZDNet reports that:
People on Microsoft’s answers forum and on Reddit are complaining about Blue Screen of Death, or BSOD, issues that began occurring after installing cumulative update, KB4467682, released last Tuesday for Windows 10 version 1803.
Permit me to repeat, for emphasis. Microsoft should be testing these patches before they’re pushed. I’m not talking about employee-tested dogfood. I’m talking about real, live testing regimens, out in the real world.
The only way that’s going to happen is if Microsoft has a real testing method set up. Leave the ninja cats and cute narwals to the marketing folks. I’m talking about targeted tests, for people with skin in the game.
The Windows Insider Release Preview Ring is made to test cumulative updates before they’re installed. But that only works for one version of Win10.
As of this moment, the Release Preview Ring is only for Win10 1809. There should be similar test rings for all supported versions of Win10 — at the very least, 1709, 1803 and 1809. And then, gosh, Microsoft should actually use them.
I really don’t understand what’s so hard here.
Thx @MikeFromMarkham