0x80070643 Fatal Error During Installation | Fast Fixes

Seeing error code 0x80070643 is annoying because it’s vague. It can pop up during Windows Update, a Microsoft Store app install, an Office patch, or a plain old .msi installer. The good news is that the fix is often repeatable right away once you match the error to the place it happens.

This guide gives you a clean, no-drama path to get installs working again on Windows 10 and Windows 11. You’ll start with quick checks that take minutes, then move into deeper repairs like resetting Windows Update parts, repairing system files, and handling the WinRE partition case that’s tied to certain security updates.

What 0x80070643 Means And Why It Shows Up

0x80070643 is the Windows “fatal error during installation” code. In plain terms, an installer asked Windows to apply changes and Windows returned an install failure. On many systems it maps to the Windows Installer error family that includes error 1603, a common MSI failure state. The usual triggers are permissions, encrypted folders, missing system components, or a service that can’t write where it needs to.

That broad meaning is why two people can see the same code and need different fixes. The trick is to pin down which “installer” is failing.

Reproduce the failure once while you watch where it happens. Settings under Windows Update points to servicing. A setup wizard points to Windows Installer or the app. If you can, grab what Windows logs: in Update history note the KB number, or in Event Viewer check MsiInstaller events near the failure time.

On a managed PC, installs can be blocked by policy. Note the time and app name, then sync policies and retry once.

Before you start changing things, confirm which bucket you’re in. Look at the message in Settings, Windows Update history, or the installer window. If you see a specific KB number, write it down. If it’s an MSI, note the app name and version.

0x80070643 Fatal Error During Installation On Windows 10 And 11

This section is the fastest path for most home PCs. It targets the shared plumbing behind Windows Update, Store installs, and many app patches. Work top to bottom, stopping when the install succeeds.

Restart And Clear The Easy Blocks

A restart can clear a stuck Windows Installer service, a pending reboot state, or a file lock. It sounds simple, yet it often turns a repeat failure into a clean install.

• Restart Windows — Reboot, then try the same install once.
• Free Some Space — Keep at least 10 GB free on the C: drive so servicing tools can expand files.
• Pause Third-Party Antivirus — If you run non-Microsoft security software, pause it briefly and retry the install.

Run The Built-In Windows Update Troubleshooter

When the failure happens inside Windows Update, let Windows try its own fix first. On Windows 11, you’ll find it under Settings, System, Troubleshoot, Other troubleshooters. On Windows 10, it sits under Settings, Update & Security, Troubleshoot.

• Open Settings — Go to Troubleshooters and run Windows Update.
• Apply Suggested Fixes — Accept repairs, then reboot if asked.
• Retry The Update — Install the same update again.

Repair System Files With DISM And SFC

If Windows servicing files are damaged, updates can fail with 0x80070643 fatal error during installation. DISM repairs the component store, and SFC repairs protected system files. Run these in an elevated terminal.

1. Open Admin Terminal — Right-click Start, pick Terminal (Admin) or Command Prompt (Admin).
2. Run DISM RestoreHealth — Type DISM /Online /Cleanup-Image /RestoreHealth and press Enter.
3. Run SFC — Type sfc /scannow and press Enter.
4. Restart — Reboot, then try the install again.

Reset The Windows Update Cache

Corrupt cache files in SoftwareDistribution can trap you in a loop where the same update downloads, fails, then retries. Resetting the cache forces Windows to rebuild it from scratch.

1. Stop Update Services — In an admin terminal, run net stop wuauserv and net stop bits.
2. Rename Cache Folders — Run ren %systemroot%\SoftwareDistribution SoftwareDistribution.old and ren %systemroot%\System32\catroot2 catroot2.old.
3. Start Services — Run net start bits and net start wuauserv.
4. Retry Updates — Go back to Windows Update and try again.

When The Error Is Tied To A WinRE Security Update

A big spike in this error happened with Windows Recovery (WinRE) security updates like KB5034441. In that case, Windows Update can download the patch, then fail near the end with 0x80070643 because the hidden recovery partition does not have enough free space for the updated WinRE image. Microsoft published KB5028997 with step-by-step instructions to resize partitions so the WinRE update can install.

If your Update history lists KB5034441, start here. If you don’t see a WinRE KB, skip to the next section.

Check WinRE Status And Recovery Partition Space

