Quick answer

Error 0x80070643 (ERROR_INSTALL_FAILURE) has two main causes on Windows 11 and Windows 10: a Windows Recovery Environment (WinRE) security update failing because the hidden recovery partition lacks 250 MB of free space (logged as Event ID 4502 with ErrorPhase 2), or a general MSI, Microsoft Defender or .NET installer failure. Check Event Viewer for Event ID 4502 first: if present and WinRE sits right after C:, resize the recovery partition by 250 MB using Microsoft’s KB5028997 reagentc and diskpart sequence; otherwise reset SoftwareDistribution and repair .NET / system files.

Fix steps

4 steps

Diagnostic workbench
Contents

At a glance

Applies to
Windows 11 and Windows 10 (WinRE updates, Defender & .NET/MSI updates)
First check
Check Event Viewer System log for Event ID 4502 (ErrorPhase 2)
WinRE cause
Hidden Recovery partition too small; Microsoft KB5028997 adds 250 MB
Before diskpart
Back up important files and BitLocker recovery keys first

Provenance

  • Nov 21, 2026Published

Error 0x80070643 (ERROR_INSTALL_FAILURE) frustrates people because Windows Update reuses this single return code for three completely different failures—and running generic sfc /scannow advice never fixes the most common one.

Before running a single command, open Settings > Windows Update > Update history and read which item failed alongside 0x80070643:

What failed in Update historyActual root causeJump straight to
Windows Recovery Environment (WinRE) update (e.g. KB5034441 on Windows 10, or System Event ID 4502 on Windows 11/10)Hidden OEM/Windows Recovery partition is ~500 MB and lacks 250 MB free space to stage Safe OS updatesBranch A (Step 1 & Step 2 — Microsoft KB5028997 resize)
Security Intelligence Update for Microsoft Defender AntivirusCorrupted local Defender signature cache or paused WinDefend serviceBranch B (Step 3 — 60-second Defender cache refresh)
Cumulative Windows Update, .NET Framework update, or MSI appCorrupt SoftwareDistribution cache, stopped msiserver, or damaged CBS component storeBranch C (Step 4 — Update cache, msiserver & DISM/SFC)

Step 1. Confirm the WinRE partition space bug (Event ID 4502)

Microsoft’s KB5028997 bulletin notes that starting with modern monthly servicing, Windows updates the Recovery Environment (winre.wim) in place—and logs a specific System event whenever the recovery partition is too small:

  1. Right-click Start -> Event Viewer -> Windows Logs > System.
  2. Click Filter Current Log…, enter 4502 in the Event IDs box, and click OK.
  3. If Event 4502 appears with "Windows Recovery Environment servicing failed" and ErrorPhase 2, you have confirmed the recovery partition space shortage (CBS_E_INSUFFICIENT_DISK_SPACE masked behind 0x80070643).

Step 2. Branch A — Expand the WinRE Recovery partition by 250 MB (KB5028997)

Back up first: Modifying disk partitions carries data-loss risk if a wrong partition index is typed. Back up important personal files and export your BitLocker recovery key before opening diskpart.

Microsoft’s KB5028997 method works only when the WinRE recovery partition sits immediately to the right of (after) your OS C: partition on the same disk. Verify that layout in step 2 below before deleting anything!

  1. Open Command Prompt as Administrator (cmd -> Run as administrator) and check current WinRE location:

    reagentc /info
    

    Read the Windows RE location line—for example: \\?\GLOBALROOT\device\harddisk0\partition4\Recovery\WindowsRE. Write down the harddisk number (0) and partition number (4). (If WinRE already says Disabled, check Disk Management (diskmgmt.msc) first to see whether a Recovery Partition sits directly to the right of C:.)

  2. Temporarily disable WinRE (this moves winre.wim safely inside C:\Windows\System32\Recovery while you resize the partition):

    reagentc /disable
    
  3. Open diskpart and inspect your disk and partition order:

    diskpart
    list disk
    
    • Note whether an asterisk (*) appears under the Gpt column on your OS disk (* = GPT, blank = legacy MBR).
    • Select your OS disk (replace <OS-disk> with the disk number from step 1, such as 0) and list its partitions:
      sel disk <OS-disk>
      list part
      
    • Stop and verify: confirm your Primary OS partition (C:) sits directly before the Recovery partition index from step 1 (for example, Partition 3 = Primary 930 GB, Partition 4 = Recovery 520 MB). If Recovery is Partition 1 or 2 before C:, type exit and run reagentc /enable—do not delete a front-of-disk partition!
  4. Shrink the OS partition (C:) by 250 MB and remove the undersized old recovery shell (replace <OS-part> and <WinRE-part> with your exact numbers from list part):

    sel part <OS-part>
    shrink desired=250 minimum=250
    sel part <WinRE-part>
    delete partition override
    
  5. Create and format the new larger recovery partition (which automatically claims the old recovery space plus the new 250 MB):

    • On a GPT disk (* in the Gpt column—almost all UEFI Windows 11 and modern Windows 10 PCs; see UEFI & Secure Boot check):
      create partition primary id=de94bba4-06d1-4d40-a16a-bfd50179d6ac
      gpt attributes =0x8000000000000001
      format quick fs=ntfs label="Windows RE tools"
      
    • On a legacy MBR disk (no * in the Gpt column):
      create partition primary id=27
      format quick fs=ntfs label="Windows RE tools"
      set id=27
      
  6. Confirm the volume, leave diskpart, and turn WinRE back on:

    list vol
    exit
    reagentc /enable
    reagentc /info
    

    Confirm Windows RE status says Enabled, reboot once, and re-run Settings > Windows Update > Check for updates.

