This browser is no longer supported.
Upgrade to Microsoft Edge to take advantage of the latest features, security updates, and technical support.
![](data:image/svg+xml, %3Csvg xmlns='http://www.w3.org/2000/svg' height='64' class='font-weight-bold' style='font: 600 30.11764705882353px "SegoeUI", Arial' width='64'%3E%3Ccircle fill='hsl(128, 8%, 22%)' cx='32' cy='32' r='32' /%3E%3Ctext x='50%25' y='55%25' dominant-baseline='middle' text-anchor='middle' fill='%23FFF' %3EA%3C/text%3E%3C/svg%3E)
Windows 10 22h2 security update [KB5034441] fails to install with code: 0x80070643 problem was solved for me with reinstallation of Windows 10 using the Media Creation tool . Took about 5 hours . But the security update that has been giving everyone problems downloaded on the second try . I have , over the last 2 days , been checking for updates to see if it really worked and it appears in the control panel as downloaded . I want to thank that guy who suggested that fix . I did not do a clean install . I kept my files and apps
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.
I have still been facing the same problem with KB5034441 and error 0x80070643. I really don't understand why Microsoft can't either fix the problem themselves or issue another patch to resolve the problem. Why isn't this update being corrected? I really don't feel comfortable personally messing with hard drive settings!
It seems Microsoft hasn't fix, and isn't in any great hurry to fix this error.
Multiple suggestions, some dangerous enough to cause potential boot failure.
Why hasn't Microsoft just removed this abysmal failure from the update lineup?
Millions of Windows users are frustrated over this constant failure. Maybe 10% of the users managed to get it to install. Bravo Microsoft. Yet another push by your software developers that fails as soon as the door is opened. It was nice back in the days of WinXP, 7 and 8.1 where we could go in and block those updates that failed and Microsoft refused to fix. Now you just cram it down everyone's throat, hoping it eventually works! I don't blame people who try to hold onto 7 or 8.1. At least we had some control not just over damaging updates, but we could control the sequence.
Here is another way to state what I think Mr. Besler was saying: Most of us are not computer techs. We don't want to tamper with settings. If we must, at least make the instructions intelligible to non-savvy people who comprise the majority of MS users. As to this update, either fix it, give us easy non-threatening instructions on how we can fix it, or make it go away so it doesn't try to update each time we boot up. That said, can anyone provide some guidance?
Yeah, that's not a fix....
That’s my point. So the update shouldn’t be applied. So why is Windows Update trying to apply an inappropriate update? When recovery is disabled and the drive is bitlocked.
Shouldn’t it detect this and then mark the update as not required instead of trying to apply it and then fail?
