Skip to content

Est. 2011ยทMicrosoft Partner ID 7033487ยทDelivery under 3 minยทSupport 7 days a week

Your vault is empty.

Free Fix 0x80070643

Windows RE update fails with 0x80070643 – recovery partition too small

11 min read Updated October 5, 2026 Windows Crashes & Boot Recovery

Fix it now

0x80070643 is ERROR_INSTALL_FAILURE – a generic fatal error during installation, not a code that means anything about partitions. On the recovery environment servicing update it usually is a space problem: Microsoft’s documented procedure needs 250 MB of free space in the recovery partition, and Windows cannot grow that partition on its own.

Run these in an elevated Command Prompt, in order, and read the output before going further

reagentc /info
reagentc /disable
diskpart
list disk
list part
  1. Read reagentc /info first. If it reports Disabled, run reagentc /enable and retry the update; that alone resolves a fair number of cases and no partition work is needed.
  2. If it is enabled, note which partition holds the image and look at its free space. Microsoft’s manual procedure is written around finding 250 MB.
  3. The documented sequence is: reagentc /disable, shrink the Windows partition by 250 MB with shrink desired=250 minimum=250, delete the recovery partition with delete partition override, create a replacement, format it, then reagentc /enable.
  4. On a GPT disk create it with create partition primary id=de94bba4-06d1-4d40-a16a-bfd50179d6ac followed by gpt attributes =0x8000000000000001. On MBR use create partition primary id=27 and, after formatting, set id=27.
  5. Format with format quick fs=ntfs label="Windows RE tools", then list vol, exit, and reagentc /enable. Confirm with reagentc /info.

If the partition work fails or you change your mind part way through, run reagentc /enable anyway. Microsoft says so explicitly, and it is what stops you leaving a machine with no recovery environment at all.

If the update installs and reagentc /info reports Enabled, you are done. If not, the next section covers what the update is actually doing and why the obvious fix is unavailable.

Why it happens

The recovery environment is a Windows PE image, winre.wim, usually held on a small partition of its own. Servicing it is not a matter of copying a new file over the old one: the update mounts the image, applies changes and commits them, and that needs working space alongside the existing file. On a partition sized to the byte when the machine was built, there is none, and the installer returns a generic fatal error.

That is worth stating carefully, because 0x80070643 does not mean what it is often said to mean. It is ERROR_INSTALL_FAILURE, error 1603, published simply as a fatal error during installation. It is returned by all sorts of installers for all sorts of reasons. Reading it as a partition size problem is a reasonable bet on this particular update and a bad habit everywhere else – which is why the first step here is to read reagentc /info rather than to open diskpart.

The obvious fix, extending the partition, is not available. Windows extends a partition only into unallocated space immediately following it, and the recovery partition normally sits after the Windows volume – so shrinking the Windows volume creates free space in the wrong place. That is why the documented repair deletes the recovery partition and creates a new, larger one in the space you freed.

The companion codes describe the same event from other layers. 0x8024200B is the Windows Update handler reporting that the installer it launched failed to install or uninstall one or more updates. 0x80070002 is ERROR_FILE_NOT_FOUND, the system cannot find the file specified, which is what you see when the recovery image or the path recorded for it is gone: the environment was disabled, the image was removed by a cleanup, or an earlier repair left the pointer aimed somewhere that no longer exists.

The recovery partition has no room to work in

You have this one if reagentc /info shows an enabled environment on a partition with very little free space, and the update fails at the same point every time.

  1. Back up anything you cannot lose and verify you can read the backup, because the next steps delete a partition.
  2. Run reagentc /disable, which moves the image onto the Windows volume.
  3. In diskpart, select the Windows partition and run shrink desired=250 minimum=250.
  4. Select the recovery partition, delete partition override, create the replacement with the correct id for the partition style, format it and run reagentc /enable.

Read the partition list carefully before deleting anything. The recovery partition is the small NTFS one; the EFI system partition is the small FAT32 one and must not be touched.

The recovery environment is switched off

You have this one if reagentc /info reports Disabled, so there is nothing for the update to patch.

  1. Run reagentc /enable from an elevated prompt and retry the update.
  2. If enabling fails, the image is probably missing. Take winre.wim from \Windows\System32\Recovery inside a mounted install image of the same build.
  3. Place it in a folder on the Windows volume and register it: reagentc /setreimage /path C:\Recovery\WindowsRE /target C:\Windows, then reagentc /enable.

Disk encryption is in the way

You have this one if The machine is encrypted, and partition operations fail or the system asks for a recovery key part way through.

  1. Suspend BitLocker before touching partitions: manage-bde -protectors -disable C:.
  2. Have the 48-digit recovery key available regardless, from the Microsoft account, Entra ID or Active Directory.
  3. Carry out the partition work, then resume protection deliberately with manage-bde -protectors -enable C:.
  4. With a third-party encryption product, follow the vendor’s process rather than resizing partitions on a volume it manages.

Microsoft documents that protection resumes automatically at the next restart unless you pass -rebootcount, with 0 suspending indefinitely. Do not rely on a restart you may not get.

The machine has a manufacturer’s recovery layout

You have this one if Several small partitions exist, some belonging to a factory restore feature, and the layout does not match the standard one.

  1. Identify which partition the recovery environment actually uses from reagentc /info before assuming anything.
  2. Leave the manufacturer’s factory restore partition alone unless you accept losing that feature.
  3. Where there is no safe space to work with, leave the recovery environment on the Windows volume: disable it and let reagentc /enable place the image on C:, where free space is plentiful.

Full reference

