Solution for the error 0x8000FFF in Windows 7

Topic

New Reply

Thanks to two reports from an anonymous poster and @Pradeep_Dixit here, there is a solution for the Error 0x8000FFF. It seems that an old Servicing St
[See the full post at: Solution for the error 0x8000FFF in Windows 7]

12 users thanked author for this post.

AlexEiffel, Elly, deuce120, ch100, Microfix, Geo, Mordhaus, Myst, abbodi86, GreatAndPowerfulTech, geekdom, woody

Reply | Quote

Replies

Thanks PK.

According to my historic notes, KB3177467 was only offered to both my Windows 7 x64 home desktop machines in October 2016, and then only after installing the security rollup KB3185330 which was itself reported to be problematic and causing lockups, although my notes indicate that it installed ok for me. The recommendation at the time was that KB3177467 was installed on its own. Incidentally, my notes also record that October 2016 was the first month of the new “cumulative rollup” updating system. I installed both updates ok at that time, on both machines.

I think it likely that my updating procedures in those days were purely, or at least primarily, based on Patch Lady Susan’s Patch Watch articles on Windows Secrets, so it’s possible that she will have some additional records of the goings-on that month!

2 users thanked author for this post.

cesmart4125, GreatAndPowerfulTech

Reply | Quote

@seff glad your keeping notes I seem to recall at the inception of the Cumm. update model for Win7 back then getting errors or security warnings about opening html links which was a pain at the time, fixed with a batch file and rectified later on that year Nov or Dec seem to recall that was one of the few problems with Win7 updates hence I posted this question yesterday other wise for real “Show Stoppers” you have to delve back as far as 2012 for similar symptoms such as 0x8000FFF If memory serves me its about a twice a year thing with Win7 April and Fall/Autumn you generally know as the Picture and frame reappear on the log in Screen. Thx for clearing that up so as usual they may languish in WUD update until its cleared up. Pretty sure its covered here as apart from a few exceptions normally most stuff that comes down the WUD Chute is slung in there. Wouldn’t hurt for most folks to either wade through installed updates or run “wimc qfe” from a CMD prompt before installing.

Reply | Quote

Any idea if this is going to be for everyone or just certain computers or processors ? Any harm in just going ahead and installing before doing the rollup regardless of your configuration ? Hope they get it fixed before next month.

Reply | Quote

KB 3177467 may already be installed on your computer, and once it is installed you will not have the problem again.

Go to Windows Update. In the bottom left click on “View installed updates.” Scroll down to the section on Windows and see if it is listed. It will help to sort the list by name by clicking on the column title at the top. If it is already installed, you do not need to download and install it.

8 users thanked author for this post.

pmcjr6142, SueW, Geo, Pepsiboy, AusJohn, Myst, Heavenly, woody

Reply | Quote

or enter KB3177467 in the Installed Updates search box

Reply | Quote

That works too!

Reply | Quote

I had already installed this update back in early November 2016, just checked a bit ago. I actually see two identical updates for Nov. 2, ’16. Not sure why. I’ll wait on Defcon 3 to install September updates. Also, I initially did a search for this update in my Installed Updates and it came up with nothing found. It was when I did a manual search down the list that I found this update had indeed been installed.

MacOS iPadOS and sometimes SOS

Reply | Quote

willygirl,

I also did a search for this update in my Installed Updates and it came up with nothing found.  Then I tried to download this update, and a message appeared stating I already had downloaded this update.

Go figure.  From now on, I will run Windows Update a second time after I download updates.

Edit to remove HTML – Please use the “Text” tab in the post entry box when you copy/paste

1 user thanked author for this post.

Myst

Reply | Quote

As always, the recommendation is that you do not install any updates before overall clearance is given here, no matter whether it’s an update itself or merely a pre-requisite fix prior to installing an update. If your computer is running fine now, then leave well alone until Woody raises the DefCon rating to 3 or higher and then read the related article before doing anything. If the recommendation at that time is that you need to ensure that you have a pre-requisite fix installed then that is the time to deal with it, not now. We are still in the very early stages of establishing the reliability of this month’s updates and the likelihood is that they may well be hot-fixed or even pulled by Microsoft before you need to do anything. Sit tight!

Never was patience ever a greater virtue than on the second Tuesday of the month!

1 user thanked author for this post.

Myst

Reply | Quote

I just checked my installed updates for KB3177467, it was installed September 21, 2016 but I will still wait for the all clear.

Windows 11 Pro
Version 23H2
OS build 22631.5189

1 user thanked author for this post.

