Windows Update’s bifurcated mess

Topic

New Reply

Now we know why this week’s Preview patches behave so strangely. Details coming in Computerworld Woody on Windows. Thx, @abbodi86!
[See the full post at: Windows Update’s bifurcated mess]

3 users thanked author for this post.

abbodi86, Alex5723, Elly

Reply | Quote

Replies

This scenario does bring to mind the old GWX click-on-red-to-install disaster.

On permanent hiatus {with backup and coffee}
offline▸ Win10Pro 2004.19041.572 x64 i3-3220 RAM8GB HDD Firefox83.0b3 WindowsDefender
offline▸ Acer TravelMate P215-52 RAM8GB Win11Pro 22H2.22621.1265 x64 i5-10210U SSD Firefox106.0 MicrosoftDefender
online▸ Win11Pro 22H2.22621.1992 x64 i5-9400 RAM16GB HDD Firefox116.0b3 MicrosoftDefender

Reply | Quote

There’s no record of when that change was made.

Bottom line says, “Last Updated: Jul 22, 2020”.

Reply | Quote

You’re right. The KB article was originally posted on July 21, and updated on July 22.

Reply | Quote

[Alex5723]

” …and Chromium-based Edge updates are now handled by the new, polite “Download and install” Windows Update program.”

I don’t think ChrEdge updates has anything to do with “Download and Install”. ChrEdge has its own update mechanism (following Chrome releases).

• This reply was modified 4 years, 10 months ago by Alex5723.

Reply | Quote

I’m still waiting to see – and relying on y’all to tell me if you see something.

Reply | Quote

I ment the First Time Installer update KB4559309, it’s handled by UUP

although i don’t get it nowadays

2 users thanked author for this post.

woody, Elly

Reply | Quote

I’m on Win10 home 18363.959 and here is what I see.

Reply | Quote

Is this machine in the Windows Insider Release Preview Ring?

Do you have the TargetReleaseVersionInfo registry key?

Reply | Quote

woody wrote:

Do you have the TargetReleaseVersionInfo registry key?

I have the TargetReleaseVersionInfo key.

2020-07 Cumulative Update Preview for Windows 10 Version 1909 for x64-based Systems (KB4559004) is now hidden. (WUMgr)

I’m not an Insider.

On permanent hiatus {with backup and coffee}
offline▸ Win10Pro 2004.19041.572 x64 i3-3220 RAM8GB HDD Firefox83.0b3 WindowsDefender
offline▸ Acer TravelMate P215-52 RAM8GB Win11Pro 22H2.22621.1265 x64 i5-10210U SSD Firefox106.0 MicrosoftDefender
online▸ Win11Pro 22H2.22621.1992 x64 i5-9400 RAM16GB HDD Firefox116.0b3 MicrosoftDefender

1 user thanked author for this post.

woody

Reply | Quote

woody wrote:

Is this machine in the Windows Insider Release Preview Ring?

Do you have the TargetReleaseVersionInfo registry key?

I am not  an insider.

About the “TargetReleaseVersionInfo registry key”, I don’t know what this is.

 

Reply | Quote

I just read the article about TargetReleaseVersionInfo registry key and I don’t

have this key. It is said that it work’s only on Pro, Enterprise, Education.

1 user thanked author for this post.

woody

Reply | Quote

See @abbodi86’s detailed explanation below.

I wonder how Microsoft could make this more complicated?

Reply | Quote

Some observations about the “Optional Updates” section:

– only 1 optional update is allowed at a time, either feature update or preview CU

– specifying TargetReleaseVersion to the same OS version gives the preview CU as optional update (i also tested setting it to lower version, same result)

– specifying TargetReleaseVersion to higher OS version gives its feature update as normal update

– optional update section show up only if no other normal updates are pending in queue (at least i never got them together, i have to hide ir install normal updates first)

– deferring updates (feature or quality) eliminate the behavior of the section, and the updates (if/when detected) are handled normally (like security updates)

i tested deferring each to 1 day, with TargetReleaseVersion in play, but preview CU don’t show up at all
without TargetReleaseVersion, i get feature update

what’s funny is that on v1809, if you don’t set any deferrals you get v1909
if you set few days deferrals you get v2004

i did not test any “Pause Updates” scenarios, because it’s not easy to control
but based on Woody’s experience, i guess it works as pressing “Check for updates” button, and it respects Optional Updates section

8 users thanked author for this post.

Perq, doriel, geekdom, woody, Microfix, Alex5723, PKCano, Elly

Reply | Quote

Saturday Night Dump just came via Windows Update:

2020-05 Microsoft Edge Update for Windows 10 Version 1909 for x64-based Systems (KB4559309)

