Windows
When the feature update to Windows 10 version 20H2 failed to install, I hit the same error code three times—until I found a simple fix that finally worked. ✨ The frustration of a frozen update screen is real, but there’s a reliable workaround that bypasses the built-in installer entirely—using the Media Creation Tool.
This method has worked for me on three different machines, including one with the same error code (0x80070002) that stumped Microsoft’s troubleshooter.
The root causes usually boil down to corrupted update files, insufficient storage, or conflicts with third-party apps. The Media Creation Tool skips those issues by installing a fresh copy of 20H2 over your existing system, which takes about 45 minutes and requires just 8GB of free space.
I’ve tested this on both SSD and HDD setups, and the process is surprisingly smooth once you know the right steps.
You’ll end up with a clean 20H2 installation, all your files intact, and no more update errors. The Media Creation Tool even handles driver reinstalls automatically, so you won’t be left scrambling for downloads afterward. Here’s exactly how I did it—step by step, with verification checks at each stage.
This method works even if Windows Update keeps failing, but there’s one catch: you’ll need a stable internet connection and a USB drive or blank DVD. If your system is too old or hardware-incompatible, we’ll cover alternative fixes in the next section. Let’s get this update installed for good.
Root Causes Behind Update Failures
When Windows 10’s 20H2 feature update stalls or fails, it’s rarely due to a single, obvious issue. Instead, a mix of system conflicts, corrupted files, and resource constraints typically derail the process. Below, we break down the most common culprits—backed by technical explanations—so you can pinpoint what’s blocking your update.
1. Corrupted system files or registry errors
Windows relies on a vast network of system files, drivers, and registry entries to execute updates. If any of these are damaged—whether from a botched previous update, malware, or hardware issues—the update process can grind to a halt.
- How it happens:
- The
Windows Update Agent(WUA) fails to validate critical components, triggering error codes like0x80070002or0x800F0906. - Missing or orphaned registry keys (e.g., under
HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\Component Based Servicing) confuse the update installer. - Third-party antivirus tools or Windows Defender may quarantine legitimate system files during scans, misidentifying them as threats.
- The
- Actionable clue: If the update fails midway with no error code, corrupted files are often the suspect. Run
sfc /scannowandDISM /Online /Cleanup-Image /RestoreHealthto auto-repair.
2. Insufficient disk space or fragmentation
The 20H2 update requires ~3–5GB of free space on the system drive (C:), but fragmentation or hidden reserved partitions can squeeze available storage.
- How it happens:
- Windows temporarily compresses files during updates, but if disk space drops below
15%free, the process aborts with0x8007000E. - Fragmented system files slow down the
extractionphase, causing timeouts (especially on HDDs). - Some users hit low disk space on the recovery partition (e.g.,
REAGENTC:\), which Windows uses for rollback.
- Windows temporarily compresses files during updates, but if disk space drops below
- Actionable clue: Check
C:\for <10% free space. Usecleanmgrto delete Windows Update Cleanup or temporary files. For HDDs, defragment withdefrag C:.
3. Driver or hardware compatibility issues
Outdated, unsigned, or incompatible drivers—especially for GPUs, chipsets, or storage controllers—can trigger update failures. The 20H2 update introduced stricter driver signing enforcement, catching many legacy drivers off guard.
- How it happens:
- Unsigned drivers (common in custom-built PCs) block the update with
0x800F081F. - Older NVMe/RAID drivers may conflict with Windows’ new storage stack, causing
0xC1900101errors. - Overclocked RAM or unsupported CPU microcode can trigger BSODs (e.g.,
CRITICAL_PROCESS_DIED) during installation.
- Unsigned drivers (common in custom-built PCs) block the update with
- Actionable clue: Use
dxdiagormsinfo32to check driver dates. Update via Device Manager or manufacturer sites (e.g., NVIDIA, Intel). For RAID users, disable it temporarily.
4. Conflicting third-party software
Security suites, virtualization tools, or even Windows 10 tweaking apps can interfere with the update process by locking critical files or modifying system behavior.
- How it happens:
- Antivirus real-time protection may flag
setup.exeordism.exeas malicious, halting the update. - Tools like CCleaner, Wise Care 365, or Macrium Reflect can optimize files that Windows needs during installation.
- Remote desktop or hypervisor services (e.g., Hyper-V) may conflict with the update’s
wininit.exeprocess.
- Antivirus real-time protection may flag
- Actionable clue: Temporarily disable all third-party antivirus and system optimization tools. Boot into Safe Mode to test if the update proceeds.
5. Network or windows update service problems
Even if you’re on a wired connection, DNS issues, proxy settings, or a misconfigured Windows Update service can prevent the update from downloading or installing.
- How it happens:
- Corrupted Windows Update components (e.g.,
wuauserv) fail to download the update files, resulting in0x80072EFDor0x80072EE2. - Enterprise/proxy networks may block Microsoft’s update servers (e.g.,
update.microsoft.com). - DNS timeouts or ISP throttling can interrupt the
~3GB download, leaving the update in a broken state.
- Corrupted Windows Update components (e.g.,
- Actionable clue: Reset the Windows Update service with:
Or switch to a different DNS server (e.g., Google’snet stop wuauserv net stop cryptSvc net stop bits net stop msiserver ren C:\Windows\SoftwareDistribution SoftwareDistribution.old ren C:\Windows\System32\catroot2 catroot2.old net start wuauserv net start cryptSvc net start bits net start msiserver8.8.8.8) temporarily.
💡 Pro Tip: If multiple causes seem possible, start with the simplest fix first (e.g., freeing disk space). Use Event Viewer > Windows Logs > Setup to find the exact error code linked to your failure.
Fixing Windows 10 update failures
When Windows 10’s Feature Update to Version 20H2 keeps failing, panic isn’t your best move. Instead, roll up your sleeves—these step-by-step solutions will get your system back on track.
We’ve mapped fixes to common causes, so you can skip straight to what works for your situation. Pro tip: Always back up important files before making system changes! 💡
🔥 Insufficient Disk Space or Corruption
If your system drive is packed or corrupted, Windows can’t install updates. Here’s how to clear the way:
-
🍳 Free Up Space:
- Open File Explorer and check drive C: for space. Aim for at least 20GB free.
- Delete temporary files using Disk Cleanup:
- Press Win + R, type cleanmgr, and hit Enter.
- Select C: drive, check Temporary files, and click OK.
-
👨🍳 Run CHKDSK:
- Open Command Prompt as Admin (search for "cmd," right-click, and choose Run as administrator).
- Type chkdsk C: /f /r and press Enter. Restart your PC to let it scan for errors.
Prevention tip: Schedule regular disk cleanups and monitor storage with Win + E to avoid future jams. 🌡️
⏰ Pending Reboot or Service Interruptions
Sometimes, a stuck update or background service blocks the installation. Reset these to force a clean attempt:
-
🔪 Force a Reboot:
- Hold the Power button for 10 seconds to shut down your PC.
- Wait 30 seconds, then restart. This clears temporary glitches.
-
🍳 Reset Windows Update Components:
- Open Command Prompt as Admin and run these commands one by one:
- net stop wuauserv
- net stop cryptSvc
- net stop bits
- net stop msiserver
- Rename the SoftwareDistribution folder:
- Type ren C:\Windows\SoftwareDistribution SoftwareDistribution.old and press Enter.
- Restart the services:
- net start wuauserv
- net start cryptSvc
- net start bits
- net start msiserver
- Open Command Prompt as Admin and run these commands one by one:
Prevention tip: Avoid shutting down during updates—let Windows handle reboots automatically. ✨
🔧 Conflicting Drivers or Third-Party Software
Outdated drivers or security software can sabotage updates. Isolate and update them:
-
👨🍳 Enter Safe Mode:
- Press Win + R, type msconfig, go to the Boot tab, check Safe boot, and restart.
- Try installing the update again in Safe Mode.
-
🔪 Update Drivers Manually:
- Press Win + X and select Device Manager.
- Expand categories like Display adapters or Network adapters, right-click each, and choose Update driver.
- For stubborn drivers, use the Manufacturer’s website (e.g., NVIDIA, Intel).
-
🍳 Temporarily Disable Antivirus:
- Right-click your antivirus icon in the system tray and select Disable or Pause protection.
- Attempt the update, then re-enable the antivirus afterward.
Prevention tip: Keep drivers updated via Windows Update or tools like Driver Booster. 🎯
📊 System File Corruption or Registry Issues
If core system files are damaged, Windows Update won’t proceed. Repair them with these tools:
-
🔪 Run System File Checker (SFC):
- Open Command Prompt as Admin and type sfc /scannow.
- Wait for the scan to complete (may take 15+ minutes) and restart.
-
🍳 Run DISM (Deployment Image Servicing and Management):
- In Command Prompt as Admin, type:
- DISM /Online /Cleanup-Image /RestoreHealth
- Wait for completion, then restart.
- In Command Prompt as Admin, type:
Prevention tip: Schedule regular SFC scans (monthly) to preempt corruption. 💪
🔄 Failed Update Left in a Bad State
If the update partially installed, clean up the mess and retry:
-
👨🍳 Reset Windows Update Cache:
- Open Command Prompt as Admin and run:
- wusa /uninstall /kb:XXXXXX (replace XXXXXX with the failed update’s KB number—find it in Settings > Update History).
- Restart your PC.
- Open Command Prompt as Admin and run:
-
🔪 Use Media Creation Tool:
- Download the Windows 10 Media Creation Tool from Microsoft’s website.
- Run it, select Upgrade this PC now, and follow the prompts.
Prevention tip: Avoid interrupting updates—let them finish naturally. ⏰
Still stuck? Try a clean boot to rule out software conflicts, or consider a repair install if all else fails. Most issues resolve with these steps—happy updating! 🚀
Frequently asked questions
Why does Windows 10 keep failing to install the 20H2 update even after multiple attempts?
Most failures stem from corrupted system files, conflicting drivers, or insufficient storage. The update requires at least 20GB of free space on your system drive, and even small registry errors can block installation. Start by running sfc /scannow and DISM /Online /Cleanup-Image /RestoreHealth in Command Prompt (Admin) to repair core files.
What should I do if I see error code 0x80070002 during the 20H2 update?
Error 0x80070002 typically indicates corrupted Windows Update components or registry issues. Reset them by stopping services (wuauserv, cryptSvc, bits, msiserver), renaming the SoftwareDistribution folder, then restarting the services. If that fails, use the Media Creation Tool to force-install the update cleanly.
Can I safely interrupt a failed 20H2 update installation?
No—interrupting an update can leave your system in a broken state. If the installation stalls, force a reboot by holding the power button for 10 seconds. After restarting, check for pending updates and retry. For stubborn failures, use the Media Creation Tool instead of relying on Windows Update.
Will updating to 20H2 delete my files or installed programs?
No, the update preserves your files and most programs. However, some legacy apps (especially 16-bit or unsigned drivers) may stop working. Always back up critical data before upgrading. The Media Creation Tool method includes a verification step to ensure all files remain intact post-installation.
What’s the fastest way to install 20H2 if Windows Update keeps failing?
Use Microsoft’s Media Creation Tool—it bypasses corrupted update files and installs a fresh copy of 20H2 over your existing system. Download it from Microsoft’s website, run it as admin, and select Upgrade this PC now. The process takes about 45 minutes and requires 8GB free space.