Myst

Reply | Quote

Good idea. In the heat of tracking down errors, it’s easy to forget that we’re still on MS-DEFCON 2. For a reason! Normal people shouldn’t have to deal with this garbage.

10 users thanked author for this post.

deuce120, Myst, HiFlyer, Pepsiboy, AusJohn, Frwin, cesmart4125, Mordhaus, Jan K., fernlady

Reply | Quote

Most ‘normal people’ don’t understand anything that goes on ‘under the hood’ of Windows  and trust Microsoft by default settings. Another set are  socially engineered to keep their PC OS and programs updated to avoid malware.

1 user thanked author for this post.

HiFlyer

Reply | Quote

Thank you Woody and your MVPs for the great advice.

I say again, Thanks to all the brave people for installing updates one hour after they are released.

These people are chomping at the bit and raring to go and when they do, they then scream “help me!”

It is thanks to these people that the bugs are found almost immediately.

Either they are Microsoft fan boys or just do not pay attention to the MS defcon rating.

I do understand some do not have a choice and for those, I am sorry.

Reply | Quote

Like Seff, I installed KB3177467 in October 2016. fernlady installed in September 2016.

It looks like some people did not do their 2016 installs and now it is causing a little bit of an ado on this site.

Edit to remove HTML

Reply | Quote

This happened because of the idiosyncrasies of SSU installation.

The SSU must be installed by itself. It does not show up in the Windows Update queue unless there is no pending important update in the queue. So each month (back then updates were separate) you installed your updates and if there were any unchecked updates in the important updates, the SSU did not show up. Ad infinitum. So many people never saw or installed the SSU.

But if you recall that during that time we were hunting for “speedup” patches to keep Windows Update from searching “forever.” KB 3177467 was one of the last “speedup” patches before the Cumulative Updates started. And it is one of the ones we still recommend installing FIRST before going online with a clean install.

6 users thanked author for this post.

Elly, ch100, geekdom, AusJohn, abbodi86, woody

Reply | Quote

When KB 3177467 was first released by Microsoft I recall at the time a discussion regarding servicing stack updates not being offered by Windows Update unless there were no other updates available.  My recollection is that even if other updates were available Windows 7 users could still get KB 3177467 by hiding the updates offered by Windows Update and then using Windows Update to check again for updates.  My recollection is that KB 3177467 would then be offered by Windows Update and users could install it.  After installation of the servicing stack update users could unhide the updates previously hidden so that they could be installed.

Reply | Quote

That is correct. But it would not show up in the Update queue unless there were no pending updates, checked or unchecked.

Reply | Quote

I was simply trying to say (perhaps in a long-winded way) that for those who prefer to use Windows Update to obtain updates rather than downloading them manually from the catalog, they should still be able to get KB 3177467 using Windows Update if they first hide any pending updates.

Reply | Quote

Too many updates to hide.
Just hide the current one, install everything up to that time, which means August 2018 and only after that unhide the September 2018 update. And learn a lesson from it.

Reply | Quote

True @PKCano, good effort to find and provide this solution, but in the last 2 years there were many opportunities to have KB3177467 as the only update remaining to be installed and as such showing in WU. And for those still believing that they know what they do by manually downloading from the Catalog and installing selected updates, this instance should teach them a lesson. There are in reality only a selected few who really understand the under the hood Component Based Servicing mechanism. On this forum there is only one single poster understanding this in the deepest detail at the architectural and design level and only few others who are able to install correctly manually and instruct others how to do it.
Microsoft is responsible only to resolve the issues of those who download and install using the supported and recommended procedure, like any other manufacturer of products in fact. Nothing unusual here.

Reply | Quote

My KB3177467 was an optional update and probably unchecked. I wasn’t to smart in 2016. I sure have learned lots since then.

Windows 11 Pro
Version 23H2
OS build 22631.5189

Reply | Quote

No, KB3177467 has always been a Critical Update of the category which should never be avoided.

There is a single potential exception in that category of Critical Updates which is KB2952664.
Literally hundreds of millions of people currently use Windows 10 which include the functionality provided by KB2952664 on Windows 7 so I am wondering if that one is actually useful to avoid. Avoiding KB2952664 may create dependency problems in the future, but this was not the case yet.

Probably KB3177467 did not show because you had other updates missing and pending which should raise a red flag in relation to the procedure followed by some posters here.

Reply | Quote

