How to Fix Windows Update Error 0x800f0923
What error 0x800f0923 means
Error 0x800f0923 is the Windows Update failure code for an incompatible driver or program. When Windows tries to install a cumulative update or a new feature version, it checks whether the drivers and software already on the PC will work with the incoming version. If something fails that check, Windows aborts the install and reports 0x800f0923 rather than pushing ahead and risking crashes, broken hardware, or a PC that will not boot after the upgrade.
It shows up most often on feature updates and on cumulative updates that touch driver-level components. You will see it in Settings > Windows Update > Update history next to the failed update, and retrying the same update just produces the same code again until the incompatible item is dealt with. That is actually useful: the error is telling you the blocker is on your PC, not in the update itself, and the fixes below work through the suspects from most to least likely.
Common causes
- An incompatible driver: an old graphics, audio, storage, or network driver that the new Windows version does not support is the single most common trigger.
- Outdated or abandoned software: old utilities, driver updaters, disk tools, and third-party antivirus that have not kept pace with current Windows builds can block an upgrade.
- A recently added device or program: new hardware with a half-baked driver, or software installed just before the update failed, is a prime suspect.
- Jammed update cache: a corrupt download or database inside the SoftwareDistribution or catroot2 folders can make every retry fail with the same code even after the real blocker is gone.
- Corrupt system files or a damaged component store: broken servicing files can prevent an otherwise compatible update from installing, which looks exactly like a compatibility failure.
How to fix error 0x800f0923 — step by step
Work through these fixes in order. Most people clear this error by step 2.
- Update your drivers from the manufacturer's site A driver that the new Windows version does not support is the most common trigger of 0x800f0923. Open Device Manager by right-clicking Start and choosing Device Manager, then look for any device with a yellow warning icon and update those first. Better still, go to your PC or motherboard maker's support downloads page, enter your exact model number, and install the latest chipset, graphics, audio, network, and BIOS or UEFI firmware drivers. If you recently added new hardware, update or temporarily remove that device's driver first, then retry the update. Driver updates from Device Manager alone are often not enough, because Windows Update rarely carries the newest manufacturer drivers.
- Remove incompatible or outdated software Open Settings, go to Apps, then Installed apps, and sort by install date. Uninstall anything you installed recently, plus old utilities that have not been updated in years, such as old disk tools, driver updaters, and third-party system optimizers. Temporarily uninstall third-party antivirus as well, since security software is a frequent compatibility blocker during upgrades. Restart the PC after removing the software, then open Settings, Windows Update, and click Check for updates. If the update now installs, reinstall the removed programs one at a time from their latest versions.
- Run the Windows Update troubleshooter Open Settings, go to System, then Troubleshoot, then Other troubleshooters. Click Run next to Windows Update and let it scan. The tool checks the update services, re-registers the update components, and clears stuck download queues automatically. Restart the PC when it finishes, then open Settings, Windows Update, and check for updates again.
- Reset the Windows Update components Right-click Start and open Terminal (Admin) or Command Prompt (Admin). Stop the update services with these commands:
net stop wuauserv,net stop cryptsvc,net stop bits, andnet stop msiserver. Then rename the two cache folders withren C:\Windows\SoftwareDistribution SoftwareDistribution.oldandren C:\Windows\System32\catroot2 catroot2.old. Now start the services again:net start wuauserv,net start cryptsvc,net start bits, andnet start msiserver. This clears the jammed download cache and stale update database that can make a retry fail with the same code. Windows rebuilds both folders automatically. Restart the PC and retry the update. - Repair system files with SFC and DISM In an administrator terminal, run
sfc /scannowand wait for it to finish, which takes 10 to 20 minutes. If it reports errors it could not fix, follow withDISM /Online /Cleanup-Image /RestoreHealth, which repairs the component store the SFC tool draws from and takes 15 to 30 minutes. Restart the PC after each tool finishes, then try the update again. Damaged servicing files can make an otherwise compatible update fail again and again. - Install the update manually or do an in-place upgrade repair Find the KB number of the failed update in Settings, Windows Update, Update history. Go to catalog.update.microsoft.com, search that KB number, and download the package that matches your Windows version and edition. Double-click the downloaded .msu file and follow the prompts. If the manual install also fails, download the Media Creation Tool from microsoft.com and run it, choosing Upgrade this PC now and keeping your files and apps. The tool reinstalls Windows over itself and resets the whole servicing stack, clearing update failures that survive every other fix. Keep the PC plugged into power and do not interrupt it while it runs.
Did this fix it? Quick checklist
- Drivers updated from the manufacturer's site, especially graphics, audio, chipset, and storage
- Recently installed and long-outdated software removed, third-party antivirus temporarily uninstalled
- Windows Update troubleshooter run, with a restart when it finished
- SoftwareDistribution and catroot2 renamed, services restarted, SFC and DISM run clean
If the error still appears after all six steps, unplug non-essential USB devices and try again — an external drive, printer, or dock with an old driver can be the hidden blocker. Also check that your PC meets the target Windows version's requirements (for Windows 11, TPM 2.0 and Secure Boot) and that you have at least 20 GB of free space on the system drive. As a last resort, back up your files and do a clean install using USB media created by the Media Creation Tool.
Frequently asked questions
What does error 0x800f0923 mean?
Error 0x800f0923 means a driver or program on your PC is not compatible with the Windows version being installed. Windows blocks the update on purpose so an incompatible driver cannot destabilize the system after the upgrade. It is a compatibility problem, not a sign that your files are damaged.
How do I find which driver is incompatible?
Start with Device Manager: right-click Start, choose Device Manager, and look for devices with a yellow warning icon. Then check your PC or motherboard maker's support page for driver updates, beginning with graphics, audio, chipset, and storage drivers. If you recently added new hardware, that device's driver is the prime suspect — update it or temporarily remove the device and retry the update.
Is it safe to rename the SoftwareDistribution folder?
Yes. The SoftwareDistribution folder only holds downloaded update files and the update database, and the catroot2 folder holds update signatures. Windows rebuilds both automatically the next time it checks for updates. Renaming instead of deleting also lets you restore the old folder if something goes wrong.
The update installed manually but Windows Update still fails. Is my PC broken?
No. The manual installer from the Microsoft Update Catalog does not use the same pipeline as Windows Update — it skips the download queues, the update services, and the SoftwareDistribution database. When a manual install works but Windows Update fails, it means your system is healthy and only the update plumbing was jammed, which is a separate problem from the compatibility block that 0x800f0923 reports.