Windows 11 update error: what the code means and how to fix it

Published By helps.wiki editorial team

A Windows 11 update error means Windows Update, or the install step after it, failed and left a hex code such as 0x8007000d or 0xC1900101. Start with a restart and the built-in Windows Update troubleshooter, then free disk space, check drivers and services, and reset the update components if the error stays.

Applies to:Windows 11all versionsWindows 10most steps also apply
On this page

What it means

"Windows 11 update error" is not one problem. It is the name people give to any failed update that ends in Something went wrong or Install error with a code starting 0x. The cause differs from code to code, but the first digits usually tell you which part of Windows gave up.

Codes starting 0x8024 come from the Windows Update agent itself (download, data store, update handler). Codes starting 0x8007 are ordinary Windows errors passed through, for example 0x80070005 (access denied) or 0x80070422 (a service is not running). Codes starting 0x800f come from component servicing, and 0xC1900 codes come from the setup step of a feature update.

The fixes below go from the quickest and safest to the most invasive. Work through them in order and test Windows Update after each one. If your code has its own page, use it: 0x80070005, 0x800f0922, 0x80073701, 0x800f0831, 0x80244007.

Symptoms and causes

You are likely dealing with this problem if:

  • Settings > Windows Update shows "Install error" with a code, or "Failed to install".
  • The update sits at 0%, at 100%, or somewhere between 51% and 99%.
  • Windows undoes changes after a restart.
  • Windows Update says "Checking for updates" forever, or cannot find the update.

The usual causes, most common first:

Corrupt update cache or system files
A damaged SoftwareDistribution folder or damaged Windows files are the most common reason. Typical codes: 0x8007000d, 0x80070057, 0x80080005, 0x800F081F, 0x80073712.
Not enough disk space
A nearly full system drive stops updates. Some third-party sources also blame a full System Reserved/EFI partition for 0x800f0922 and 0x8007000E, but Microsoft's page only mentions low disk space.
Faulty or incompatible drivers
Network and display drivers are the usual suspects, especially for 0xC1900101.
Update services stopped or the update database in a bad state
Seen with 0x80070422, 0x80248014 and 0x80240034.
Security software, VPN or proxy interference
Antivirus or backup tools can lock files (0x80070020), and VPNs or proxies can break the connection (0x800705b4, 0x80070005, 0x800f0922). A proxy set only at user level and not in WinHTTP can also block updates. Proxies must allow HTTP RANGE requests (0x80d05001).
Wrong date and time, or no administrator rights
Both can make an update fail early.
Network or firewall blocking Microsoft's update servers
Microsoft lists *.windowsupdate.com, *.update.microsoft.com, *.delivery.mp.microsoft.com and *.dl.delivery.mp.microsoft.com as endpoints that must be reachable. The Windows Defender Firewall service must also be running (0x800706D9).
Work or school policy
On managed devices, WSUS or Group Policy conflicts, or updates not approved on the WSUS server, can block installation.
Temporary server load
Code 0x8024402d (WU_E_PT_LOAD_SHEDDING) means the update server was busy. Nothing is wrong with your PC and the device retries on its own.

How to fix it

Work through these in order. They start with the quickest, safest checks and move to deeper repairs; stop as soon as the problem is gone.

1.Restart and run the Windows Update troubleshooter

Easy

A restart clears a half-finished install, and the troubleshooter fixes common service and cache problems automatically.

  1. Restart the PC, then open Settings > Windows Update and select Check for updates again.
  2. If it fails again, open Settings > System > Troubleshoot > Other troubleshooters.
  3. Next to Windows Update, select Run and follow the prompts. The Get Help app also offers a Windows Update troubleshooter.
  4. Restart once more if the troubleshooter reports it changed something, then check for updates.

2.Check power, connection, account, and date and time

Easy

Simple conditions such as a wrong clock, missing admin rights or a flaky connection cause failures that look serious.

  1. Keep the PC plugged in and on a working internet connection.
  2. Unplug USB drives, docks and other peripherals you do not need.
  3. Make sure you are signed in with an administrator account.
  4. Open Settings > Time & language > Date & time, turn on the automatic time and time zone options, and select Sync now.

3.Free up disk space

Easy

Updates need room to download and unpack. For an operating system upgrade Microsoft states at least 16 GB free (32-bit) or 20 GB free (64-bit). Ordinary monthly updates need less, but a nearly full drive still causes trouble.

  1. Open Settings > System > Storage and check how much space is free on the system drive.
  2. Remove or move files and apps you no longer need until there is plenty of free space, then retry the update.

4.Update or reinstall network and display drivers

Moderate

Buggy drivers, mainly network and display, are a known cause of 0xC1900101.

  1. Get the latest network and display drivers from your PC or hardware manufacturer's website and install them.
  2. If the code is 0xC1900101, open Device Manager, uninstall the network or display driver, restart so Windows reinstalls it, and retry.
  3. If it still fails, try the update after a clean boot (starting Windows with only essential services) to rule out software conflicts. Follow Microsoft's clean boot instructions for your version.

5.Make sure the Windows Update service is running

Easy

