Reported error 0x8000FFFF with the Win7 Monthly Rollup KB 4457144

Topic

New Reply

Reputable report. Anybody else seeing it? No discernible pattern just yet.
[See the full post at: Reported error 0x8000FFFF with the Win7 Monthly Rollup KB 4457144]

3 users thanked author for this post.

ymo1965, geekdom, walker

Reply | Quote

Replies

Yes, Woody, I have just experienced this error. The “retry” also failed with the same error code. Not sure how to proceed! Help!

Windows 7, Home Premium, Group A.

 

Reply | Quote

on windows 7 home premium same issue for me, i was wondering if i should ‘hide’ the update? it looks important so im unsure, i had 3 important updates today, 2 worked, 4457144 did not, any ideas? im guessing its on Microsoft’s end

Reply | Quote

i hid the update, any word on the issue?

Reply | Quote

Aerosmith you will probably be waiting a few days at least for people to report it, and Microsoft to investigate it. Then they have to fix it.

We want to thank you for testing the patch.

Keep an eye on woody’s site. Eventually a fix, or a decision of what to do will be made.

1 user thanked author for this post.

Kranium

Reply | Quote

aerosmith598 wrote:

I hid the update, any word on the issue?

Hiding a problematic update is how it has always been done with Windows, that is, until Windows 10 came along.

Group "L" (Linux Mint)
with Windows 10 running in a remote session on my file server

3 users thanked author for this post.

ymo1965, Kranium, johnf

Reply | Quote

Looks like another bumpy month. I’ll be sitting on my hands waiting for the all clear.

Windows 11 Pro
Version 23H2
OS build 22631.5039

2 users thanked author for this post.

Myst, BobbyB

Reply | Quote

Fernlady yes. My friends and I wait until the week before the next patch tuesday when woody says to proceed.

Thanks to the brave people that install one hour after the updates are released.

3 users thanked author for this post.

Myst, BobbyB

Reply | Quote

Brave? Oh yes, you mean like the people who make a living testing parachutes?

Reply | Quote

will hiding it have a drastic effect on my machine? i mean do i NEED it? i normally get them the same day they are released, i havent seen a error message like this on a major update before, normally the ones marked ‘recommended’ i dont bother

Reply | Quote

It won’t hurt anything to wait a while an see what is causing this error. You can hide the update temporarily or set your Windows Update to either “Check for updates but let me decide whether to download and install them” OR “Never check for updates.” When the problem is resolved, you can reverse those settings to your normal ones.

4 users thanked author for this post.

Elly, walker, Myst, BobbyB

Reply | Quote

I just installed it here on a Win7 and didn’t see issues.  It was a slow install though.  Do you need updates?  Ultimately yes we all need to ensure our machines are up to date on patches.  Do you need them today?  Probably not.  Today is testing day.

Susan Bradley Patch Lady/Prudent patcher

10 users thanked author for this post.

Elly, ymo1965, walker, Chris B, Myst, Moonbear, fk5353, abbodi86, woody, BobbyB

Reply | Quote

MS-DEFCON is 2; unless you are a beta tester, don’t install current updates.

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

4 users thanked author for this post.

Demeter, walker, Kranium, woody

Reply | Quote

Did you saw (in catalogue) the long list of patches, replaced by KB4457145 and far more longer by ~44? Interesting…

Reply | Quote

Is this error being seen on install or afterwards?  I have installed on a couple of Windows 7 machines in test environment and I haven’t seen any errors.

Reply | Quote

With so many issues with updates after the fact. Why even download them in first place. Our pc’s have more trouble with these darn rollups and rollouts.  Between a good AV, and software updates, we’re just as safe or venerable whether we have microsoft security UD or not. I didnt update for nearly 1.5 to almost 2 yrs and all was well. SMH

1 user thanked author for this post.

Reply | Quote

Having the same issue fully updated windows 7 64bit

1 user thanked author for this post.

woody

Reply | Quote

Follow-up to my earlier post:

#216891

Edit: Sorry, anonymous posters cannot add attachments.

Reply | Quote

I registered now to add the attachment. This is the info if it helps. I also tried to fix the windows update, tried to manually update from the catalog, and deleted the download folder for windows update then tried to redownload. Same issue.

Reply | Quote

There is a solution for the error 0x800FFF on Win7. See this post and the following discussion.