The commands, and what each one does

Command Purpose
reagentc /info Reports whether the recovery environment is enabled and where its image lives
reagentc /disable Turns the environment off and moves the image onto the Windows volume. Online only
reagentc /enable Turns it back on, placing the image on a recovery partition if one is available
reagentc /setreimage /path <folder> /target C:\Windows Registers a recovery image you supplied
reagentc /boottore Starts the recovery environment at the next restart, which is a fast way to prove it works
manage-bde -protectors -disable C: Suspends BitLocker; resume with -enable

The documented partition sequence, in full

reagentc /info
reagentc /disable
diskpart
  list disk
  sel disk <OS disk index>
  list part
  sel part <OS partition index>
  shrink desired=250 minimum=250
  sel part <WinRE partition index>
  delete partition override
  list disk
  create partition primary id=de94bba4-06d1-4d40-a16a-bfd50179d6ac
  gpt attributes =0x8000000000000001
  format quick fs=ntfs label="Windows RE tools"
  list vol
  exit
reagentc /enable
reagentc /info

That is the GPT path. On an MBR disk, replace the create line with create partition primary id=27 and add set id=27 after the format. list disk in the middle is there for a reason: it shows an asterisk in the Gpt column, which is how you know which of the two branches you are on.

Deleting and recreating partitions is destructive if you select the wrong one. Take a backup you have verified you can read, write down the current partition layout before you start, and never run delete partition override without re-reading the partition list immediately beforehand.

Reading the three codes correctly

Code Published as What it actually tells you
0x80070643 ERROR_INSTALL_FAILURE, 1603: fatal error during installation An installer failed. Nothing about partitions is implied by the code itself
0x8024200B WU_E_UH_INSTALLERFAILURE The update handler is reporting that the installer it launched failed
0x80070002 ERROR_FILE_NOT_FOUND The recovery image, or the path recorded for it, is not there

0x80070002 is the one that changes the plan. If the image or its registration is missing, resizing a partition achieves nothing; you need to supply an image and register it first. reagentc /info distinguishes the two cases in a second.

Sizing the replacement

Microsoft’s procedure shrinks the Windows volume by 250 MB, which is the space the update needs. Whether to take more is a judgement call rather than a documented requirement: a larger recovery partition leaves headroom for future servicing, at the cost of a little more of the Windows volume. If you take more than 250 MB, take it deliberately and record what you did, because the next person following the KB will expect to see the documented numbers.

If you would rather not touch partitions at all

  • Disable the recovery environment and let reagentc /enable place the image on the Windows volume, where free space is not a constraint. The environment still works; it is simply not on its own partition.
  • On a machine with an unusual manufacturer layout, that is often the least risky option available.
  • Hiding the update is a third option and a real choice, not a fix – you are electing to run an unpatched recovery environment, which is a place where a vulnerability matters.
  • On a fleet, consider whether reimaging with a correctly sized layout is cheaper than resizing partitions on machines one at a time.

Every code this article covers

Code What it points at Source
0x80070643 ERROR_INSTALL_FAILURE (1603): fatal error during installation. A generic installer failure, not a code specific to the recovery partition Microsoft Learn
0x8024200B WU_E_UH_INSTALLERFAILURE: the installer failed to install or uninstall one or more updates Microsoft Learn
0x80070002 ERROR_FILE_NOT_FOUND: the system cannot find the file specified. On this update, the recovery image or its recorded location is missing Microsoft Learn

Confirm the fix worked

  1. reagentc /info reports Status Enabled with a location on the new partition.
  2. Windows Update history shows the recovery environment update as installed.
  3. Hold Shift and choose Restart, or run reagentc /boottore, and confirm the recovery menu appears and offers Troubleshoot.
  4. The recovery partition shows comfortable free space in Disk Management.
  5. If BitLocker was suspended, confirm manage-bde -status C: shows protection back on.

Questions people ask about this

Can I just hide the update and move on?

You can, and the machine keeps working, but you are choosing to run an unpatched recovery environment. That environment is a place where a vulnerability matters, so it is worth fixing properly when you have an hour free.

Will shrinking the Windows volume lose data?

Shrinking a volume that has free space is a normal, non-destructive operation, and Windows will not shrink below what the data requires. You are about to delete a partition on the same disk, though, so take a backup and verify you can read it first.

How much space should the new partition have?

Microsoft’s procedure frees 250 MB, which is what the update needs. Taking more leaves headroom for future servicing but is a judgement call rather than a documented requirement, so decide deliberately and record it.

Does 0x80070643 always mean the recovery partition is too small?

No. It is ERROR_INSTALL_FAILURE, a generic fatal error during installation, and plenty of other installers return it. On this particular update the partition is the usual cause, but read reagentc /info before assuming – if it reports Disabled, or 0x80070002 appears, the partition was never the problem.

Does any of this need a licence or paid software?

No. diskpart, reagentc and BitLocker management are built into Windows, the update is free, and nothing about this error relates to activation.

Related error codes

Was this article helpful?

Your feedback helps us improve our documentation.

Related articles

Free Fix NETWORK_BOOT_DUPLICATE_ADDRESS 0x000000BC and PXE boot failures on WDS License Error 0xC0000221 bad image checksum and 0xC0000428 signature check failure at boot Free Fix STATUS_SYSTEM_PROCESS_TERMINATED 0xC000021A and CRITICAL_PROCESS_DIED 0x000000EF Free Fix ATTEMPTED_EXECUTE_OF_NOEXECUTE_MEMORY 0x000000FC and DEP blue screens
โ† Back to Knowledge Base