ErrorFix
Windows PC Errors

How to Fix Windows Update Error 0x80070643

By ErrorFix · Updated October 19, 2026 · 8 min read

Error 0x80070643Plain English: "Fatal error during installation" — an update started installing but the installer crashed or aborted partway through, so Windows reports the whole update as failed.
Quick answer: This code almost always means a damaged .NET Framework or a corrupted update pipeline. Repair the .NET Framework from Control Panel, run Microsoft's .NET Framework Repair Tool, then reset the Windows Update components. For Windows Recovery Environment updates, also check that the recovery partition has enough free space.

What error 0x80070643 means

Error code 0x80070643 maps to ERROR_INSTALL_FAILURE, and Windows renders it as "Fatal error during installation." Unlike errors that complain about a bad download, this one means the download was fine and the installation itself blew up midway. Something the installer depended on was broken, blocked, or missing, so it gave up partway through and rolled the update back.

This code has a clear pattern: it hits .NET Framework cumulative updates more than anything else, followed by Microsoft Defender definition updates and Windows Recovery Environment (WinRE) updates such as KB5034441 and KB5057589. The WinRE cases are special — KB5034441 famously fails when the recovery partition is too small, and Microsoft later confirmed that the KB5057589 failure message is often a false alarm after the update actually installed. But don't let that fool you: when 0x80070643 appears on a .NET Framework or feature update, the install genuinely failed, and retrying it without fixing the underlying damage fails again and again. Work through the steps below in order; most PCs update cleanly again by step 4.

Common causes

How to fix error 0x80070643 — step by step

Work through these fixes in order. The .NET steps come first because they solve most cases.

  1. Run the Windows Update troubleshooter. Open Settings, go to System, then Troubleshoot, then Other troubleshooters. Click Run next to Windows Update and follow the prompts. Let it apply any repairs it finds, then restart your PC and try updating again. A failed installation can leave the update stack in a stuck state, and the troubleshooter clears that state automatically — it's worth the two minutes even though it won't fix a genuinely damaged .NET install.
  2. Repair the .NET Framework. Open Control Panel, go to Programs, then Programs and Features, and find Microsoft .NET Framework 4.x in the list. Select it, click Change or Uninstall, and choose Repair when prompted. Let the repair run to completion without interrupting it — it can look stalled, so give it time. Restart the PC when it finishes, even if Windows doesn't ask you to, because the repair replaces system files that stay locked until reboot. This is the single most effective fix for 0x80070643, since the error hits .NET cumulative updates hardest.
  3. Run the official .NET Framework Repair Tool. If the Control Panel repair didn't clear it, download the .NET Framework Repair Tool from Microsoft's website, right-click the downloaded file, and choose Run as administrator. The tool scans every installed .NET version, detects problems automatically, and applies repairs. Click through its wizard, let it finish, restart the PC, and try the update again. This catches framework damage that the standard repair option misses.
  4. Reset the Windows Update components. Right-click Start and choose Terminal (Admin). Stop the update services one at a time: net stop wuauserv, net stop cryptSvc, net stop bits, net stop msiserver. Rename the caches with ren C:\Windows\SoftwareDistribution SoftwareDistribution.old and ren C:\Windows\System32\catroot2 catroot2.old. Restart the services with net start wuauserv, net start cryptSvc, net start bits, and net start msiserver. Windows rebuilds both folders from scratch, which clears out any broken state the failed installation left behind.
  5. Run the System File Checker and DISM. In the same admin terminal, type sfc /scannow and press Enter, then wait for the scan to finish. Follow it with DISM.exe /Online /Cleanup-image /Restorehealth and give it 15 to 20 minutes. These two tools repair the Windows components sitting underneath the installer — when they are corrupted, an update can download perfectly and still crash mid-installation with 0x80070643.
  6. Rule out antivirus interference and update Defender manually. Open the Windows Security app, go to Virus and threat protection, and click Check for updates so Defender definitions install outside the failing pipeline. If you use a third-party antivirus, temporarily disable it and retry the update — security software that hooks into installer operations is a known trigger for this exact code. Re-enable protection afterward.
  7. Check the recovery partition for WinRE updates. If the failing update is a Windows Recovery Environment update such as KB5034441, open an admin terminal and run reagentc /info to inspect the recovery configuration. These updates need roughly 250 MB of free space on the recovery partition to stage their files; on PCs with undersized recovery partitions the update physically cannot install. Your options are to shrink the main partition and enlarge the recovery partition, or to hide that specific update if you don't rely on the recovery environment. Note the exception: for KB5057589, Microsoft confirmed the update installs correctly despite the 0x80070643 message, so a reboot plus a daily update scan normally clears that particular false failure.

Did this fix it? Quick checklist

If the error survives all seven steps, note the exact KB number in Settings, then Windows Update, then Update history, and install that update manually from the Microsoft Update Catalog — a manual install bypasses the damaged download pipeline and often succeeds where the automatic one fails. As a last resort, an in-place upgrade using the Media Creation Tool rebuilds the entire update stack while keeping your files and apps.

Frequently asked questions

What does error 0x80070643 mean?

Error 0x80070643 is ERROR_INSTALL_FAILURE, shown as 'Fatal error during installation.' It means an installer started but crashed or aborted partway through. On Windows Update it most often hits .NET Framework cumulative updates, Microsoft Defender definition updates, and Windows Recovery Environment updates.

Why does 0x80070643 keep failing on .NET Framework updates?

Because the .NET Framework installation on the PC is already in a damaged or inconsistent state, often from an earlier interrupted update. Each new .NET cumulative update tries to patch the broken install and aborts with the same code. Repairing the framework from Programs and Features, or with Microsoft's .NET Framework Repair Tool, usually breaks the loop.

Do I need to resize my recovery partition for the KB5034441 error?

The WinRE update KB5034441 fails with 0x80070643 when the recovery partition has less than about 250 MB of free space, because the update cannot stage its files. Check with reagentc /info. You can shrink the main partition, move the recovery partition, and enlarge it — or hide that specific update if you do not rely on WinRE and Microsoft's guidance for your system says it can be skipped.

Microsoft says the error is a false alarm on KB5057589. Can I ignore it?

For the WinRE update KB5057589, Microsoft confirmed the update applies correctly during the reboot even though Windows Update still shows 0x80070643. A daily scan and a restart normally clear the false failure message. This only applies when the failing item is that specific WinRE update — do not ignore 0x80070643 on .NET Framework or feature updates, because those genuinely fail to install.

Related fixes