3 users thanked author for this post.

Elly, walker

Reply | Quote

The error occurred for me during the installation phase; no issues with downloading the update. More importantly, there was NO BSOD upon reboot. I was able to retry the installation of the update as often as I liked, even though the error code was the same for each attempt.

3 users thanked author for this post.

Elly, rontpxz81, woody

Reply | Quote

I am guessing the affected Machines with kb4457144 are all x64 (amd64,64bit) or is this common to x86 (32bit) as well? Well it arrived on my Win7x86 machine yet to fire up the Win7x64 machines yet and as for Win8.1×64 never seems to any worries there YET!

Reply | Quote

Yes, I am getting the error 0x8000FFFF on KB4457144 as well.  Great!

1 user thanked author for this post.

woody

Reply | Quote

Are you running 32-bit Windows, or 64-bit?

Anything odd about your machine?

Reply | Quote

A wild guess… are you on an AMD machine?

Reply | Quote

To anonymous that said, “Yes, I am getting the error 0x8000FFFF on KB4457144 as well. Great!” could you please give some information about your PC?

Can we please have; OS, bit, CPU, and maybe Video (nvidia, ati, intel, etc.), even brand of network card would help.

It could be related to the OS, the chipset, the CPU (Intel or AMD) who knows, but we need a common denominator.

Thank you.

Reply | Quote

Tried on Win7, group B, x86,x64, older hardware on Intel chipset… no problem.

1 user thanked author for this post.

BobbyB

Reply | Quote

The machine is a VM, Intel, Xeon, 64 bit.

VMware Virtual SVGA 3D Graphics Adapter, VMware, Inc. compatible

OS is Windows 7 Enterprise SP1.

Thanks!

Reply | Quote

Hi Folks, I also got this error, then I went to the Microsoft Update Catalog website to get the standalone package for this update:

http://catalog.update.microsoft.com/v7/site/Search.aspx?q=KB4457144

There one can download either a .msi or a .exe file. The .exe file has only 32 KB instead of 320 MB.
It seems that this .exe file is broken, and if windows tries to install a broken file this can not work.
Maybe it would work to install the .msi file, but I didn’t try yet.

Many greetings from Germany, Ivan

Reply | Quote

The .exe file is bundled with the update KB 4457144 and is automatically executed when you download through Windows Update.

If yoy are using the Catalog, download both files and put them in the same location (on the desktop or in a folder). When you double click on the .msu file (that’s the update) the .exe file is automatically executed in the process. You do not need to click on the .exe file.

1 user thanked author for this post.

walker

Reply | Quote

Yes, but if the same broken file that one can download as a standalone .exe file is bundled to be used in the automatic Windows Update method, then it would fail. Maybe this is the problem?
It correctly should have approx 230 MB.

Reply | Quote

You need both files. The .msu file is large, the .exe file is small. You only double click on the .msu file. You do not need to click on the .exe file as it gets executed automatically in the process of install of the .msu file.

1 user thanked author for this post.

walker

Reply | Quote

I understand, so is it that the exe file kind of starts the msi file in the Windows Update method?

Reply | Quote

The instructions are given twice above. The .exe does not “start” the .msu file. You were instructed to NOT click on the .exe file.

If you do not understand the instructions you should be using Windows and not the Catalog manual download/install. The Catalog is not for average users but for those who understand patching.

1 user thanked author for this post.

walker

Reply | Quote

I just tried putting the .exe (pciclearstalecache_7e856b95c514e1ec18de7263030237e8ef0160a8.exe) next to the .msu but I’m getting the same error. I also tried executing the .exe first, but I still get the same error on using the .msu.

What is the source of this information? I’ve installed hundreds of msu’s and have never seen one that requires copying another file next to it.

Reply | Quote

Hey Y’all,

FWIW, I just installed 4457144 and 4 other updates on my Dual Boot (Win 10 Insider/Win 7 HP) Dell 1564 Laptop w/o problems.

Of course I had a brand new Macrium Reflect Image before attempting this!

HTH 😎

May the Forces of good computing be with you!

RG

PowerShell & VBA Rule!
Computer Specs

Reply | Quote

Hmm… is this going to be another MS “oh, give us a couple of months and we’ll get around to fixing it” and then “nah, sorry, can’t be bothered” like the SSE2 issues earlier this year?

