What happened to KB 4462923, the October Win7 Monthly Rollup?

Topic

@PKCano has been on a mission to find what it takes to get Windows Update to offer this month’s Win7 Monthly Rollup. It ain’t easy. Details coming in
[See the full post at: What happened to KB 4462923, the October Win7 Monthly Rollup?]

8 users thanked author for this post.

Heavenly, Elly, Myst, jburk07, HiFlyer, WildBill, flackcatcher, geekdom

Replies

Please see #227057 for the original posting of what it took to get KB4462923 (2018-10 Security Quality Monthly Rollup to appear.

8 users thanked author for this post.

abbodi86, Elly, Myst, woody, jburk07, HiFlyer, geekdom, Microfix

I had errors in the original version of the article, but I think it’s accurate now.

3 users thanked author for this post.

Elly, Microfix, PKCano

I’m still showing it, but it’s unchecked. When we go to Defcon 3, I plan to install the other checked updates, reboot and then check the box and install 4462923. Does this sound like the right way to go ? I already install version 2 of 3177467.

KB4462923 is still unchecked and hidden again.

Edition Windows 11 Pro
Version 23H2
Installed on ‎10/‎19/‎2022
OS build 22631.2715

I installed the October MSRT, but no KB3177467 (ver 2) showed.

So I further installed the 5 MS Office 2010 updates and KB3177467 immediately showed up and was checked, however, then the WUpdate Optional category is totally missing.  PK made mention in one of the many posts that installing KB3177467 would/should bring the Optional category back. Is this true?

I am holding at the Checked KB3177467 stage pending further instructions, or should I proceed to install it and await further instructions from here?

Please follow the link in my post above.

If it’s this difficult to find and get to install, perhaps we shouldn’t press our luck by hunting it down and then installing it.

@Woody, don’t you always advise us not to check any updates which aren’t already checked?

Group "L" (Linux Mint)
with Windows 8.1 running in a VM

2 users thanked author for this post.

HiFlyer, WildBill

Advising users with Windows 7 to install the SSU v2 as it’s now classified as a ‘security update’ seems to be out of control (Thanks MS)
I’ve now got the SSU v2 installed and the unchecked October SQMR hidden but, I think the issue here is what happens if you don’t install the SSU v2, guess we’ll see in November if the proverbial hits the fan.

Win8.1/R2 Hybrid lives on..

2 users thanked author for this post.

Myst, HiFlyer

If metadata hasn’t been changed to install KB3177467-v2 prior to installing other updates, November Patch Tuesday will echo October Patch Tuesday.

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.

HiFlyer

Causing more confusion..which seems to be the intent.

Win8.1/R2 Hybrid lives on..

3 users thanked author for this post.

Myst, woody, HiFlyer

WAIT FOR THE DEFCON RATING TO GO TO 3 OR ABOVE.

DON’T INSTALL ANYTHING YET!!!!

5 users thanked author for this post.

Elly, Myst, woody, pmcjr6142, Lars220

I always take the view (once we’re at DefCon 3 or higher (one can always be optimistic)) that if an update isn’t offered and checked in Windows Update then it’s not intended to be installed and I won’t install it. I have zero interest in chasing up any updates for manual installation.

2 users thanked author for this post.

Myst, Microfix

I intend to wait for MS-DEFCON 3(+) and the accompanying Computerworld article for directions, and advise the same for others. But I also recognize there are valued contributors like PKCano testing these scenarios to assist in crafting the advice Woody will write. In that spirit I’m pulling together a few thoughts to pose an experimental trial.

We know that September brought KB2952664 into the standard model for a fully updated Windows7 according to Microsoft. One fallout effect is the offer of KB3150513, ignored by our usual protocols in the GroupA/B systems. When a full cycle of updates cleared the important queue following Septembers batch, either by install or hidden, KB3177467-v2 appeared in early October. This is widely acknowledged as a prerequisite for October updates in either GroupA/B directions.

Has the specific case been tried where accepting everything Microsoft offers without interpretation? My thought is that Microsoft specifically wants KB2952664 and KB3150513 onboard, functioning, and reporting back before moving on with more updates.

If I have missed reading this case tested by trial, I apologize for not seeing it and appreciate your considering the possibility.

I installed the 2018-10 Oct Rollup on my TEST machine. Nothing broke that I noticed. But I hid KB3150513 when it showed up  – didn’t want it anyway!