Step 3. Branch B — 0x80070643 on Microsoft Defender Security Intelligence updates

If Update history shows 0x80070643 on a Security Intelligence Update (KB2267602), leave your disk partitions untouched and flush Defender’s local signature cache from Command Prompt (Admin):

"%ProgramFiles%\Windows Defender\MpCmdRun.exe" -removedefinitions -dynamicsignatures
"%ProgramFiles%\Windows Defender\MpCmdRun.exe" -SignatureUpdate

Wait 60 seconds for -SignatureUpdate to print Signature update finished. No updates needed (or finish downloading), then click Retry in Windows Update.

Step 4. Branch C — 0x80070643 on .NET Framework, cumulative updates, or MSI installers

When 0x80070643 hits a .NET Framework patch or cumulative update with no Event ID 4502 in Event Viewer, work Microsoft’s Windows Update reset sequence:

  1. Confirm the Windows Installer (msiserver) service isn’t disabled: press Win + R -> services.msc -> scroll to Windows Installer -> double-click and verify Startup type is Manual (never Disabled).
  2. Clear a corrupted SoftwareDistribution download cache from Command Prompt (Admin):
    net stop wuauserv
    net stop bits
    del /f /s /q %windir%\SoftwareDistribution\Download\*
    net start bits
    net start wuauserv
    
  3. Repair the Windows component store and system files:
    DISM /Online /Cleanup-Image /RestoreHealth
    sfc /scannow
    
  4. If .NET Framework updates alone still return 0x80070643, download and run Microsoft’s official .NET Framework Repair Tool (NetFxRepairTool.exe) from microsoft.com, restart, and re-check Windows Update. (If system file corruption keeps returning after DISM, check drive SMART health in our SSD health check guide.)

Frequently asked questions

What does Windows Update error 0x80070643 mean?
0x80070643 is Windows’ generic Win32/MSI installation failure code (ERROR_INSTALL_FAILURE). Because Windows Update wraps several different installers under that one return code, you must check which update failed in Settings > Windows Update > Update history: a Windows Recovery Environment (WinRE) update points to a full recovery partition, a Microsoft Defender intelligence update points to a stale signature cache, and an app or .NET update points to Windows Installer or corrupted servicing files.
How do I know if my 0x80070643 error is the WinRE partition bug?
Microsoft’s KB5028997 guidance gives an exact check: open Event Viewer > Windows Logs > System and look for Event ID 4502 showing ‘Windows Recovery Environment servicing failed’ with ErrorPhase 2 (or check whether the failed KB in Update history is a Windows Recovery Environment update such as KB5034441 on Windows 10).
Is it safe to shrink C: and recreate the WinRE partition in diskpart?
Microsoft documents the exact 250 MB shrink-and-recreate procedure in KB5028997, provided your existing WinRE recovery partition sits immediately after the OS (C:) partition on the same disk. Still, any partition edit carries data-loss risk if you select the wrong partition number: back up personal files and save your BitLocker recovery key before running diskpart.
What if my Recovery partition is BEFORE my C: partition instead of after it?
Stop before deleting anything. Microsoft’s KB5028997 steps require the recovery partition to sit directly after the OS partition so shrinking C: creates contiguous space next to WinRE. If your recovery partition sits at the front of the disk, re-enable WinRE (reagentc /enable) rather than deleting the front partition.
Why am I getting 0x80070643 on a Microsoft Defender antivirus update?
When 0x80070643 appears on Security Intelligence Update for Microsoft Defender Antivirus rather than a WinRE or cumulative OS patch, do not touch disk partitions. Clear Defender’s cached definitions with MpCmdRun.exe -removedefinitions -dynamicsignatures and MpCmdRun.exe -SignatureUpdate from an Administrator Command Prompt.

Sources and corrections

Last updated
Methodology
See our methodology for research and review standards. It draws on 4 cited sources, listed below, each checked against the original page on the date above. All WinRE diagnostic markers (System Event ID 4502, ErrorPhase 2) and every reagentc / diskpart command (250 MB shrink, GPT GUID de94bba4-06d1-4d40-a16a-bfd50179d6ac, attribute 0x8000000000000001, MBR ID 27) come verbatim from Microsoft Support article KB5028997 opened November 21, 2026 (UTC). General Windows Update cache reset and DISM/SFC steps come from Microsoft Support’s Windows Update troubleshooting documentation opened the same day.
Corrections
Spotted an error? Email a correction with the affected line and what you found. The draft includes this page’s address. Verified changes are recorded here. Contact details.

About the author

I am Lowell K. Wood IV. I research, write and maintain everything on TechFuelHQ from St. Louis County, Missouri.