Microsoft pushes yet another version of KB 4023057

In the perennial bad news department:

Yesterday Microsoft released yet another version of KB 4023057, the Update to Windows 10, versions 1507, 1511, 1607, 1703, 1709, and 1803 for update reliability. This is the 20th or 30th version of the patch.

As I said on Nov 19, the last time it was updated:

@ch100 has offered the only explanation that makes sense to me:

KB4023057 was and still is one of the most weird and unexplained updates in the recent times. This update has never been offered to WSUS, but only to Windows Update. This would indicate that it meant for unmanaged end-users and unmanaged small business users…

This patch may be harmless, but why it was released and where it actually applies, it is still a mystery.

It’s most likely associated with the 1809 rollout, although why it didn’t appear in early October when 1809 first raised its ugly head leaves me baffled.

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.

Heads up! Microsoft finally releases a new build of Win10 version 1809

KB 4469342 (its fifth iteration, I believe) just went out the Windows Update chute. It brings Win10 version 1809 up to build 17763.168.

The main 1809 page lists several fixes, including one for the mapped drive reconnection bug. It also lists active blocks for Win10 1809 machines running Morphisec SDK, some Intel display drivers, F5 VPN, an older Trend Micro OfficeScan version, and AMD Radeon HD2000 and HD4000 GPUs.

You should assume that you’ll get bumped up to 1809 sooner or later, unless you actively block it. Presumably the rollout push will go with all due deliberation.

Computerworld Woody on Windows.

Michael Horowitz: Killing Windows Update on Win10

Horowitz has a fascinating “cheat sheet” reviewing various methods of blocking Win10 updating.

With Windows 10, there are three aspects to disabling Windows Update: shutting down multiple Services, disabling many Scheduled Tasks and preventing the parts of Windows Update that can not be shut down from phoning home. Microsoft has limited the first two options, some services and started tasks can not be disabled, even by Administrative users. And, like the Walking Dead, some services and tasks that we can disable, get re-enabled over time.

It’s a very thorough look at a very tough — and timely — topic.

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

New Win10 1809 Release Preview beta build 17763.168, and another acknowledged bug

Credit: Helar Lukats

That’s the fourth version of KB 4469342, only available to those in the Windows Insider Release Preview Ring.

Much to its credit, Microsoft’s waiting until this Win10 1809 is ready.

Computerworld Woody on Windows.

Third version of Win10 1809 build 17763.167 has just been posted on the Windows Update site

Per @abbodi86

1809 CU KB4469342 got third release (but still version 17763.167)

http://download.windowsupdate.com/d/msdownload/update/software/updt/2018/11/windows10.0-kb4469342-x64_7bfd1fd5075c9bbda80cc5134f26204b1e5bc3df.cab

http://download.windowsupdate.com/d/msdownload/update/software/updt/2018/11/windows10.0-kb4469342-x86_eb7d9373ca1b44272eab193e4e1f95e22f497a51.cab

These are NOT for regular Windows users. They’re direct links into Microsoft’s Windows Update holding area, presumably for admins who want to test machines without going through the usual Windows Insider sign-up process.

No idea what’s different.