1. Open Admin Terminal — Use Terminal (Admin).
2. Check WinRE — Run reagentc /info and confirm WinRE is enabled.
3. Inspect Partitions — Open Disk Management and look for a Recovery partition near the end of Disk 0.

Resize The Recovery Partition Using Microsoft Instructions

Partition resizing has risk. Back up anything you care about, and follow Microsoft’s sequence exactly. The KB5028997 steps use diskpart to shrink the OS partition, then extend or recreate a larger recovery partition before re-enabling WinRE.

• Back Up First — Save files to an external drive or cloud storage.
• Follow KB5028997 — Use Microsoft’s commands and sizes for your setup.
• Re-enable WinRE — Confirm with reagentc /enable and reagentc /info.
• Install The Update — Retry KB5034441 in Windows Update.

Some PCs have OEM layouts that make resizing harder. If the steps don’t apply cleanly, a local repair shop or your device maker’s help desk can assist with a safe resize plan.

Fixes For MSI And App Installer Failures

When the error pops up in an app installer, treat it like an MSI failure first. Common causes include lack of admin rights, encrypted install targets, or missing permissions on system folders.

Run The Installer With Admin Rights

• Close The Installer — Exit the setup window fully.
• Right-Click The Setup File — Pick Run as administrator.
• Install To A Simple Path — Prefer C:\Program Files for apps, not a synced folder.

Check For Pending Reboots And Installer Service Health

• Restart Once — Clear a pending reboot state.
• Restart Windows Installer — Run services.msc, find Windows Installer, then restart it.
• Retry Install — Run the same setup again.

Grab A Log That Points To The Real Failure

With MSI packages, a log can turn guesswork into a direct fix. You can generate one with the installer itself.

1. Create A Folder — Make C:\Temp if it doesn’t exist.
2. Run MSI With Logging — Use msiexec /i "path\app.msi" /L*v "C:\Temp\install.log".
3. Search For Return Value 3 — In the log, that marker often sits near the failing action.

If the log shows access denied, install to a local folder and confirm Windows can write to C:\Windows\Temp. Deleting files in that Temp folder can remove a lock and let the next run finish.

If you’re deploying apps through Intune, test a manual install on one affected device. If manual install works, the issue can be detection rules or install context, not the app itself.

Repairing .NET When Installers Depend On It

A lot of installers call into .NET components. If .NET is damaged, you can see 0x80070643 fatal error during installation when patching Office, installing some desktop apps, or applying Windows updates that touch .NET.

Confirm Which .NET You’re Using

Windows 10 and 11 include newer .NET components as part of the OS, and older .NET components can be optional features. Your goal is not to “install every .NET ever.” Your goal is to repair what the failing installer expects.

• Check Windows Features — Open “Turn Windows features on or off” and see if .NET 3.5 is enabled when an older app needs it.
• Install Pending .NET Updates — In Windows Update history, look for .NET updates that failed.

Use Repair Steps That Don’t Break Your Setup

1. Run DISM First — Repairing the component store can also repair .NET pieces shipped with Windows.
2. Repair Or Reinstall The App — If the error is tied to one app, uninstall it, reboot, then install the newest build.
3. Retry The Update — Return to Windows Update and run the same patch.

If you are stuck on a specific .NET update, grab the KB number from Update history and install it from the Microsoft Update Catalog. That route can skip some caching issues.

A Clean “Last Resort” Path That Still Stays Safe

If you tried the steps above and the same install still fails, you have two reliable options that keep your files intact.

Install The Update Or App Manually

For Windows updates, use the KB number to download the standalone installer from the Microsoft Update Catalog, then run it as admin. For apps, download a fresh installer from the vendor, not a third-party mirror. This cuts out corrupted downloads and stale installers.

• Match The Exact KB — Use Update history to confirm the KB.
• Download From Microsoft — Use the catalog for Windows updates.
• Reboot After Install — Give Windows a clean start before testing.

Do An In-Place Repair Install

An in-place repair install reinstalls Windows system files while keeping apps and personal files. It’s a solid move when servicing components are too tangled for spot fixes.

1. Download The Windows ISO — Get it from Microsoft’s official Windows download page.
2. Run Setup — Choose to keep personal files and apps.
3. Update Again — After the repair, run Windows Update.

After you’re back to a clean install state, rerun the original action that triggered the error and confirm it completes without a rollback.

Send us your feedbackTell us what you thought about this post

Name * Email *

Your comment *

Quick check — what is …? *

Send feedback