Now KB5015814 won't install

Hello Ken. I'm Greg, 10 years awarded Windows MVP, here to help you.

Are these updates bothering you in some way? Windows Updates usually eventually sorts them out, but it has to scan 1.5 billion PC's every few days so it can get behind and may take awhile to sort them out as to priority, or process the telemetrics to adjust the update to avoid failure.. So you can ignore it and not micro-manage updates if they are not bothering you.

There are some fixes others have reported for those Updates here you can try:

https://ugetfix.com/ask/how-to-fix-kb5014668-fa...

https://www.youtube.com/watch?v=LybFiawwcdM

You can also try manually installing them to see if that works:
http://test.catalog.update.microsoft.com/v7/sit...

When you say not to give "canned" replies, do you mean the Updates fixes that work most, collected from tens of thousands of Update cases I''ve handled here, which I've prioritized according to what works most, give out dozens of times every day, and which work more than half the time? Those are only given if it's reported that NO Updates will install or other serious dysfunction. You don't have that situation, correct?

Feel free to ask back any questions. Based on the results you post back I may have other suggestions if necessary.

______________________________________________

Standard Disclaimer: There are links to non-Microsoft websites. The pages appear to be providing accurate, safe information. Watch out for ads on the sites that may advertise products frequently classified as a PUP (Potentially Unwanted Products). Thoroughly research any product advertised on the sites before you decide to download and install it.

Sorry, I didn't mean to sound like no one was giving valid suggestions. I know these fixes have worked for most in the past but this seems, and I only says seems, that this problem doesn't fit the mold. And yes, I've edited my original post to list that 3 other updates did download and install without a problem. It appears that only cumulative updates are failing for me. Maybe this would steer me in another direction??

I was hoping that MS or some advisor here was aware that there might be a valid "fix" for this specific problem which MS might have put out.

I really do appreciate that you and other Independent Advisors take the time to help people.

So if I may ask, do you recommend to just wait this out and not worry about trying to install the cumulative updates for a while or maybe give it another shot with one or more of your suggested fixes?

Thanks... really...

Ken M.

Edited: Let me say this in another way... since I am receiving and successfully downloading and installing other updates, would any of the suggestions not really apply in this situation?

This one is giving me fits as well...Did not have any problems with updates before this one today KB5015814...It installed on some systems...Failed on most systems. Have already tried using the StandAlone installer file...Nope...Still not installing...I'm trying various troubleshooting steps now but so far have not found a successful fix.

I, too, am having this problem on all three of my Windows 11 computers with both the Windows Update and the standalone installer. The update gets to 100% and then says it failed. I have run DISM and SFC to no avail.

One thing that I have noticed on two of the three machines is that if BITS is set to automatic and running when the update starts, it is reset to manual and off when it fails. I don't know if that has anything to do with the problem, but it did seem a bit quirky.

This isn't a fix... but if you didn't try to install the optional KB5014668 at the end of June, that had the same problem and in my thread on that one, some people were able to install it with great difficulty and some couldn't. But now, some think that if you can install KB5014668, then this one will install. It's a long thread but if you didn't try to install it, this is that thread. Can't install KB5014668 - Microsoft Community I'm not saying to install it but it seems to be the same problem so this might be the first time some are seeing it. No one seems to know what the common thread is that is causing this problem.

Hopefully an authorized MS fix will be forthcoming in the near future.