Windows Update Fails Due to Incorrect Settings: Complete Guide

In this guide I explain, in a close language and step by step, everything you should check in Windows 10 and Windows 11: since quick checks (reboot, connection, space) to more advanced techniques such as SFC/DISM, clearing caches (SoftwareDistribution and catroot2), resetting system components, uninstalling problematic patches, or manually installing updates. We also collect the most common error codes and what to do with each one, plus recent bugs in Windows 11 24H2.

What types of updates are there and why they can fail?

Before you touch anything, it's a good idea to understand the context. Windows delivers two families of patches: cumulative updates (they fix security, stability and bugs and usually arrive periodically, often twice a month) and the feature updates (version jumps with major new features). Both arrive by Windows Update and they are downloaded/installed automatically, although you can search for them manually.

If Windows Update isn't responding, we have alternatives. You can download specific patches from the Microsoft Update Catalog (ideal when a specific KB fails) or use the media creation tool to force the latest version of Windows 10 or the Windows 11 Update Assistant. These methods, when used correctly, can unblock many issues when the Internet is out of reach or when Update stops working.

Why does the error appear? They usually influence Corrupted update files, low free space, driver conflicts, or stopped services. An unstable connection, overly aggressive third-party antivirus, incorrectly modified registry keys or Unmet requirements in Windows 11 (TPM 2.0, etc.).

Essential checks before anything else

1. Restart the PC. It sounds like a cliché, but a hard reboot kills hung processes and restarts services. It's not the same as power cycling with start Quick.
2. Check the Internet. In Windows 11: Start > Settings > System > Network & Internet. In Windows 10: Start > Settings > Network & Internet > Wi-Fi. Check network status and reconnect to Wi-Fi/Ethernet if necessary. You can test connectivity with ping and clear DNS with ipconfig /flushdns.
3. Sufficient disk space. Windows requires at least 16 GB (32 bit) or 20 GB (64 bit) to update. On computers with very small disks, a usb drive Support. Use Disk Cleanup and delete temporary files to avoid backups.
4. Wait and disconnect peripheralsIf the problem is with the servers, sometimes just waiting is enough. Also, disconnect Non-essential USBs and if you see unknown devices in the Device administrator, temporarily uninstall them to rule out conflicts.
5. Avoid metered connections. On networks marked as metered, Windows Update may slow down. Review that setting or learn how to limit bandwidth to downloads complete.

Use the Windows Update Troubleshooter

Windows comes with a specific tool that detects and corrects inconsistencies: pending reboots, BITS, stopped services, connectivity, stuck caches, etc. This is the first major filter that should be run.

• Windows 11: Start > Settings > System > Solve problems > Other troubleshooters > Windows Update > Run. When finished, restart the PC and returns to Search for updates.
• Windows 10: Start > Settings > Update and security > Solve problems > Additional troubleshooters > Windows Update > Run the solver. Repeat the update check after the reboot.

If it doesn't fix everything, you can run it more than once to hunt for residual errors. In complicated scenarios, there is also the Microsoft Advanced Solver downloadable for Windows Update.

Restart services and clear Windows Update caches

Sometimes Update does not start because of a hung service or because corrupted cache files. Let's start with services:

Graphic option: press Windows + R, writes services.msc, accept and search Windows Update. Right click > Restart. In Properties, leave the Startup type to Automatic and apply changes.

With Symbol of the system (Admin): Open cmd as administrator and execute, one by one:

net stop bits
net stop wuauserv
net stop appidsvc
net stop cryptsvc

Now clear the caches. Don't delete the folders, only its content:

C:\Windows\SoftwareDistribution
C:\Windows\System32\catroot2

Restart the services:

net start wuauserv
net start appidsvc
net start cryptsvc

If the problem persists, you can reset keys and components Windows Update with the tool Reset Windows Update (wureset.exe). Run it as administrator and choose to restore components; it usually unlocks hard settings.

Check system and disk integrity (SFC, DISM, and CHKDSK)

When there is damaged system files, Update crashes. Run CFS and DISM in this order (in cmd as admin):

sfc /scannow
DISM /Online /Cleanup-Image /CheckHealth
DISM /Online /Cleanup-Image /ScanHealth
DISM /Online /Cleanup-Image /RestoreHealth

SFC repairs protected files and DISM fixes the Windows image. Reboot when finished and try Update again.

