Troubleshoot Windows Update Error Codes Safely
What to do first
Record the code and check in the order of troubleshooting, restart, capacity/communication.
This is a general troubleshooting guide, not an announcement of a current outage.
Affected products and symptoms
- Product
- Windows
- Versions and conditions
- Windows 11 / Windows 10
- Error codes and identifiers
- 0x800705b40x800F081F0x800737120x800704220x80070020
Symptoms
- Updates fail to download or install
- Stuck at the same percentage or a code appears
Causes and conditions
Possible causes include communication, capacity, pending restarts, corrupted files, and stopped services.
Before you start
- Back up important files
- Record error codes, KB numbers, and update history
Precautions
- Back up important files in advance
- Check the impact before deleting, initializing, or resetting the network.
Tools and official pages used in this guide
Review the official requirements, screen names, and limitations for this procedure.
Step-by-step instructions
Record the displayed error code, KB number, and failure time in [Settings] > [Windows Update] > [Update history]. In Windows 11, open [Settings] > [System] > [Troubleshoot] > [Other troubleshooters], or in Windows 10, open [Settings] > [Update & Security] > [Troubleshoot] > [Additional troubleshooters], and select Run under Windows Update. If you go to Get Help, complete the troubleshooter and record the reported problem and result.
Restart your PC normally even if the diagnosis is ``Fixed'' or ``Unspecified problem.'' Open [Settings] > [Windows Update], complete any pending [Restart now] first, and then select [Check for updates]. Check if the original KB progresses from "Downloading" to "Installing" or immediately stops at the same code.
Connect your laptop to AC power and make sure you aren't using a metered connection or a VPN that's easy to disconnect. Check the free space on your C: drive in Settings > System > Storage, and if the update screen indicates insufficient space, check cleanup recommendations. Safely remove any USB memory or external disk that is not the installation destination, and use only necessary devices such as the keyboard and mouse.
Official links for this step
- Windows Update troubleshooter
Review the official requirements, screen names, and limitations for this procedure.
- Windows Update troubleshooter
If the error is still 0x800F081F or 0x80073712 after retrying, suspect component store corruption and proceed to the DISM/SFC procedure on this site. Since 0x80070422 is related to the organization's policy or an invalid update service, give the code to the administrator without changing the service settings on the management PC. 0x80070020 may cause conflicts between files in use, so try again immediately after restarting. If the same code remains, save the update history screen and time and submit it to Microsoft Support.
Check the result
- The target KB is displayed as [Installed successfully] in [Update history]
- After rebooting, [Windows Update] displays [You are up to date] or the following specific instructions.
If the problem continues
- 0x800F081F/0x80073712 goes to DISM/SFC guide
- For 0x80070422 on an organization-managed PC, check the policy with the administrator without manually changing the service.
- If the same code continues, pass the KB, code, and time to Microsoft Support.
Scope of this guide
Troubleshooting guide — General diagnostic procedures. It does not describe a specific current incident.
Frequently asked questions
Do you turn off the power immediately when it stops at 0% or 100%?
Keep the network connection and AC power stable first. If there is no change after waiting a long time and Windows is operational, try troubleshooting after a normal reboot.
Would you like to manually reset the update service?
Don't make it the first step. Even after troubleshooting and rebooting it still fails and only with administrator guidance.
Official sources and dates
Source publication or resolution date: Not specified. Sources checked: 2026-09-05. The check date is not the date the problem first occurred. Interface labels can vary between versions and display languages.