And I need to reset TargetReleaseVersionInfo registry key to 1909 again.

On permanent hiatus {with backup and coffee}
offline▸ Win10Pro 2004.19041.572 x64 i3-3220 RAM8GB HDD Firefox83.0b3 WindowsDefender
offline▸ Acer TravelMate P215-52 RAM8GB Win11Pro 22H2.22621.1265 x64 i5-10210U SSD Firefox106.0 MicrosoftDefender
online▸ Win11Pro 22H2.22621.1992 x64 i5-9400 RAM16GB HDD Firefox116.0b3 MicrosoftDefender

1 user thanked author for this post.

abbodi86

Reply | Quote

As follow-up:

online▸Win10Pro 1909.18363.959 x64 i3-3220 RAM8GB HDD Firefox79.0 Windows{Image/Defender/Firewall} is now offline.
2020-05 Microsoft Edge Update for Windows 10 Version 1909 for x64-based Systems (KB4559309) was offered and installed via Windows Update on this machine.

————

offline▸Win10Pro 1909.18363.959 x64 i5-9400 RAM16GB HDD Firefox79.0 Windows{Image/Defender/Firewall}is now online.
2020-05 Microsoft Edge Update for Windows 10 Version 1909 for x64-based Systems (KB4559309) has not been offered via Windows Update on this machine.

On permanent hiatus {with backup and coffee}
offline▸ Win10Pro 2004.19041.572 x64 i3-3220 RAM8GB HDD Firefox83.0b3 WindowsDefender
offline▸ Acer TravelMate P215-52 RAM8GB Win11Pro 22H2.22621.1265 x64 i5-10210U SSD Firefox106.0 MicrosoftDefender
online▸ Win11Pro 22H2.22621.1992 x64 i5-9400 RAM16GB HDD Firefox116.0b3 MicrosoftDefender

1 user thanked author for this post.

abbodi86

Reply | Quote

Not meant to be a silly question (I explain below), but are the Windows 10 1909 running different CPU’s or do you use VM’s?

Windows Defender seems different on every PC ranging from Windows 7 to Windows 10 (all Pro versions except for one Home version of Windows 10). One time I had 2 Windows 7 Pro OS’s but the CPU’s were different and Windows 7 seem to run different versions of Windows Defender. So is the same thing happening with Windows Update, differences because of different CPU hardware?

Reply | Quote

[geekdom]

Different computers, different CPU.

The offline computer had hard drive failure, so it’s not possible to test what updates would come down the Windows Update pipe on that machine. I have no theories as to update availability.

On permanent hiatus {with backup and coffee}
offline▸ Win10Pro 2004.19041.572 x64 i3-3220 RAM8GB HDD Firefox83.0b3 WindowsDefender
offline▸ Acer TravelMate P215-52 RAM8GB Win11Pro 22H2.22621.1265 x64 i5-10210U SSD Firefox106.0 MicrosoftDefender
online▸ Win11Pro 22H2.22621.1992 x64 i5-9400 RAM16GB HDD Firefox116.0b3 MicrosoftDefender

• This reply was modified 4 years, 10 months ago by geekdom.

Reply | Quote

I’m setting up a brand new custom W10 Pro workstation for a brand new exec. I wiped the drive, installed the OS from an official 1909 ISO from a couple of months ago, personalized the desktop a bit, set a 21-day delay for quality updates (and a 180-day delay for feature updates), and clicked check for updates. Before I could react, I was informed that it was installing this .NET Preview along with the stuff I actually wanted:

2020-07 Cumulative Update Preview for .Net Framework 3.5 and 4.8 for Windows 10 Version 1909 for x64 (KB4562900)

Upon restart, it’s now running 1909 build 18363.959.

Note that the Preview I got was different than the one than KB4559004, the one that Woody saw. Mine was KB4592900.

That machine does not have either of the WindowsUpdate\TargetReleaseVersionInfo or the WindowsUpdate\TargetReleaseVersion registry values.

Group K(ill me now)

Reply | Quote

That machine does not have either of the WindowsUpdate\TargetReleaseVersionInfo or the WindowsUpdate\TargetReleaseVersion registry values.

Those can be set in Group Policy under Windows Update for Business.
See #2276103

1 user thanked author for this post.

RTEsysadmin

Reply | Quote

Yes, thanks. The machine hasn’t been joined to the domain yet, and it will get that key when it is.

Group K(ill me now)

Reply | Quote

RTEsysadmin wrote:

The machine hasn’t been joined to the domain yet

And it was able to download and install updates?! How was that possible?

cheers, Paul

Reply | Quote