This week’s “Preview” patches led to some bizarre, unexplained, and self-contradictory behavior. Here’s what we’ve been able to piece together, based on what actually happened – not on what Microsoft says is supposed to happen.
Two general sets of “Preview” patches arrived on Tuesday:
- Optional, non-security, C/D Week Cumulative Updates for Win10 versions 1809, 1903, 1909, and various Servers, but not Win10 version 2004. Microsoft stopped distributing the C/D Week patches in March because of the “public health situation,” but started pushing them again this week.
- July 21, 2020 Cumulative Update Previews for .NET Framework 3.5 and 4.8 on various versions of Win10. These are optional, non-security Preview patches released later in the month. Microsoft pushes Previews for .NET patches on Win10 infrequently; this year we’ve only seen two, one of them in January, the other in February.
They’re Previews, which means the fixes on offer are still in testing. Normal users shouldn’t go anywhere near them.
In the past, the Preview patches (for both Win10 and .NET) have appeared as a jumbled mess in the Win10 updating scheme, leading to a universal cry to avoid clicking “Check for updates.” Not long ago, doing so gave Microsoft carte blanche to install anything and everything in the update queue, including any of these “Preview” test patches lying around.
Starting with Win10 version 1903, though, Microsoft changed its wayward ways by adding an important new feature that allows you to Pause Updates. At about the same time, Microsoft implemented (but didn’t bother to document) the Download and install prompt that we now take for granted. The prompt forces you to approve an optional update before it’s installed.
Microsoft showed off a version of that option in an article last week (see screenshot).
MicrosoftDon’t expect to see that Download-and-install prompt on your machine any time soon. Microsoft hasn’t even released the “2020-07 Cumulative Update Preview for Windows 10 Version 2004.”
The Download-and-install intermediate step is an important one. It keeps normal users from accidentally installing test versions of upcoming patches – the Preview updates.
Download and install? Not.
With Microsoft’s new-found (and greatly appreciated!) implementation of the “Download and install” block on optional updates, you might expect that the two new Preview patches would appear as Download-and-install options on Win10 version 1909 (and 1809 and 1903) machines.
As I explained earlier this week, that didn’t happen. Working on two production Win10 version 1909 machines I found that, much to my surprise, the Win10 Preview and the .NET Preview behave quite differently – and neither triggered the polite “Download and install” prompt.
The .NET Preview behaved more-or-less like an old-fashioned Windows patch:
- On a Win10 version 1909 machine with Pause Updates set, clicking on Resume Updates installed the .NET Preview KB 4562900. That’s behavior consistent with (but different from) the old Check for updates sandbagging – if you Resume Updates, you get the optional, non-security .NET Preview installed whether you want it or not, with no warning. Bam.
- On a Win10 version 1909 without Pause Updates set, the .NET Preview appears in the wushowhide list. Thus, you can manually block installing the .NET Preview, if you know the tricks. Clicking on Check for updates installs the Preview, just like in the not-so-good old days.
The optional, non-security, C/D Week Win10 version 1909 Preview didn’t show up at all on my machines. Try as I might, with Updates Paused or Resumed, clicking Check for updates with wild abandon, I couldn’t get the Win10 Cumulative Update Preview KB 4559004 to install, and couldn’t even get it to show up, with or without a Download and install prompt.
That left me scratching my head.
The bifurcated Update
It turns out that Windows Update isn’t the single, monolithic system that’s advertised in Microsoft’s Download and install announcements. As @abbodi86 points out:
- .NET, Flash and CPU Microcode updates (including this week’s .NET Preview) are handled by the legacy “blast them if they check for updates” Windows Update program
- Cumulative Updates (including this week’s Win10 Cumulative Update Preview), version changes (“feature updates”) and Chromium-based Edge updates are now handled by the new, polite “Download and install” Windows Update program.
It seems that the folks at Microsoft didn’t know about the schizoid behavior, either. In the original Knowledge Base article for the .NET Cumulative Update Preview, under “How to obtain and install the update,” Microsoft’s instructions used to say:
Go to Settings> Update & Security > Windows Update. In the Optional updates available area, you’ll find the link to download and install the update.
That would correspond to the new, polite way of doing things. But sometime in the past couple of days, that KB article has been modified to say:
To download and install this update, go to Settings > Update & Security > Windows Update, and then select Check for updates.
That’s accurate – it’s the old “blast them if they check for updates” approach. There’s no record of when that change was made.
The missing optional, non-security, C/D Week Preview
On your machine, can you see KB 4559004, the Win10 version 1909 (or 1903) cumulative update Preview? (For Win10 version 1809 customers it’s KB 4559003.) Neither can I, as you can see in the screenshot below.
MicrosoftThe Preview should appear as a Download and install option – at least, that’s what Microsoft’s Chris Morrisey described a week ago:
In response to feedback, these validated, production-quality optional releases will be now called “Preview” releases for clarity, and will be offered only for Windows 10 and Windows Server, version 1809 and later…. To simplify update management for IT, these “Preview” releases will be delivered in the “C” week only…for those in the Windows Insider Program or Windows Insider Program for Business, in-development versions of these non-security updates will be released to the Release Preview Channel in the “B” week.
Which contradicts almost everything we saw this week.
Once again, @abbodi86 came to the rescue, clarifying:
You will only see the Win10 Cumulative Update Preview on machines that have joined the Release Preview Channel. As of Friday morning on this “C” week, that means Win10 1809, 1903 and 1909 machines in the Windows Insider Release Preview Channel will get the Preview offer in polite “Download and install” fashion.
You won’t see the Preview offered to Win10 version 2004 machines. It isn’t out yet – Morrisey’s comment about “B” week notwithstanding.
There’s also some (undocumented) relationship between the TargetReleaseVersion group policy and whether the Preview patch shows up. I talked about Win10 version 2004’s TargetReleaseVersionInfo in June. Apparently the policy now has some effect on versions 1809, 1903 and 1909.
Perhaps some day Microsoft will document some of this stuff. But I won’t hold my breath.
Windows Update – the user interface, the group policies, the registry settings, and interactions within the spaghetti code – has been an unholy mess for years. With new definitions, new settings, (partially) deprecated settings, conflicting settings, and completely inscrutable – sometimes demonstrably wrong – documentation, it’s a wonder that we get any work done.
We keep plugging on AskWoody.com.
Copyright © 2020 IDG Communications, Inc.
