Short description:<\/b> A practical guide on how to fix Windows Update error 0xC1900202 in Windows 10 and Windows 11: hardware compatibility checks, free space cleanup, Windows Update cache reset, System Reserved or EFI partition issues, system file repair, and upgrading through an official ISO image.<\/p>\n
Windows Update error 0xC1900202 usually appears during a major feature update or an upgrade to a newer version of Windows. The process may reach 70%, 80%, 90%, or even almost 100%, then suddenly fail and roll the system back to the previous state. Instead of a successful update, you see a message such as \u201cInstallation failed,\u201d \u201cWe couldn\u2019t install this update,\u201d or a similar Windows Update warning.<\/p>\n
At first glance, it looks like Windows Update is simply broken. The computer downloads gigabytes of update files, prepares the installation, restarts several times, wastes your time, and then returns to the same version of Windows. In some cases, Windows keeps trying again automatically, fails again, and repeats the same loop.<\/p>\n
Error code 0xC1900202 is especially common when upgrading from Windows 10 to Windows 11 or when installing a large Windows 10 feature update. The good news is that this error is usually caused by specific and understandable reasons: unsupported hardware, not enough free space, a small EFI or System Reserved partition, damaged update cache, or corrupted system components.<\/p>\n
Error 0xC1900202 is often not a sign that Windows Update itself is completely damaged. In many cases, Windows refuses to finish the update because the computer does not meet upgrade requirements or because the system does not have enough resources to complete the installation safely.<\/p>\n
For Windows 11, this is very common. TPM 2.0, Secure Boot, a supported processor, enough RAM, a 64-bit system, and sufficient disk space are important requirements. If one of these requirements is missing, the upgrade may fail with code 0xC1900202.<\/p>\n
A more basic reason is a full system drive. Large Windows updates need temporary space to unpack files, prepare the new system image, store rollback data, and install new components. If the C: drive has only a few gigabytes free, the update may start normally but fail near the end.<\/p>\n
Another common cause is a small System Reserved or EFI partition. These partitions store boot files and service information required during the update. On older computers, especially systems upgraded from earlier Windows versions, this partition may be only 50\u2013100 MB. That can be too small for modern feature updates.<\/p>\n
In practice, many users try to upgrade an older laptop to Windows 11 without checking hardware requirements first. Windows downloads the update, starts installation, restarts, and then silently rolls everything back. The result is error 0xC1900202 in the update history and no useful explanation on the screen.<\/p>\n
If you need a quick solution, start with the simplest actions first. In many cases, the combination of disk cleanup, Windows Update cache reset, and ISO-based upgrade solves the problem without deeper repair work.<\/p>\n
For many home and office computers, this is enough. If the update still fails, move through the full step-by-step process below.<\/p>\n
Open Settings \u2192 System \u2192 About<\/b> and check:<\/p>\n Then open Settings \u2192 System \u2192 Storage<\/b> and check how much free space is available on drive C:. For a major update, 20 GB is the bare minimum. In real use, 25\u201330 GB or more is much safer.<\/p>\n If you are upgrading to Windows 11 and the processor is unsupported, TPM 2.0 is missing, Secure Boot is disabled, or the system has too little RAM, error 0xC1900202 may be caused by hardware limitations. In that case, software repairs alone may not solve the issue.<\/li>\n Start with built-in cleanup tools:<\/p>\n After cleanup, reboot the computer and check free space again. If less than 15\u201320 GB is still available, Windows Update may continue to fail.<\/li>\n Press Win + X<\/b> and open Windows Terminal (Admin)<\/b> or Command Prompt (Admin)<\/b>.<\/p>\n Run:<\/p>\n sfc \/scannow<\/b><\/p>\n Wait until the scan finishes. It may take 10\u201320 minutes.<\/p>\n Then run:<\/p>\n DISM.exe \/Online \/Cleanup-image \/Scanhealth<\/b><\/p>\n DISM.exe \/Online \/Cleanup-image \/Restorehealth<\/b><\/p>\n SFC checks and repairs protected Windows system files. DISM repairs the component store used by Windows Update and system servicing. If damaged components were blocking the update, these commands may allow the upgrade to continue normally.<\/li>\n Open Command Prompt as administrator and run these commands one by one:<\/p>\n net stop wuauserv<\/b><\/p>\n net stop cryptSvc<\/b><\/p>\n net stop bits<\/b><\/p>\n net stop msiserver<\/b><\/p>\n Rename the update cache folders:<\/p>\n ren C:\\Windows\\SoftwareDistribution SoftwareDistribution.old<\/b><\/p>\n ren C:\\Windows\\System32\\catroot2 Catroot2.old<\/b><\/p>\n Start the services again:<\/p>\n net start wuauserv<\/b><\/p>\n net start cryptSvc<\/b><\/p>\n net start bits<\/b><\/p>\n net start msiserver<\/b><\/p>\n After this, restart the computer and try Windows Update again. Windows will recreate the SoftwareDistribution and Catroot2 folders automatically.<\/li>\n Open each service and check its startup type. For most systems, Automatic<\/b> or Automatic (Delayed Start)<\/b> is appropriate. If a service is stopped, start it manually.<\/p>\n This step is especially useful on computers where Windows Update was previously disabled with registry tweaks, privacy tools, optimization utilities, or corporate policies.<\/li>\n Typical signs include repeated update rollback, failure near the final installation stage, and no clear explanation in the Windows Update interface.<\/p>\n You can check partitions through Disk Management<\/b>:<\/p>\n If the partition is very small, for example 50\u2013100 MB, a feature update may fail because Windows cannot write the required boot files. Expanding this partition can solve the problem, but this operation must be done carefully.<\/p>\n Use a reliable partition manager only if you understand what you are changing. Before modifying system partitions, create a full backup of important data. Do not delete EFI, Recovery, or System Reserved partitions. Removing the wrong partition can make Windows unbootable.<\/li>\n This method often bypasses Windows Update cache problems and update assistant failures. It is one of the best ways to fix persistent 0xC1900202 errors when the hardware is compatible.<\/li>\n Before starting the upgrade, disconnect:<\/p>\n Leave only the keyboard, mouse, main monitor, and network connection if needed. This reduces the chance of driver conflicts during installation.<\/li>\n Before a major upgrade, temporarily disable third-party security tools or uninstall them if they have a history of blocking updates. After the upgrade finishes successfully, reinstall or enable them again.<\/p>\n Do not disable security software permanently. This is only a temporary troubleshooting step for the update process.<\/li>\n If Windows Update no longer shows error 0xC1900202, the issue is resolved. This is also a good moment to create a fresh backup or system image.<\/li>\n<\/ol>\n Deleting \u201cunused\u201d system partitions.<\/b><\/p>\n Some users open Disk Management, see a small EFI or System Reserved partition, and assume it is safe to delete. After that, Windows may stop booting completely. These partitions are not junk. Do not remove them unless you fully understand their purpose.<\/p>\n Hard power-off during update installation.<\/b><\/p>\n If Windows is configuring updates, do not turn off the computer unless it is clearly frozen for a very long time. Interrupting an update can cause boot loops, rollback failures, or file system corruption.<\/p>\n Clearing SoftwareDistribution without stopping services.<\/b><\/p>\n Deleting update cache files while Windows Update services are running can fail or damage the cache further. Always stop the required services first.<\/p>\n Ignoring Windows 11 hardware requirements.<\/b><\/p>\n If the computer has no TPM 2.0, unsupported CPU, disabled Secure Boot, or too little RAM, repeated upgrade attempts may keep failing. Check the requirements before wasting time on repair commands.<\/p>\n Using aggressive \u201cdebloat\u201d and optimizer tools.<\/b><\/p>\n Some tools disable update services, remove components, modify policies, or block background services. Later, when the user tries to update Windows, the system fails with confusing errors.<\/p>\n Trying to fix everything at once.<\/b><\/p>\n Changing services, partitions, drivers, registry settings, and update files all at the same time makes troubleshooting harder. Work step by step and restart after major changes.<\/p>\n 1. What does Windows Update error 0xC1900202 mean?<\/b><\/p>\n Error 0xC1900202 usually means Windows cannot complete a feature update or upgrade because of system requirements, insufficient disk space, a small EFI or System Reserved partition, damaged update files, or incompatible hardware.<\/p>\n 2. How do I fix error 0xC1900202 in Windows 11?<\/b><\/p>\n Check TPM 2.0, Secure Boot, CPU support, RAM, and free disk space. Then reset the Windows Update cache, repair system files with SFC and DISM, and try upgrading through an official Windows 11 ISO if normal Windows Update fails.<\/p>\n 3. Is error 0xC1900202 always caused by unsupported hardware?<\/b><\/p>\n No. Unsupported hardware is common during Windows 11 upgrades, but the same error can also be caused by low disk space, corrupted update cache, damaged system files, or a small boot partition.<\/p>\n 4. Can low disk space cause Windows Update error 0xC1900202?<\/b><\/p>\n Yes. Large Windows updates need enough temporary space to download, unpack, install, and store rollback files. If drive C: is nearly full, the update may fail before completion.<\/p>\n 5. Can I fix 0xC1900202 by using a Windows ISO file?<\/b><\/p>\n Often, yes. Mounting an official Windows ISO and running setup.exe with the option to keep personal files and apps can bypass Windows Update cache problems and complete the upgrade successfully.<\/p>\n 6. Should I delete SoftwareDistribution to fix this error?<\/b><\/p>\n You should not simply delete it while Windows Update is running. Stop the update services first, rename the SoftwareDistribution folder, restart the services, and let Windows create a fresh cache.<\/p>\n 7. What is the safest first step?<\/b><\/p>\n The safest first steps are freeing space on drive C:, restarting the computer, running SFC and DISM, and checking Windows Update services. These steps do not change disk partitions and are relatively low risk.<\/p>\n 8. Can antivirus software cause Windows Update error 0xC1900202?<\/b><\/p>\n Yes. Some third-party antivirus tools and system optimizers can interfere with major Windows updates. Temporarily disabling or uninstalling them before the upgrade may help.<\/p>\n 9. What should I do if the error comes back after every attempt?<\/b><\/p>\n Try an ISO-based in-place upgrade, check the EFI or System Reserved partition size, update chipset and storage drivers, disconnect external devices, and verify hardware compatibility. If nothing works, a clean Windows installation with a full backup may be faster.<\/p>\n 10. Is it safe to ignore error 0xC1900202?<\/b><\/p>\n It is not recommended. Ignoring update errors may leave the system without important security patches and stability fixes. If the computer is used for work, online banking, business accounts, or stored passwords, unresolved update problems increase risk.<\/p>\n If you are working with Windows updates, system stability, storage, or security, these sections may also be useful:<\/p>\n\n
\n
\n
\n
\n
\n
\n
\nUseful Tips<\/h3>\n
\n
\nCommon Mistakes<\/h3>\n
\nFrequently Asked Questions<\/h3>\n
\nRelated Articles<\/h3>\n
\n
\nBookmarks<\/h3>\n