Oh, I agree we don’t want it. But is it the condition required by Microsoft?

I don’t believe KB3150513 is “required.”

1 user thanked author for this post.

jburk07

Maybe stumbling over definitions of words here. I do not believe the update named KB3150513 is an optional update that carries the classification “required” which italicizes its display and moves it to the important queue when appropriate settings are set.

Rather I am posing the possibility Microsoft will not preselect KB4462923 with a checked box until a certain requisite condition is met. And that condition may be having KB3150513 telemetry in a log available for Microsoft to review before granting the checkmark (X gets the square) we are looking for.

I am not demanding you make the trial, PKCano. As a volunteer you go way beyond the contribution of most and I admire you for it. I’m only trying to state a test condition for anyone willing to perform the trial. I do not have an available test bed that I am willing to commit. But since a main blog topic asked the question, I wanted to contribute a possible explanation. Thanks also to GoneToPlaid, who wrote similarly earlier than I.

anonymous wrote:

Rather I am posing the possibility Microsoft will not preselect KB4462923 with a checked box until a certain requisite condition is met. And that condition may be having KB3150513 telemetry in a log available for Microsoft to review before granting the checkmark (X gets the square) we are looking for.

KB3150513 will not show up in Windows Update until either KB2952664 or its functionality is installed. If KB2952664 (as a separate patch) has previously been hidden, you will not see KB3150513 at all.

KB4462923 2018 -10 Rollup (and the Sept Preview) contain the functionality of KB2952664. KB3150513 cannot be a prerequsite for KB4462923 to be checked, or KB2952664 (as a standalone patch) would have had to be mandatory (which it is not).

3 users thanked author for this post.

cesmart4125, Elly, Microfix

I began from the standpoint that our theoretical test bed was already current through September, which includes the KB2952664 functionality. ( I thought in both GroupA/B protocols, but I may be wrong on that point. )

My eventual goal would be to propose taking all updates offered, then following @abbodi86 ‘s good work in AKB 2000012. But we had not gotten that far yet.

I am failing at my side of the communication exchange, so will withdraw until a new approach occurs to me.

KB2952664 functionality was NOT in the Sept 2018-09 Rollup and has NEVER been in the Group B patches. The functionality was added in the 2018-09 PREVIEW Rollup, which is an unchecked optional update. So if you were patched through Sept Rollup, and had not ever installed KB2952664, you do not have the patch or its functionality and would thus never see KB3150513.

BTW using @bbodi86 ‘s method does NOT prevent the installation of the functionality if you install the Oct 2018-10 Rollup. It only “neutralizes” it after the fact. You will still see KB3150513 afterward. You can HIDE it!!!!!

1 user thanked author for this post.

Elly

From the Redmond point of view, is that the problem?

I agree with all your prior advice. Darth Vader may be altering the deal further. And this may be an early indicator.

I am anonymous#post-228166. I read today’s headline, linked article, and comments on this topic before writing above. Then my very next topic review was the two week old item where Gone to Plaid, Steve T, and HiFlyer discussed the same idea. Acknowledging credit here. Carry on good folks!

I found it here

https://catalog.update.microsoft.com/v7/site/Search.aspx?q=KB4462923

And it downloaded successfully

This whole time I thought I had the October update offered. That’s what the list says: the 2018-10 update. But it turns out it’s 3177467–even though version 1 is already in my list of installed updates.

Is it normal to get version 2 if you already installed version 1? Note that I did a full reinstall of Windows 7 this year, and so I did not install said update using Windows Update, but through a program that downloads all updates ahead of time that was recommended to me in these forums.

KB3177467 v1 and v2 are not the same. The contained files are the same, but KB3177467 v1 is optional, while KB3177467 v2 is classified as a “security” update. The metadata is different.

Edit to correct KB number to KB3177467

6 users thanked author for this post.

cesmart4125, Elly, Myst, woody, geekdom, Microfix

Is there any harm if I (once the Defcon is changed) go ahead and accept version 2? Or should I hide it?

That is a question Woody will answer in his instructions for safe patching on ComputerWorld when he raises the DEFCON number to 3 or above. DEFCON-2 means WAIT.

Yes, I know about the DEFCON levels, as per my previous post. I am glad that Woody plans to address this when he changes the DEFCON level. It did not occur to me that he would do so. I’ve never noticed the instructions for Windows 7 varying at all.

