Solved Is there a way to prevent specific KB5014668 from installing ?

Yeah @glassskuter I've been doing some googling and there's a few posts. Error 0x8000FFFF seems to be the most common error people are having, but I've yet to find anyone else who has 0x080073701 like me. Most people describe the update loop which I never had, or the update reaching a certain point & then giving a message about undoing changes (which I also never had). Mine downloads, appears to climb in percentages, until the moment it reaches 100% on the installation progress, but instead of then flicking to ask me to restart, it brings up the error message.

Interestingly I found some posts on reddit that implicates Malwarebytes, which apparently caused problems for people on 15th June Patch Tuesday. It was for those running the (then) beta 4.5.10.200, which is now not a beta & the version I have installed on this Windows 11 machine. I had no probs with the June Patch Tuesday, but MBAM didn't update to that version until the day after.... Anyway for me disabling it completely hasn't worked, even though it did for some. Discussion here with a link through to here

I've actually just uninstalled MBAM *just* in case some drivers that load with the programme still being installed are getting in the way, though I feel that is a bit of a long shot. I'm going to repeat the SFC & bat file etc & I'll report back if it's changed anything for the better. (I feel doubtful it will - my symptoms don't match).

Powershell as well as wushowhide.diagcab both failed to hide this update. Windows update manager worked great

I run chkdsk c: /f like 5 times and each time it say fixing system partition. it never finish fixing

catspyjamas said:

but I've yet to find anyone else who has 0x080073701 like me.

Click to expand...

Error code 0x80073701 means ERROR_SXS_ASSEMBLY_MISSING The referenced assembly could not be found.

Don't waste any more time troubleshooting and perform an in-place upgrade.

Manually fixing the error can be tedious and take a long time.

Leave Malwarebytes off the system while performing the in-place upgrade.

Use the Support Tool from Malwarebytes too.


Answer the Reinstall Malwarebytes for Windows pop-up window with: No.

When done perform the In-place Upgrade.

Tekkie Boy said:

Error code 0x80073701 means ERROR_SXS_ASSEMBLY_MISSING The referenced assembly could not be found.

Don't waste any more time troubleshooting and perform an in-place upgrade.

Manually fixing the error can be tedious and take a long time.

Leave Malwarebytes off the system while performing the in-place upgrade.

Use the Support Tool from Malwarebytes too.

https://support.malwarebytes.com/hc/en-us/articles/360039023473-Uninstall-and-reinstall-Malwarebytes-using-the-Malwarebytes-Support-Tool

Answer the Reinstall Malwarebytes for Windows pop-up window with: No.

When done perform the In-place Upgrade.

Click to expand...

Thanks Tekkie Boy. I did as instructed. The Malwarebytes Support Tool did not behave as per the instructions for the MBAM removal tool though. I ensured I selected NO to the offer to reinstall Malwarebytes, but at step 9, instead of it popping up with a window to restart the computer, it brought up a set up installation wizard for Malwarebytes Privacy, which I had already uninstalled a few days ago. I ran the tool again to see if I'd get the prompt to restart (to make sure the clean up was actually complete), but it just stayed stuck on "cleaning up". The log saved to my desktop looked like it had completed though, so I restarted the machine & ran the MB Support Tool one more time, & once again got the installation wizard to set up Malwarebytes Privacy instead of a restart window. So I closed the Privacy set up wizard & the MB Support Tool & proceeded with next steps - as far as I could tell MBAM & MB Privacy were both fully gone.

The repair went smoothly. KB423057 + the June CU + the June .NET updates were in WU waiting to be installed on completion, and curiously - 02-2022 CU preview for .NET Framework 3.5 & 4.8 ( KB5010474). On restart, all the June ones had installed, but the Feb .NET one one was in the queue to be installed. Weird that the NON preview .NET update dated 06-2022 installed before the preview 02-2022 one did. You'd think the June one would supersede the Feb one??

The failed KB5014668 update was still sitting in the Optional Updates following successfully installing everything else. I decided it might be prudent to make sure there were no issues after the above updates were installed, so I ran DISM Check health & Scan health - no corruptions. Then I crossed fingers & tried the failed update again (via WU - not the catalogue). Was delighted to see restart now at the end instead of an error box! On reboot it shows as successfully installed in my history, & my winver confirms 22000.778! Yay!

Ran a SFC after reboot & no integrity violations. Planning to keep MBAM OFF my Win 11 machine for now as I do not have faith that this will be fixed before Patch Tuesday. From posts I have seen on Reddit (linked to in #21 of this thread), Malwarebytes were informed of the issue affecting Windows 11 MBAM users with the June Patch Tuesday updates, & logs were sent to them then. The CU in June caused the same error & same behaviour. Luckily I was not affected that time, but I didn't get the affected version of MBAM (4.5.10.200) until the day after Patch Tuesday. I did have the affected error code 0x8000ffff with the first 2 attempts to install KB5014668, which is the error other MBAM users are reporting. It only changed to 0x080073701 after I'd run SFC etc & retried.

Side note - I have installed the Windows 10 preview CU KB5014666 on my Win 10 machines which all run MBAM too (clearly a tiger for punishment). No installation errors, but they all had stuff to fix in SFC. So it seems that the MBAM conflict is just for Windows 11.

@catspyjamas
Congrats
I have MB 4.5.10 I will try that tomorrow. Problem that I am afraid I dont find the activation code so after I uninstall it I can not reinstall it again. Since you wont install it again I recommend Kaspersky Security Cloud – Free, that would be my second choice.

William654 said:

@catspyjamas
Congrats
I have MB 4.5.10 I will try that tomorrow. Problem that I am afraid I dont find the activation code so after I uninstall it I can not reinstall it again. Since you wont install it again I recommend Kaspersky Security Cloud – Free, that would be my second choice.

Click to expand...

Most paid programs have an online account you can access through the program.
You should be able to find your activation code there.
Either that or you won't need it, because of the online account.
Sort of like tying Windows to a Microsoft account. It "remembers" your activation.

I don't know how Malwarebytes does it, but I would imagine they do it... somehow.
I know Bitdefender does it like Microsoft, er... Microsoft does it like Bitdefender. :)

Heck... even Macrium Reflect is like that. I remember activating the paid version. It was almost like they required your resume, birth certificate and passport to activate the program. Like 5 factor authentication.

Honestly, I would never have figured out how Bitdefender kept track of my activation. But, they have a 24/7 customer service line. For various reasons at one time or another, over the years... I wanted to do a clean
UN-install and reinstall of BD. I had to call... and they walked me through it.
I wasn't required to call, but I had to because I couldn't figure it out, the first time.

These days, it's like Gmail or Youtube or Amazon remembering your password for you.
They remember everything online... for you.



The internet these days, is just filled with... remember.

William654 said:

@catspyjamas
Congrats
I have MB 4.5.10 I will try that tomorrow. Problem that I am afraid I dont find the activation code so after I uninstall it I can not reinstall it again. Since you wont install it again I recommend Kaspersky Security Cloud – Free, that would be my second choice.

Click to expand...

Hey, you may not need to do a repair upgrade, as you haven't got error code 0x080073701. That is the only option if the usual fix (i.e. DISM Restore Health) for error 0x080073701 fails. You may find you can install it once you've completely uninstalled MBAM & reset WU.

Your license key is written inside the app. Just open MBAM, go to Settings>Account & you'll see your key & if you have it, an ID. Also the Support Tool downloads your key to a text file on your desktop for if you want to re-install MBAM. I'd write it down somewhere just in case.

I may install MBAM again once I've seen enough evidence of this issue being fixed. It's not the first time MBAM has caused me issues, so I'm undecided.

EDIT I've just seen that Tekkie Boy has given you some specific instructions for your situation in one of your other threads about this issue here, including what to do if the steps do not work. The advice is for your error 0x8000ffff. Best of luck to you!

Thanks for your feedback.

And I'm glad to hear that everything is working now.

catspyjamas said:

Weird that the NON preview .NET update dated 06-2022 installed before the preview 02-2022 one did. You'd think the June one would supersede the Feb one??

Click to expand...

The newer Net Framework update replaces the old one, so it usually has priority for installation over the older one.

catspyjamas said:

EDIT I've just seen that Tekkie Boy has given you some specific instructions for your situation in one of your other threads about this issue here, including what to do if the steps do not work. The advice is for your error 0x8000ffff. Best of luck to you!

Click to expand...

Nobody has to follow my requests.

If @William654 would like to do an in-place upgrade, he's more than welcome to do so.

I would have been interested to find out more precisely why the error is caused.

And maybe it would be possible to fix the bug without an in-place upgrade.

I'm just curious if Microsoft will change anything in the update and if the LCU can be installed on the next patch day.

Have a nice day.

Solved like this: I am now on v22000.778

It is like life does not have enough problems so I have to take care of this. Yes MalewareBytes has a problem with this update and here is how I solve it:

- Open MB settings and disable autostartup , AI, self protection, rootkit and maybe others
- Restart
- Run Windows update reset components batch file
- Restart
- Open windows services and run the service "Windows Modules installer" leave it as manual without it you will get error 0x80070bc9
- Download the install the update from Windows updates as normal
- Restart you are on 778

Virus..err..update successfully installed