0x80070643 Error | Windows Update Fixes That Work

If you saw this code in Windows Update, in Microsoft Store, or while installing an app, you’re dealing with the same core problem: Windows tried to commit a package and the installer backed out. The good news is that this code is rarely “mysterious.” It’s usually one of three things: a corrupted download cache, broken system files, or a component that updates rely on.

This guide walks you through a clean order of fixes, from quick wins to deeper repairs. You’ll know what to try first, what each step changes, and how to confirm you’re done at home.

What This Error Code Means On Windows

0x80070643 maps to a Windows Installer failure that’s often described as a fatal error during installation. You’ll see it when Windows Update tries to install a cumulative update, a security update, a servicing stack update, or a .NET-related patch. You can also see it when installing a desktop app that uses MSI or when a setup process calls the Windows Installer service.

The code by itself doesn’t tell you which file failed. It tells you the installer stopped in a way it couldn’t roll back from. That points to a small set of usual suspects.

• Corrupted update cache — The downloaded bits in SoftwareDistribution don’t match what Windows expects, so install fails mid-way.
• Component store damage — The Windows component store (WinSxS) has corruption, so updates can’t stage or commit cleanly.
• .NET install trouble — Many Windows updates include .NET patches; if the .NET feature on your PC is damaged, the update can fail.
• Windows Installer or cryptography glitches — Installer services, certificates, or catalog files get stuck and block verification.
• Security software interference — Some third-party antivirus tools hook into installs and can block file replacement.

You don’t need to guess which one you have. The order below is built to surface the easiest fix first, then move to steps that repair Windows itself.

Fast Checks That Save Time

Confirm The Exact Update Or App That Fails

Start by noting what’s failing. In Windows Update, open the update history and copy the KB number, if one is shown. If it’s a Store app or desktop installer, note the app name and version. This helps later if you choose a manual install.

Try A Clean Restart And One Reattempt

A stalled installer session can hold locks on files. A restart clears those locks and restarts update services in a clean state.

1. Restart The PC — Use Start > Power > Restart, then wait for the desktop to fully load.
2. Run Windows Update Again — Go to Settings > Windows Update and select Check for updates.

Use This Quick Triage Table

Peek At The Failure In Reliability Monitor

Reliability Monitor lists recent install failures and the process name that triggered them. It can show whether the failing piece is Windows Update, MSI, or an app installer.

1. Open Reliability Monitor — Press Win+R, type perfmon /rel, press Enter.
2. Open The Red X Entry — Pick the failure day, then open details.
3. Note The Failing App Name — Use the name when you pick a fix.

Next, move to repairs that fix Windows files and the component store. These steps are safe, built-in, and often the turning point.

0x80070643 Error In Windows Update With .NET Patches

When the failing item is a .NET patch, this error can mean your .NET feature registration is damaged. Windows Update may download the patch fine, then fail when it tries to apply it to the installed .NET components. The fastest move is to repair the Windows image, then run a .NET-specific repair.

Repair The Windows Component Store With DISM

DISM checks the component store that Windows uses as the source of truth for system components. If the store is damaged, updates can’t stage properly.

1. Open Terminal As Admin — Right-click Start, select Terminal (Admin), then accept the prompt.
2. Run The RestoreHealth Command — Paste the command below, press Enter, and wait for it to finish.

DISM /Online /Cleanup-Image /RestoreHealth

If DISM reports it repaired corruption, restart once before you try Windows Update again.

Scan And Repair System Files With SFC

SFC validates protected system files and replaces damaged ones with known-good versions.

1. Run System File Checker — In the same admin terminal window, run the command below.
2. Restart After Completion — Reboot to let Windows finish file replacements.

sfc /scannow

Run The Microsoft .NET Repair Tool

If the failure keeps pointing to .NET updates, use Microsoft’s repair utility. It checks common setup issues and applies a set of safe fixes.

1. Download The Repair Tool — Get it from Microsoft Download Center and save it locally.
2. Run The Tool — Accept the license, let it scan, then apply the fixes it recommends.
3. Restart If Asked — A reboot is common after .NET repair steps.

You can find the download by searching Microsoft Download Center for “.NET Repair Tool” or by using the official page with ID 30135.

Reinstall The .NET Feature From Windows Features

If your PC uses the optional .NET 3.5 feature, a damaged feature payload can block related updates. Turning the feature off and back on forces Windows to refresh what’s installed.

1. Open Optional Features — Press Win+R, type optionalfeatures, then press Enter.
2. Toggle .NET 3.5 — Clear the .NET 3.5 box, accept, then restart when prompted.
3. Enable It Again — Reopen Optional Features, check .NET 3.5, then let Windows install the files.