With Macrium Image at the ready ….. All Sept WU’s Installed without issue. Did 2-Re-Starts as normal routine …..  KB4457144 W7 Sec-Qual Rollup; KB4054530 Net Frmwk (4.7.2); KB4457918 Sec-Qual Net Frmwk 3.5.1 -to- 4.7.2; KB890830 MSRT; KB4227175 Excel ’10 32-Bit.

W7-64 SP1, i5 Sandy Bridge per signature. Other than skipping Mar ’18 my Grp A WU’s have gone without issue other than 2-3 Re-Starts for sluggish behavior sometimes, not always. Good Luck to All!

W10 Pro 22H2 / Hm-Stdnt Ofce '16 C2R / Macrium Pd vX / GP=2 + FtrU=Semi-Annual + Feature Defer = 1 + QU = 0

3 users thanked author for this post.

jburk07, Chessie, cesmart4125

Reply | Quote

fernlady wrote:

I just checked my installed updates for KB3177467, it was installed September 21, 2016 but I will still wait for the all clear.

I just checked mine and I have it installed  in September too   But will still wait till we get the all clear before installing the September ones this year 

Reply | Quote

OK, I just got thrown a BIG loop…I checked my update history and it said KB3177467 was not installed. Per Woody, downloaded the standalone, ran it, and it told me it was _already_ installed!

Went back into WU, checked four times, even viewed Hidden Updates, and brother, it ain’t there either!

What am I to believe? The blasted OS won’t let me install KB3177467 stand-alone… Could it be part of some other package and is just not showing up as a standalone?

“Aaaargh! Here comes another Nibbling Duck!!”<SOB!>

(Sorry about that…but as Woody said, “Normal people shouldn’t have to stand for this.” Not that being ‘normal’ is anything to brag about…but even we geeks have our breaking points.)

As Groucho said, “Any questions? Any answers?”

Win7 Pro SP1 64-bit, Dell Latitude E6330 ("The Tank"), Intel CORE i5 "Ivy Bridge", 12GB RAM, Group "0Patch", Multiple Air-Gapped backup drives in different locations. Linux Mint Newbie
--
"The more kinks you put in the plumbing, the easier it is to stop up the pipes." -Scotty

Reply | Quote

Look under “View Installed Updates” (bottom left of Win Upd).
Click on the title of the Name col. to sort on the col.

1 user thanked author for this post.

Nibbled To Death By Ducks

Reply | Quote

I used the control panel, add and remove programs, view installed updates on the left, then type in the number in the search box.

2 users thanked author for this post.

cesmart4125, Nibbled To Death By Ducks

Reply | Quote

That works too!

1 user thanked author for this post.

Nibbled To Death By Ducks

Reply | Quote

