Forum Discussion
KB5034441 fails to install with error code 0x80070643.
Status
Confirmed
Affected platforms
Client VersionsMessage IDOriginating KBResolved KB
Windows 10, version 22H2 WI706429 KB5034441 -
Windows 10, version 21H2 WI706430 KB5034441 -
Devices attempting to install the January 2024 Windows Recovery Environment update (the Originating KBs listed above) might display an error related to the size of the Recovery Environment's partition. The Windows Recovery Environment (WinRE) is used to repair or recover from issues affecting Windows.
Resulting from this error, the following message might be displayed.
"0x80070643 - ERROR_INSTALL_FAILURE"
Workaround: It might be necessary to increase the size of the WinRE partition in order to avoid this issue and complete the installation. Note that 250 megabytes of free space is required in the recovery partition. Guidance to change the WinRE partition size can be found in KB5028997: Instructions to manually resize your partition to install the WinRE update.
Next steps: We are working on a resolution and will provide an update in an upcoming release.
- DurahamJan 14, 2024Copper Contributor
SusanBradleyGeek I do not have BitLocker installed, so don't even need the patch. I do have 522MB free space on my Partition Drive, which ought to be more than ample. Still no successful install.
- VHL001Mar 03, 2024Copper Contributor
SusanBradleyGeek I have a WRE of 509MB and still get this error. Plus the fixes here are beyond the scope of most users.
- Arto_MontonenJan 13, 2024Copper ContributorI resized the Windows 10 partition and removed the WinRE partition according to Microsoft's instructions. The disk is MBR because there is no star for GPT. Before the changes, WinRE was on disk 0 and partition 3. Now WinRE points to disk 0 and partition 2 and partition 2 is the Windows 10 operating system!
I followed these instructions:
https://support.microsoft.com/en-us/topic/kb5028997-instructions-to-manually-resize-your-partition-to-install-the-winre-update-400faa27-9343-461c-ada9-24c8229763bf- Arto_MontonenJan 13, 2024Copper Contributor
Arto_Montonen I deleted partition 3 which was WinRE. I created a new NTFS partition without name and drive letter via Windows Disk Management. In the CMD window, I changed the partition ID number. I using the disk part program, when the correct disk and partition have been selected. The ID number can be viewed with the det part command and the set part 27 command sets the ID number, which is the recovery ID partition number of the MBR disk. After that, WinRE starts pointing to disk 0 and partition 3 again when I enable WinRE function again.
- Arto_MontonenJan 13, 2024Copper ContributorSet id=27 not set part 27.
- mmhp87May 21, 2024Copper ContributorThe Instructions in this link surely allowed me to install kb5034441 on the machines where it was failing before, but i always ended up with winre.wim on my C:\ drive and not in the newly created recovery partition, leaving that one empty and useless ???
in order to actually use the resized recovery partition i had to addtitionally do step
6b: assign letter R
(7. exit)
7a: mkdir R:\Recovery\WindowsRE
7b: copy C:\Windows\System32\Recovery\winre.wim R:\Recovery\WindowsRE\
7c: reagentc /setreimage /path R:\Recovery\WindowsRE /target C:\Windows
(8. reagentc /enable)
reagentc has to find a valid winre image for the command setreimage to complete and thus being able to re-enable winRE using the new recovery partition.
after completing those steps i retried to install kb5034441 successfully and confirmed the recent change date and different filesize of the winre.wim
also i'd recommend removing letter R from the WinRe partition after confirming a working recovery.
- shanen0Jul 10, 2024Copper ContributorSeemed like an easy solution--but it didn't work. It did seem to cause the failure to happen more quickly. I remain extremely leery of manually tweaking the disk partitions. I do NOT have the expertise and I believe a juicy mistake will kill the computer.
Rather amazing to me that this problem started more than six months ago in this discussion. Perhaps older from whenever I first encountered it. And it remains unresolved, with fresh reports still appearing. My theory is that Microsoft is merely hoping that the victims' computers will die. Or perhaps the people will die before their computers?
In conclusion, I hate Microsoft even more than before. If that is possible.