KB5034441 0x80070643 error despite no WinRE volume

STRESSED · 18 Jan 2024

Like many Win10 users, I am getting the 0x80070643 error when I try installing the KB5034441 update. The claim everyone makes is that this is due to the WinRE volume not having enough space. But I don't even have a WinRE partition -- I've disabled WinRE and deleted its partition.

What is going on here? And will a repair install help? I was considering doing a repair install for other reasons anyway. Is there a way to tell if a repair install would include KB5034441? If it didn't include it, I don't see the point.

Hearsepilot · 18 Jan 2024

The consensus of advice is to await an updated KB

STRESSED · 18 Jan 2024

Thanks. I was considering doing a repair install for other reasons, which is why I asked. If I could kill two birds with one stone, I will. I just don't want to do a repair install if the MCT or whatever hasn't been updated yet to include the KB5034441 fix.

Ghot · 18 Jan 2024

STRESSED said:

Thanks. I was considering doing a repair install for other reasons, which is why I asked. If I could kill two birds with one stone, I will. I just don't want to do a repair install if the MCT or whatever hasn't been updated yet to include the KB5034441 fix.

I disabled, and removed the Recovery partition, and removed the Win RE parts as well.
If you get these results (RED) from the commands shown (YELLOW), then you don't need the KB5034441 update.
In my situation, there is nothing there for the hackers to... hack.

Search your C:\ (Windows partition), for winre.wim
[normally located in... C:\Windows\System32\Recovery]
If it's not there, you probably don't need this update.

KB5034441 0x80070643 error despite no WinRE volume-image1.png

If you use 3rd party backup software, you don't really need a Recovery partition.
And even if you may need it for something... you can access it from the Windows install media.

And... as @Hearsepilot mentioned, MS is claiming to have a fixed update ready by March-ish.

STRESSED · 18 Jan 2024

The WinRE partition is definitely not there. This is what I'm showing as far as the reagentc /info command:

Code:

>reagentc /info

Windows Recovery Environment (Windows RE) and system reset configuration Information:

    Windows RE status:         Disabled
    Windows RE location:
    Boot Configuration Data (BCD) identifier: 00000000-0000-0000-0000-000000000000
    Recovery image location:
    Recovery image index:      0
    Custom image location:
    Custom image index:        0

REAGENTC.EXE: Operation Successful.

I do have "C:\Windows\System32\Recovery\Winre.wim" but since I use TeraByte Unlimited imaging products, I'm thinking I need to keep it around. I think those utilities use that Winre.wim file as a basis for creating bootable images for flash drives and such.

I'm a bit afraid to run "reagentc /enable" on account of not being sure what Windows will do... Probably create a new WinRE partition without further prompt?

SIW2 · 18 Jan 2024

I think those utilities use that Winre.wim

yes

Probably create a new WinRE partition without further prompt?

No if you do not already have a recovery partition it will be set to %systemdrive%\recovery\windowsre which will be a hidden folder on your existing os partition.

You do not need this update if the PC does not have a recovery partition.

https://support.microsoft.com/en-au/...a-2fdea17075a8

STRESSED · 19 Jan 2024

Symptom: When you try to apply this update on a PC that has no recovery partition, the update is unsuccessful and you receive the error 0x80070643 ERROR_INSTALL_FAILURE.

Next step: You do not need this update if the PC does not have a recovery partition. In this case, the error can be safely ignored. We are working on a resolution and will provide an update in an upcoming release.

Thank you for pointing me to this. So if they ever get their act together, I'll simply stop being offered the update (which I know I can hide now).

The time and stress they've cost users over this one update is absolutely astronomical.

Berton · 20 Jan 2024

I have corrected the issue in 3 computers by resizing that small partition, shrink the largest partition slightly [I have used 1GB/1000MB] and increase/resize the small one by the same amount. This example shows I increased the 513MB partition by 1000 to 1.48GB, other computers will have a different size for that partition.

unifex · 22 Jan 2024

I can confirm that increasing the size of the Recovery partition leads to the successful installation of the update. I just want to add a link to the Microsoft Support page with detailed instructions on how to resize the partition since I could not do it using the Disk Management.

https://support.microsoft.com/en-us/...9-24c8229763bf

Berton · 22 Jan 2024

unifex said:

I can confirm that increasing the size of the Recovery partition leads to the successful installation of the update. I just want to add a link to the Microsoft Support page with detailed instructions on how to resize the partition since I could not do it using the Disk Management.

https://support.microsoft.com/en-us/...9-24c8229763bf

I looked at that linked page, it's for an earlier update, KB5028997. I made the change to the small partition between the OS/C: and the winre. And like you it couldn't be done in DM, I use a bootable Linux Mint LiveUSB and the GPARTED program included in it. It takes longer to run Windows Error Checking followed by Optimizing on the drive first than to reboot to the USB and change the partition.