June 2020 patch overview: Three different ways MS is fixing its bugs this month

Topic

New Reply

June was a very strange month for Windows patching: A traditionally botched patch with a manual-download-only Out of Band fix A botched Windows patch
[See the full post at: June 2020 patch overview: Three different ways MS is fixing its bugs this month]

7 users thanked author for this post.

geekdom, SueW, lurks about, rc primak, Elly, Seff, abbodi86

Reply | Quote

Replies

Succinctly put, as ever, Woody!

2 users thanked author for this post.

lurks about, woody

Reply | Quote

[rc primak]

So here I was minding my own business with Windows Updates. (I know, we’re still on MS-DEFCON-2, but I update the final week or weekend of the month. I have practical reasons, like Zoom Meeting schedules, for my choice of timing.) I am still on Version 1909 (Pro) and did not get upgraded to 2004. (The notice still says I’ll get 2004 when my machine is ready for it. Deferral was keeping that put off for 365 days from the time I upgraded to Version 1909 this spring.)

Nevertheless, either the regular monthly June CU, or else the later catalog-only CU update (which fixes potential printer issues), changed the Windows Updates Settings Window. The Advanced Options no longer included any deferrals, only Pause Until. I have Windows 10 Pro. So the change is apparently retroactive on all users who apply the June CU.

Now I have to go into my Group Policies and freeze out the 2004 upgrade before it gets foisted on me. I had Feature Updates on a 365-day deferment since my 1909 upgrade. So that should hold, if I’ve been reading this site correctly. The madness never gets put on hold at Microsoft!

Thanks to Woody, Susan and PK Cano, among others here, for updating the instructions so that we can still defer Feature Updates.

-- rc primak

• This reply was modified 4 years, 8 months ago by rc primak.

Reply | Quote

[cyberSAR]

Hi rc, I’ve installed both those patches and my deferral settings are still there.

Just checked 3 other machines which have both installed, 1 of which was done yesterday, and all still have the settings available.

• This reply was modified 4 years, 8 months ago by cyberSAR.

2 users thanked author for this post.

rc primak, woody

Reply | Quote

They are there in my 1909 also. I have June Patch Tues updates, but I have not installed the OOB printer-fix CU.

2 users thanked author for this post.

rc primak, woody

Reply | Quote

Same for  me – CU only, no OOB, and the deferral options are there.

1 user thanked author for this post.

rc primak

Reply | Quote

If you have any deferral set in Group Policy, the pulldown settings for Quality and Feature deferrals will not show in the GUI under Advanced options. The deferral settings in GP have to be “not configured.”

3 users thanked author for this post.

rc primak, Lars220, woody

Reply | Quote

I think that must be the problem.

Reply | Quote

Actually, there’s another reason those deferral settings might not show up in Windows 10 Pro. I was using a Standard User Account when I noticed the settings were not visible in the User Interface.

When I later checked in my Administrator Account, the settings were still there.

I had never noticed this difference before the recent posts about Version 2004 here. at AskWoody.

Were it not for the discussions about Version 2004 here at AskWoody, I would have tried the Admin. Account immediately, without posting anything here. I guess sometimes we see things we want to see, and interpret them according to our current concerns. It happens to me sometimes, anyway.

False Alarm!!

Sorry about that.

I should have posted this much sooner, but I was busy all day today.

Thanks for the PM, PK Cano. Thanks for looking into it, Woody.

By the way, this incident did get me to look at what Group Policy Settings I will need when and if I upgrade to Version 2004. So thanks to everyone here for all the coverage. It’s been valuable, if for me a bit premature.

-- rc primak

Reply | Quote

I’ve been keeping an eye on the radar-I don’t update til its level 3, but then I gotta ensure that the 2004 or whatever new version doesn’t try to invade when updating the usual safe updates.

Reply | Quote

I’ve only seen a very few reports of people being pushed to 2004. In general, you have to specifically click to install it. Details here:

https://www.computerworld.com/article/3232632/how-to-block-the-windows-10-may-2020-update-version-2004-from-installing.html

Reply | Quote

Outside of reading this site, how does an ordinary home user stay aware of all the quirks of modern windows updating? Does Microsoft post notices someplace? Do they use your ms account to push messages?
Inquiring minds want to know.

1 user thanked author for this post.

WildBill

Reply | Quote

There’s the Windows release health dashboard… assuming Microsoft admits to all of the reported issues with patches (spoiler: they don’t).

2 users thanked author for this post.

WildBill, woody

Reply | Quote

https://www.theregister.com/2020/07/01/windows_10_2004_rollout/

Not specifically about the June rollout, but relevant?

1 user thanked author for this post.

woody

Reply | Quote

That’s a general overview of the Win10 version 2004 rollout – which isn’t going very well, IMHO.

