Windows 10 error code 0x20017 (often shown as C1900101-0x20017) appears during a feature update or upgrade, and it means the installation failed during the driver or system preparation phase. The fix is to free up disk space, remove conflicting drivers and peripherals, run the Windows Update troubleshooter, and then retry the update; in stubborn cases, the Media Creation Tool or an in-place repair will get the update installed.
What This Error Code Actually Means
Windows 10 uses a set of internal error codes to report upgrade problems. 0x20017 is one of the C1900101 series, which the Windows engineering team uses for failures that occur during the driver installation phase of a feature update. The update process downloads the new OS files, prepares the system, then tries to install and configure drivers. When a driver misbehaves, the system rolls back to the previous version and shows this error.
You’ll most often see it when upgrading from Windows 10 to a newer feature release (for example, from version 21H2 to 22H2) or when installing a major cumulative update. The error can also appear on a clean install attempt if the installation media is corrupted or the hardware has an incompatible driver.
Why It Happens: Common Triggers
There is no single cause, but the following are the most frequently reported:
- Insufficient disk space – the upgrade needs around 20–30 GB free for temporary files, even if the final install is smaller.
- Third-party antivirus or security software – these can interfere with the upgrade process, especially if they hook into the kernel.
- Outdated or incompatible drivers – especially display, network, and chipset drivers.
- Connected peripherals – USB devices, external drives, and even some printers can cause the driver phase to fail.
- Corrupted system files – a damaged Windows component store or system image.
- BIOS/UEFI settings – secure boot, TPM, or legacy boot settings that conflict with the new version.
It’s worth noting that the error is not a hardware failure – it’s a software-level rollback. Your PC is still functional; the update just didn’t stick.
Step-by-Step Fixes (In Order of Likelihood)
Try these in order. Most users resolve the error with the first few steps.
- Free up disk space. Open Settings > System > Storage and remove temporary files, or use the Disk Cleanup tool. You need at least 20 GB free, but 30–40 GB is safer.
- Unplug all non-essential peripherals. Disconnect external hard drives, USB hubs, printers, and even your phone. Keep only a mouse and keyboard (and a monitor, obviously).
- Run the Windows Update Troubleshooter. Go to Settings > Update & Security > Troubleshoot > Additional troubleshooters and select Windows Update. Run it and restart.
- Temporarily disable third-party antivirus. Right-click the AV icon in the system tray and choose “disable” or “pause protection.” Do not uninstall it yet – just turn it off for the upgrade. If you use a third-party firewall, disable that too.
- Update your drivers manually. Go to your PC manufacturer’s support site (Dell, HP, Lenovo, etc.) and download the latest chipset, display, and network drivers. Install them, restart, then retry the update.
- Run DISM and SFC. Open Command Prompt as Administrator and run:
DISM /Online /Cleanup-Image /RestoreHealth
thensfc /scannow
Restart and try again. - Use the Media Creation Tool. Download the tool from Microsoft’s website, run it, and choose “Upgrade this PC now.” This often bypasses the Windows Update path that’s failing.
- Perform an in-place repair. If the Media Creation Tool fails, mount the ISO (double-click it), run
setup.exe, and choose “Keep personal files and apps.” This reinstalls Windows while preserving your data.
If all else fails, you can try a clean install (backup your data first), but that’s a last resort.
How to Read the Log Files
Windows writes detailed logs for every upgrade attempt. The most useful ones are:
C:\$WINDOWS.~BT\Sources\Panther\setuperr.logC:\$WINDOWS.~BT\Sources\Panther\setupact.logC:\Windows\Panther\setuperr.log(after the rollback)
Open setuperr.log in Notepad and look for lines with “Error” or “Failed”. The text around the error will often mention a specific driver (e.g., atikmdag.sys for AMD graphics) or a device. If you see a driver name, update or uninstall that driver before retrying.
These logs are large, but you don’t need to read everything – just search for “0x20017” or “Error” and look at the lines immediately before and after.
What Not to Do (Common Mistakes)
Many users make the error worse by trying the wrong things. Avoid these:
- Don’t force-restart during the upgrade. The update can take 30–60 minutes. If it looks stuck, wait at least an hour before touching anything.
- Don’t run multiple “fix” tools at once. Running DISM and a third-party registry cleaner simultaneously can cause more damage.
- Don’t disable Secure Boot or TPM unless you know why. That can cause a different error (0x800F0922) and may prevent the update entirely.
- Don’t uninstall your antivirus permanently. Just disable it temporarily. Re-enable it after the upgrade.
- Don’t skip the driver updates. Even if Windows says “you’re up to date,” the manufacturer’s site may have a newer driver.
When to Consider a Clean Install
If you’ve tried all the steps above and the error persists, a clean install is the most reliable solution. It eliminates any driver or system corruption that’s causing the failure. Before doing that:
- Back up all personal files to an external drive or cloud.
- Note your installed applications – you’ll need to reinstall them.
- Download the Windows 10 Media Creation Tool and create a USB drive.
- Boot from the USB, choose “Custom install,” and delete the existing partitions (or just the OS partition).
After the clean install, you’ll be on the latest version and can restore your files. This is more time-consuming but almost always works.
Frequently Asked Questions
Will I lose my files if I use the Media Creation Tool to upgrade?
No, the “Upgrade this PC now” option keeps your personal files and installed apps. It’s essentially the same as a Windows Update feature upgrade, just delivered via a different channel. However, it’s always wise to back up before any major update.
Can this error be caused by a failing hard drive?
Yes, but it’s rare. If the disk has bad sectors, the upgrade may fail to write files. Check disk health with chkdsk /f or a tool like CrystalDiskInfo. If the drive is failing, replace it before attempting the update.
Why does the upgrade roll back instead of just showing an error?
Windows is designed to revert to the previous version if the new one fails to install correctly. This is a safety feature – it prevents you from being left with a broken OS. The rollback process is automatic and usually takes 5–15 minutes.
Is this error related to Windows 11?
No, 0x20017 is a Windows 10 error. Windows 11 has its own set of error codes, though some are similar. If you’re trying to upgrade to Windows 11 and see this code, you’re likely still on Windows 10 and the update is a Windows 10 feature update.
How long should I wait before giving up on a fix?
If you’ve tried the first five steps and the error still appears, move to the Media Creation Tool. If that fails, try the in-place repair. Only after those two fail should you consider a clean install. Most users resolve it within a day of trying these steps.
Can I skip the update and just stay on my current version?
Yes, but you’ll miss security patches and eventually lose support. Windows 10 reached end of support on October 14, 2025, so you should upgrade to a supported version or move to Windows 11 if your hardware allows. Staying on an unsupported version is a security risk.
Related
General steps for current mainstream versions; menus can differ by device and version. See the disclaimer or report an error.
More in this bed
- Multi-Cloud GPU Failover Design Guide
- Error Code Currant Destiny? Meaning & Fixes
- Spotify Jam Not Working on Mobile? Fixes That Work
- Windows 10 No Internet Secured WiFi Error Fix
- AirPlay with Roku Multi-Device Setup: A How-To
- How to Set a Timer on iPhone (iOS 18 & 17)