Windows 7 Updates - are they going out with a bang?

[Kick]

September 2018 and October 2018 second Tuesday Windows Updates for Windows 7

 

After problem free updates for a considerable time, I have experienced certain issues with the September and October updates.

 

On the second Tuesday of September there were four updates that I needed:

KB890830 (the Malicious Software Removal Tool x64 - September 2018); KB4457144 (Security Monthly Quality Rollup); KB3177467 and KB2952664 (both described as x64 update for Windows 7). All four were described as important. KB4457144 failed and failed again when I retried. I ran the Update troubleshooter (https://support.microsoft.com/en-us/help/4027322/windows-update-troubleshooter). I then visited https://answers.microsoft.com/en-us/windows/forum/windows_10-update/how-toreset-windows-update-components-in-windows/14b86efd-1420-4916-9832-829125b1e8a3 and downloaded the batch file ‘WuReset for Windows 7’ and ran it as an administrator. This appeared to resolve the issue and everything ran smoothly until the October updates.

 

On the second Tuesday of October, Initially, there were two ‘important’ updates and one ‘recommended’ update that I required:

The 'important' KB4462923 (Security Monthly Quality Rollup x64) and KB890830 (the October 2018 Malicious Software removal Tool x64) and the 'recommended' KB4459922 (Security and Quality Rollup for .NET Framework 3.5.1 to 4.7.2 for Windows 7 etc x64). With much relief these installed successfully. I rebooted the system to complete the installation and confirmed the updates were successfully installed. I then opened the Action Center and found there was another update ready to install. This was KB3177467 (the Security Monthly Quality Rollup from September that had been already successfully installed four weeks previously). I double checked first in my ‘Windows Update History’ and then in ‘Programs and features’ where KB3177467 was shown in both as installed. Rather than risk any additional problems, I have hidden KB3177467 rather than uninstall the existing installation and install it again from Windows Update.

 

Everything now seems to be running correctly bar an occasional warning (yellow triangle) in the Event Viewer “.NET Runtime Optimization Service (2.0.50727.8798) - Version or flavor did not match with repository: Microsoft.Security.ApplicationId.PolicyManagement.Cmdlets”. The warning does not appear every session and there appears to be no noticeable impact on my computer activities so for the time being I am ignoring it.

 

I notice, in online searches, that there have been many reports of problems with the last two Windows 7 monthly updates - it appears I have been lucky as others have experienced far worse problems, some of them ongoing. I read of serious issues with Windows 10 updates including BIOS being corrupted after updates but Windows 7 has escaped major problems - perhaps that is about to change over the remaing period of Microsoft support for Windows 7!

 

I’ve set up an Ubuntu 18.04 desktop which, so far, is running well and will be my main computer. My Windows 7 system will be disconnected from the internet when Microsoft cease support in 15 months time (or perhaps earlier if Microsoft don’t improve on their recent updates record).

[plodr]

The Servicing Stack update, 3177467 should have been installed first. MS should have offered this alone and first and only after that was installed, offered the other patches.

3177467 came out in Sept. 2016 and I didn't install it. It was updated in Oct. 2016 and I still didn't install it.

I used to get a WindowsSecrets newsletter where Susan Bradley, who now posts at the Ask Woody (Woody Leonhard site) as the Patch Lady said in May 2017 that there were 3 patches Windows 7 users should have. I then installed 3177467 at the end of May 2017, after checking my history to see if I had the 3 items she recommended.

 

I assume because of this, and the fact that I go to the catalog and grab the Security only patches, I haven't had a problem. Note: I have yet to install October's patches. MS releases them, discovers there are problems so MS pulls them then re-releases them and hopes that the problems are fixed. If not, they are pulled again. (Windows 1809 has been twice so far).

 

Since I don't want to be a beta tester for MS, I wait until the end of the month, image our four computers then I install the patches.

[Kick]

Hi Plodr,

 

My Windows 7 system is fairly new (Spring this year) and replaced my old HP SFF 32bit desktop when its power supply began to fail (it was not an economically viable repair job so I got myself a 'no system installed' desktop and a Windows 7 SP1 professional OEM disc). I'm sure that I had not been previously installed KB3177467 before it was offered this September. With the fiddling around I had to do to get the September updates installed, I did eventually discover that KB3177467 had to be installed before the other September updates. Now this month I have been offered KB3177467 again but it did not show until the other October items had been installed and the computer restarted.

 

As I said, I have hidden KB3177467 and it will remain hidden until I can be sure I really need it to replace the September installation - would the update retain the same KB number if it is an updated version? If this is the case, would I need to uninstall the presently installed version or would the hidden October version, if I unhide it, install correctly over the top of previous version?

 

I always create a backup image of my C: partition every month just before the second Tuesday Windows updates (using Macrium Reflect). I do another image backup a couple of days after the updates if all is running correctly. I keep these image backups for roughly three months before deleting the older ones (I also keep a set of image backups for each partition taken after the original update immediately following the the installation of the operating system.

[plodr]

Trust me, you need it. All iterations of the Servicing Stack retain the original KB number 3177467.

 

Susan Bradley is renowned for getting to the heart of Windows patching. She is a MS MVP

Susan Bradley - Third Tier

(there is a Canadian physician with the same name.)

Small Business Susan

She no longer writes for WindowsSecrets Susan Bradley | Windows Secrets

so I can't link to the article she wrote in 2017 mentioning 3 patches that all Windows 7 users should be sure are installed. They are 3020369, 3177467 and 3172605

You can now find her at askwoody

Patch Lady – 31 days of paranoia – day 12 @ AskWoody

 

Look at the items under Executive Summary here, if you want a 2nd opinion

Microsoft Windows Security Updates October 2018 release overview - gHacks Tech News

Windows 7 and Windows Server 2008 R2 PCs require the Servicing Stack Update 3177467 prior to installation of the October 2018 updates.

Just google the update, set the time for the past week and you might find other articles telling you to install it first.

[Kick]

Trust me, you need it. All iterations of the Servicing Stack retain the original KB number 3177467.

 

Hi Plodr,

 

Thanks for your advice. I have unhidden the KB3177467 update and installed it without problem.

 

Regarding "Windows 7 and Windows Server 2008 R2 PCs require the Servicing Stack Update 3177467 prior to installation of the October 2018 updates", KB3177467 did not appear in my October Patch Tuesday updates until after I had received and installed the others and restarted the computer so I am hoping there will be no problem because I have installed it afterwards - so far so good though.

 

I've made a note of Susan Bradley (the patch lady) and the Ask Woody website which I have now bookmarked - many thanks for that suggestion.

 

Cheers for now, Kick.

[plodr]

IMHO, the "check for updates" is broken. An update that should be installed to fix updating should have been show by itself. Apparently this isn't happening.

 

Rather than trust MS to show me what is needed, I read a few sites and depend on the pros there to tell me how to proceed.

[Kick]

Hi Plodr,

 

The September Patch Tuesday updates included a version of KB3177467 with the other updates but no advice to install it first so hence the initial problems I experienced that month. However the October Patch Tuesday updates did not include a version of KB3177467 until after the other updates had been safely installed and the computer restarted. It was only after that point that Windows Update showed KB3177467 as being ready for installation. Clearly MS separated KB3177467 deliberately from the other October updates but in a way that meant users would install the other updates before KB3177467. As I explained in an earlier post, not understanding the significance of KB3177467 until your helpful explanation, I thought this was Windows Update causing more problems by repeating an already installed update so I hid it. After your explanation, I unhid it and iKB3177467 seemed to install without problems. Since then I have noticed no problems so hope my system has been updated correctly.

 

You say you believe that "check for updates" is broken but I am not sure if your are suggesting that I still have a problem on my system or you are just suggesting there are inefficiencies in general with MS "Check for Updates".

 

Thanks for your continued support. Cheers, Kick.

[plodr]

No, I'm not suggesting a problem on your end. This is all on MS's end. If they knew that 3177467 was needed before updates would work, why didn't they offer it alone, have you reboot then offer the other updates.

 

Many people had trouble getting Sept. and now Oct. to install yet MS waited a long time before it was mentioned that the Servicing Stack Update aka 3177467 was the issue.

[Kick]

Hi Plodr,

 

Thanks for the clarification. Something to look out for in future Patch Tuesdays I suppose but perhaps nothing compared with what some Windows 10 users are experiencing.

 

Cheers, Kick.

[plodr]

Hah, apparently the Patch Lady tried to install the October updates and discovered what I posted earlier.

Patch Lady – 7 Metadata problems @ AskWoody