Getting hit with Windows Update Error 0x80071a91 feels kinda frustrating — it usually pops up when there’s something funky with the update service or the system component store that’s gone sideways. It’s not uncommon for Windows updates to get stuck, especially after big system changes or if some files got corrupted. This guide walks through a few hacks that have actually worked to get rid of that stubborn error, so your system can finally update smoothly again.

How to Fix Windows Update Error 0x80071a91

Access Troubleshoot Settings and Run the Windows Update Troubleshooter

This first step is kinda like kicking the tires and seeing if Windows can sniff out the problem itself. The built-in troubleshooter is pretty decent at spotting common issues with the update service, especially if the error is related to a broken service or mismatched files. Sometimes it fixes it right away, other times it’s just a good start.

  1. Hit the Windows key or click the Start button.
  2. Type Troubleshoot settings into the search bar and open it.
  3. Scroll down to Other troubleshooters and click on it.
  4. Find Windows Update and click Run.

The troubleshooter will scan your system for common issues like stuck downloads or corrupted components. If it finds something, it’ll often fix it on the spot. Not always, but it’s worth a shot.

Run SFC / System File Checker to Fix Corrupted Files

If the troubleshooter didn’t make a difference, there’s a good chance some core system files got corrupted or went missing. Running sfc /scannow can catch these and replace them. Trust, Windows has to make it harder than it should sometimes, but this tool is pretty reliable for fixing damaged system files.

  1. Search for cmd or Command Prompt in the Start menu.
  2. Right-click on it and choose Run as administrator. Yep, you need admin access for this one.
  3. When the black window pops up, type sfc /scannow and hit Enter.
  4. Now, sit back and wait. It might take a few minutes, especially if there’s a lot to scan. It’ll tell you if it finds issues and repairs them automatically.

Sometimes, it’s as simple as that — fixing some missing or corrupted files could do the trick. On some setups, this scan needs a restart afterward, so be prepared for that.

Use DISM to Repair the Windows Image

If the SFC didn’t solve the problem, especially if the error message hints at component store corruption, try DISM. It’s a more powerful tool that repairs the Windows image itself, kinda like a deep clean for Windows’ core files. This command is known to fix those stubborn errors that SFC can’t handle alone.

  1. Open Command Prompt as administrator if it’s not already.
  2. Type this command exactly: DISM /Online /Cleanup-Image /RestoreHealth
  3. Press Enter and let it run. It can take some time, maybe 15-20 minutes.
  4. Once it’s finished, it’s worth rerunning the SFC scan again just to be safe.

This step fixes a lot of deep system corruptions that cause update errors, at least in my experience. Sometimes the process fails, but often it clears up whatever nonsense was blocking updates.

Reboot and Re-Test the Update

After all those scans, a fresh restart helps. Windows needs to reboot so that changes take effect, especially after fixing system files or repairing the image. Just hit Start > Power > Restart. Then try running the update again from Settings > Update & Security > Windows Update.

Extra Tips & Fixes You Might Need

While these steps fix the common stuff, here are some other things worth keeping in mind:

  • Double-check that your Windows version is actually up to date — sometimes critical updates are missing, causing weird errors.
  • Disable any third-party antivirus temporarily because some AVs can interfere with Windows Update. Of course, do this only if you’re comfortable, and re-enable afterward.
  • In more stubborn cases, resetting Windows Update components manually or doing a clean boot to eliminate background interference can help. For example, running commands like net stop wuauserv, deleting cache folders at C:\Windows\SoftwareDistribution and DeliveryOptimization, then restarting the services.
  • If nothing works, sometimes a system reset or repair install might be the last resort. Because Windows has to make things harder than they should, but sometimes that’s what it takes.

Wrap-up

Most of the time, running SFC, DISM, and a reboot can fix that frustrating update error. It’s not always straightforward, especially on older machines or after big updates, but these commands target the core issues pretty reliably. Sometimes it’s just a matter of patience and trying these steps in order. If it helps, great — if not, a more radical fix like resetting Windows might be the way to go. Fingers crossed this helps someone finally get those updates moving!

Summary

  • Run the Windows Update troubleshooter from Settings > Troubleshoot > Other troubleshooters
  • Use sfc /scannow to repair corrupted system files
  • Run DISM /Online /Cleanup-Image /RestoreHealth to fix the Windows image
  • Reboot and try updating again
  • Check for update issues, disable third-party antivirus, or reset Windows Update components if needed

Final Words

This whole process is kind of annoying, but debugging Windows update errors often takes a bit of trial and error. Usually, a few simple commands and a reboot do the trick. Just keep in mind, sometimes you gotta get a little dirty with registry edits or manual component resets if nothing else works. Hopefully, this shaves off a few hours for someone. Good luck!