This time is different. We have the Servicing Stack, which doesn’t show up until the important update queue is empty, and has to be installed by itself. And there is the October Rollup, which doesn’t show up until you hide the Sept Preview, and when it does, it’s unchecked. There is nothing to say Microsoft won’t change things again – there are still two weeks till Patch Tues. So there is no rush at this point.

1 user thanked author for this post.

Elly

Currently shown in catalog, x86 (32-bit), x64 (64-bit):

KB4462923 last updated 10/15/2018:
https://www.catalog.update.microsoft.com/Search.aspx?q=4462923

KB3177467 last updated 10/8/2018:
https://www.catalog.update.microsoft.com/search.aspx?q=3177467

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

Windows Update Catalog gave me to files:
(1) pciclearstalecache_f9e6352a8a36bd5304229012049c66ab267923f2.exe
(2) windows6.1-kb4462923-x64_5c4506692214692bf846da33052edb1dc5752156.msu

Should I install them both, or only kb4462923?
If both of them needed to be installed, what is their installation order?

Also, I have manually uninstalled KB2952664.

Thanks for your help.

Windows 7 Pro x64.

anonymous wrote:

Windows Update Catalog gave me to files: (1) pciclearstalecache_f9e6352a8a36bd5304229012049c66ab267923f2.exe (2) windows6.1-kb4462923-x64_5c4506692214692bf846da33052edb1dc5752156.msu Should I install them both, or only kb4462923? If both of them needed to be installed, what is their installation order?

If you don’t know the answer to those questions, you should not be using the MS Catalog.

And, I’d be willing to bet you haven’t uninstalled all the versions of KB2952664 if you have been letting them install through Windows Update. Look again and see if it’s still there. You have to uninstall ALL of the versions that have installed.

The real question that nobody is asking:

Does KB4462923 fix any critical security exploits that we should be aware of?

What security fixes are we specifically missing out on by not installing it?

1 user thanked author for this post.

woody

That goes to the heart of the question.

PK, did you mean to say KB3177467 V1 and V2 are not the same?

How did KB3150513 enter the discussion?

Please see #228210.

So are there now also two versions of KB3150513?

And what is this KB, and how is it received?

Sorry, that should have been KB3177467 in post #228210. It has been corrected. Sorry for the confusion.

2 users thanked author for this post.

cesmart4125, Microfix

Please, I beg to receive your pardon in this case. I introduced that unrelated KB## into this topic inside a separate line of thought.

It is possible the rapid exchange has caused PKCano to cross thoughts, and I’m sure all will be adjusted soon.

I’m getting KB whiplash, too. Witness the numerous mistakes I made in the first version of the Computerworld article.

KB4462923 has been sitting in my “update window” since early October. i was just waiting for final Woody’s comment before i download and install.  but since it is end of month, so even without Woody’s final instruction whether to download/install, i just checked the KB box and install.  download and installation seems to be seamless. post installation, i have been running my PC for 2 hours. no issue.  nothing out of the ordinary.  will report back if i see anything different later.

Glad you had no problems.
We are still two weeks out from Patch Tuesday (there were 5 Tues this month), still waiting on Win10 v1809 as well. So no rush for DEFCON-3 – we still have plenty of time.

1 user thanked author for this post.

Demeter

It’s getting to be like Abbot and Costello’s “Who’s on First” with patches…any mortal could be confused  by now! Me, I’m just sitting on the bottom waiting for the all-clear/surface horn.

Congrats and thanks to all who are making the efforts up there where the KB shrapnel, shells, and other munitions of  IT are going off!

Win7 Pro SP1 64-bit, Dell Latitude E6330, Intel CORE i5 "Ivy Bridge", 12GB RAM, Group "0Patch", Multiple Air-Gapped backup drives in different locations. Linux Mint Greenhorn
--
"Nine out of 10 doctors say Acid Reflux is mainly caused by computers."

2 users thanked author for this post.

Demeter, Myst

The hide KB4462927 and then hide KB4457139 approach brought out KB4462923 for my Windows Pro x64.
Thanks.

Installed successfully SSU KB3177467 v2  2 days ago from MS update catalog. Had previously installed v1  01/10 2018. Changed Update settings to “Check but let me choose when to download and install”. Ran update. Just one update selected as important: KB890830, October MSRT. Optional updates listed: KB4462927, 2018-10 Preview of monthly quality rollup for Win 7 x64, KB4462500, 2018-10 Preview of quality rollup for .NET framework, KB4459922, 2018-10 security and quality rollup for .NET framework, “recommended”. I don’t see any of the Oct. updates mentioned in the threads. 1 hidden update, KB2952664. Win 7 Pro x64 Pro SP1, GRP. A (mostly) i7-core Haswell, HP ZBook.

