Microsoft confirms it can't fix KB5034441 0x80070643 error on Windows 10

May 2, 2024
Windows 10

Microsoft has officially confirmed that it will not fix the KB5034441 0x80070643 error on Windows 10. Users ran into the error in January this year, when the company released the first set of security updates for Windows 10 and Windows 11.

However, the Patch Tuesday release came with a problem of its own, the KB5034441 0x80070643 error. For those unaware, here is a brief description of the issue. Trying to install the update on Windows 10 resulted in an error message that said Error Install Failure, and it would not go away even if you tried to reinstall the update. It affected the following platforms: Windows 11 version 21H2, Windows 10 version 22H2, Windows 10 version 21H2 and Windows Server 2022.

The error was soon acknowledged as a known issue by Microsoft, and it explained that the update patched a security flaw related to the Windows Recovery Environment (WinRE). Attackers could have exploited the vulnerability to bypass BitLocker encryption using WinRE. The actual problem with the update was that it could not install the update because the recovery partition was not large enough, aka insufficient disk space. FYI, the WinRE partition requires 250 megabytes of free space to install the update. Ironically, some users who experienced the error said that they do not even have a recovery partition on their computer. That's because the update was failing to detect whether the partition existed.

Microsoft could not pull the update because of the nature of the patch, i.e. it is a high security risk that it poses, it has to be addressed. This also meant that users continued to experience the error every time they checked for updates and tried to download the package.

Microsoft says it can't fix KB5034441 0x80070643 error via Windows Update

Users have been waiting for a fix for it for four months, and now Microsoft says it cannot fix it. As Neowin reports, a support page on the Redmond company's website states that an automatic resolution of the KB5034441 0x80070643 error will not be available in a future Windows update. That sounds bad, but don't worry. It doesn't necessarily mean the problem cannot be fixed. There are solutions available for it, but Microsoft says that users will need to resolve the issue manually.

The company has provided some instructions on how to fix the issue, i.e. to increase the size of the WinRE partition. It may seem like a daunting task, but take it one step at a time, and you should be able to do it. You may want to take a look at Martin's tutorial to learn how to fix the 0x80070643 error install failure using Disk Management.

A lot of users may not be tech-savvy to make the changes themselves. There is an easier way to extend the Windows RE Partition. Microsoft has provided a codescript that you can copy and paste in PowerShell, you can find the code here. I recommend taking a backup of your PC before trying the above script, just to be on the safer side.

Did you run into the 0x80070643 error? Share your experience with us in the comments.

Article Name
Microsoft confirms it can't fix KB5034441 0x80070643 error on Windows 10
Microsoft says it can't fix KB5034441 0x80070643 error through Windows Update
Ghacks Technology News

Tutorials & Tips

