Here’s a rewritten version of the blog post, crafted to be more natural, engaging, and reader-friendly while keeping all the original guidance intact.
How to Fix Windows Update Error 0x80070643: 2026 Guide
By Hisan Kidwai
February 22, 2026
If you’re reading this, chances are you’ve run into the dreaded Windows Update Error 0x80070643. You know the drill—you’re just trying to keep your system up to date, and suddenly you’re staring at a message that says, “There were some problems installing updates.” Annoying, right?
This error can pop up for a handful of reasons, which means the fix could be as simple as a quick restart or as involved as repairing core system components like the .NET Framework. But don’t worry—I’ve broken it all down step by step. Let’s get your updates back on track.
What Causes This Error?
Error 0x80070643 usually shows up in Windows Update with one of these messages:
- “There were some problems installing updates, but we’ll try again later…”
- “Failed to install on [date] – 0x80070643.”
So what’s behind it? A few things could be at play:
- Corrupted Windows system files
- Problems with the .NET Framework
- Damaged registry entries
- An incomplete previous Windows update
- Interference from third-party antivirus software
The good news? Each of these has a fix.
Before You Begin
First things first: restart your PC. Seriously. A fresh reboot clears out temporary glitches and gives your system a clean slate. It’s quick, costs nothing, and sometimes solves the problem outright. If the error sticks around after the reboot, try the methods below.
1. Restart Windows Update Services
Often, the issue is just a stuck Windows Update service. Restarting it can get things moving again.
Here’s how:
- Press Windows + R, type
services.msc, and hit Enter. - In the Services window, scroll to Background Intelligent Transfer Service (BITS) and Windows Update.
- Right-click each one and select Restart.
That’s it. Try running Windows Update again and see if the error clears.
2. Run the Windows Update Troubleshooter
Windows has a built-in troubleshooter that’s actually useful. It scans your system for common update problems and can often fix them automatically.
To run it:
- Open Settings and go to Update & Security > Troubleshoot > Additional troubleshooters.
- Select Windows Update, then click Run the troubleshooter.
- Follow the on-screen prompts.
Let it do its thing—it might just save you a lot of manual effort.
3. Repair the .NET Framework
The .NET Framework is essential for many Windows apps, and if it gets corrupted, it can interfere with system updates. Luckily, Microsoft provides a dedicated .NET Framework Repair Tool to fix this.
- Download the tool from Microsoft’s official website.
- Run it and follow the instructions.
- Once it’s done, restart your system.
This step has resolved the 0x80070643 error for many users, so it’s definitely worth a try
4. Temporarily Disable Antivirus Software
If you’re using third-party antivirus software like McAfee, Norton, or even some firewalls, they can sometimes block critical update files. That’s often enough to trigger this error.
Temporarily disable your antivirus, then try the update again. Just don’t forget to turn it back on afterward. If the update succeeds, you might want to check your antivirus settings for an option to allow Windows Update through.
5. Run a System File Check (SFC & DISM)
Corrupted or missing system files are a common culprit behind update errors. Windows has two built-in tools—SFC and DISM—that can scan and repair them.
Here’s how to run them:
- Open Command Prompt as an administrator.
- Type the following command and press Enter:
sfc /scannow- Wait for it to complete, then run this next command:
DISM.exe /Online /Cleanup-image /RestorehealthBoth tools will automatically repair what they find. Once they’re done, restart your PC and check for updates again.
Wrapping Up
There’s nothing more frustrating than an update that refuses to install—especially when you’re not sure why. Hopefully, one of these steps helped you kick Error 0x80070643 to the curb.
If you’ve tried everything and the error still won’t budge, it might be time to reach out to Microsoft Support. They can dig deeper into your system logs and help find a resolution.
Got a fix that worked for you? Or still stuck? Let me know in the comments—I’d love to hear how it went.