It’s almost as though it hadn’t been tested properly before someone hit the Go button. Surely not?

By the way… clicking “Check for updates” won’t get you to version 2004, in spite of what the article says. You have to specifically, explicitly click on a link to install version 2004.

Reply | Quote

Woody, since you updated us on the M$ codex bugs, will you still be publishing a “Woody on Windows” article, or is that scratched? Understanding not all Computerworld readers access the website & vice versa…

Bought a refurbished Windows 10 64-bit, currently updated to 22H2. Have broke the AC adapter cord going to the 8.1 machine, but before that, coaxed it into charging. Need to buy new adapter if wish to continue using it.
Wild Bill Rides Again...

Reply | Quote

Just posted it.

Unfortunately, the Computerworld article went into edit before I saw @abbodi86’s post, which says that MS is wrong – the two vulnerable codecs exist on EVERY Win10 machine since version 1809 (except N and LTSC). MS says they’re only on machines that have installed the optional “HEVC from Device Manufacturer” codecs from the Microsoft Store.

That’s a very important distinction because MS is patching a security hole in Windows via the Microsoft Store.

What a mess.

Come to think of it, that approach isn’t all so different from this month’s Outlook patch, which fixed a hole in Windows by updating the Office 365, er, Microsoft 365 Click-to-Run.

Reply | Quote

[tcc089]

Thanks again Woody, PKCano, et al for keeping us informed on this.

My apologies for posting a new post about CVE-2020-1425 and 1457 this morning, even though I had searched the site before posting and didn’t find anything. PKCano pointed me to this posting.

Many thanks!

• This reply was modified 4 years, 8 months ago by tcc089.

Reply | Quote

Are there any other ways MS could use to update W10? I would think they only need 1 method for Windows itself but 3 is a sign of idiocy or incompetence.

Reply | Quote

woody wrote:

I saw @abbodi86‘s post, which says that MS is wrong – the two vulnerable codecs exist on EVERY Win10 machine since version 1809

I don’t have HEVC codec on my Windows 10 1909 Pro (May patches).
I do have Microsoft’s HEIF image extensions.

1 user thanked author for this post.

stanhutchings

Reply | Quote

Please excuse me but I’m confused (it has been awhile tho).  Woody says:  “A botched Windows patch that knocked out Outlook Click-to-Run, fixed by a fix for Outlook”.

I’m running Win 7, I have Office 2010, and I don’t use Outlook.

First – does this botched Windows Patch apply to Win 7 as well as 8.1 and all the 10’s?

And second – does this botched Windows Patch botch up the Outlook in Office 2010?

Should I be worried about this?   Thanks.

Being 20 something in the 70's was far more fun than being 70 something in the insane 20's

Reply | Quote

The patch does not apply to Win 7 or affect Outlook 2010. You don’t need to worry about it.

2 users thanked author for this post.

woody, Charlie

Reply | Quote

What is the thinking about the out of band printer issue patches such as KB4567521 for W8,1 and Server 2012 R2? Should the optional patch be installed immediately after installing the June 2020 security and quality CU or only after determining whether you have printer/print spool problems? It sounds as if all the associated issues may not be initially apparent and it might be wise to just routinely install the optional patches. Any thoughts?

Reply | Quote

Not official advice here, but I went ahead and applied the patch from the Catalog. Susan Bradley says Microsoft says the same corrections will be included in the July CU, so this was probably not necessary. Anyway, no ill effects, as far as I can see so far.

-- rc primak

Reply | Quote

Is there some way to delay updates in 1909 past 7/06/2020???

Reply | Quote

See the BlogPost “Is there a way to cheat Pause Update?” and read the comments on the Lounge how people did this.

Reply | Quote

Thanks! Disconnected WiFi, Hit resume updates, got the no internet warning. Was able to go from 7/06 to 8/06 by hitting the pause button. That ought to be enough time to get patching instructions from Woody on all the June chaos, fingers crossed!

Reply | Quote

[geekdom]

Regarding CVE-2020-1425 and CVE-2020-1457 updates via Microsoft Store, “Update installation may fail” silently with access denied. Recap and information is here:

https://borncity.com/win/2020/07/03/addenum-to-the-out-of-band-windows-codecs-library-security-patch-via-store/

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, 8 months ago by geekdom.
• This reply was modified 4 years, 8 months ago by geekdom.

1 user thanked author for this post.

woody

Reply | Quote

woody wrote:

very few reports of people being pushed to 2004.

Yesterday in an occasionally used 1903 or 1909, when I opened Settings’ WU dialogue,
I saw not Check for updates, instead a prompt for the restarting of Windows in order to install 2004.
I chose to go with it.

I regard that as a push.

Reply | Quote