Previous Post: «
Next Post: «


  1. K. W. Moore said on May 7, 2024 at 6:49 pm

    In checking, my Recovery Partition is already 1000 MB in total and has 1000 MB (100%) in free space, but the update continues to fail. I guess I’ll keep ignoring the problem.

  2. HateGates-IV said on May 4, 2024 at 8:23 pm

    We are all stupid. Yes, we have given Microsoft the keys to our cars. Forget the hackers, Microsoft, in one month has figured out how to force you off your VPN, let their ‘updates’ eat a quarter GB of play space. They kill off your computer hardware as W11 blows up your W10 computer hardware. Stop support of W8.1 way before it’s death. Microsoft is too big and too unchecked. Three updates and Microsoft can brick 3/4 of American computers. How can we allow this monopoly to continue? Standard Oil was split when they had this power. Presidents Teddy Roosevelt and Taft put a temporary end to companies that have too much power and are screwing the citizens. Where’s the outrage? Stop Microsoft NOW!

    1. Anonymous said on May 20, 2024 at 9:25 pm

      Preach! This is unacceptable.

  3. Anonymous said on May 3, 2024 at 6:18 pm

    Just humble Microsoft trying to end Win 10 :)

    1. DD said on May 4, 2024 at 1:39 pm

      Not just W10. I’ve had a much improved computing experience since ditching Microsoft everything for Linux.

  4. TelV said on May 3, 2024 at 9:59 am

    On it mentions that if users fail to reboot after applying the script the system may start reformatting your disk which may lead to data loss. Worth noting.

    Fortunately, my system is running Windows 11 22h2 and isn’t affected by this bug. But how can Microsoft say they won’t fix it when Windows 10 still have another 17 months of support left? It’s incomprehensible that Microsoft would adopt this attitude and think they can get away with it. They caused the problem with their lousy programming so they have to fix it.

  5. Bisscute said on May 3, 2024 at 8:15 am

    One of the first things I do after a clean, local-account install is to fire up a linux live usb and delete the windows recovery partition and then expand the partition next to it in windows to reclaim that space for all kinds of leisure activities. Why? I will never ever use it. Neither will my Windows install.

  6. AC said on May 2, 2024 at 11:00 pm

    Looking forward to the class-action lawsuit making a few lawyers wealthy, while giving the masses a coupon for 10% off their next corporate screwing.

  7. ITDude said on May 2, 2024 at 8:30 pm

    In-place upgrade without data deletion fixed it for me on several machines.

  8. Maniford said on May 2, 2024 at 7:48 pm

    I always delete the Recovery Partition, as I have a different scheme for desaster recovery that proved to be successful though a decade. I will always get this error message.

    Why is no one at Microsoft capable to scan a system during the update process and if the – to be – updated Recovery Partition doesn’t exist, don’t even bother trying an update?

  9. plusminus_ said on May 2, 2024 at 5:17 pm

    I’ve been using a PS script mentioned in a comment on another article (IIRC) and then hiding the update with wumgr:

    A bit annoying that I’ve had to do this sort of manually for 40-50 computers at work *and* home but at least it’s a ‘solution’.

  10. Gilgamesh said on May 2, 2024 at 5:15 pm

    No, no need. But it is better removing the whole WinRE partition. I don’t see any reason to keep it. It just increases the attack vector like the mentioned CVE. If I need to boot in WinRE I can always use the official ISO if I didn’t prepare bootable media with WinRE specifically.

  11. John said on May 2, 2024 at 4:49 pm

    I don’t think advising people to try and resize a partition is a good ideal. I personally never bothered with Bitlocker on my personal PC’s. Then you have the problem with OEM recovery as well. Another wasted space if you ask me, because who really wants to recover to a much older version by way of a imagine created when the PC was initially built? If I have problems with an install image I usually end up doing a fresh install anyway.

  12. Carl said on May 2, 2024 at 4:37 pm

    Cannot Fix?

    Based on my recent experience it is more likely a “Will Not Fix” seeing how close it is to “End Of Life” for Windows 10…

    Only a few days ago I downloaded a new Windows 10 install package thinking that this issue would have been fixed…

    Needless to say when this new install updated the KB5034441 update failed with error 0x80070643… Upon further checking found that the WinRE partition created was only 250Mb in size… So, obviously there would not be 250Mb free (the install drive was 1TB so plenty of room)

    My conclusion: “Will Not Fix” is M$ actual stance – because they could have fixed the install package to create a larger WinRE partition on a fresh install…

  13. John G. said on May 2, 2024 at 3:57 pm

    I am pretty sure that they don’t care anymore what is happening now or in the future with W10. Or even worst, I bet that they don’t want to solve nothing. They all are using MacOS or ChromeOS. LOL, sorry, I couldn’t avoid the joke. Thanks for the article! :]

  14. Fish said on May 2, 2024 at 3:54 pm

    Never trusted Bitlocker at all. Oh,

    Kept ignoring by hiding KB5034441,
    until April’s Patch Tuesday when I
    allowed it, and saw it sail smoothly.


    Well, with m$’s patchy record, I can
    only add hopefully.

    1. Gilgamesh said on May 2, 2024 at 5:18 pm

      It’s OK to not trust BitLocker. But are you telling me that not having any protection is better than weak protection?

      1. Sultan Of Swing said on May 4, 2024 at 5:37 am


        So you’re saying a broken condom is better than no condom. I’m sure the no-condom people have the sense to not go sticking their junk in everything.

  15. Tachy said on May 2, 2024 at 3:17 pm

    You can also do a clean reinstall of 10 with the latest iso. It will make the re partition big enough to avoid this issue.

  16. pHROZEN gHOST said on May 2, 2024 at 3:01 pm

    Never underestimate the power of the MicroShaft!

  17. karlo said on May 2, 2024 at 1:18 pm

    It’s the first time I hear M$ creates bugged update and decides not to fix it. Windows as a service really sucks.
    The simpliest way to fix that is to hide KB5034441 update with wumgr or WU Minitool.

  18. Stefan said on May 2, 2024 at 7:46 am

    Is it necessary to fix it if you dont even use stupid bitlocker?

    1. reader said on May 2, 2024 at 1:43 pm

      This is good question, does just leaving this update out block future security updates or something? I.e. is it a required perquisite for anything non-bitlocker related?

      1. Haakon said on May 2, 2024 at 8:49 pm

        Referring to Martin’s “how to” article and his Disk Management screen shot and “…the instructions work only if the recovery partition is after the OS partition.”

        FEB 2020 default install to 500 GB 970 EVO+ using WIN PRO 10 OEI DVD v1909:
        In left to right order…
        System Reserved 579 MB NTFS Healthy (System, Active, Primary Partition)
        SYSTEM (C:) 418.62 GB NTFS Healthy (Boot, Page File, Crash Dump, Primary Partition)
        46.58 GB Unallocated

        Note, the word “recovery” is absent.

        And what could go wrong with all the other slapped together “workaround” schemes out there?

        Sure, I could image before trying. Because recovery from images NEVER fail.

        I have the same question as Stephan: >>>>>> Do I even need this KB? <<<<<<

        (My data lives on a 500 GB 970 EVO+ as D: which is backed up to a local NAS and iDrive. So if my system goes up in smoke, I just copy that over to a D: on a new system and install needed software to the new C: drive.)

        Interesting that MS considers this issue resolved.

      2. EP said on May 2, 2024 at 6:58 pm


        leaving out or hiding this update does NOT prevent future security updates

Leave a Reply

Check the box to consent to your data being stored in line with the guidelines set out in our privacy policy

We love comments and welcome thoughtful and civilized discussion. Rudeness and personal attacks will not be tolerated. Please stay on-topic.
Please note that your comment may not appear immediately after you post it.