Another round of “optional, non-security, C/D Week” patches for Win10 1909, 1903, 1809

Topic

New Reply

We just got another set of “optional, non-security, C/D Week” patches for Win10 versions 1903 and 1909 (KB 4566116) and 1809 (KB 4571748). There’s a l
[See the full post at: Another round of “optional, non-security, C/D Week” patches for Win10 1909, 1903, 1809]

4 users thanked author for this post.

Fred, dgc-art, abbodi86, geekdom

Reply | Quote

Replies

I use WUMgr to check for (and hide updates, if necessary). Both of these updates were shown in WUmgr, hidden in WUMgr, and are not installed.  DON’T USE Check for updates:

• 2020-08 Cumulative Update Preview for .NET Framework 3.5 and 4.8 for Windows 10 Version 1909 for x64 (KB4570723)
• 2020-08 Cumulative Update Preview for Windows 10 Version 1909 for x64-based Systems (KB4566116)

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.

madquack

Reply | Quote

In theory, Check for updates should be OK.

In theory.

I still don’t see an Optional Updates section in Windows Update (Start > Settings > Update & Security). Win10 1909. That’s where this particular patch should be available – and it isn’t, at least on my production machines.

Reply | Quote

Followup:

I used WUMgr to unhide updates and used Check for updates.

• 2020-08 Cumulative Update Preview for .NET Framework 3.5 and 4.8 for Windows 10 Version 1909 for x64 (KB4570723) installed immediately.
• 2020-08 Cumulative Update Preview for Windows 10 Version 1909 for x64-based Systems (KB4566116) shows under Optional updates available.

DON’T USE Check for updates.

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

Yep, that’s the same problem we had last week. The .NET preview gets installed as soon as Pause runs out, or you click Check for Updates.

Blech.

Interesting that you’re seeing this one in an Optional Updates block. I still don’t see it here.

Reply | Quote

Of course you don’t want to install them – unless you’re concerned about time zone information for Yukon Province.

Or you want WSL2:

Microsoft brings Windows Subsystem for Linux 2 to Windows 10 1903 and 1909

1 user thanked author for this post.

woody

Reply | Quote

Paul Thurrott has an interesting take on the WSL 2 situation:

If Microsoft can arbitrarily bring major features like WSL 2.0 to previous versions, why even have versions?

Reply | Quote

Haven’t you noticed that’s already happening?
Some of the documentation for the updates (like in the Catalog list of some updates) already says “v1903 and later”
Prediction: within a year (or at least by the time Win7/8.1 go away) all Win10 will get the same CU and SSU (like 1903/1909 do now, but across the board except maybe for Insiders) and the distinction will be only what “Features” are turned ON.

1 user thanked author for this post.

woody

Reply | Quote

I still don’t understand the reasoning behind .NET framework cumulative update previews installing automatically when you check for updates. Why doesn’t next month’s Windows 10 Cumulative Update Preview follow this behavior?

 

Windows 10 update behavior is so strange!

1 user thanked author for this post.

woody

Reply | Quote

I don’t understand either, but apparently MS hasn’t fixed the bug yet.

Assuming it is a bug.

https://www.computerworld.com/article/3568351/windows-update-is-a-bifurcated-mess.html

1 user thanked author for this post.

madquack

Reply | Quote

woody wrote:

I don’t understand either,

Win10/Pro, version 1909. FU=365, QU=0, GPE=#2, notify download/install.

Odd as well is the fact that the Week C patch KB4570723 (2020-08) Cumulative Update Preview for .NET Framework 3.5 and 4.8 for Windows 10, Version 1909 for x64-based system released August 19, 2020 to the WU legacy queue and hidden by me with wushowhide on August 20, 2020 has disappeared from wushowhide today August 24.

As with all Previews, I hid it as soon as I learned that it was in the queue, but today August 24 it is no longer in wushowhide, neither hidden or unhidden.

I checked Update History and it has not installed either.

Does anyone have an idea of why it just disappeared from wushowhide?

Reply | Quote

I still have and get KB4570723 in scans

Reply | Quote

abbodi86 wrote:

I still have and get KB4570723 in scans

When I sent that note on August 24, 2020 at 1:13 PM (which is CST), only the last two items showed up in “Show hidden updates”. Now, at 7:30 PM (EST), the first three are back. It looks like wushowhide gets confused sometimes – not listing hidden items that have actually been hidden.

I’ve not ever run into this problem before. (I keep my own record of what has been hidden and later unhidden with dates and times – just to keep track of things.)

Reply | Quote

Legacy WU agent don’t have choices, since they stripped it down in Windows 10

they added optional behavior to the new UUP agent starting v1903

they can “fix” .NET Preview CU status if they moved it to UUP side in the next Wndows 10 version (21H1)

2 users thanked author for this post.

geekdom, woody

Reply | Quote

abbodi86 wrote:

they can “fix” .NET Preview CU status if they moved it to UUP side in the next Wndows 10 version (21H1)

Does that mean that they are planning on moving dotNETs Previews to the UUP side in 21H1? Or is that just a wish/suggestion?

If they do do this, that would put Previews, no matter whether CU Previews or dotNet Previews, on the same side. Seems more consistent to me.

Reply | Quote

A suggestion 🙂

Reply | Quote

They listened 🙂

the new Windows Insider Dev build 20211.1005 now handle .NET 4.8 patch via UUP

3 users thanked author for this post.

woody, PKCano

Reply | Quote

Took them 2 years and 4 months to finally accomplish that 😀

Release Preview update for Windows 11, version 22H2 (22621.1192) now include .NET CU (as companion update, similar to SSU)

1 user thanked author for this post.

geekdom

Reply | Quote

Where’s the preview?

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

