How to Fix Windows Update Error 0xC1900223

By ErrorFix · Updated October 20, 2026 · 9 min read

What error 0xc1900223 means

Error 0xc1900223 is a Windows Update error. Microsoft’s official wording says it indicates “there was a problem downloading and installing the selected update” and adds that “Windows Update will try again later.” In other words, this is a download problem, not an installation problem: the update never arrived in usable condition, so there was nothing clean to install.

The classic version of this error appears during a big feature update — historically the update would stall around 97% and then fail with 0xc1900223. That pattern tells you a lot: almost everything downloaded, but the transfer was interrupted or the downloaded files failed verification at the end. So the suspect list is short: the connection between your PC and Microsoft’s servers broke, something on your network filtered or blocked the traffic, or the local download cache became corrupted. It is rarely a sign that the update itself is bad.

Common causes

• Lost connection to Microsoft’s update servers: a flaky or dropping connection interrupts the download, and the failed partial files trigger the error.
• VPN, proxy, or network-wide ad blocker filtering: services like Pi-hole, aggressive DNS filters, VPNs, and proxies can block the endpoints Windows Update needs, which is a well-documented cause of this code.
• Corrupted SoftwareDistribution or Catroot2 cache: the folders where Windows stores update downloads and signature data get tangled, so fresh downloads can’t verify.
• Corrupted system files or update components: damaged Windows system files break the update machinery itself, and the download fails no matter how good the connection is.
• Too little free disk space: feature updates need roughly 10 to 20 GB of free space for the download and staging files; running out mid-download produces this error.

How to fix error 0xc1900223 — step by step

Work through these fixes in order. Steps 1 and 2 resolve most cases because this error is usually temporary.

1. Retry the update and rule out a temporary server hiccup. Press Windows + I to open Settings, go to Windows Update, and click Check for updates or Retry. Microsoft’s own description of this error says Windows Update will try again later — and sometimes that is all it takes, because the Microsoft server was simply overloaded or the network hiccupped. If it fails again immediately, wait an hour or two and retry once more before moving on.
2. Run the Windows Update troubleshooter. Press Windows + I to open Settings, then go to System, then Troubleshoot, then Other troubleshooters. Find Windows Update in the list and click Run. Follow the on-screen prompts and let it apply any suggested fixes. Restart your PC when it finishes, then head back to Windows Update and try again. This built-in tool catches the most common stuck-update states automatically.
3. Disable VPN, proxy, and network-wide ad blockers. Disconnect your VPN app completely, and in Settings go to Network & internet, then Proxy, and turn off any manual proxy and the “Automatically detect settings” toggle if it’s misbehaving. If your home network uses a network-wide ad blocker like Pi-hole, pause or disable it while the update installs — these filters are a documented cause of 0xc1900223 because they can block Microsoft’s update endpoints. Retry the update on the unfiltered connection.
4. Free up disk space. Press Windows + I, go to System, then Storage, and check the free space on your C: drive. If you’re under 20 GB, open Cleanup recommendations on the same page and clear temporary files, and empty the Recycle Bin. Feature updates stage gigabytes of files before installing, and a download that runs out of room mid-transfer surfaces as exactly this error.
5. Reset the Windows Update components. Right-click the Start button and choose Terminal (Admin) or Command Prompt (Admin). Run these commands one at a time to stop the update services:
   net stop wuauserv
net stop cryptSvc
net stop bits
net stop msiserver
   Then rename the two corrupted download caches with:
   ren C:\Windows\SoftwareDistribution SoftwareDistribution.old
ren C:\Windows\System32\catroot2 catroot2.old
   Restart the services with:
   net start wuauserv
net start cryptSvc
net start bits
net start msiserver
   This clears the tangled download cache and lets Windows rebuild it fresh. Go back to Settings, then Windows Update, and check for updates again.
6. Repair corrupted system files with SFC and DISM. Open Terminal or Command Prompt as administrator and run DISM /Online /Cleanup-Image /RestoreHealth — this repairs the Windows component store and can take 10 to 20 minutes, so let it finish. When it completes, run sfc /scannow to scan and repair protected system files. Restart your PC afterward and retry the update. This pair of tools fixes 0xc1900223 when corruption in the update machinery itself is the root cause.
7. Install the update manually from the Microsoft Update Catalog. Open Settings, go to Windows Update, then Update history, and note the KB number of the update that failed. Search that KB number on the Microsoft Update Catalog, download the package that matches your system (x64 for most PCs), and run the installer yourself. Manual installation bypasses the Windows Update engine, its caches, and its network stack entirely — it pulls the files straight from Microsoft’s CDN and applies them locally. If the update is a feature update rather than a single KB, the Media Creation Tool’s “Upgrade this PC now” option achieves the same bypass.

Did this fix it? Quick checklist

• Windows Update completes without error 0xc1900223
• The update that kept failing now shows as installed in Update history
• Your VPN, proxy, or ad blocker is re-enabled after the successful install
• Your C: drive still has comfortable free space after the update

One thing people get wrong about this error: it doesn’t mean the update is broken or that you need a clean install. The error is Windows’ way of saying the delivery failed, not that the package is bad — that’s why retrying, clearing the cache, and unblocking the network fix it almost every time. And remember that “try again later” line in Microsoft’s description: if a server is just busy, no amount of command-line surgery beats a patient retry. Only escalate to resets and manual installs if the error repeats across multiple days.