Microsoft lists a stopped or disabled service for codes such as 0x80070422 and 0x80248014. If the update hangs at the scan stage, the Update Orchestrator service should also be running.

  1. Press WinR, type services.msc and press Enter.
  2. Double-click Windows Update, set Startup type to Automatic, and select Start if the service is stopped.
  3. Check that Update Orchestrator Service is running too, and that Windows Defender Firewall is running (stopping it is unsupported and gives 0x800706D9).
  4. Retry the update.

6.Test without a VPN and third-party security software

ModerateChanges settings

Microsoft suggests removing third-party security software temporarily if the error persists. This is most relevant to 0x800705b4, 0x80070005, 0x80070020 and 0x800f0922.

Before you start: Only do this on a trusted network and for as long as the test takes. Turn the security software back on afterwards. Do not disable Windows Security or the Windows firewall for this test.

  1. Disconnect from any VPN.
  2. Temporarily turn off your third-party antivirus or security suite, using its own settings.
  3. Run Check for updates again.
  4. Turn the security software back on straight away, whether or not the update worked.

7.Reset the Windows Update components

Moderate

This renames the update cache folders so Windows rebuilds them from scratch. Microsoft recommends it, and the folders are recreated automatically.

  1. Open Command Prompt as administrator (search for it, then choose Run as administrator).
  2. Run these commands one after another:
    Command Promptrun as administrator
    net stop bits
net stop wuauserv
ren %systemroot%\softwaredistribution softwaredistribution.bak
ren %systemroot%\system32\catroot2 catroot2.bak
net start bits
net start wuauserv
  3. Restart the PC and check for updates again.

8.Repair the system image and system files

Moderate

Microsoft recommends this for 0x80070057, 0x80080005, 0x800F081F and 0x80073712, and it helps with damaged files in general.

  1. In an administrator Command Prompt, run DISM first and wait for it to finish:
    Command Promptrun as administrator
    DISM.exe /Online /Cleanup-image /Restorehealth
  2. Then run System File Checker:
    Command Promptrun as administrator
    sfc /scannow
  3. Restart and retry the update.

9.Check the disk for errors

AdvancedChanges settings

File system errors on the system drive can make updates fail, and this check can find and repair them.

Before you start: Back up important files first. A disk check that repairs errors can, in rare cases, change or lose damaged data.

  1. In an administrator Command Prompt, run the command and confirm when asked to schedule it for the next restart:
    Command Promptrun as administrator
    chkdsk /f C:
  2. Restart the PC and let the check finish before signing in, then retry the update.

10.Fix the proxy settings (mostly managed or work PCs)

AdvancedChanges settings

If a proxy is configured only for the user (Internet Explorer settings) and not in WinHTTP, Windows Update cannot use it.

Before you start: Use this only if you know your PC is supposed to use a proxy. Check with your IT department first, because the wrong proxy breaks internet access for system services.

  1. In an administrator Command Prompt, copy the user-level proxy into WinHTTP:
    Command Promptrun as administrator
    netsh winhttp import proxy source=ie
  2. Or set it by hand, replacing the placeholders with your proxy's details:
    Command Promptrun as administrator
    netsh winhttp set proxy ProxyServerName:PortNumber
  3. Make sure the proxy and firewall allow the Microsoft update addresses listed in the causes above, and that the proxy allows HTTP RANGE requests. On a work PC this is a task for your network administrator.

11.Repair or reinstall Windows as a last resort

AdvancedBack up first

If every step above fails, the Windows installation itself may be damaged. Microsoft's support page points to its installation tool for a repair or clean install.

Before you start: Back up your files before you begin. A clean install erases the drive and its apps, and only an in-place repair is meant to keep your files.

  1. Copy your documents, photos and other personal files to an external drive or cloud storage.
  2. Follow the reinstall steps on Microsoft's Troubleshoot problems updating Windows page, using Microsoft's own installation tool.

Check that it worked

  • Settings > Windows Update shows "You're up to date" or the pending updates install without an error code.
  • After the restart, Windows does not roll back the changes.
  • Update history lists the update as successfully installed.

If it still fails

  • Write down the exact code and search for it on Microsoft's Windows Update error code list, which describes what each code means. Codes with their own page on this site are linked in the introduction.
  • If the PC belongs to your workplace or school, contact your IT department. WSUS or Group Policy settings can only be changed by them.
  • If the code is 0x8024402d, wait and try again later, since it only means the server was busy.
  • Contact Microsoft Support through the Get Help app or the Microsoft Support site, and have the error code and the update name ready.

Questions

Is it safe to rename the SoftwareDistribution folder?

Yes. Microsoft's own troubleshooting page recommends it, and Windows rebuilds the folder the next time it checks for updates.

Why does the same code get different advice on different pages?

Microsoft's tables cover some codes only for Windows 10 or Windows 11, and many codes have several possible causes. Work through the steps in order rather than looking for one exact match.

Sources

  1. Troubleshoot problems updating WindowsOfficial · Microsoft Support
  2. Windows Update error code list by componentOfficial · Microsoft Learn
  3. Windows Update issues troubleshootingOfficial · Microsoft Learn

Browse