Anything to push some more Windows 7 users onto Windows 10, so it seems.

Reply | Quote

No issue here, x64, Intel cpu

can any of those which failed for them zip and share C:Windows\Logs\CBS\CBS.log?
or the whole CBS folder if there are multiple files
maybe we could trace the error cause

1 user thanked author for this post.

woody

Reply | Quote

Yes, seeing the exact error code on pre-prod testing VMs (ESXi 5.5, VM v10) and SOE hardware (Lenovo T470s, Intel i5), Windows 7 Enterprise x64. Both the standalone MSU installers from the Update Catalog and the cabs deployed through WSUS/ConfigMgr show the issue.

Testing 2008 R2 now

1 user thanked author for this post.

woody

Reply | Quote

Get back to us, please…

Reply | Quote

I just installed KB4457144 in W7 x64 with intel cpu with no issues.

But I realized something: I went to the system32 folder and sorted by modified date to see what files have changed, and 133 files updated, like the one that fixes the thask scheduler 0day, schedsvc.dll, have the actual date and hour I executed KB4457144, 2018-09-12 8:45.

I thought every windows file (at least exe and dll) would have the real modification date, I think it used to be that way. Is this a normal behavior with cumulative updates?

Reply | Quote

Original files dates are preserved only if you installed the update from Windows Update or by running msu file directly

installing with DISM and cab file gives the installed files current modification date

4 users thanked author for this post.

Elly, woody, liamZ, Bill C.

Reply | Quote

Hi, thanks for answer, so maybe something is wrong with my system?

Cause I installed the msu file:

windows6.1-kb4457144-x64_5ca467d42deadc2b2f4010c4a26b4a6903790dd5.msu

Any idea of what is causing this?

Reply | Quote

You Double-clicked and installed?
it should have preserve files dates

anyway, it’s just cosmetic thing, it doesn’t affect the system of files integrity

Reply | Quote

Yes, I know, but you know… “something” is wrong, and I don’t know what or why…

I have checked my other W7 x32 installation and does not preserve file dates  either, so I think there is some tweak I have done that is causing this behavior.

Maybe it is that I have moved c:\SoftwareDistribution to another partition and created a junction to it?

Reply | Quote

Hello,

I don’t know if it is relevent but I’m encountering this issue (error 0x8000FFFF or -2147418113) at work with KB4343900 (Windows 7 August 2018 cumulative update) on :

– 2 x86 machines out of 577

– 94 x64 machines out of 1067

Regards.

5 users thanked author for this post.

OldBiddy, walker, Microfix, woody, BobbyB

Reply | Quote

So within 14hrs of release, patches have been rolled out to 1644 machines!
Don’t you have VM’s on differentiating hardware devices to test on prior to rolling them out at your work?

Windows - commercial by definition and now function...

Reply | Quote

He’s talking about the August update, not the September one.

1 user thanked author for this post.

woody

Reply | Quote

Precisely. And that makes me wonder if this is something new with the September Rollup, or if we’re just seeing many reports of an old problem.

1 user thanked author for this post.

walker

Reply | Quote

The problem are slow ms-update-servers because of lightning-strike on 4th september.

https://siliconangle.com/2018/09/04/severe-weather-impacts-microsofts-azure-cloud-services-texas/

https://rcpmag.com/articles/2018/09/11/microsoft-cloud-outage-postmortem.aspx

 

 

Reply | Quote

Apologies to anon #216969 reading blind spot <embarrassed>

Windows - commercial by definition and now function...

Reply | Quote

AMD or Intel?

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

I haven’t installed any September updates, but I also encountered an error installing the August security roll up, KB4343900, as I posted here: #215426

KB4343900 Installed ok the second time I tried. I’ve never had problems installing updates before.

Reply | Quote

On my Intel Notebook, the installation without problems. On my AMD-PC, I will waiting for better times.

Regards
Andreas

Reply | Quote

I’ve discussed this unspecified error (with other patchday issues) within my blog post

Patchday issues with updates & WSUS (September 11, 2018)

Possible cause may be:

• damaged system file (sfc /scannow may help)
• a virus infection (check your system for that)

Maybe that helps.

Ex Microsoft Windows (Insider) MVP, Microsoft Answers Community Moderator, Blogger, Book author