To check the disk (bad sectors, metadata):

chkdsk C: /F /R

Change C: by the Windows drive if applicable. If CHKDSK detects damage, it will attempt to repair it and will mark bad sectors if not possible. A high number of bad sectors suggests change the disk.

Remember: SFC/DISM They deal with the logical integrity of the system; CHKDSK focuses on the storage physical. They are complementary and highly recommended when Update fails to install.

Antivirus and software conflicts, drivers and hardware

A classic: third-party antivirus interfering with Windows Update. Temporarily disable it (or uninstall it) and try again leaving it alone Microsoft DefenderIf this works, contact your antivirus manufacturer or wait for a compatible update.

Attention to specific components: files aksfridge.sys or aksdf.sys, Storage Spaces in Parity and drivers with copy protection can cause errors. In Windows 11 24H2, Microsoft blocked the update on computers with sprotect.sys (Hold ID 56318982) until conflicts are resolved.

In stubborn cases, update the BIOS / UEFI If you know how to do it and avoid tools that modify Windows (optimizers, aggressive “cleaners” or third-party firewalls). A “Smart App Control” that is too strict can also block apps of the system; review it if you suspect false positives.

System Restore, uninstall patches and requirements (Windows 11 special)

If everything was fine before and suddenly Update fails, pull System Restore. Find “Create Restore Point” > tab System protection > System Restore > choose a previous point (preferably the oldest one after the last stable update) and confirm. It doesn't delete your files.

You can also uninstall problematic updates: Settings > Update & security (or Windows Update in Windows 11) > Update history > Uninstall updates. Locate the KB that is causing trouble (for example, KB5051987 in Explorer problems) and delete it. Restart and check.

Windows 11 Requirements: If you upgraded by skipping the minimums (TPM 2.0, 4GB RAM, 64GB storage, DirectX 12 and WDDM 2.0 compatible GPU), you may encounter errors in Update. Enable TPM on BIOS if it is disabled and you are considering upgrading hardware.

Also check that Windows is activated successfully, as errors like 0x80240023 (license not accepted) may appear. If nothing works, consider Reset this PC (Settings > Update & security > Recovery > Get started). Back up first.

Manually install updates and alternatives without Update

When Update insists on failing, install the KB manually: enter the Microsoft Update Catalog, search by KB number or version (e.g., 22H2/23H2/24H2) and download the package that matches your architecture (x64/ARM). After installing, it usually unclog the normal channel from Windows Update.

For full version jumps, use the media creation tool from Microsoft (Windows 10) or the Installation wizard (Windows 11) and, if you prefer, create a bootable USB to make a repair facility keeping files and apps.

When space is short or the network is slow, these ways out of Update They are a miracle cure. Make sure you choose the exact package for your system (version/edition/architecture) to avoid incompatibilities.

Most common Windows Update errors and how to address them

The list is long, but I'll leave you with a quick diagnostic guide with probable cause and suggested action for each code:

0x80072EE2: : Communication problems with servers. Check firewall, file hosts, proxy/VPN, set Update servers as “trusted zone” in IE, try the Catalogue, run ipconfig /flushdns and, if applicable, adjust MTU on the router.

0 x 80070490: : Corrupt package or required file not found. Clear caches (SoftwareDistribution/catroot2), use the solver and DISM/SFC.

0 x 80070422: : Services disabled. Put Windows Update on Automatic and restart it.

0x800700d8: This could be a postponed update or a software conflict. Review policies, disable antivirus, and clear caches.

0x8007010b (ERROR_DIRECTORY): Invalid or nonexistent directory. Check temporary paths and permissions; clear caches.

0 x 80240035 (WU_E_UPDATE_NOT_PROCESSED): Generic processing error. Solver, services, and DISM.

0 x 80246013: associated with Update and Microsoft Store, typically connection. Check network and proxy/VPN.

0x8007045b (ERROR_SHUTDOWN_IN_PROGRESS): Installation stuck with reboot pending. Run the solver to unblock.

0x800f0845: very old and elusive, sometimes it is fixed with a reboot and retry; if not, DISM/SFC.

0x8024401f and 0x8024402f: Corrupt cache, proxy/VPN, or third-party software. Clear caches, disable proxy/VPN, and try again.

8020002E: Update component not loading. Check for active essential services and software conflicts.

0x8007043c: necessary services not running, common in Safe Mode. Boot normally and try again.

