This guide walks you through the most effective ways to resolve Windows update error 0x80070643, which typically appears during the installation of cumulative updates or .NET Framework updates. The error indicates a problem with the Windows Update component or a corrupted system file. By following the steps below, you can clear the error and get your system updating normally again.
What You’ll Need
- A Windows administrator account (you’ll need to approve UAC prompts).
- Stable internet connection.
- At least 20 GB of free disk space on the system drive (temporary files can accumulate).
- Optional: a USB drive or external storage for backing up important files before major repairs.
Step-by-Step
- Run the Windows Update Troubleshooter. Go to Settings > System > Troubleshoot > Other troubleshooters. Select Windows Update and click Run. Follow the prompts. This automated tool can fix common update issues like corrupted cache or misconfigured services.
- Clear the SoftwareDistribution folder. Open Command Prompt as administrator (search for “cmd”, right-click, choose “Run as administrator”). Type the following commands one by one, pressing Enter after each:
net stop wuauserv
net stop cryptSvc
net stop bits
net stop msiserver
Then rename the folders:ren C:\Windows\SoftwareDistribution SoftwareDistribution.oldandren C:\Windows\System32\catroot2 catroot2.old. Restart the services withnet start wuauserv,net start cryptSvc,net start bits,net start msiserver. Try Windows Update again. - Run System File Checker (SFC) and DISM. In the same Command Prompt, run
sfc /scannow. Wait for it to finish. Then runDISM /Online /Cleanup-Image /RestoreHealth. This repairs system image corruption that can cause update failures. Restart your PC after both complete. - Free up disk space. Error 0x80070643 often occurs when the system drive is low on space. Use Storage Sense (Settings > System > Storage) to delete temporary files, or manually clean up the
C:\Windows\Tempfolder. Aim for at least 20 GB free. - Install the update manually. Go to the Microsoft Update Catalog, search for the specific KB number that’s failing (you can find it in Windows Update history). Download the version matching your system architecture (x64 or x86) and install it by double-clicking the .msu file.
- Perform a repair upgrade (in-place upgrade). Download the Windows 11 Installation Assistant or the Windows 10 Media Creation Tool from Microsoft’s official site. Run it and choose “Upgrade this PC now”. This reinstalls Windows while keeping your files and apps. It often resolves persistent update errors.
- Reset Windows Update components manually. If the above fails, open Command Prompt as admin and run these commands to reset the Windows Update components:
net stop wuauserv
net stop cryptSvc
net stop bits
net stop msiserver
rd /s /q C:\Windows\SoftwareDistribution
rd /s /q C:\Windows\System32\catroot2
net start wuauserv
net start cryptSvc
net start bits
net start msiserver
Then restart and try updating.
Common Mistakes
- Skipping the Disk Space Check: Many users ignore low disk space, which is a frequent cause of this error. Always check free space first.
- Running SFC without DISM: SFC alone often fails if the system image is corrupted. Always run DISM first or after SFC.
- Not restarting after service stops: After stopping services, always restart the computer before attempting updates again, otherwise the old folders may be locked.
- Downloading the wrong update version: Ensure you download the correct architecture (x64 vs x86) from the Update Catalog. Installing the wrong one will fail.
Tips
- Create a restore point before making major changes (search “Create a restore point” in Start). This lets you roll back if something goes wrong.
- Check for pending reboots: Sometimes a pending reboot from a previous update can block new ones. Restart your PC before troubleshooting.
- Use the Windows Update Assistant: For feature updates, the Update Assistant often works when Windows Update fails.
- Keep your drivers updated: Outdated drivers, especially storage drivers, can interfere with updates. Update them via Device Manager or manufacturer sites.
Troubleshooting
If the error persists after all steps:
- Check the CBS.log: After a failed update, open
C:\Windows\Logs\CBS\CBS.logand look for lines with “Error” or “Failed”. This can indicate which component is causing the issue. - Try a clean boot: Disable all non-Microsoft services and startup items (msconfig), then try the update. This isolates third-party conflicts.
- Use the Windows Update Reset script: Microsoft provides a PowerShell script that automates the reset process. Search for “Windows Update Reset” on Microsoft’s official site.
- Check for disk errors: Run
chkdsk /f /rin Command Prompt as admin. This scans for and repairs disk errors that can cause update failures. - If all else fails, perform a clean install: Back up your data and reinstall Windows from scratch. This is the most drastic but guaranteed fix.
Frequently Asked Questions
What exactly does error 0x80070643 mean?
It’s a generic Windows Update error that usually indicates a problem with the update installation process, often due to corrupted system files, insufficient disk space, or a faulty update component.
Why does this error occur specifically with .NET Framework updates?
.NET Framework updates often require more disk space and are sensitive to system file corruption. The error frequently appears when the .NET installation is incomplete or when the system drive is full.
Will I lose my files if I do a repair upgrade?
No, a repair upgrade (in-place upgrade) keeps your personal files, installed apps, and settings. It only replaces Windows system files, so your data remains intact.
How long does the DISM command take?
It can take anywhere from 10 minutes to an hour, depending on your system speed and internet connection. It’s normal for it to appear stuck at 20% for a while; don’t interrupt it.
Can I skip the problematic update?
You can hide the update temporarily using the “Show or hide updates” troubleshooter tool from Microsoft, but it’s not recommended to skip security updates permanently. The error usually affects a specific KB, and you can wait for the next cumulative update which may include the fix.
Is it safe to delete the SoftwareDistribution.old folder?
Yes, after you’ve successfully updated, you can delete the SoftwareDistribution.old folder to free up space. It only contains old update cache files that are no longer needed.
Related
General steps for current mainstream versions; menus can differ by device and version. See the disclaimer or report an error.
More in this bed
- How to Play Minesweeper: Rules, Tips, and Winning Strategy
- Browser SQL Sandbox for Games: Build Guide
- Fix 0x80070005 DISM Error & the 0x800070005 Typo
- Fix Access Denied Adding Shared Printer in Windows 10
- Snapchat Face Swap: Step-by-Step Guide
- Fix a Computer Chair Height Adjuster: Step-by-Step