Windows PC Errors

How to Fix Windows Update Error 0x800f0920

Error 0x800f0920Plain English: Windows Update spotted a hang while installing the update and stopped on purpose — the update plumbing jammed, not your files.
Quick answer: Restart the PC and retry the update. If it fails again, run the Windows Update troubleshooter (Settings > System > Troubleshoot), reset the update components by renaming SoftwareDistribution and catroot2, repair files with SFC and DISM, then install the failed update manually from the Microsoft Update Catalog.

What error 0x800f0920 means

Error 0x800f0920 is the Windows Update failure code for CBS_E_HANG_DETECTED — in other words, the update engine detected a hang while the Component-Based Servicing system was working on the install and aborted it rather than risk leaving the system half-updated. It is a servicing problem, not a file problem: the delivery pipeline jammed instead of the payload being broken.

It shows up most often on cumulative updates and feature updates, usually after a previous update did not finish cleanly or after a forced shutdown during an install left servicing in a stuck state. You will see it in Settings > Windows Update > Update history next to the failed update, with a button to retry that just produces the same code again. The fixes below clear the jam from the outside in, starting with the simplest.

Common causes

How to fix error 0x800f0920 — step by step

Work through these fixes in order. Most people clear this error by step 3 or 4.

  1. Restart your PC and retry the update A full restart clears stuck servicing operations and pending reboots left behind by an earlier update, which is the most common trigger of 0x800f0920 in the first place. Press the Windows key, go to Power, and choose Restart so it is a real restart and not Sleep. When you are back at the desktop, open Settings, go to Windows Update, and click Check for updates. If the update installs this time, the hang was a leftover transient lock and you are done.
  2. 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 resets 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.
  3. 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, and net stop msiserver. Then rename the two cache folders with ren C:\Windows\SoftwareDistribution SoftwareDistribution.old and ren C:\Windows\System32\catroot2 catroot2.old. Now start the services again: net start wuauserv, net start cryptsvc, net start bits, and net start msiserver. This clears the jammed download cache that the hang detection choked on, and Windows rebuilds both folders automatically. Restart the PC and retry the update.
  4. Repair system files with SFC and DISM In an administrator terminal, run sfc /scannow and wait for it to finish, which takes 10 to 20 minutes. If it reports errors it could not fix, follow with DISM /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. Corrupted servicing files are a classic reason the hang detector fires.
  5. Install the update manually from the Microsoft Update Catalog 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 x64 package that matches your Windows version and edition. Double-click the downloaded .msu file and follow the prompts. The manual installer bypasses the broken update pipeline entirely, which is exactly what 0x800f0920 complains about.
  6. Do an in-place upgrade repair Download the Media Creation Tool from microsoft.com and run it, choosing Upgrade this PC now. When offered, keep 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

If the error still appears after all six steps, check for a pending Servicing Stack Update in the Microsoft Update Catalog — some cumulative updates refuse to install until the matching SSU is in place, and the failure looks exactly like 0x800f0920. Also try disconnecting non-essential USB devices and temporarily disabling third-party antivirus during the update attempt; both have been documented as servicing hang triggers. 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 0x800f0920 mean?

Error 0x800f0920 is Microsoft's code for CBS_E_HANG_DETECTED. It means the Windows Update engine detected a hang while the Component-Based Servicing system was working on an install, so it aborted the update instead of risking a half-installed system. It signals stuck update plumbing rather than corrupt user files.

How do I find which update failed with 0x800f0920?

Open Settings, go to Windows Update, then Update history. The failed update is listed there with its KB number and the date it failed. You need that KB number if you plan to install the update manually from the Microsoft Update Catalog, which is step 5 of this guide.

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 failed. 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 the classic 0x800f0920 pattern.