How to Fix Windows Update Error 0x80070643
If Windows Update stops partway through and leaves you with error code 0x80070643, you’re looking at one of the more common — and more misunderstood — update failures on Windows 10 and Windows 11. The update either refuses to install at all, or it installs everything except one piece, then reports this code and asks you to restart.
The good news is that 0x80070643 is rarely a sign of serious damage to your system. In the large majority of real cases, it comes down to one of two things: a Windows Update component that’s stuck or corrupted, or — increasingly common on newer builds — a hidden recovery partition that’s too small to hold an updated Recovery Environment. Neither one requires reinstalling Windows.
Quick explanation: this guide walks through what the error code actually means, the two situations that cause it most often, and the specific things to check — in order — before you consider anything as drastic as a Windows reset.
For the full feature list and usage details, you can also visit the Fixyfier Documentation.
Quick Answer
Error 0x80070643 is a generic “installation failed” code, not a description of what’s actually wrong. On most PCs today, it shows up when Windows Update tries to refresh the Windows Recovery Environment (WinRE) and the hidden recovery partition doesn’t have enough free space to fit the new recovery image — in that case, the rest of the update usually installs fine, and Microsoft has confirmed it’s generally safe to leave alone in the short term. If the error appears on a normal feature or security update instead, it’s more likely a stuck Windows Update component, and running the built-in troubleshooter followed by DISM and SFC resolves it in most cases.
What Error 0x80070643 Actually Means
0x80070643 translates to ERROR_INSTALL_FAILURE, a Windows Installer code that simply means “something in this installation did not complete.” It isn’t specific to Windows Update — the same code shows up when a regular desktop application’s installer fails, which is part of why searching for it online turns up such a wide mix of unrelated advice.
When it appears during Windows Update, it means one particular package inside a larger update batch failed to apply, while Windows Update itself is still working normally. That distinction matters: a generic-sounding error name makes this look more alarming than it usually is, and it’s worth confirming which specific update failed — Settings > Windows Update > Update history will show you the exact KB number tied to the failure — before assuming the worst.
Checking Update History takes under a minute and tells you immediately whether you’re dealing with a WinRE-only failure or something affecting your actual Windows installation — worth doing before trying any fix below.
Why This Error Shows Up During a Windows Update
There are two situations that account for the great majority of real-world 0x80070643 reports. The first is a Windows Update component that’s gotten into a bad state — often because a previous update was interrupted by a shutdown, a dropped connection, or low disk space partway through installation. Windows Update keeps a local cache of downloaded files and a record of what’s already been applied, and if either one gets corrupted, later updates can fail with this same generic code.
The second cause has become much more common on Windows 11 over the last couple of years: the update trying to install actually targets the Windows Recovery Environment (WinRE), a small hidden partition used for repair tools like Startup Repair. Microsoft periodically ships security patches for WinRE bundled inside regular cumulative updates, and if that recovery partition is too small — a common situation on PCs upgraded from older Windows versions — the WinRE portion of the update fails with 0x80070643, even though the main operating system update installs correctly.
Telling these two apart is the difference between a five-minute fix and wasted time repairing system files that were never the problem — the next two sections cover both.
Quick Fixes to Try Before Anything Else
Before touching any system files, rule out the simple explanations. Restart the PC properly — not sleep, a full restart — and try the update again from Settings > Windows Update > Check for updates. A meaningful share of update failures, including this one, clear up after a clean restart because it releases files that Windows was still holding open from the failed attempt.
Next, check how much free space is on your main drive. Windows Update needs headroom to stage files before installing them, and running low — especially under 10-15 GB free — is enough to cause installation failures with exactly this kind of generic error code. If space is tight, clearing temporary files and old Windows Update leftovers (Settings > System > Storage > Temporary files) is worth doing before you try again. Finally, run the built-in Windows Update Troubleshooter from Settings > System > Troubleshoot > Other troubleshooters — it automatically resets a handful of update-related settings and services that commonly cause this exact failure.
Fixyfier’s Quick Fix section bundles the temp-file and Disk Cleanup steps above into a single click — Clear Windows Temp Folder, Clear User Temp Folder, and Launch Disk Cleanup — and its troubleshooter list includes the Windows Update troubleshooter directly, so you don’t have to hunt through Settings menus for either one.
Repairing Windows Update Components with DISM and SFC
If the quick fixes don’t resolve it, the next step is repairing the Windows component store that Windows Update relies on. Two built-in tools handle this: DISM (Deployment Image Servicing and Management), which repairs the underlying Windows image, and System File Checker (SFC), which scans for and replaces damaged system files. Run them in that order — DISM first, since SFC can fail silently if the component store itself is already damaged.
Open Terminal or Command Prompt as administrator and run the DISM restore-health command below, then follow it with SFC once DISM finishes. Both scans can take anywhere from five to twenty minutes depending on your drive speed, and it’s normal for DISM to show no progress change for several minutes at a time — let it finish rather than closing the window.
DISM /Online /Cleanup-Image /RestoreHealth
sfc /scannowThis is the same repair pair Microsoft documents for corrupted system files. Fixyfier’s Deep Fix section runs both directly — Run DISM RestoreHealth and Run SFC — as one-click actions instead of typed commands, if you’d rather not open Terminal yourself.
Recommended While You Troubleshoot
Stay Protected While You Chase Down Update Errors
Troubleshooting a stuck Windows Update often means downloading extra tools, standalone update packages, or driver files from third-party sites. NordVPN encrypts that traffic so your connection stays private, especially if you're working from public Wi-Fi while you fix this.
Protect My ConnectionChecking the Recovery Partition (WinRE) Issue
If update history shows the failure is specifically tied to a WinRE-related update, or if DISM and SFC found nothing wrong, the recovery partition is the more likely culprit. You can check its status directly: open Command Prompt as administrator and run the command below to see whether WinRE is enabled and how it’s configured.
If the recovery partition is too small to fit the new WinRE image, Windows will keep failing this specific update on every cumulative update cycle until the partition is resized — which usually means using a partition tool to shrink an adjacent partition and extend the recovery partition into that space, a process Microsoft has published detailed steps for since this became a widespread issue. It’s a more involved fix than most people need for a single failed update, which is why the next section matters.
reagentc /infoThere’s no automatic tool that resizes this for you — it’s a manual partition operation — so it’s worth being confident this is actually the cause, via the
reagentc /info check above, before you touch partition sizes at all.When It’s Safe to Leave This Error Alone
Microsoft has publicly acknowledged that when 0x80070643 is caused specifically by a failed WinRE update, the rest of Windows Update — including the security-critical parts — installs normally, and the operating system itself isn’t left in a vulnerable or broken state. In that situation, the practical advice is to stop retrying the same update, since it will keep failing until the partition is resized, and simply let it be superseded by the next cumulative update.
The exception is if 0x80070643 is blocking an update that isn’t WinRE-related — a feature update or a security patch for Windows itself. In that case, don’t ignore it: work through the repair steps above, and if the error persists after DISM, SFC, and a troubleshooter run, that’s the point where contacting Microsoft support or a technician makes more sense than continuing to retry the same fixes.
If it turns out to be a normal update failing rather than a WinRE-only one, that’s exactly the scenario the DISM, SFC, and troubleshooter steps above are built to catch — worth working through before assuming anything more serious is wrong.
Frequently Asked Questions
Is it safe to ignore Windows Update error 0x80070643?
Usually yes, but only when it’s specifically tied to a failed WinRE (Recovery Environment) update — Microsoft has confirmed this doesn’t affect the rest of Windows Update or leave your PC less secure. Check Settings > Windows Update > Update history to confirm which update is actually failing before deciding to ignore it.
Why does error 0x80070643 keep happening every time I retry the update?
Retrying installs the same update the same way, so if the real cause is a too-small recovery partition or a corrupted update component, nothing changes between attempts. The fix has to address the underlying cause — resizing the partition or repairing the component store with DISM and SFC — not just trying again.
Do I need to reset Windows to fix this error?
Almost never. A full reset addresses this error indirectly at best, and it’s a much bigger step than the problem usually calls for. DISM, SFC, and — if needed — resizing the recovery partition resolve the vast majority of 0x80070643 cases without touching your installed apps or files.
Let Fixyfier Take the Guesswork Out of Update Errors
Fixyfier runs the exact repair steps in this guide as one-click actions instead of typed commands: Run DISM RestoreHealth and Run SFC from its Deep Fix section, the Windows Update troubleshooter from its troubleshooter list, and Clear Windows Temp Folder or Launch Disk Cleanup from Quick Fix — so you can work through them in order without leaving the app.