If you don’t see the .NET 3.5 box, skip this step. Many Windows 11 installs only use the newer .NET 4.x line that ships with Windows.

At this point, retry Windows Update. If you still hit the 0x80070643 error, the next steps reset the update plumbing and rebuild the local cache.

Reset Windows Update Components Without Guesswork

Windows Update relies on a small set of services plus a cache folder that stores downloads and metadata. If any of that gets stuck, updates can fail in a loop. Resetting the components forces Windows to rebuild those parts from scratch.

Stop Update Services And Rename Cache Folders

This method is easy to undo because it renames folders instead of deleting them.

1. Open Terminal As Admin — Use Terminal (Admin) again.
2. Stop Update Services — Run each line and wait for “stopped” messages.

net stop wuauserv
net stop bits
net stop cryptsvc

3. Rename The Cache Folders — These commands create fresh folders the next time update runs.

ren %systemroot%\SoftwareDistribution SoftwareDistribution.old
ren %systemroot%\System32\catroot2 catroot2.old

4. Start Services Again — Bring the services back up.

net start cryptsvc
net start bits
net start wuauserv

Now run Windows Update again. The first check can take longer because Windows is rebuilding the cache.

Run The Built-In Windows Update Troubleshooter

If you prefer a guided fix, Windows includes a troubleshooter that resets pieces of the update stack.

1. Open The Troubleshooter — Settings > System > Troubleshoot > Other troubleshooters.
2. Run Windows Update — Select Windows Update, then Run.

Fix Install Failures Caused By Disk, Permissions, Or Security Tools

Sometimes the update mechanism is fine and the failure is local: low disk space, file permissions, or a security tool blocking replacement of files. This section is a quick sweep that catches those cases.

Free Space And Clear Temporary Files

Updates need working room. If you’re tight on disk, the install can fail late in the process.

• Check Free Space — Open Settings > System > Storage and confirm you have several GB free on C:.
• Clean Temporary Files — In Storage, open Temporary files, select safe items, then Remove files.

Temporarily Disable Third-Party Antivirus

If you use third-party antivirus, pause real-time protection during the update attempt. Some tools block system file swaps and trigger install failures.

• Pause Real-Time Scanning — Use the antivirus UI to pause protection for a short window.
• Retry The Update — Run Windows Update once, then turn protection back on.

Install The Update Manually By KB Number

If one update keeps failing, manual install can bypass a glitch in the download flow. You’ll need the KB number from update history.

1. Open The Microsoft Update Catalog — Search the KB number, then pick the match for your Windows version and architecture.
2. Run The Standalone Installer — Download the .msu file, run it, then restart.

Manual install is also a clean way to confirm if the issue is in the Windows Update client or in the package itself.

When The Error Keeps Coming Back

If you’ve run DISM, SFC, reset the update components, and repaired .NET, yet the same install code returns, treat it as a deeper Windows servicing issue. The steps below are the last moves that still keep your files intact.

Try An In-Place Repair Install

An in-place repair install reinstalls Windows system files while keeping your apps and personal files. It often fixes servicing stack glitches that normal repair commands can’t clear.

1. Get The Official Windows Installation Media — Use Microsoft’s Windows 11 or Windows 10 installation media tool.
2. Run Setup From Windows — Start setup inside Windows, pick Keep personal files and apps, then proceed.
3. Recheck Updates After Setup — Once the repair completes, run Windows Update again.

Check The Update Logs When You Need A Clue

If you need a concrete hint about what failed, Windows can generate update logs from PowerShell. This is handy when the error seems tied to a single component.

1. Generate Windows Update Logs — In an admin PowerShell window, run the command below.

Get-WindowsUpdateLog

The command creates a log file on your desktop. Look for the failing KB number and the lines around the failure time.

Confirm You’re Fixed

Once updates install, do a quick confirmation so you don’t get pulled back into the loop next patch day.

• Run Windows Update Twice — After the first successful install and restart, check again to catch any follow-up packages.
• Review Update History — Confirm the failed item now shows as Successfully installed.
• Remove Old Cache Folders — If all is stable for a day or two, you can delete SoftwareDistribution.old and catroot2.old to reclaim space.

Most PCs are fixed well before this last section. If you reached this point and still see failures, a repair install is often the clean line between “stuck forever” and “back to normal.”

Send us your feedbackTell us what you thought about this post

Name * Email *

Your comment *

Quick check — what is …? *

Send feedback