(kb5034441) wont install with error code (0x80070643)

CAD4466HK

2[H]4U
Joined
Jul 24, 2008
Messages
2,979
I just had to deal with this shit on three different client PC's since yesterday. Hopefully this helps someone.

I don't know why I'm still surprised MS releases a patch that can be broken by the lack of 250MB.

"This update addresses a security vulnerability that could allow attackers to bypass BitLocker encryption by using Windows Recovery Environment (WinRE)."

"Some PCs might not have a recovery partition that is large enough to complete this update. Because of this, the update for WinRE might fail. You will receive the error message, "Windows Recovery Environment servicing failed.” To help you recover from this failure, this article provides instructions to manually resize your recovery partition if you get a system ErrorPhase of 2. This requires your device to have the recovery partition after the OS partition. Use the steps below to verify this."

https://www.bleepingcomputer.com/ne...security-update-fails-with-0x80070643-errors/

Fix:
https://support.microsoft.com/en-gb...e-update-400faa27-9343-461c-ada9-24c8229763bf
 
Does the free version of MiniTool Partition Wizard work, or do I need to purchase the pro version?
 
I had this occur on a few Windows 10 computers. Upgrading them to Windows 11 solved the issue on all of them.
 
I had this occur on a few Windows 10 computers. Upgrading them to Windows 11 solved the issue on all of them.

Yikes, that's an awful solve 😂

Any word if MS are going to reissue this patch, or do I have to do this janky workaround...?
 
Also this:

'This requires your device to have the recovery partition after the OS partition."

Mine is not... am I screwed?
 
i knew this sounded familiar...
i just ran into this at work on friday. after a few attempts at installing and failing, i skipped it. oh well...
 
Hmm, just noticed the update failed on my work computer that has over 500MB available in recovery. Says it only needs 250.
 
Hmm, just noticed the update failed on my work computer that has over 500MB available in recovery. Says it only needs 250.
Unfortunately, Windows 10 creates a recovery partition, usually around 500 MB, which is not large enough to support the new Windows RE image (winre.wim) file, causing the 0x80070643 error when attempting to install the update.
The fix increases the recovery partition by 250MB.
 
drives.PNG


Am I basically screwed? There is nothing to expand the partition into...
 
Yeah but I think both require this condition:

'This requires your device to have the recovery partition after the OS partition."

My drive not set up this way, so there is nothing for the Recovery Partition to "expand into" I think.
 
Yeah but I think both require this condition:

'This requires your device to have the recovery partition after the OS partition."

My drive not set up this way, so there is nothing for the Recovery Partition to "expand into" I think.
Try using the partition wizard, if it doesn't work, it's not the end of the world since it's just for bitlocker and it's your personal machine and not a clients.
 
I just ran into this on a fresh install of 10 home.

I guess MS is working on a fix: https://www.bleepingcomputer.com/ne...ng-on-a-fix-for-windows-10-0x80070643-errors/
Yeah that script was in the OP from Bc. Scroll down.

https://www.bleepingcomputer.com/ne...security-update-fails-with-0x80070643-errors/

+ I think it's more of a band aid than a fix due to this:
From BleepingComputer's tests, you may also have to use Microsoft's Show or Hide Tool to hide the KB5034441 update after running the script, so Windows Update won't keep trying to install the buggy update and display an error.
 
I got tired of it and just used MiniTool Partition Wizard to extend it to a little over 1g, then installed the update. The only option when extending the partition was 1g. I could not add just a few mb's with MiniTool.
 
I got tired of it and just used MiniTool Partition Wizard to extend it to a little over 1g, then installed the update. The only option when extending the partition was 1g. I could not add just a few mb's with MiniTool.
That's strange because I can get it to go as low as 80mb.

1706034688569.png
 
It's problems like this one that make me thankful to be a Windows 7 user.
 
Try using the partition wizard, if it doesn't work, it's not the end of the world since it's just for bitlocker and it's your personal machine and not a clients.

Using the "Extend Partition" feature doesn't work ("Cannot extend the specified partition. Not enough free space.")

Using "Move/Resize Partition" I get the window below, but nothing I click on does anything - it's like there is no option to actually do anything with that partition:

1706047519636.png
 
That is because there is not enough room on the RIGHT side of the partition to resize it. You have to grab space from drive C using the Extend option. Using the slider worked for me, even though I gave it more than enough space. Not a big deal because most hard drives are now large, so giving it a total of 1gb is not a big deal.
 
So the ordering now is: Recovery -> EFI -> C-drive.

