Error 0x80070643 is one of the most stubborn codes in the Windows Update catalog. It translates to a fatal error during installation, which is Microsoft’s way of saying the update’s installer gave up halfway. On laptops it shows up most often with the Windows Recovery Environment update KB5034441, and the root cause is almost comically mundane: the recovery partition the manufacturer created is simply too small to hold the new recovery image.

Because the failure happens at the same point on every attempt, hammering the Retry button changes nothing. The installer needs about 250 MB of free space inside that hidden recovery partition, and most OEM partitions were carved out years ago with barely any headroom. The permanent fix is to give the partition room to breathe, then clear out the debris left behind by the failed attempts.

Before you touch partitions, though, it pays to rule out the simpler causes. A corrupted download cache, a damaged .NET Framework install, or an antivirus product interfering with the installer can all produce the same 0x80070643 code. The steps below start with the quick checks and build up to the partition resize that fixes the classic KB5034441 failure.

Why this happens

  • Recovery partition is too small. The WinRE update needs roughly 250 MB of free space in the recovery partition, and factory partitions on most laptops ship with far less, so the install fails every time.

  • Corrupted .NET Framework installation. Because 0x80070643 is the generic installer-failure code, damaged .NET security updates are a frequent trigger when the framework’s own store is broken.

  • Stale Windows Update cache. A half-downloaded package sitting in the SoftwareDistribution folder makes the installer trip over the same damaged files on each retry.

  • Component store corruption. If the WinSxS servicing stack is damaged, CBS cannot stage the update payload and the installer aborts with this code.

  • Antivirus interference. Third-party security suites sometimes quarantine or lock update payload files while the installer is writing them.

  • Low free space on the system drive. Large cumulative updates need several gigabytes of working room on C: to extract and stage files before installing.

  • Conflicting pending updates. Another update holding the servicing lock can cause this installation to fail instead of queuing politely behind it.

How to fix it

Work through these in order — diagnose first, then act.

Fix 1: Fix 1: Enlarge the recovery partition

This is the definitive fix for the KB5034441 variant of 0x80070643. You shrink the Windows partition by 250 MB and hand that space to the recovery partition using diskpart. It sounds intimidating, but it is a routine, well-documented procedure.

  1. Press Win + X, choose Terminal (Admin), and type diskpart, then press Enter.
  2. Type list disk, then select disk 0 (the disk Windows is installed on), then list partition. Note the numbers of the OS partition and the recovery partition, plus their sizes.
  3. Type select partition X (your Windows partition), then shrink desired=250 minimum=250 to free 250 MB.
  4. Type select partition Y (the recovery partition), then extend to absorb the freed space.
  5. Type exit, restart the laptop, and run Windows Update again.

Fix 2: Fix 2: Run the Windows Update troubleshooter

Before resizing anything, let Microsoft’s own troubleshooter take a pass. It resets stuck services, clears bad cache entries, and repairs the update database. It will not fix a too-small recovery partition, but it clears the simpler variants of this error in a couple of minutes.

  1. Open Settings, then System, then Troubleshoot, then Other troubleshooters.
  2. Click Run next to Windows Update and let the scan finish.
  3. Apply every fix it recommends, then restart the laptop.
  4. Check for updates again to see whether the error is gone.

Fix 3: Fix 3: Clear the SoftwareDistribution folder

Failed attempts leave damaged payload files behind, and the installer keeps reusing them. Deleting the download cache forces Windows Update to fetch a fresh, intact copy of the package.

  1. Open Terminal as administrator.
  2. Run net stop wuauserv and net stop bits to pause the update services.
  3. Open File Explorer, go to C:\Windows\SoftwareDistribution, and delete everything inside the Download subfolder.
  4. Back in Terminal, run net start wuauserv and net start bits.
  5. Retry Windows Update.

Fix 4: Fix 4: Repair the .NET Framework installation

Since 0x80070643 frequently rides along with .NET security updates, repairing the framework removes a whole class of triggers. Windows lets you toggle the framework off and on, which rebuilds its installation cleanly.

  1. Open Control Panel, then Programs, then Turn Windows features on or off.
  2. Uncheck every .NET Framework entry, click OK, and restart when prompted.
  3. Return to the same dialog, re-check the .NET entries, click OK, and restart again.
  4. Run Windows Update and confirm the error no longer appears.

Fix 5: Fix 5: Run SFC and DISM

If the component store itself is damaged, no installer will succeed until it is repaired — the same root cause behind error 0x800f0988 . SFC checks protected system files while DISM repairs the underlying Windows image that SFC depends on. Run them in this order.

  1. Open Terminal as administrator and run sfc /scannow. Wait for it to reach 100 percent.
  2. Then run DISM /Online /Cleanup-Image /RestoreHealth and let it finish, which can take 15 to 30 minutes.
  3. Restart the laptop and try the update once more.

Fix 6: Fix 6: Install the update manually from the Microsoft Update Catalog

When the automatic pipeline keeps failing, bypass it. Downloading the standalone KB package and installing it by hand sidesteps the broken download cache entirely, and the catalog lets you pick the exact KB that is failing.

  1. Find the failing KB number in Settings, then Windows Update, then Update history.
  2. Visit the Microsoft Update Catalog and search for that KB number.
  3. Download the package matching your system (x64 for most laptops) and run the .msu file.
  4. Restart when prompted and verify the update in your history.

Fix 7: Fix 7: Clean-boot and retry the installation

Background programs, especially third-party antivirus and system utilities, can lock files the installer needs. A clean boot starts Windows with only Microsoft services, giving the update a clear run at the system.

  1. Press Win + R, type msconfig, and open the Services tab. Check Hide all Microsoft services, then click Disable all.
  2. Open the Startup tab, click Open Task Manager, and disable every startup item.
  3. Restart, run Windows Update, and confirm the install succeeds before re-enabling your normal startup.

Closing

Error 0x80070643 looks scary because it never explains itself, but on laptops it almost always comes down to the recovery partition being too small for the WinRE update or a damaged installer cache. Work the list from the troubleshooter up through the partition resize, and the update that failed ten times in a row will usually sail through on the next attempt. For step-by-step help grabbing the standalone package, see our guide on installing KB updates manually from the catalog , and Microsoft’s Windows support hub has the official troubleshooter walkthrough if you want the vendor version of these steps.

Frequently asked questions

What does Windows Update error 0x80070643 actually mean?
It is the generic code for a fatal error during installation, which means the update’s installer crashed partway through. On Windows 10 and 11 laptops it most often appears with the Windows Recovery Environment update, KB5034441, when the recovery partition is too small to hold the new WinRE image.
Why does KB5034441 keep failing with 0x80070643?
That specific update needs roughly 250 MB of free space inside the recovery partition, and most factory partitions ship with far less. Until the partition is enlarged, every retry fails at exactly the same point, so resizing the partition is the only lasting fix for that KB.
Is it safe to resize the recovery partition with diskpart?
Yes, when done carefully on the correct disk. You shrink the Windows (C:) partition by 250 MB and extend the recovery partition into the freed space. Back up important files first, double-check partition numbers with list partition, and never touch the EFI system partition.
Can I just ignore error 0x80070643?
You can, but the failed update will keep retrying and the error will sit in your update history indefinitely. Worse, the underlying cause, a cramped recovery partition or a damaged installer, can block future cumulative updates too, so it is worth fixing properly once.