Discussion in 'other software & services' started by emmjay, Aug 15, 2016.
We had some discussion about it earlier this year. At the moment I can't find all the links (I'm currently in the process of updating), but here is one:
@BoerenkoolMetWorst There's also some information at the following link.
Still hitting Error 0x8000FFF when installing the Win7 Monthly Rollup? There's a reason. by Woody Leonhard.
As per post #605 ... . If you are not getting the Oct 2018 release of KB3177467 offered through windows update (because you did not install the first release in September 2016), you could try temporarily hiding all of the windows updates you have waiting to be installed (to clear the WU queue), to try to trick Windows Update into sending it. If that does not work, you just have to download it from the catalog. I can not think of any other solution.
Well, this morning I found my entire windows update queue void of all updates thanks to Microsoft (I did not hide anything). One update sent KB3177467 (October release) - which is interesting because I installed the original version of KB3177467 in September 2016. This is getting more and more confusing. I am assuming that Microsoft has pulled the October rollup for W7 or more likely this is their way of making sure that everyone installs the updated SSU before any of the October updates are installed.
Is there a site where a Windows 8 fan can pick up the whole shooting match all rolled into one.
This nibbles and bits act is so old it's boring and many times not worth the hassle.
But do appreciate @mood and others helping in keeping up with all these recents. Microsoft is such a bummer. They don't realize how very superior Windows 7 & Windows 8 is to so many devoted users.
I don't seem to see much problems on my Win 7 Pro 64-bit with the October updates.
I didn't install the latest servicing stack update (SSU).
I have KB3177467 installed from September 2016; so that's probably not the latest version (?).
I manually downloaded (from the catalog) and installed:
- 2018-10 Cumulative Security Update for Internet Explorer 11 for Windows 7 for x64-based systems (KB4462949)
- 2018-10 Security Only Quality Update for Windows 7 for x64-based Systems (KB4462915)
Then I used WU to get and install:
- the Office 2010 updates
- the .Net Framework update KB4459922.
(Those updates installed in that order)
As said, I don't see much problems.
I'm not sure whether I should install the latest SSU (KB3177467) from the catalog, just to be sure (if only for the future) ....
Like the rest of us, you will have to wait for Microsoft to issue an official statement. Yes, I know that is like waiting for Godot. Hopefully they will fully explain what the user is actually required to do. If not, the decision is yours - err on the side of caution is probably the best way to go.
If Microsoft decides not to do what is right by the consumer, hopefully a techie will compare the original SSU to the updated SSU to see if any specific system files have changed. I have not seen that as yet.
About servicing stack update (SSU) (KB3177467) :
There is the one from September 2016 and the one from October 2018.
But what is so different between the two?
Isn't the only difference that the one from September 2016 was "critical" and the one from October 2018 is classified as a "security fix".
The KB3177467 says:
And when we go to that blog by John Wilcox of Microsoft:
To me it seems, going by what I posted in reply #611, the only difference is that it was reclassified. That's all.
I could manually install the "new" one. I'll have to think about it.
Yes, it has been reclassified. From non-security to security.
Windows Update is checking to see if the September 2016 version is installed and even if it is, WU is offering the October version for install. It might be a requirement under the cumulative monthly rollup process - the newer release may contain some specific code so that the stop error does not occur.
On my system WU is not offering the October version .....
Yesterday when I updated Win 7, it gave me the October Quality Rollup and the Malicious Software Removal Tool first, installed those, and then lastly gave me KB3177467 by itself. So I'd bet on your first guess above... that something is amiss in the October Rollup and they pulled it.
KB3177467 (Servicing stack update for Windows 7 SP1 and Windows Server 2008 R2 SP1: October 9, 2018) is only offered in Windows Update when Windows Update doesn't have any other updates listed (such as a Rollup, for instance). Or, in other words, KB3177467 won't appear in Windows Update until the whole Windows Update queue is cleared.
Still hitting Error 0x8000FFF when installing the Win7 Monthly Rollup? There's a reason.
Windows users are still hit with error 0x8000FFFF
Aha, thank you !!
My rollup for W7 was pulled but i still have the Oct .net rollup for W7.
Wow, that's weird... Yesterday I got everything else BUT the October .NET Rollup.... seems very inconsistent...
Not as unchecked optional update, either?
Tuesday, I got KB4459922 offered as unchecked optional ('recommended') update.
Ok, maybe it was under Optional. I have a rule to not install any of the Optional updates, and no recommended either, so I don't look there often. Just whatever comes thru as important. I'll have to check again next time I restore my 7 image. I'm in 10 now...
Everyone getting different results does not surprise me. I am sure there are a lot of reasons, some obvious and some not.
I have found a techie who stated that he compared the Sept 2016 and Oct 2018 versions of KB3177467 and found no differences. That is, all files are the same size and have the Sept 2016 date alongside them. I do not link to twitter comments, so you can take this with a grain of salt. Martin Brinkmann at gHacks stated that the Oct 2018 version is a prod to sysadmins who ignored it in 2016. As a security update they will not ignore it. The care and feeding of the enterprise has no bounds . At this time we do not know if the Oct 2018 version will be the go-to version for future patches. It would not hurt to install it over the Sept 2016 version. MS may choose not to clarify, so we will not know until that becomes an issue.
EDIT 10/12: The Oct 2018 version does not install over the September 2016 version. Both versions will show on your system with the same KB number. The 2016 version is 18.104.22.168 (superseded/update) and the 2018 version is 22.214.171.124 (installed/security update).
My understanding at this time is that both these patches are designated 'permanent', and not removable. In other words you can not uninstall them (control panel or dism). Microsoft states that any attempt to uninstall a permanent update (dism or otherwise) may corrupt windows update.
I found this article on how to uninstall a 'permanent' update (safely) and it works, but it has risks...
Imagine what it must be like to participate in a windows update team meeting on a Wednesday at Redmond. Must be wild.
FYI. Just checked for updates, and this is what I see (Win7 64-bit):
You get the 'recommended' Security and Quality Rollup update for .NET Framework, KB4459922, offered as 'Important'. I suppose in Windows Update "Give me recommended updates the same way I receive important updates" is checked. With a default Windows installation that is the default setting. I have that unchecked, and because of that, I get recommended updates offered as optional, recommended.
And the fact that you get the 2018-09 Preview offered, that is probably because the 2018-10 Rollup is pulled, as emmjay reported.
That is correct.
Separate names with a comma.