https://www.borncity.com/win/

1 user thanked author for this post.

woody

Reply | Quote

Its not a virus issue, also, it would be pretty much impossible that EVERY user that cant update 57144 has a computer virus.

Reply | Quote

Windows 7 Ultimate x64.

Not seeing this error but after installing either the quality or security only patches I lose the ability to rename directories upon their creation.

Rolled back and it works as it should.

4 users thanked author for this post.

Kranium, woody, Seff, columbia2011

Reply | Quote

That’s a new one. I wonder if anyone else who has installed the updates successfully has put this to the test, or could do so? It would certainly be useful to know if this was a one-off.

2 users thanked author for this post.

awGROM, woody

Reply | Quote

I have installed the Sept Rollup on one VM (Win7 Ult x64, Intel i7 Ivy Bridge) so far and I do not have that problem.

4 users thanked author for this post.

walker, awGROM, Seff, woody

Reply | Quote

Applicable updates installed; I have no problem renaming directories.
(KB4457918)
(KB4457144)
(KB890830)

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

3 users thanked author for this post.

Chessie, awGROM, Seff

Reply | Quote

Thanks for the feedback Guys.

Based on you guys not having the same problem I hit the search engine.

Found others who have had the same problem in the past and a solution.

So I reinstalled the security only patch (KB4457145) , rebooted  – still had the problem.

After backing them up I deleted the 5 registry keys identified in the fix, rebooted, now all is good.

Cheers

Link that pointed me to the fix, provided by Mr Andersen (Neo??) 🙂

https://answers.microsoft.com/en-us/windows/forum/windows_7-files/cannot-rename-folders-in-windows-7-could-not-find/8fd250d8-8e4a-4053-b31c-9513081b8566

 

 

1 user thanked author for this post.

Kranium

Reply | Quote

Whilst your comments are appreciated, and obviously helpful, I personally have no intention of ever embarking on the deletion of registry keys in order to get a Windows Update working properly. I’d rather bring forward January 2020 and stop all updating to be honest! I strongly recommend that those of limited technical knowledge like myself stay well clear of the registry.

1 user thanked author for this post.

Reply | Quote

i will admit i have used windows 7 for years, since maybe 2012? and this is the first time i have ever not been able to get an update due to an error, so before we all panic lets assume its a issue they know about and will fix, also, i read what the update actually fixes, and i didnt even use or recognize half of the programs, like the first is windows media, i dont even think i have that.  Also, for anyone who uses MSE) Microsoft security essentials) the update failed to load and slowed and pretty much made MSE non functional, while i was trying to install 4457144 i did a regular MSE update as i do 5 times a day, and it took literally 25 minutes to ‘search’ for an update, the second i ‘hid’ 4457144, it worked fine, updated in a few minutes as it should, so you see, its a error that is pretty severe, I’m keeping it hidden until next month.

Reply | Quote

To clarify, my computer is Windows 7 x64 Home Premium with an Intel i5-2410M processor. So I am surprised to hear that only AMD processors are affected. But I tried very early yesterday afternoon and have not tried again this morning.

Reply | Quote

I don’t think anyone yet knows what the common thread for failure is. That’s why information that you and others are providing is important.

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

are their any blue screen reports for people who have been able to install it?

Reply | Quote

Not seeing a problem on Win7/Ent/32bit (4 PCs updated).

GaryK

Reply | Quote

I ran into this issue updating Windows Server 2008 R2 systems using the the Monthly Rollup KB4457144. It failed on all servers with the 0X8000FFF error.

The same effective patches are available as a cumulative update for IE11 and Windows Server 2008 R2. These are:

2018-09 Cumulative Security Update for Internet Explorer 11 for Windows Server 2008 R2 for x64-based systems (KB4457426)

2018-09 Security Only Quality Update for Windows Server 2008 R2 for x64-based Systems (KB4457145)

Installing the separate updates works, but does not supersede the August 2018 Monthly Roll up.

I hope this helps.

Reply | Quote

@anonymous:  It helps to show that the updates you are referring to are for September.   There are so many update issues causing problems, and many are NOT for September, so it makes it that much more difficult for an “illiterate” such as I, to try to make sense out of it all.

Appreciate the information.  Thank you.

Reply | Quote

its being reported on several websites, just ‘google’  kb4457144 error, its widespread.