Will the tool let me shrink C-drive by 1GB, move the Recovery partition into the "new" 1GB space, then expand the partition to fill that space?

That feels like high risk of something breaking... and what happens to the random 500MB chunk at the start of the drive?
 
So I got a new hard drive and decided to clone it and then do all the tomfoolery with DiskPart... still no dice. Getting error 0x80070643 with the same update.

Here's the partition setup now, with old drive still installed. Am I missing anything?

1707163562460.png
 
So I got a new hard drive and decided to clone it and then do all the tomfoolery with DiskPart... still no dice. Getting error 0x80070643 with the same update.

Here's the partition setup now, with old drive still installed. Am I missing anything?

View attachment 632919
make it bigger? i just ran into this on my aunts HP laptop, said to ignore it for now, but her partition was already 950mb and it was failing.
 
So I got a new hard drive and decided to clone it and then do all the tomfoolery with DiskPart... still no dice. Getting error 0x80070643 with the same update.

Here's the partition setup now, with old drive still installed. Am I missing anything?

View attachment 632919
Maybe because you cloned the issue too? Try it without cloning, and what's up with the 500MB of unallocated space?
Other than that I'm just shooting from the hip here.
 
make it bigger? i just ran into this on my aunts HP laptop, said to ignore it for now, but her partition was already 950mb and it was failing.
The clients that I've done since and after have all worked except one and I just hid the update, mine is only 850MB and it worked, some weird shit with this update indeed.
 
Maybe because you cloned the issue too? Try it without cloning, and what's up with the 500MB of unallocated space?
Other than that I'm just shooting from the hip here.

The 500 MB is where the old recovery partition used to be (I just didn't bother moving all the partitions backwards to fill it).

I need to clone anyway to move to the new SSD, and I don't really want to mess with the original disk until everything works properly...

The clients that I've done since and after have all worked except one and I just hid the update, mine is only 850MB and it worked, some weird shit with this update indeed.

Yeah this is what the MS support article suggests.

https://support.microsoft.com/en-gb...e-update-400faa27-9343-461c-ada9-24c8229763bf

I am getting to this part" To format the partition, run format quick fs=ntfs label=”Windows RE tools”" and for some reason it's failing. So everything else up until that point worked ok...
 
id suggest skipping it for now. it will either get fixed or bundled into a future update.
 
I wonder has anyone checked to see if the windows installation media image has been updated to incorporate the enlarged partition to accommodate this update yet?
 
I wonder has anyone checked to see if the windows installation media image has been updated to incorporate the enlarged partition to accommodate this update yet?
I dl'ed a new ISO a week ago and it was still 522MB, which is 23MB bigger than it originally was, but also still too small for the update to install.
 
Wow way to stay on top of things MS. Maybe they need some common sense incorporated into their business as usual mentality. Maybe I'm just expecting too much.
 
I have a 1.8gig winre on my m.2 , with 426mb being used on that winre...... so
plenty of space free

kb5034441 won't install........ tried multiple times , just hidding it using wushowhide......
 
View attachment 635957

During the January update round MS issued a security update for Windows 10 that should fix a security issue which could allow an attacker to bypass Bitlocker encryption using the Windows Recovery Environment. Except the update throws an unexplained error code for many users: 0x80070643. As it turns out the error is caused by MS changing how WinRE is updated from now on: cumulative updates instead of small patches. Except for many users when they originally installed Windows 10, the installer was not prepared for this so the automatically created Recovery partition is not large enough to apply this update out of no fault of their own.

Since then MS has issued a manual workaround for installing the update. But the workaround involves resizing your system and recovery partitions, so it is only recommended if you are desperate to have this update installed and know what you are doing.

Most people were hoping that in the February patch Tuesday MS would sort out the issue properly, but unfortunately that's doesn't seem to be the case. The erroneous patch hasn't been pulled and no updated version was issued. It is unclear when can we expect MS to properly fix the issue instead of a workaround that is risky even for enthusiasts.

Until now the issue was a mere inconvenience, but since you can't opt out of the broken update even if you don't use Bitlocker, it can interfere with the installation of any further updates as well, as it tries to install it first, but fails blocking the entire update process.

Windows 10 KB5034441 is still broken with 0x80070643 error
seems this is still an issue for some.
i did updates on a fresh install of 10 22h2 on friday and this update wasnt even offered, it skipped to the feb update.
 
this is sorta still happening. i just tried updating a couple Dell laptops. it shows and offered this update but the download for it just cancels part way now....
 
Back
Top