0x80240FFF: Update services with problems. Restart services and reset components.

0 x 80073712: Corrupt internal files. DISM/SFC and, if persists, repair installation.

0x8e5e03fa: CBS (Component Store) corruption. Strong DISM and cache flush.

800F0A13: Corrupted/moved system files. DISM/SFC usually fixes this.

8024A000 (WU_E_AU_NOSERVICE): Update service malfunctioning. Restart and restore components.

0x800f081f: DLLs are missing in WinSxS. Wait and retry, or DISM with source if necessary.

0x8007371c (ERROR_SMI_PRIMITIVE_INSTALLER_FAILED): Clears Update cache and runs resolver.

0xa0000400: typical in feature updates. Releases 20-30 GB, restart the network and close apps that use the network.

0xc0000017: “no memory available” for areas marked as bad. In cmd (admin):

bcdedit /enum
bcdedit /deletevalue {badmemory} badmemorylist

Reboot and retry.

0 x 80240023: License terms not accepted. Review activation, re-enter key if applicable and run the solver.

0xc004f075 (SL_E_SERVICE_STOPPING): License server stopping. Update/Activation resolvers and slmgr.vbs.

0 x 80070541 (ERROR_INVALID_GROUP_ATTRIBUTES): This is usually a patch issue. Wait for a fix from Microsoft or install it manually.

0xc19001e1 (MOSETUP_E_PROCESS_SUSPENDED): Essential process paused. Disable antivirus, disconnect external hardware, free up space or use the media creation tool.

C80003F3: Unknown error. Troubleshooter and clearing caches are usually sufficient.

0xca020007: usually indicates corrupted system files. Run SFC/DISM and if not, repair installation with ISO.

0 x 80240061: : software conflict. Solver, clean SoftwareDistribution/catroot2 and attempt manual installation.

0 x 80070659: not very descriptive. Try Solver, manual installation, and if it's missing, install . NET Framework 4.

80040005 – 0x20007 (SafeOS phase, drivers): verify requirements, install drivers from Windows Update, update BIOS if necessary.

0 x 80246001: : No download URL found. Download the KB at the Catalogue and apply manually.

0 x 80248014: Update files are missing/corrupted. Run:

DISM.exe /Online /Cleanup-Image /RestoreHealth /Source:C:\RepairSource\Windows /LimitAccess

Reboot and retry Update.

0x800706b5: Windows fails to complete the installation. Restart and try again; if the problem persists, use the Troubleshooter.

0 x 80070643 (KB5034441/WinRE): Out of space on the recovery partition. Use the script Microsoft official to resize Win or wait for it to be corrected.

0x8024A003: Update client is outdated or corrupt. Repeat DISM with /Source as above.

Other common codes (applies reboot, manual installation from Catalog and, if applicable, DISM with /Source): 0x802200B, 0x800f0905, 0xc8000247, 0x80070437, 0x8007012a, 0x80070763, 0x80040154, 0x8024a203, 0x80096004, 0x800f0990, 0x80248007, 0x800f020b, 0x80300024.

Recent issues in Windows 11 24H2 and how to fix them

The cumulative and 24H2 have brought a tail: Mouse pointer “disappearing” in Chromium apps (Chrome/Edge), a 8,63 GB Update cache that was not removed, and the patch KB5051987 “breaking” Explorer (does not open or hangs while explorer.exe is running in the background). There have also been blockages in 98-99% installation and blue screens with codes like 0x800f0993, 0x800F081F, 0x80070032, 0xC004F211.

Connectivity: After installing certain cumulative updates, some reported Broken Bluetooth (headphones that no longer pair) and USB cameras integrated into monitors that “cannot start” despite having a driver. In parallel, Ctrl + Alt + Del or Task Manager They stopped working in specific situations and smart app control crashed system components (including WSL).

What to do: Uninstall the problematic KB (e.g. KB5051987), run the Solver, clear caches and if nothing works, pause updates and wait for the fix from Microsoft. On devices with sprotect.sys, there's a update lock (ID 56318982) until the manufacturer fixes the driver. If the huge cache doesn't clear, consider a clean installation When you can.

Remember that Windows 10 has free support ending on 14th October 2025; in the coming months there will be a mass migration to Windows 11Consider preparing your equipment (drivers, TPM, backups) to reduce setbacks.