Reply | Quote

I was :
anonymous – “Yes, I am getting the error 0x8000FFFF on KB4457144 as well.  Great!”

I was able to resolve this be uninstalling KB4343900.  It reverts to KB4338818.  Then I did a retry on KB4457144.  I hope that MS fixes this.

OS Name    Microsoft Windows 7 Enterprise
Version    6.1.7601 Service Pack 1 Build 7601
System Model    VMware Virtual Platform
System Type    x64-based PC
Processor    Intel(R) Xeon(R) CPU E7-L8867  @ 2.13GHz, 2128 Mhz, 2 Core(s), 2 Logical Processor(s)

Thanks!

Reply | Quote

I am also seeing the failure on windows 7, 64-bit machines, intel. The machines had all other required updates prior to the failure.

Reply | Quote

Monthly Rollup 4457144: Install successful 2018-09-12 12:00 (EST) after many failed attempts in August with error 0x8000FFFF. Windows 7 (64) Ult. Intel i7-3770. NVidea driver & card.
I used windows update. Windows did it’s thing then did a double reboot. An hour later all is fine so far: no network device issue, no error 0x8000FFFF.
I had first successfully installed the NET Framework 4.7.2 update (4457035) that also would not install since August. I checked if everything looked good, killed all the running apps (anti-virus, firewall, a File manager background process, etc. and went for it. I will follow up if any problem(s) comes up in the next day or so.
Best of…luck?
J.

Reply | Quote

The same thing happened to 3 2012 R2 servers as well.  0x8000FFFF error and it fails to install even after repeated attempts.

Reply | Quote

Patch KB4457144 will be installed after installing Stack Update “Servicing stack update for Windows 7 SP1 and Windows Server 2008 R2 SP1 – Windows Server 2008 R2 SP1 – KB3177467 (x64)” for 2008 R2 OS

4 users thanked author for this post.

Kobold Curry Chef, PKCano, geekdom, woody

Reply | Quote

OS: Windows 7 Home Premium 64-bit Service Pack 1
CPU: Intel Core i5-3570K Ivy Bridge 3.4GHz LGA 1155 77W Quad-Core Desktop Processor w/ Intel HD Graphics 4000
Video Card: SAPPHIRE 100355-1GOCL Radeon HD 7850 1GB 256-bit GDDR5
Update KB4457144 failed = error 8000FFFF

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

Reply | Quote

feedback from MS premier support:

install Servicing Stack KB3177467 (September 2016), restart computer, install KB4457144.

KB3177467 ist pre-requisite for KB4457144

3 users thanked author for this post.

PKCano, columbia2011, woody

Reply | Quote

the KB3177467 update does not require restarting the computer. you can install KB4457144 right after installing KB3177467

1 user thanked author for this post.

woody

Reply | Quote

Can confirm installing Servicing Stack KB3177467 (September 2016) then KB4457144 + reboot works successfully. (no reboot required between the 2 KB installs)

Reply | Quote

Conversation continues here:
https://www.askwoody.com/forums/topic/solution-for-the-error-0x8000fff-in-windows-7/

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

Hi all,

I’m thankful for this forum, it helped me identify the problem which crashed my Windows 7. The cumulative update in August (4343900) caused BSOD, I had to hide it to prevent reinstalling. Now 4457144 does the same, my computer just had a BSOD. I uninstalled the update, but I wonder, will I have to do this every month?
Will windowsupdate send me an update that crashes my computer every month?

Reply | Quote

Windows Updates are CUMULATIVE. The next one contains the current one.

But check out the thread here, it might help. Be sure KB 3177467 is installed on your machine.

1 user thanked author for this post.

walker

Reply | Quote

Two Win 7 machines Intel CPUs- no problems installing all of September updates.

Reply | Quote

Reply #217204 did the trick on my problem Win7x64 machine. The other five worked fine.

Reply | Quote

My Windows 7 (SP1, 32-bit) machine already has KB3177467 (installed back in October 2016) but fails to install KB4457144, so this solution doesn’t work for me.

In fact, I haven’t been able to install any of the Security Monthly Quality Rollup updates since October 2017 (KB4041681). Anyone in the same boat?

Reply | Quote

anonymous wrote:

In fact, I haven’t been able to install any of the Security Monthly Quality Rollup updates since October 2017 (KB4041681). Anyone in the same boat?

Before you think about  KB4457144, first you need to resolve whatever it is that stopped your PC updating since last October. Try the Windows update troubleshooter.

https://support.microsoft.com/en-us/help/4027322/windows-update-troubleshooter

After running the update troubleshooter run Windows update manually. Some updates need to be installed in order. Windows should do that for you but, that means you may need to restart, run Windows update again (possibly more than once) before Windows is right up-to-date. If you are group B, you’ll need to work up which updates to hide each time.

 

Group A (but Telemetry disabled Tasks and Registry)
1) Dell Inspiron with Win 11 64 Home permanently in dock due to "sorry spares no longer made".
2) Dell Inspiron with Win 11 64 Home (substantial discount with Pro version available only at full price)

