Now KB5015814 won't install

Anonymous
2022-07-12T18:42:32+00:00

OK. I tried to run updates today, 7/12. I got the exact error and reactions as when I tried to install KB5015814 that I got for the KB5014668 failure last month.

I ran scripts, tried a lot of advisor recommendations and did the in place upgrade (but rolled it back) for KB5014668 so who knows what was changed or broken then????

Does anyone have something that WILL work this time? I really don't want to spend 5 or 6 hours and get no where again.

Will an in place upgrade work or will restoring an image from before June 22 be a better option. I don't want to do that unless it's a last option.

Please don't have me run the canned things to correct an update error. It didn't work last time so I really would like something that is known to work if that is at all possible.

Thanks.

edited..... 3 other updates did install without issue:

Intel SoftwareComponent 2130.1.15.0

Security Intelligence Update KB2267602

Malicious Software Removal Tool KB890830

Windows for home | Windows 11 | Windows update

Locked Question. This question was migrated from the Microsoft Support Community. You can vote on whether it's helpful, but you can't add comments or replies or follow the question.

0 comments

78 answers

Sort by: Newest
Most helpful Newest Oldest
  1. Anonymous
    2022-08-12T11:56:08+00:00

    I wanted to state that this method works!

    I too had the issue with the two updates but decided to wait until after "patch Tuesday" before jumping on the reinstall windows option.... Maybe Microsoft will actually fix a problem.

    Imagine my angst when, on Tuesday, I now had THREE UPDATES that wouldn't install. Thanks Microsoft!

    After I came across the article bondisdead posted....

    Thank you for this thread! For me I had to 1) disable all Real-Time Protection features of Malware Bytes: Web Protection, Malware Protection, Ransomware Protection and Expliot Protection and 2) open Windows Features control panel, then uncheck .NET Framework 3.5. After a restart and a few pop-up messages from programs which probably required .Net 3.5, I was able to install updates KB5015814, followed by KB5015882. I then re-enabled .NET 3.5 framework and Malwarebytes Real-Time Protection features. Windows update is finally clean after the last 1+ month, and a bunch of useless generic YouTube vides.

    ...., I decided to give it a try and I can say that (with a few more reboots than suggested in the article) this method absolutely works. My PC is now all caught up again.

    I do hope that this will not be something that I (and all of you) will have to do every time from now on... we'll see.

    Thanks to one and all who have gotten us all here.

    Was this answer helpful?

    1 person found this answer helpful.
    0 comments
  2. Anonymous
    2022-08-09T18:41:04+00:00

    Did you also uncheck NET Framework 4.8?

    Yes, I unchecked net 4.8.

    Was this answer helpful?

    0 comments
  3. Anonymous
    2022-08-09T17:10:12+00:00

    Did you also uncheck NET Framework 4.8?

    Was this answer helpful?

    0 comments
  4. Anonymous
    2022-08-08T16:23:10+00:00

    Thank you for this thread! For me I had to 1) disable all Real-Time Protection features of Malware Bytes: Web Protection, Malware Protection, Ransomware Protection and Expliot Protection and 2) open Windows Features control panel, then uncheck .NET Framework 3.5. After a restart and a few pop-up messages from programs which probably required .Net 3.5, I was able to install updates KB5015814, followed by KB5015882. I then re-enabled .NET 3.5 framework and Malwarebytes Real-Time Protection features. Windows update is finally clean after the last 1+ month, and a bunch of useless generic YouTube vides.

    OMG this worked for me! Thank you so much! Finally, my windows updates are clear, and my OCD is sastified :)

    Was this answer helpful?

    0 comments
  5. Anonymous
    2022-08-06T13:25:04+00:00

    I know nothing about the ISO "fix" or if it has the chance to scramble or disable things. I'll just wait until MS fixes it, but I'm not holding my breath.

    Was this answer helpful?

    0 comments