Windows Update error 0x80071160 is the kind of computer problem that feels like your PC looked at a perfectly normal update and said, “No thanks, I choose chaos.” One minute you are trying to install a cumulative update, security patch, or feature update. The next minute, Windows 10 throws an error code that looks like it was generated by a tiny robot having a bad Monday.
The good news is that update error 0x80071160 is usually fixable. It commonly points to trouble with Windows Update components, corrupted update cache files, damaged system files, interrupted update services, or a problem inside the Windows component store. In plain English: Windows may know an update exists, but the machinery that downloads, verifies, stages, and installs it is not working smoothly.
This guide walks through practical ways to fix Windows 10 update issues, starting with the easiest repairs and moving toward advanced solutions. You do not need to be a certified system administrator, although you may briefly feel like one when Command Prompt starts obeying you.
What Is Windows Update Error 0x80071160?
Error 0x80071160 can appear when Windows 10 fails to download or install an update. Some users see it with cumulative updates, while others run into it when trying to move an older Windows 10 build to a newer one. The message may show up in Settings > Update & Security > Windows Update, usually after Windows attempts installation and then rolls back or stops.
Although Microsoft does not always publish a friendly, one-sentence translation for every error code, this one is often associated with broken update files, Windows Update database issues, or problems in the component store. The component store is the part of Windows that keeps system files and repair resources. When it gets messy, updates can fail the way a recipe fails when half the ingredients are missing and the oven is judging you.
Common Causes of Windows 10 Update Error 0x80071160
Before fixing the error, it helps to understand what may have caused it. Windows Update depends on several moving parts, including update services, cached files, system integrity tools, disk space, Microsoft servers, drivers, and background security software.
Corrupted Windows Update Cache
Windows stores temporary update files in the SoftwareDistribution folder. If those files are incomplete or damaged, Windows may keep trying to install a bad package. This is like reheating leftovers that were already questionable the first time.
Damaged Catroot2 Folder
The Catroot2 folder helps Windows verify update signatures. If verification data becomes corrupted, Windows may reject an update even when the update itself is legitimate.
Stopped or Glitched Update Services
Windows Update relies on services such as Windows Update, Background Intelligent Transfer Service, Cryptographic Services, and sometimes Windows Installer. If one of these services is stopped or stuck, the update process may fail.
Corrupted System Files
System file damage can block updates, especially if the damaged files are needed during installation. This is where tools like DISM and SFC become useful.
Not Enough Disk Space
Windows updates need room to download, unpack, install, and roll back if something goes wrong. A nearly full drive can stop the process before it finishes.
Third-Party Interference
Antivirus tools, firewall rules, VPN clients, optimization apps, and driver utilities can occasionally interfere with update installation. They usually mean well, but sometimes they guard the door so aggressively that even Windows cannot get inside.
Before You Start: Quick Safety Checklist
Before running repairs, do three simple things. First, restart your PC. Yes, it sounds painfully basic, but pending operations and stuck services often clear after a restart. Second, back up important files to an external drive or cloud storage. Most update repairs are safe, but smart users do not tempt fate. Third, plug in your laptop or make sure your desktop has stable power. A power cut during system repair is not a plot twist anyone needs.
Fix 1: Run the Windows Update Troubleshooter
The Windows Update Troubleshooter is the best first step because it checks common update problems automatically. It can reset certain settings, detect pending restart issues, and repair update-related problems without requiring manual commands.
- Click Start.
- Open Settings.
- Go to Update & Security.
- Select Troubleshoot.
- Click Additional troubleshooters.
- Choose Windows Update.
- Click Run the troubleshooter.
- Apply any recommended fixes.
- Restart your PC and check for updates again.
If error 0x80071160 returns, do not panic. The troubleshooter is helpful, but it is not a wizard with a tiny cape. Move on to the next repair.
Fix 2: Check Disk Space and Clean Temporary Files
Windows 10 updates can fail when the system drive is low on storage. Even if the update package looks small, Windows may need extra space for extraction, temporary files, restore data, and installation logs.
To free up space:
- Open Settings.
- Go to System > Storage.
- Click Temporary files.
- Select safe cleanup items such as temporary files, delivery optimization files, and recycle bin contents.
- Click Remove files.
You can also run Disk Cleanup:
- Press Windows + S.
- Type Disk Cleanup.
- Select your Windows drive, usually C:.
- Click Clean up system files.
- Remove old update files and temporary files.
After cleaning, restart the PC and try Windows Update again. If your computer has a tiny 32 GB or 64 GB drive, consider moving photos, videos, downloads, and installers to an external drive. Windows Update loves free space the way cats love cardboard boxes.
Fix 3: Restart Windows Update Services
If an update service is stuck, restarting the service can clear the issue. This is a gentle repair and often works when Windows Update is frozen, endlessly checking, or failing immediately.
- Press Windows + R.
- Type services.msc and press Enter.
- Find Windows Update.
- Right-click it and choose Restart. If it is stopped, choose Start.
- Do the same for Background Intelligent Transfer Service and Cryptographic Services.
Then return to Windows Update and click Check for updates. If the same error appears, reset the update cache manually.
Fix 4: Reset Windows Update Components Manually
This is one of the most effective ways to fix Windows Update error 0x80071160. It stops update services, renames the update cache folders, and lets Windows create fresh folders the next time it checks for updates.
Open Command Prompt as administrator, then run these commands one at a time:
Restart your computer after running the commands. Then open Settings > Update & Security > Windows Update and click Check for updates.
Renaming these folders does not delete your personal files. It only forces Windows to rebuild update-related cache data. Think of it as clearing out a messy workshop so the mechanic can finally find the wrench.
Fix 5: Run DISM to Repair the Windows Component Store
If the component store is damaged, Windows Update may fail repeatedly. The Deployment Image Servicing and Management tool, better known as DISM, can scan and repair the Windows image.
Open Command Prompt as administrator and run:
This process may take several minutes. It can look stuck at certain percentages, so give it time. Do not close the window just because the progress bar appears to be meditating.
When DISM finishes, restart your PC. If DISM reports that it repaired corruption, that is a good sign. Now run System File Checker.
Fix 6: Run System File Checker
System File Checker, or SFC, scans protected Windows system files and replaces damaged versions when possible. It works especially well after DISM repairs the component store.
Open Command Prompt as administrator and run:
Wait until the scan reaches 100%. You may see one of several results. If Windows says it found corrupt files and repaired them, restart and try Windows Update again. If it says it could not repair some files, run DISM again, restart, then run SFC once more.
Fix 7: Install the Update Manually
If Windows Update fails but you know the exact KB number, you can manually install the update using the Microsoft Update Catalog. This is useful when one specific cumulative update keeps failing.
- Find the KB number shown in Windows Update, such as KB5032189.
- Search for that KB number in the Microsoft Update Catalog.
- Choose the correct version for your system, such as Windows 10 22H2 x64.
- Download the .msu package.
- Run it and follow the prompts.
- Restart when asked.
Make sure you download the correct architecture. Most modern Windows 10 PCs use 64-bit Windows, but it is worth checking under Settings > System > About. Installing the wrong package will not help, and Windows will look at you like you brought a toaster to a printer repair shop.
Fix 8: Temporarily Disable Third-Party Antivirus or VPN Tools
Security software is important, but it can sometimes block update processes. If you use a third-party antivirus, firewall, VPN, or system optimizer, temporarily disable it and try Windows Update again.
Do this carefully. Disable protection only long enough to test the update, avoid suspicious websites during the test, and turn protection back on immediately afterward. If disabling the tool fixes the issue, update the security app itself or check its settings for Windows Update exceptions.
Fix 9: Try a Clean Boot
A clean boot starts Windows with minimal non-Microsoft services and startup programs. This can help identify whether background software is blocking updates.
- Press Windows + R.
- Type msconfig and press Enter.
- Go to the Services tab.
- Check Hide all Microsoft services.
- Click Disable all.
- Open Task Manager and disable unnecessary startup apps.
- Restart and try Windows Update again.
After testing, return to System Configuration and re-enable your normal services. A clean boot is not meant to be your permanent lifestyle. Your PC deserves its usual apps back, assuming they behave.
Fix 10: Use an In-Place Repair Upgrade
If nothing else works, an in-place repair upgrade can reinstall Windows system files while keeping your personal files and apps. This is one of the strongest repairs before considering a clean installation.
Use Microsoft’s Windows installation media, choose the option to upgrade the current PC, and select Keep personal files and apps. Read every screen carefully before clicking Install. This process can repair deep Windows corruption that blocks updates.
Because Windows 10 has reached the end of mainstream support, users should also consider whether the device is eligible for Windows 11 or enrolled in a valid Extended Security Updates path. If your Windows 10 PC is no longer receiving free security updates, fixing update errors may only solve part of the bigger maintenance problem.
How to Prevent Error 0x80071160 in the Future
Prevention is not glamorous, but neither is staring at a failed update screen at 1:00 a.m. Keep at least 15–20 GB of free space on your Windows drive when possible. Restart your PC regularly instead of letting it hibernate for weeks like a digital raccoon. Avoid interrupting updates once they begin. Keep drivers updated through your PC manufacturer or Windows Update. Remove old cleanup utilities that promise miracles but mostly delete things Windows was still using.
Also, create restore points before major changes. A restore point will not fix every update problem, but it gives you another recovery option if a driver or patch causes trouble.
Real-World Example: When the Cache Is the Villain
Imagine a Windows 10 laptop that downloads a cumulative update, reaches installation, fails with error 0x80071160, restarts, then fails again. The user runs the troubleshooter, but the error returns. After checking storage, there is enough space. The next step is resetting the Windows Update components. Once SoftwareDistribution and Catroot2 are renamed, Windows downloads a clean copy of the update and installs successfully.
That pattern is common because Windows Update can get trapped by a bad cached package. The PC keeps trying to reuse broken files, like a chef insisting the burnt pancakes are still “basically breakfast.” Clearing the cache forces Windows to start fresh.
Experience Notes: What Usually Works Best in Practice
After dealing with Windows update failures on home PCs, office desktops, and aging laptops, one lesson becomes clear: do not start with the most dramatic solution. Many people jump straight to reinstalling Windows, but error 0x80071160 often responds to simpler repairs. The best practical order is restart, troubleshooter, storage cleanup, service restart, update component reset, DISM, SFC, then manual installation.
In real troubleshooting, the reset of SoftwareDistribution and Catroot2 is often the turning point. When an update has failed several times, Windows may keep reusing files that were damaged during download or interrupted during staging. Renaming those folders gives the system a clean update workspace. It feels almost too simple, but it works often enough that it deserves a top spot in the repair sequence.
Another practical lesson: DISM before SFC is usually the smarter order when update corruption is suspected. SFC repairs individual system files, but it relies on a healthy repair source. If the component store is unhealthy, SFC may complain or fail halfway through. Running DISM first is like fixing the toolbox before asking the toolbox to fix the house.
Disk space also causes more update drama than users expect. A PC can appear to have “some” space left and still fail because Windows needs temporary working room. This is especially true on budget laptops with small internal storage. Clearing temporary files, removing old downloads, and uninstalling unused apps can turn a stubborn update into a normal one.
It is also worth being patient with repair commands. DISM may sit at one percentage for a long time. SFC may seem slow. Windows Update may pause during installation. Closing windows, forcing shutdowns, or repeatedly restarting can make the problem worse. Give each process time to finish before deciding it failed.
Finally, remember the bigger Windows 10 context. Since Windows 10 support has ended for standard consumer servicing, update behavior may depend on your version, eligibility, organization policy, or Extended Security Updates status. If your device is compatible with Windows 11, upgrading may be the cleaner long-term solution. If the PC must remain on Windows 10, keeping it backed up and properly enrolled for security updates matters more than ever.
Conclusion
Windows Update error 0x80071160 looks intimidating, but it usually points to repairable update problems: corrupted cache files, stopped services, damaged system files, component store issues, or low disk space. Start with the Windows Update Troubleshooter, clear storage, restart update services, and reset Windows Update components. If the error continues, use DISM and SFC, install the update manually, or perform an in-place repair upgrade.
The most important rule is to move step by step. Do not reinstall Windows before trying the practical fixes. Your computer may not be broken; it may just be tangled in its own update shoelaces. Untie them carefully, restart, and let Windows try again.