Given that it’s gone from being an unchecked optional update to being a critical pre-requisite for updates, is it too much to hope that MS will reclassify it in the catalog so it’ll show up for those of us who hid it in the past? (I had to trawl through the history of my WSUS server to see that I had marked it declined back in the day due to numerous reports of issues with the update.

No matter where you go, there you are.

1 user thanked author for this post.

Nibbled To Death By Ducks

Reply | Quote

I wonder who’s the blame for not installing SSU once it released

SSU is always important and safe, it should have been installed long time ago
regardless if first WU push was a little bit problematic (i.e. KB3177467 was offered together with other pending updates)

Reply | Quote

? says:

a person can also run (administrator) CMD>systeminfo.exe | findstr KB3177467 to see if this specific update is installed and\or (admin) CMD>systeminfo.exe to see ’em all. back in Septemeber 2016 i must have deemed this update as yet another evil one since it is not installed. my notes from then remind me of all the winx tomfoolery and microsoft’s molasses speed update servers (to force me to convert or die).

1 user thanked author for this post.

Nibbled To Death By Ducks

Reply | Quote

KB3177467? I just checked my Windows 7 installations and it is NOT there. I remembered back at that time I did not install it, so I am not surprised.

However, does this episode mean that for Group B patchers like myself, I still have to install this thing before attempting to install the September (and later) security only updates?

Still, why do so many people have to install these Rollups as soon as they were released? All of them are on automatic update? We should thank them anyway, because we might never know about these problems then, haha.

As Woody said, why should we have to deal with these issues? If the Rollup requires that update, and it is not present, should Windows Update then download and install that update first?

Hope for the best. Prepare for the worst.

3 users thanked author for this post.

Jan K., PerthMike, Nibbled To Death By Ducks

Reply | Quote

If the Rollup requires an update, and it is not present, should Windows Update then download and install that update first?

What a brilliant idea!

Should be really simple and easy to implement as well.

But we are after all dealing with Microsoft and their AI here, so odds are not good…

Reply | Quote

“Now, I’m not a drinking man, but…”

Went through CMD line query, it now shows up.

Went thru the control panel routine, it now shows up.

Went thru the WU section “installed updates”, it now shows up.

I swear it was NOT showing up earlier, under ANY method of search.

I’ll go a step ahead of Woody: “No intelligent life-form should have to go through this.” Does this fall under “Cruel and unusual punishment?”

Some day in the far future, as OS will accurately detect a problem, accurately inform the user what the problem is, then fix it accurately. Self-detecting, self-repairing.

I know, Star Trek.

Thanks to all who responded!

I’m going to visit my old friend Jack Daniels.

Win7 Pro SP1 64-bit, Dell Latitude E6330 ("The Tank"), Intel CORE i5 "Ivy Bridge", 12GB RAM, Group "0Patch", Multiple Air-Gapped backup drives in different locations. Linux Mint Newbie
--
"The more kinks you put in the plumbing, the easier it is to stop up the pipes." -Scotty

Reply | Quote

“Update History” is NOT a good indicator of what is installed on your computer. If you install an update, then uninstall it, it still shows in the history as installed because, well, history is history. It was installed at one point by WU. But WU doesn’t record an uninstall you do yourself.

Always use “View installed updates” to see what is really still installed on your PC.

4 users thanked author for this post.

Elly, OldBiddy, geekdom, Microfix

Reply | Quote

It’s interesting, but I also couldn’t see whether KB3177467 was installed on my system when I searched the list of installed updates. It’s wasn’t in Update History either. And I searched this way and that, but couldn’t see it anywhere. When I downloaded it from the Microsoft Catalog and tried to install it, it said that it was already installed on my system! So hopefully I’ll be ok when I need to install the September update.

Reply | Quote

dir /b C:\Windows\servicing\Packages\*KB3177467*

1 user thanked author for this post.

OldBiddy

Reply | Quote

Thank you, @abbodi86. I did find it in the location above that you suggested . These packages have long file names as your wildcard indicates. I don’t know why my searches didn’t reveal the file. While I am an unsophisticated windows user, I thought I knew how to do basic file searching! But I appreciate your help so when the time comes to install the September updates hopefully I won’t encounter any problems.

Reply | Quote

For what it’s worth in case anyone is interested, I did finally locate KB3177467 when I searched Installed Updates. I just hadn’t allowed the list of updates to become fully populated before I began the search. The list exceeded 300 updates, but I didn’t notice I started the search before it had finished loading.

1 user thanked author for this post.

Elly

Reply | Quote

PKCano wrote:

Thanks to two reports from an anonymous poster and @Pradeep_Dixit here, there is a solution for the Error 0x8000FFF. It seems that an old Servicing St[See the full post at: Solution for the error 0x8000FFF in Windows 7]

Thanks! I don’t do Patreon so I am sending a donation through paypal. Having that unfixed was like an itch I couldn’t scratch!

Reply | Quote

I had KB4457144 fail yesterday and today on Win 7.  Then with your information, I went directly to Microsoft Update and installed KB3177467. (Sorry but I’m paranoid about clicking links and installing things from people I don’t know.)

Let Windows Update try a third time on KB4457144 and it worked!

THANK YOU SO MUCH!
The Vanguardian

Reply | Quote

The links in the main blog post are direct download links to the MS Catalog for KB 3177467.

1 user thanked author for this post.

geekdom

Reply | Quote

I’ve run into a spoofed site before, person I helped had malware redirecting them to a fake bank site. Luckily they noticed the site was different before they put in their account and password.

Reply | Quote

I too encountered several failed attempts on the KB4457144 update both yesterday and today, but on only one of my laptops. The other systems had no issues with the download and install, so I was puzzling over the reason. All are running Win 7 Pro 64 bit on Intel i7 or i5. Then I stumbled onto your site. After reading your posts about KB3177467 and checking all the computers, the only one without that update installed was the one that kept getting the error code. After installing KB3177467 (64 bit version), the KB445144 installed via Windows Update without any hiccups. THANK YOU (although I know it’s a bit premature to relax since who knows what problems lurk in the successfully installed security update)!

Reply | Quote

WARNING: The “systeminfo” command has a nasty bug: it produces a truncated patch list when there are more than 245 installed patches!

If you have win7 machines that have been in service for a very long time, with a large number of installed patches, then “systeminfo” may not list KB3177467, even when it actually is present.

I have two such machines, one with 330 patches and another with 645 patches. On both of these machines, the numerically-sorted patch list produced by “systeminfo” is truncated well before it ever gets anywhere near the 3177000 mark.

Here’s a better/safer command to use:

wmic QFE | findstr 3177467

 

 

5 users thanked author for this post.

jburk07, Microfix, RetiredGeek, columbia2011, satrow

Reply | Quote

My thanks to the OP. This was the trick to installing KB4457144 on my problem machine.

Reply | Quote

Okay, since I’m apparently the most outspoken Group B person, I’ll be the first to ask this:

Does this only apply to KB4457144 or does the Security Only KB4457145 need it too?

Thanks    

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

2 users thanked author for this post.

geekdom, Microfix

Reply | Quote

It would be interesting to know if anyone from Group B has beta tested this particular patch.

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.

Elly

Reply | Quote

If I understand the function of metadata correctly, could the metadata for this particular patch (KB4457144) be revised by Microsoft to include a check and install of KB3177467?

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

James Bond 007 wrote:

KB3177467? I just checked my Windows 7 installations and it is NOT there. I remembered back at that time I did not install it, so I am not surprised. However, does this episode mean that for Group B patchers like myself, I still have to install this thing before attempting to install the September (and later) security only updates?…

Yes, you do have to install it. I too am Group B. I have had KB3177467 installed on all of my Win7 computers ever since October 2, 2016. I encountered no issues after installing this update. Info about KB3177467:

KB3177467 — Servicing stack update for Windows 7 SP1 and Windows Server 2008 R2 SP1: September 20, 2016
This update replaces the following updates:
Update for Windows 7 for x64-based Systems (KB2533552)
Update for Windows 7 for x64-based Systems (KB3020369)
Prerequisites:
To apply this update, you must install Service Pack 1 for Windows 7 or Windows Server 2008 R2.

 

1 user thanked author for this post.

geekdom

Reply | Quote

Charlie wrote:

Okay, since I’m apparently the most outspoken Group B person, I’ll be the first to ask this: Does this only apply to KB4457144 or does the Security Only KB4457145 need it too? Thanks

I don’t know. Regardless, all Win7 users should have the KB3177467 servicing stack update installed. I am not willing to uninstall KB3177467 in order to revert to the prior servicing stack update which was KB3020369 so that I could test whether or not the Security Only KB4457145 will properly install when using the older servicing stack.

For Group B users, I recommend installing any servicing stack updates by themselves — as in not trying to install any other updates at the same time. After installing KB3177467, reboot your computer and wait 15 minutes before installing subsequent updates. My recommendation is in line with what is mentioned in the KB article for KB3177467. The upshot from the KB article is that the prior servicing stack update (KB3020369) has timing issues when installing windows updates.

Separately, I will install and test the September Security Only KB4457145 update late Friday night. If I encounter any issues, then I can restore my OS partition from yesterday’s backup while I sleep.

 

2 users thanked author for this post.

Charlie, geekdom

Reply | Quote

Nibbled To Death By Ducks wrote:

OK, I just got thrown a BIG loop…I checked my update history and it said KB3177467 was not installed. Per Woody, downloaded the standalone, ran it, and it told me it was _already_ installed! Went back into WU, checked four times, even viewed Hidden Updates, and brother, it ain’t there either! What am I to believe?

BY FAR the easiet way to check if an update is “for sure” installed is to open RegEdit, click the “Edit” tab, click “Find”, then search for the KB number (drop the KB and search for 3177467 in this case).  If an update is installed it will always return it’s info this way. As an example when I search for 3177467 the return is:

Key Name: (left column) (forum word wrapped)

amd64_microsoft-windows-servicingstack_31bf3856ad364e35_0.0.0.0_none_8957f279c7d227d0

Update Info: (right column) (forum word wrapped)

Package_2_for_KB3177467      ~31bf3856ad364e35~amd64~~6.1.1.1.3177467-4_neutral_LDR

1 user thanked author for this post.

columbia2011

Reply | Quote

KB articles are updated with this issue and resolution with SSU  KB3177467
https://support.microsoft.com/help/4457144
https://support.microsoft.com/help/4457145

2 users thanked author for this post.

geekdom, ch100

Reply | Quote

The MS Support page for KB4457145, the 2018-09 Security-only Update, says:

This update may fail to install with error 0x8000FFFF.

Before installing this update, install KB3177467, the last Servicing Stack Update for Windows 7 and Windows Server 2008 R2 SP1, to resolve this issue.

So Group B will also need to install KB3177467, the Sept 2016 SSU.

1 user thanked author for this post.

Elly

Reply | Quote

My computer says it’s alrd installed 3177467, but I still can’t install the new updates without crashing my computer (I’ve literally gotten a blue screen)

Reply | Quote

I could install the patch without ox8000FFF error after installed the patch 3177467. Microsoft’s product is such a pain to deal with sometimes. Thanks for the help!

Reply | Quote

Just my 2 cents.. i dont have the older stack update installed, its hidden for the reason it CRASHES your system,  and it looks like from the comments if i installed 4457144 id have a nice blue screen to look forward to, so im never installing it( nor will i ever need it, it fixes stuff like windows shell and media that i dont even use) Im sorry, but telling users to unhide and old update that WILL crash our systems just to upload an update that will cause  a BSOD is unsafe and ridiculous,  i could care less if my machine ever gets updated again, its not like if we skip a few months any amazing virus will be released, most ‘NORMAL’ users as myself with a home computer dont even know what the updates even do, they take a good hour or more to install then stalls and you need to wait however long to restart the computer, they arent needed.

1 user thanked author for this post.

PKCano

Reply | Quote

Fortunately (hopefully), most people WILL NOT follow your example. Perhaps the following information will help you understand Windows Patching better.

aerosmith598 wrote:

i dont have the older stack update installed, its hidden for the reason it CRASHES your system,

How do you know that the problems with the SSU KB3177467 reported over two years ago have not been fixed in the ensuing time? If they have, Windows Update is smart enough to not overwrite the fixes. I have installed it on all of my machines and it has not crashed any of them.

aerosmith598 wrote:

( nor will i ever need it, it fixes stuff like windows shell and media that i dont even use)

You may not use them directly, but the OS uses them. And they are, nevertheless, installed on your system. If you do not patch, you leave your system vulnerable. And if your system is vulnerable, you expose those with whom you come in contact or share files.

aerosmith598 wrote:

Im sorry, but telling users to unhide and old update that WILL crash our systems just to upload an update that will cause a BSOD is unsafe and ridiculous,

KB3177467 is a prerequisite for KB4457144. If you install KB3177467 manually, then without rebooting, install KB4457144 from Windows Update, the former will prevent the latter from causing error 0x8000FFF. The reason for the error is the prerequisite is not present.

We are still on DEFCON-2. There is no reason to install updates immediately. You have time to reconsider your decision.

2 users thanked author for this post.

jburk07, Elly

Reply | Quote

All i wanna know is if i unhide the 467 update, install it, then install KB4457144 is my screen going to be blue? yes i know i will need the patches eventually like maybe next week, i just dont want to cause problems since right now i dont have either and my computers fine.

Reply | Quote

and i did lookup the older stack update and alot of people say it loops your computer into a restart cycle and crashes it, i dont want that.

Reply | Quote

SSUs have to be installed exclusively (by themselves). If you unhide KB3177467. it will not show up in the Windows Update queue as long as there are any other pending (checked and unchecked) updates in the important update queue. You will need to hide all pending updates and keep rechecking and hiding until KB3177467 shows up – that may be a LOT of hiding. Then install the update but DO NOT restart. Unhide KB4457144, install it, THEN reboot. Then you will need to unhide all the rest of the ones you hid, search for updates and that will bring you to the current pending updates.

The easier way would be to download the SSU from the Catalog, using the link with the right bittedness in the blog post above, install it manually without rebooting, then install this month’s Rollup.

However, I repeat, there is no need to install the updates now. We are still on DEFCON-2. WAIT until the DEFCON number is 3 or above and follow Woody’s instructions.

2 users thanked author for this post.

Elly, geekdom

Reply | Quote

More and more, Group A looks like Group B.

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

Not so

For Group A, the fix for KB4457426 IE11 CU (for example) KB4463376 released 9/14 will probably be included in the 2018-09 Preview Rollup and will be included in the 2018-10 Monthly Rollup. It can thus be installed through Windows Update (eventually).

Group B will NEVER get the fix for IE11 through Windows Update.

Edit to correct the reference.

3 users thanked author for this post.

jburk07, Elly, geekdom

Reply | Quote

PKCano wrote:

Not so For Group A, the fix here will probably be included in the 2018-09 Preview Rollup and will be included in the 2018-10 Monthly Rollup. It can thus be installed through Windows Update (eventually). Group B will NEVER get the fix through Windows Update.

Separate thread, maybe? With this explanation.

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

Sorry, too many KB numbers.
That was a comment referred to KB4463376, the IE11 CUupdate. Will correct the above post to reflect.

Reply | Quote

Your explanation makes a compelling argument for Group A.

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

Why do you recommend that after installing KB3177467 users “DO NOT restart” before installing KB4457144?

Reply | Quote

Because it is not necessary.

Reply | Quote

PKCano – O. K.  Thanks.  I thought that perhaps your use of capital and bold letters in “DO NOT restart” was meant to suggest that something unpleasant might happen if the computer was restarted prior to installing KB 4457144.

 

Reply | Quote

does it matter if is reboot pc after installing KB3177467 or not and then install KB 4457145

Reply | Quote

My preference is to install the Security-only update first, then the IE11 Update. A reboot is not necessary in between.
But others have installed them in reverse order without problems. No reboot between is necessary.

Reply | Quote

@PKCano i mean KB3177467 0x8000FFF fix reboot then KB4457145 or not ? someone recommend reboot then wait 10 minutes and install KB4457145

Reply | Quote

We have not had reports that KB4457145 causes 0x8000FFF yet, only the SQMR KB4457144. But the MS pages for KB4457145 say that it may.

But you should WAIT until the DEFCON number is 3 or greater to install. We may have more information by then.

1 user thanked author for this post.

Elly

Reply | Quote

Not sure if it is helpful but Group B Win7 without KB3177467 installed. KB4457145 (Security Only) and KB4463376 (IE) installed without any obvious issues so far. Also, installed Security Only .Net update without issue.

Reply | Quote

Just want to say thanks for the correct solution to my problem with getting error code 8000FFFF every time I tried to download Security Monthly Rollup for Windows 7 64bit.

After I downloaded the update you suggested and provided the link for all is well as shown below…

 

2018-09 Security Monthly Quality Rollup for Windows 7 for x64-based Systems (KB4457144)

Installation date: ‎9/‎16/‎2018 4:13 PM

Installation status: Successful

Update type: Important

A security issue has been identified in a Microsoft software product that could affect your system. You can help protect your system by installing this update from Microsoft. For a complete listing of the issues that are included in this update, see the associated Microsoft Knowledge Base article. After you install this update, you may have to restart your system.

Reply | Quote

Weren’t there problems with KB3177467 when it was originally released?

Reply | Quote

It was just deployment problem, update itself is problem-free
a simple forced restart solves it if happened, only once

people tend to overrate some tiny problems, which now led to real problem
SSUs are very important and useful, they should never be avoided unless they cause BSODs

Reply | Quote

I tried updating to September patches today on my Win7 workstation, group A. It gave me this error.

So I remembered seeing it here and quickly read the thread. I found that the KB3177467 was hidden (the only update hidden for me). I don’t remember why it was hidden, maybe I was stuck in a reboot loop when it came out and I hid it temporarily and never thought about it because I wrongly assumed cumulative updates would be cumulative for everything because I am no expert in Windows patches. Or maybe it was at the very beginning when I was group B for a few months until I was confident to go group A and then I also wrongly assumed cumulative meant for everything except the things we always see apart like .net, Office, etc.

Anyway, I unhid the patch, but didn’t see it obviously, because thanks to you guys, I read that it was not showing due to September patches being offered (any patch hides it, right?). So I hid September patches, saw the KB3177467, tried to install it and it gave a different error code. Maybe that is why I hid it in the past. Anyway, I googled the error code 80246007  and ended up with registy fixes. I did an sfc /scannow that turned up negative. I thought no way a normal user should go through registry fixes to have Windows install updates so not me either on my work workstation. I needed an easy fix I can explain to people.

I then instead downloaded Windows Update troubleshooter, ran it, it reregistered the service (don’t know why it wasn’t registered no more I really don’t do any fancy magic on my work computer that would explain that and I am group A and I got the other cumulative updates with no issue). So after that I was able to install KB3177467, then the September updates and now I am fully patched with no issue.

I don’t follow the Defcon on purpose this time because since the task scheduler vulnerability has been out, we have received an unusually high amount of trick emails coming from our customers and other people that have us in their address book. Very fancy different emails trying to trick us into opening orders, invoices, issues of all sorts, complete with faked signature from people we know. Maybe it isn’t related to this vulnerability, but I know at least one of our customer was completely down (all the network got infected up to their server and they still try to restore without getting infected again). So to me, a user clicking the wrong link happens so easily I just thought it wasn’t worth it to not give the September patch a try.

Reply | Quote

Group B here without KB3177467 installed , KB4457145 (Security Only) installed without any issues

Reply | Quote

Check under installed updates to see if KB3177467 was installed at a much earlier date.

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

@geekdom i checked in the best way to do this via registry search for 3177467 not found so the issue with this error is only with Monthly Rollup

Reply | Quote

I am new  to this forum. Infact I joined just two minutes ago. Luckily I  have not installed KB 4457144 on my Windows 7 because I had a hunch that something is not right.

Somewhere, in the top  of the article, regarding KB3177467 it says “Close any open programs then double click on the downloaded file, agree to install, and reboot the computer when asked. After rebooting, you should be able to install the September Rollup”. 

Lower down, some member has posted this“Then install the update but DO NOT restart. Unhide KB4457144, install it, THEN reboot” 

Could someone tell me whether I should reboot my Computer after installing KB 3177467 or should I, without rebooting install KB 4457144 and then reboot once?

I would like to thank everyone here for their valued contributions to this forum.

Reply | Quote

First, check to see if KB3177467 is already installed on your computer. Look in Windows Update\View installed updates. If it is there, you will not need to install it.

If you download and manually install KB3177467 from the Catalog, reboot when asked.

If you hide all the updates in Windows Update until it shows up (that can be a lot of updates), you can install it through Windows Update. Reboot when asked, but it may not be necessary. Then unhide and install the whatever updates you want to install from the hidden ones.

Reply | Quote

Thank you PKCano for your prompt reply. Yes I have checked up from Windows Updates and seen that this Update  was actually hidden by  me earlier   and is listed amongst   hidden Updates.  So shall I go ahead  and  restore  it and install it from here only ?  I am running Windows 7 64 bit SP 1 with Intel Processor. Thank you once again.

Reply | Quote

It will not show up in Windows Update unless there are NO pending updates (checked or unchecked) in the queue.

Reply | Quote

As mentioned  earlier, KB 3177467 did   show up in my list of hidden updates. However, when I did  try to  unhide and  restore it, it suddenly vanished. So I  downloaded  the update, using the link above  and  installed KB 3177467 [ 64 bit ]. Thereafter I  restarted. After that, there  was no problem  in downloading  and installing KB 4457144. As a cross reference I checked that  both the  above  updates  are showing in the list of  installed updates.

I   remember the  good ol’ days [ till  2015 ] where  Windows Updates were downloaded and installed  without  any issues.  These  issues  have started  following Microsoft’s insistence to Window 7 Users to  upgrade  to Windows 10  even offering us a free upgrade for a limited time. Seriously I am trying to figure out  if there is any link between Microsoft’s vehement  insistence on an upgrade   and   the   regular issues faced  by Window 7 users every Patch  Tuesdays. Frankly speaking, why would I  upgrade to Windows 10, considering that there are already too many issues their users are facing. Windows 7 has always been user friendly even  till  now except when Patch Tuesdays arrive as a nightmare.

Reply | Quote

KB3125574 is missing in my environment, whereas KB 3177467 is fully deployed (so it says in sccm) and I tried to deploy KB3125574 with this months Monthly rollup and they all failed.

I had about 20 work deploying KB3125574, and if that worked then the monthly’s went OK. I’ll try deploying KB3125574 as a standalone update to a few test machines. Maybe MS will re-release whatever dependencies are broken shortly as well.

Edit to remove HTML – Please use the “Text” tab in the post entry box when you copy/paste

Reply | Quote

Why would I want to install kb4054530?  None of my programs require .NET framework 4.7.2

Thanks in advance for your advice on this update.

Charles

1 user thanked author for this post.

jburk07

Reply | Quote

Just for the record:

KB4457144 installation by Windows Update failed with Error code 8000fff on Win7 SP1, Intel CPU

Installed KB3177467 on its own as recommended

Then installed successfully KB4457144 via Windows Update

Reply | Quote

Had error 0x8000FFF on KB4457144 .

Installed KB3177467 , then installed KB4457144 successfully.

Thank you!

Reply | Quote

I had installed KB 3177467 (September 2016) in November 2016.  But MS is now offering a “new, improved” version, as Woody has just advised.  If we have the “genuine, original” one, do we need to install the new version?  I gotta know!!!

Reply | Quote

We are at AskWoody MS-DEFCON1 so it’s highly advisable to NOT patch yet.

Windows - commercial by definition and now function...

1 user thanked author for this post.

geekdom

Reply | Quote

Thanks sir, after installing KB 3177467  manually I was finally able to install 2018-09 and subsequent rollups that kept failing on 8000FFFF unknown error

Reply | Quote