A security update for the Windows Recovery Environment can fail on a machine that is otherwise healthy. The usual cause is space: the recovery partition was created years ago at 500 MB, while the current image plus the update needs more than that. Setup cannot grow a partition during an update, so it stops and reports 0x80070643.
The Windows Recovery Environment lives in its own partition near the end of the system disk, normally between 500 MB and 1 GB. Safety updates replace the image inside that partition, and the replacement needs roughly 250 MB of free space beyond the image that is already there.
On machines installed several releases ago, or upgraded in place more than once, that partition was created smaller than the current image. Setup cannot resize a partition while it installs an update, so it aborts and returns 0x80070643, which is a generic installation failure code rather than a storage error.
The failure itself is not dangerous. The previous recovery image stays in place and Windows continues to run. What it leaves behind is a machine that cannot apply later recovery fixes until the partition has room.
Open Disk Management and find the partition with no letter that is labelled Recovery. Note its size and, more importantly, how much free space it has inside.
The free space is reported by the recovery configuration tool that ships with Windows. That tool is part of the operating system and is not a feature of this software; its information switch states whether the recovery environment is enabled and how much of the partition the image occupies.
If the partition is 500 MB and the image already fills most of it, retrying the update will not help. The partition has to grow, or the recovery environment has to be moved to a partition with room.
Two approaches work. The recovery environment can be moved into the Windows partition, which frees the dedicated partition, or the recovery partition can be enlarged by taking space from the volume in front of it.
Relocating is a command line operation performed with the Windows recovery tool from an administrator prompt. It is reversible, and it leaves the dedicated partition untouched for a later attempt.
Enlarging is more predictable when the recovery partition sits immediately after the system volume, which is the usual layout. Because the free space must come from the volume in front, the system volume shrinks first and the recovery partition is then moved or extended into the gap.
Qiling Disk Master can shrink the system volume, move the recovery partition, and extend it in a single pending operation. That avoids running three separate wizards in the wrong order, and it also covers the case where unallocated space sits before a partition that Windows refuses to extend.
Open the program and confirm the disk number against Disk Management. The recovery partition has no letter and a small size, so identify it on the map rather than in a drive list.
Right-click the system volume, choose Resize Partition, and drag its end handle left by about 300 MB. Leave Windows itself with reasonable free space; do not shrink the volume to its minimum, because a full system volume causes its own failures.
Right-click the recovery partition and extend it into the new unallocated space. Confirm that the pending list shows the shrink before the extend, click Proceed, and allow the restart if the program asks for one.
After the reboot, run Windows Update again. The recovery update now has room to install, and the error should clear on the first attempt. If it returns, check the partition size once more before you look for other causes.
You can, and the update will then succeed by creating a new partition, but you lose the built-in recovery environment until Windows recreates it. Enlarging is the safer option.
Allow about 1 GB for the partition. The image uses several hundred megabytes, and the update needs roughly 250 MB free on top of that.
No, as long as the partition keeps its type and contents. Resizing changes boundaries, not files, and the configuration is read from the system volume.
Yes. The same failure appeared on Windows 10 machines with a small recovery partition, and the fix is identical.
For copying a recovery partition to another disk, see copying the recovery partition to a new hard drive.