Dealing with the Frustrating Windows Update Error 0x80070643

Struggling with the 0x80070643 error on Windows 11? Learn how to fix this persistent update issue with our step-by-step guide, including partition resizing and CMD repairs.

Fix Windows 11 Update Error 0x80070643

Windows updates are essential for keeping your system secure and running smoothly. However, for many users, the update process often grinds to a halt with a cryptic message: “Install error – 0x80070643.” This specific error code is notoriously stubborn. It usually appears when there is a conflict with the .NET Framework or, more commonly in recent years, when the Windows Recovery Environment (WinRE) partition is too small to handle the update.

If you have tried restarting your computer and clicking “Retry” a dozen times to no avail, don’t lose hope. In this comprehensive 2026 guide, we will walk through every proven method to fix error 0x80070643 once and for all.

1. Why Does Error 0x80070643 Occur?

Understanding the root cause is the first step toward a solution. Error 0x80070643 is a general error code that essentially means “a fatal error occurred during installation.” While vague, it typically stems from three main issues:

  1. Insufficient Recovery Partition Space: This is the most common reason for recent Windows 11 security updates failing. The update requires more space in the Recovery (WinRE) partition than what was originally allocated.
  2. Corrupted .NET Framework: Since many Windows components rely on .NET, a corrupted installation can block system-wide updates.
  3. Broken Windows Update Components: Sometimes the internal database or cache that manages updates becomes corrupted.

2. Method 1: The “Real” Fix – Resizing the Recovery Partition

If your update specifically fails on a “Security Update for Windows” (like KB5034441), the issue is almost certainly a lack of space in the Recovery Partition. Most systems have a 500MB partition, but newer updates need at least 750MB to 1GB.

Warning: This process involves using the Command Prompt (Admin). Please follow these steps carefully.

Step-by-Step Partition Adjustment:

  1. Open Command Prompt as Administrator: Search for “cmd,” right-click it, and select “Run as administrator.”
  2. Check WinRE Status: Type reagentc /info. If it says “Enabled,” you need to disable it first by typing reagentc /disable.
  3. Shrink the Main Drive: We need to take a little space from your C: drive to give to the Recovery partition. Use the following commands:
    • Type diskpart
    • Type list disk (identify your main disk number, usually 0)
    • Type select disk 0 (or your disk number)
    • Type list partition (find your primary C: drive partition)
    • Type select partition [Number] (replace [Number] with your C: drive partition)
    • Type shrink desired=250 minimum=250
  4. Delete and Recreate the Recovery Partition: This is the technical part where you delete the old, small partition and create a new one using the space you just freed.
    • Note: Due to the complexity of partition IDs, many users find it easier to use a free tool like Minitool Partition Wizard to simply “Extend” the Recovery partition by taking space from the C: drive.
  5. Re-enable WinRE: Once the partition is larger, go back to CMD and type reagentc /enable.

After doing this, try running Windows Update again. For 90% of users, the error will be gone.

3. Method 2: Resetting Windows Update Components

If the partition resizing wasn’t the issue, your update cache might be the culprit. We can fix this by stopping the update services, clearing the temporary files, and restarting the services.

The CMD Reset Sequence:

Open your Command Prompt (Admin) again and run these commands one by one, pressing Enter after each:

Plaintext

net stop wuauserv
net stop cryptSvc
net stop bits
net stop msiserver

Now, we rename the folders where the update files are stored so Windows is forced to create fresh ones:

Plaintext

ren C:\Windows\SoftwareDistribution SoftwareDistribution.old
ren C:\Windows\System32\catroot2 catroot2.old

Finally, restart the services:

Plaintext

net start wuauserv
net start cryptSvc
net start bits
net start msiserver

Try updating again. This “flushes” the system and often clears out stuck updates.

4. Method 3: Repairing the .NET Framework

Since error 0x80070643 is often linked to .NET Framework installation failures, Microsoft provides a dedicated tool to fix it.

  1. Download the Microsoft .NET Framework Repair Tool from the official Microsoft website.
  2. Run the tool and follow the on-screen instructions. It will automatically detect and repair common issues with your .NET setup.
  3. Once finished, restart your PC and attempt the Windows Update again.

5. Method 4: Running SFC and DISM Scans

System file corruption can also lead to installation errors. Windows has built-in tools to find and fix these corrupted files automatically.

  • SFC Scan: In CMD (Admin), type sfc /scannow. This will scan all protected system files and replace corrupted ones.
  • DISM Scan: If SFC doesn’t work, type DISM /Online /Cleanup-Image /RestoreHealth. This tool connects to Windows Update servers to download and replace damaged files.

Conclusion: Keep Your Windows Healthy

The 0x80070643 error is a classic example of a simple error message hiding a complex problem. Whether it was the Recovery Partition size or a corrupted cache, following these steps should have your Windows 11 back on track.

Regularly running disk cleanups and ensuring you have at least 20GB of free space on your C: drive can prevent many of these errors from occurring in the future. If you found this guide helpful, feel free to bookmark it for future troubleshooting!