Windows update error 0x80070643 means an update package, most often a .NET Framework update or a Windows Defender definition update, failed to install correctly. You can usually fix it by resetting the Windows Update components, repairing .NET Framework, or removing the specific failed update before retrying.
This error shows up in the update history as “Failed” next to a KB number, sometimes with the text “there were some problems installing updates.” It is one of the more common Windows Update failures because it touches two systems people rarely check: .NET Framework and Defender’s antimalware platform.
What causes error 0x80070643
The code translates to a generic installation failure. Corrupted update cache files in the SoftwareDistribution folder are the most frequent cause. A damaged or incomplete .NET Framework installation is the second, since many cumulative updates bundle .NET patches, and conflicts with Windows Defender during a definition update round out the top three.
Third-party antivirus software, a pending restart from a previous update, and low disk space can trigger the same code, so rule out the easy stuff before touching system files.
Restart and run Windows Update again
Restart your PC first. A surprising share of 0x80070643 failures clear themselves once a pending update or a locked file gets released by a reboot. After restarting, go to Settings, then Windows Update, and check for updates again.
If the same update fails a second time, note the KB number shown in the error details. You will need it if you decide to remove the update manually later.
Run the Windows Update troubleshooter
Open Settings, go to System, then Troubleshoot, then Other troubleshooters, and run the Windows Update troubleshooter. It scans for corrupted update files, broken service registrations, and permission issues, then repairs what it finds automatically. This is the fastest fix to try after a restart.
Repair or reinstall .NET Framework
Since many instances of this error trace back to a broken .NET component, run the .NET Framework Repair Tool from Microsoft’s site, or reinstall .NET Framework 3.5 and 4.8 through Control Panel, Programs, Turn Windows features on or off. Uncheck the .NET Framework boxes, restart, then recheck them and restart again to force a clean reinstall.
If you are also seeing slow boot times on the same machine, our guide to fixing a slow startup on Windows covers the startup services worth trimming after a repair like this.
Reset the Windows Update components manually
If the troubleshooter and .NET repair do not resolve it, reset the update cache manually. Open Command Prompt as administrator and stop the services first.
- net stop wuauserv
- net stop cryptSvc
- net stop bits
- net stop msiserver
Rename the SoftwareDistribution and Catroot2 folders (add “.old” to each name), then restart the same four services with net start instead of net stop. Run Windows Update again afterward. This forces Windows to rebuild the update cache from scratch, clearing out whatever corrupted file caused the failure.
Corrupted cache files behave a lot like the file integrity problems we cover in our piece on what a checksum error actually is, and the same instinct, rebuild the damaged data rather than patch around it, applies here too.
Check Windows Defender and third-party antivirus
If the failed update is a Defender definition update specifically, open Windows Security, go to Virus & threat protection, then Protection updates, and check for updates there directly instead of through the general Windows Update channel.
Third-party antivirus tools sometimes block Defender or .NET installers from writing files during an update. Temporarily disabling real-time protection on your third-party tool, running the update, then re-enabling protection is worth testing if nothing else has worked. Audio drivers get flagged by overzealous antivirus tools for similar reasons, which is one of the fixes in our sound not working on Windows guide.
Frequently asked questions
Does error 0x80070643 mean my PC is infected?
No. It is an installation failure code tied to update files or components, not a malware indicator. Run Windows Defender as a precaution, but the fix lies in the update process itself.
Will resetting update components delete my files?
No. Renaming the SoftwareDistribution and Catroot2 folders only clears cached update data. Windows rebuilds both folders automatically and re-downloads what it needs.
What if the error keeps returning after every fix?
Note the exact KB number failing and hide that specific update using the Show or Hide Updates troubleshooter from Microsoft, then let other updates install normally. You can unhide it later once a revised version of that patch ships.

Robert J. Smith is still early into his career as tech reporter but has already had his work published in many major publications including JoyStiq and Android Authority. In regards to academics, Robert earned a degree in business from Fordham University. Robert has passion for emerging technology and covers upcoming products and breakthroughs in science and tech.