Reply | Quote

KB3177467 has a dubious history itself from looking at the top mentions in a google search.

Reply | Quote

I had 0x8888FFFF error on trying to update KB4457144. After an advice to manualy install KB3177467, I could install the former update, but after a reboot there is a

PROCESS1_INITIALIZATION_FAILED

BSOD right after Starting Windows screen, every time. The only thing I can do is boot from DVD and system restore prior to updating to KB4457144.

Now, my VirtualBoxes can’t start because of crypt32.dll.

sfc /scannow does nothing.

Edit to remove HTML. Please use the “text” tab in the entry box when you copy/paste.

1 user thanked author for this post.

columbia2011

Reply | Quote

I wondering if a similar situation may occur when installing the KB4457129 cumulative update under Windows 8.1 without the KB3173424 servicing stack update for 8.1 could also cause a possible error 0x8000ffff message.

Reply | Quote

aerosmith598 wrote:

i hid the update, any word on the issue?

I tried to install KB4457918, KB4457155 and KB890830 and got the BSoD and continuous dumps as system tried to restart. Having restored to last check point, the following weird stuff occurred – Network Services unavailable, Norton had to go through Base Filtering Services recovery, the time on the PC was advanced by an hour and the Printer drivers vanished.
All now fixed but updates are well and truly hid!

Win7 x64
Intel i7-4790
12Gb Ram

Reply | Quote

VanSquished wrote:

I tried to install KB4457918, KB4457155 and KB890830…

KB4457918 .NET Framework
KB890830 Malicious Software Removal Tool

KB4457155 KB4457145, KB4457144
See here:
https://support.microsoft.com/en-us/help/4457145/windows-7-update-kb4457145
https://support.microsoft.com/en-us/help/4457144/windows-7-update-kb4457144
https://www.askwoody.com/2018/solution-for-the-error-0x8000fff-in-windows-7/
https://www.askwoody.com/patch-list-master/

Please wait to 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.

walker

Reply | Quote

Cheers – plus

oops finger trouble – I meant KB4457144

Win7 x64
Intel i7-4790
12Gb Ram

Reply | Quote

VanSquished wrote:

aerosmith598 wrote:

i hid the update, any word on the issue?

I tried to install KB4457918, KB4457144 and KB890830 and got the BSoD and continuous dumps as system tried to restart. Having restored to last check point, the following weird stuff occurred – Network Services unavailable, Norton had to go through Base Filtering Services recovery, the time on the PC was advanced by an hour and the Printer drivers vanished. All now fixed but updates are well and truly hid!

Win7 x64
Intel i7-4790
12Gb Ram

Reply | Quote

2 options:

First option: click on the erroron windows update. it will redirect you to the page with errors and solutions.
Second option: If you go to the internet: and search for the update then you find this …

https://support.microsoft.com/en-us/help/4457144/windows-7-update-kb4457144

there you see the error and the KB THAT AN UPDATE IS NEEDED prior this installation.
Search internet again OR click link.

TO MAKE IT EASY:

1. First go to this site: https://www.catalog.update.microsoft.com/Search.aspx?q=kb3177467
2. search the right operatingsystem and version (without x64 is the 32 version)  and download
3. Instal the update
4. go to this site:https://www.catalog.update.microsoft.com/Search.aspx?q=KB4457144
5. follow the same instructions as described with step 2 and 3 for this update

DONE!

Reply | Quote

Please see the solution for the problem you encountered here.

1 user thanked author for this post.

walker

Reply | Quote