Release Preview channel

will be out public next week or so

1 user thanked author for this post.

geekdom

Reply | Quote

[7ProSP1]

Hey Woody,

Yukon isn’t a province, it’s a territory.  By the same token, this would be like referring to Tennessee as a territory instead of a state.  : )

• This reply was modified 3 years, 1 month ago by 7ProSP1.
• This reply was modified 3 years, 1 month ago by 7ProSP1.

Reply | Quote

YIKES!

My parochialism is showing. Change made.

Thanks, eh?

Reply | Quote

[7ProSP1]

You’re most welcome, eh and a thanks to you as well.

• This reply was modified 3 years, 1 month ago by 7ProSP1.

Reply | Quote

[dgc-art]

Today (21 August 2020 – note the date!), my Windows 10 Pro v.1909 build 18363.1016 (August updates installed) has just had the notorious KB4023057 from way back in 2018, pushed at it. Microsoft updates are really becoming just plain weird. It goes without saying that I will not be downloading this patch.

• This reply was modified 3 years, 1 month ago by dgc-art.

Reply | Quote

V 1909 build 18363.959: Win 10 Pro. Feature updates have been delayed for some time now, to 365 days, with “Quality” (what a joke!) updates set to Zero delay, and Notify to Download Group Pol. set with option 2 per prior PKCano advice. Version target Group Pol. also set for some time, at V 1909, my current version.
…….
Just now today, I got a Systray popup saying downloads ready to install; click here. I Do Not do that, ever. First, ran WUShowhide. It shows NO updates pending. Re-ran it several times; results the same. I did open WUpdate in Settings; viewed it but clicked nothing. Then x-ed out of it. It showed KB4023057 ready to download.
…..
My Control Panel list of installed updates does not show the update having been installed before. Then, re-ran Showhide, and 4023057 Not listed as Available to Hide. The only hidden ones are this months DotNet preview, and this month’s Win10 update; plus my never-to-be-installed Flash update and last January’s Intel Update for my AMD machine. (M$ simply offering such an update makes me hugely doubt their abilities.)
…..
PS: Just before posting this, I tried Showhide one more time. Results: It now showed 4023057 available for hiding. I did so; closed out of it. Next, I re-ran it, to show Hidden Updates. 4023057 was not shown as Hidden. I re-ran it, to show those avail. for hiding; list was empty, and 4023057 Not There. Again I re-ran ShowHide; 4023057 not shown in list of Hidden ones. Viewing Win Update in Settings again: Still shows 4023057 ready for download.
…….
Windows 10, since started first using it in March of this year, is ~Just ~Not~ Reliable~.
…..
Has anyone else seen WUShowhide not picking up an update like this? Any suggestions/advice? Thanks!

Reply | Quote

This is a followup to my post # 2290474 of 2 days ago.
…..
With my Win10 Pro V 1909 Build 18363.1016; Group Pol. and Registry Notify to DL/Install, option 2; target version 1909. Recall KB4023057 popped up in WU, but never showed in Winshowhide, either before or after seeing it in WU. That was my original post. Solution: Thank you, Woody, and to Mr. Brinkmann of GHacks!!! I D/L the Win Update Disabler V 1.4. It worked ~very~ well; both to disable and re-enable. Now I have some control over WU.
……
Finally: Today just now, with WU enabled, WUShowhide ~did~ show KB4023057; Of course, I promptly hid it; my plan now is to stick on V1909. But: on re-run WUShowhide, it did not include that KB as a “hidden” update. It’s just gone. The good news: it didn’t show up in Win Update, but I then disabled WU afterward, and will continue to do so. As I said in my post 2 days ago: Windows 10, since started first using it in March of this year, is ~Just ~Not~ Reliable~. I am a retired professional, and I detest having tools which don’t work well; life is too short for that.
…..
When I finish tweaking O & O Shutup on my machine, and further disabling any telemetry that’s not already shut off: that will be the point when I will feel free to just let W10 sit; and I will daily start booting into my dual-boot Linux Mint 20 Cinnamon Ulyana. If you’ve not seen it, you really oughta take a look at it; it seems so far to be a reliable, great OS. Best to all; and thanks to Woody and all for this website, and to KYKaren, Abbodi and all, for your help !!

Reply | Quote

Running Win10 Home 1909 and decided to unpause my updates.  Of course it then runs the ‘check for updates’ so it pulled down the KB4565351 cumulative update which I expected.  But then as others are reporting, I got the KB4570723 .NET preview pushed instead of the current .NET update.

I also got some INTEL drivers pushed, and the WIN10 2004 feature update is back to showing ‘download and install’ optional

After checking for updates again, I’m still not seeing the KB 4566116 preview update.  It’s not showing up at all.

This .NET preview issue confirms my worst suspicions after a 2nd month … if you choose to pause updates on a WIN10 ‘HOME’ system you are now volunteering to be a preview tester whether you like it or not!  This has got to be a bug???

Reply | Quote

2020-08 Cumulative Update Preview for Windows 10 Version 1909 for x64-based Systems (KB4566116) could be a timed release — where an arbitrary release schedule is implemented.

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

I wonder why the newest Windows 10 versions always are always week or more behind of the older ones to get these optional updates.

It kinda diminishes the benefits of the whole optional update round because often next official patch Tuesday looms only week or so ahead. So why bother releasing these D week updates at all to public?

It’s also one more thing discouraging to be on latest Win10 version – you’ll be ‘rewarded’ by getting fixes later than others.

Reply | Quote

So why bother releasing these D week updates at all to public?

Because the users are the beta/QA testers for Microsoft.

Some users may have problems fixed by the previews and wouldn’t want to wait for next patch Tuesday.

Reply | Quote