Some links on this page are affiliate links: if you buy through them we may earn a commission, at no extra cost to you.
Windows Update error 0x8007371c is a real reported code, but Microsoft does not publish a definitive explanation for this exact value. It can occur during Windows servicing and may involve the component store, an update package, or cached update data. First verify the code and the failed KB number: it is easy to confuse with the documented codes 0x80073701, 0x80073712, and 0x8007371b.
Work through the steps below in order: restart and run the Windows Update troubleshooter, repair Windows with DISM and SFC, reset the update cache if needed, and then try the specific KB from Microsoft Update Catalog. Windows 10’s ordinary support ended on October 14, 2025, so also check whether your device has an eligible Extended Security Updates arrangement or should move to a supported operating system.
What does error 0x8007371c mean?
Microsoft’s current common Windows Update error reference does not include a dedicated entry for 0x8007371c. The exact code has appeared in historical Windows 10 reports, including a report involving the October 2020 cumulative update KB4577671 for version 1909 (Microsoft Q&A report).
Recommended Free Tools
That establishes that the code has been reported, not that it always has one cause. Because it appears during update servicing, a component-store or servicing problem is a reasonable possibility, but so are a package-specific issue, incomplete transaction, or damaged update cache. The code by itself cannot identify which one applies.
#1 Best Overall
Check that you have the exact code. Capitalization does not matter: 0x8007371C and 0x8007371c are the same hexadecimal value. The last characters do matter:
| Code | What Microsoft documents |
|---|---|
| 0x8007371c | No dedicated explanation in Microsoft’s current common-error reference. |
| 0x80073701 | Associated with a missing referenced assembly (ERROR_SXS_ASSEMBLY_MISSING) and component-store corruption. |
| 0x80073712 | Associated with component-store corruption. |
| 0x8007371b | ERROR_SXS_TRANSACTION_CLOSURE_INCOMPLETE: a servicing transaction is missing members. |
These neighboring codes are related to Windows servicing, but they are not interchangeable. Microsoft’s descriptions of them do not prove the cause of 0x8007371c.
Before you start: identify the failed update
- Open Start → Settings → Update & Security → Windows Update → View update history. Note the failed KB number and the displayed error.
- Press Win + R, enter
winver, and note your Windows version and build. - Check your system architecture—x64, x86, or ARM64—before downloading a package. You can find system details under Settings → System → About.
- Record when the failure happens: during download, installation, restart, or rollback. Also note whether the same KB fails when installed manually.
Back up important files before advanced repair. Restart once, check that the date and time are correct, free up space on the system drive, disconnect unnecessary USB devices, and temporarily disconnect a VPN. If you use third-party antivirus or endpoint software, consult its vendor’s Windows 10 guidance before disabling or removing it. Do not leave security software disabled; if you remove it for testing, make sure you can reinstall it and have any required licence information. Microsoft lists low disk space, VPN interference, security software, damaged files, and update-service problems among possible update-failure factors (Windows Update troubleshooting guidance).
Quick wins for a faster PC:
Clear out junk files and repair common Windows errorsFree Scan →Scan for outdated or missing drivers - takes under a minuteDriver Scan →Repair Windows errors before they cause bigger problemsFix Now →Fix 0x8007371c in order
1. Run the Windows Update troubleshooter
- Open Start → Settings → Update & Security → Troubleshoot.
- Select Additional troubleshooters, then Windows Update → Run the troubleshooter.
- Apply any suggested repair, restart the PC, and try Windows Update once.
The troubleshooter may not appear in exactly the same form on every Windows 10 build; some older components run automatically or are no longer available to launch manually. If the same error returns, move on rather than repeatedly running the troubleshooter. See Microsoft’s repair-troubleshooter information.
2. Repair the Windows image with DISM
Open Command Prompt as administrator: search for “Command Prompt” from Start, right-click it, choose Run as administrator, and approve the User Account Control prompt. Run:
Rank #2
- 15.6" diagonal, HD (1366 x 768), micro-edge, BrightView, 220 nits, 45% NTSC.
DISM.exe /Online /Cleanup-Image /RestoreHealthWait for the operation to finish; it may take a while. This Microsoft-recommended command checks and repairs the running Windows image. A message that the restore operation completed successfully is a good result, but it does not guarantee that the particular update will install. Microsoft’s update troubleshooting steps include DISM followed by SFC.
If DISM says it cannot find source files, do not repeat the same command indefinitely. Windows may need a matching repair source, or an in-place repair may be more appropriate. Component-store issues and unavailable repair sources are distinct servicing problems; see Microsoft’s servicing-error guidance.
3. Run System File Checker
In the same elevated Command Prompt, run:
sfc /scannowLet verification reach 100 percent, restart Windows, and retry the update. If SFC says it repaired files, the restart matters. If it says it could not repair some files, do not assume the update problem is resolved; proceed to the cache reset or review the logs and repair options below.
4. Reset the Windows Update cache
Try this if the troubleshooter and DISM/SFC have not helped. Do not do it while an update is actively installing. In an elevated Command Prompt, stop the related services:
net stop wuauserv
net stop bits
net stop cryptsvc
net stop msiserverRename the cache folders so Windows can create fresh ones while retaining a rollback copy:
Rank #3
- 10th Generation Intel Core i5-1035G1 processor
- 12GB system memory for full-power multitasking
- 256GB Solid State Drive
- 15.6" Micro-edge touchscreen display
ren C:WindowsSoftwareDistribution SoftwareDistribution.old
ren C:WindowsSystem32catroot2 Catroot2.oldStart the services again:
net start wuauserv
net start bits
net start cryptsvc
net start msiserverRestart the PC and check for updates. If a stop command says a service was not running, continue. If a service will not stop, restart Windows and try again from an elevated prompt. Renaming the folders resets cached update data; it does not repair a deeply damaged component store. Microsoft describes clearing the SoftwareDistribution update data as one troubleshooting measure (Microsoft guidance). Once updates work, you can remove the .old folders if you need the disk space.
5. Install the failed KB manually
A manual install can help distinguish a damaged download path from a broader servicing failure. Open the Microsoft Update Catalog, search for the exact KB number from update history, and select a package that matches your Windows version/build and architecture. Check its prerequisites and whether a newer update supersedes it before downloading the .msu file. Close unnecessary applications, run the downloaded installer, and restart if prompted.
The Catalog package still uses Windows servicing. If the component store, a prerequisite, or the servicing stack is the problem, the manual installer can fail too. Do not install a handful of unrelated or random KB files. Microsoft’s update-issue guidance covers checking package prerequisites and supersedence.
6. Check the servicing log if the failure persists
Advanced users or support staff can inspect C:WindowsLogsCBSCBS.log. Search around the failure time for 0x8007371c, 0x80073701, 0x80073712, CBS, CSI, “error,” or “failed.” CBS logs can be large and technical. If you ask for help, share only the relevant lines around the failure and avoid posting unrelated personal information. Do not delete or edit the log. Microsoft’s servicing guidance uses logs to investigate component-store and transaction failures.
7. Consider an in-place repair
Escalate to a Windows repair installation if DISM cannot repair the image, SFC repeatedly finds files it cannot fix, the same KB fails from both Windows Update and the Catalog, or multiple unrelated updates fail. An in-place repair reinstalls Windows system components and is designed to retain personal files and installed apps when the correct options are available. It is not risk-free, and you must verify the retention choice before proceeding.
Windows Errors? Fix Them Before They Spread
Repair common Windows errors and clear accumulated junk for a smoother, more stable PC - no reinstall needed.Free scan · no reinstallOutdated Drivers Are Slowing You Down
One free scan finds every outdated or missing driver and matches the right update for your exact hardware.Free scan · exact hardware matchRank #4
- Latitude 7480 Laptop 14"
- Intel Core i7 6th Gen i7-6600U -Core Processor 2.6GHz (3.4GHz With Turbo Boost)
- 256 GB SSD Hard Drive & 16GB Memory
- 1920x1080 FHD resolution Non-Touch with Webcam and an integrated graphics chip
- Wireless Wifi & Bluetooth
- Back up important files and confirm Windows activation status.
- Record installed applications and make sure you have any required encryption-recovery information.
- Use installation media matching the installed Windows edition, language, and architecture.
- While signed in to Windows, start
setup.exefrom that media; booting from it is generally not the route for a repair that retains apps and files. - Choose the option to keep personal files and applications only if Setup offers it. If it is unavailable, stop and find out why before continuing.
If an in-place repair is not suitable, consider System Restore, a known-good image backup, Reset this PC, or a clean installation. Back up first; the retention and app outcomes differ between these options.
Choose the next step by symptom
| What you see | What to try next |
|---|---|
| Only one KB fails | Confirm the KB, check prerequisites and supersedence, then try the matching Catalog package. |
| Several updates fail with similar 0x800737xx codes | Run DISM, then SFC; review CBS.log if the problem remains. |
| Windows repeatedly downloads the same package | Reset the SoftwareDistribution and catroot2 caches. |
| DISM cannot find source files | Use a matching Windows repair source or consider an in-place repair; do not keep repeating the same command. |
| The update fails after installing third-party antivirus or a VPN | Check the vendor’s guidance and test carefully; do not leave protection disabled. |
| Installation rolls back after reboot | Check servicing and setup logs rather than repeatedly forcing the same update. |
| Catalog installation also fails, or SFC cannot repair files | Treat it as a possible broader servicing problem and consider repair installation. |
| The code may be 0x80073701, 0x80073712, or 0x8007371b | Verify it in View update history; use guidance for the code actually shown. |
Is it worth repairing Windows 10 in 2026?
Microsoft ended ordinary Windows 10 support on October 14, 2025. The PC will continue to function, but ordinary free Windows Update security fixes and technical support ended after that date. Some eligible devices may have a separate Extended Security Updates (ESU) arrangement; check whether the specific device and account are eligible rather than assuming updates continue. Microsoft’s Windows 10 security-update notice and Windows lifecycle FAQ explain the lifecycle context.
Fixing local servicing corruption can still matter on an eligible ESU device or when you need to restore a working installation, but it does not restore ordinary free Windows 10 security updates. Check whether the PC can move to Windows 11 and whether its hardware and applications are suitable. If not, weigh an eligible security-update path against replacing the device. Microsoft 365 application updates follow separate lifecycle rules and are not the same as Windows operating-system security updates.
Avoid registry cleaners, unofficial “Windows Update fixer” downloads, and generic driver-updater utilities. They are not needed for the documented repair sequence and may add risk. Never manually delete files from C:WindowsWinSxS; Windows servicing tools manage that component store.
Frequently Asked Questions
Is error 0x8007371c dangerous?
The code itself is not a diagnosis of malware or hardware failure. It indicates an update did not complete; verify the exact code and investigate the failed update.
Best Value
Will DISM or SFC delete my personal files?
The commands shown are intended to repair Windows image and system files, not personal documents. Backing up important files is still prudent before troubleshooting or attempting a repair installation.
Can I delete the SoftwareDistribution folder?
Do not delete it while updates are running. The safer cache-reset method is to stop the relevant services and rename the folder, as described above; Windows recreates update data.
Why does installing the KB from the Catalog fail too?
A Catalog package bypasses the normal download path, but still depends on Windows servicing. A prerequisite, pending transaction, or component-store problem can make manual installation fail as well.
Do these 3 things before closing this tab:
1Clear out junk files and repair common Windows errors2Fix the driver behind crashes, sound loss and screen glitches3Repair Windows errors before they cause bigger problemsIs Windows 10 still supported?
Ordinary Windows 10 support ended on October 14, 2025. Eligible devices may have a separate Extended Security Updates arrangement; check your device’s eligibility.
Quick Recap
Product prices and availability are accurate as of the date/time indicated and are subject to change. Any price and availability information displayed on Amazon at the time of purchase will apply.