Please read the ComputerWorld article and the link in my first post at the top of this thread on how to find the Oct 2018-10 updates.

Thanks. Sitting tight for now.

What fun! M/S have now found a way to play Hide and Seek with us. I wonder what will come next? The possibilities are endless: Pass the Parcel (if you haven’t hidden the patch by the time the music stops, your computer will automatically morph into Windows X or brick up); Hunt the Thimble (we have mysteriously installed telemetry on your computer and defy you to locate it), and so on, and so on………………………………..

I don’t know how relevant this is to the topic, but KB4462923 has always been and continues to be offered through WSUS.

Any ideas why MS would keep it available in WSUS, but play hide in seek in Windows Update?

 

 

 

WSUS leaves the responsibility of curating the install process on the receiver’s end of the exchange. If the documentation is correct, and read correctly, all goes well. When a mistake is made the troubleshoot rests with the user.

Windows Update places this responsibility with Microsoft to interpret their own “metadata” that should define what can occur, what cannot occur yet, and how to move from one to the other. Users have opinions on how competent Microsoft is with this process, and that influences their ideas of why we see what we see. And continue to see many weeks after this should have been an accomplished fact.

Assume Microsoft is less than competent then we have to wait for them to figure it out and give a new solution. But assume Microsoft is competent and you must conclude this is what they intend to happen. Then there will be no new solution and we must find our own. That might include going back and doing things the Microsoft way and coping with those results afterward.

Installed the October update (after hiden 2 batches of other updates) and so far: nothing broken.

W7-32bit Home

I did install it along with

KB4054529 (language pack update 4.7.2)

KB890830 (malicious removal tool -update october)

KB4459922 (security and quality rollup for .NET Framework 3.5.1-4.7.2)

And my computer stopped working after a reboot. Only in safe mode as administrator did I get to see a message the the System Event Notification Service failed to start, refraining regular users from logging in. I started system recovery, went back to October 25th just before the patches were installed and my system worked again. There is a note with KB4462923 about network components failing to work. Maybe they found issues and keep it on the down until this is worked out?

Piet

The Servicing Stack Update KB3177467 v2 needs to be installed by itself and before the KB4462923 October Rollup. Did you install it first?

PKCano wrote:

The Servicing Stack Update KB3177467 v2 needs to be installed by itself and before the KB4462923 October Rollup. Did you install it first?

Group A Win7 SP1  UK

Hello just to let you know that KB4462923 has turned up again ticked up as an important

update – after being absent for 3 weeks or so.  Will wait till  we are told  by Woody to go ahead and install it ……

Yes, wait for DEFCON-3. Woody will have instructions.

oh woody!

KB4462923 on MS Update Catalog has a new release date – 11/1/2018

in other words, it’s back!

3 users thanked author for this post.

abbodi86, columbia2011, PKCano

Now shown in catalog, x86 (32-bit), x64 (64-bit):

KB4462923 last updated 11/1/2018:
https://www.catalog.update.microsoft.com/Search.aspx?q=4462923

KB3177467 last updated 10/8/2018:
https://www.catalog.update.microsoft.com/search.aspx?q=3177467

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.

PKCano

KB4462923 2018-10 Security Monthly Quality Rollup showed up CHECKED in the “important updates” on my Win7 today 11/1/18.

On a test machine, I installed it along with the 2018-10 .NET Rollup and MSRT without an error (Note: the SSU KB3177467 v1 was installed on my machine in 2016)

AFTER the reboot, KB3177467 v2, the Servicing Stack released 10/9/2018 appeared and installed without requiring a reboot.

1 user thanked author for this post.

abbodi86

Yup, KB4462923 just appeared (checked) in my Windows Update. Still says published 10/9/2018.  Oh myyy…

Cheers!!
Willie McClure
“We are trying to build a gentler, kinder society, and if we all pitch in just a little bit, we are going to get there.” Alex Trebek

The hash is the same and the file size is the same. Must be a metadata change to let it install without an error before KB3177467 v2 (the SSU).

When Microsoft kills something, they go to great lengths to hide the body.

See my main post – and thanks to all of you who are watching.