How to Fix Windows Update Error 0x80080005 (2026)

By ErrorFix · Updated October 21, 2026 · 8 min read

What error 0x80080005 means

Windows Update is not a single program — it is a team of background services and components that talk to each other. When you click "Check for updates," the update client asks Windows to start or connect to the services it needs: the Windows Update service (wuauserv), the Background Intelligent Transfer Service (bits), the Cryptographic Services (cryptSvc), and the Windows Installer service (msiserver). Error 0x80080005, internally known as CO_E_SERVER_EXEC_FAILURE ("Server execution failed"), means that launch or connection failed. The component that was supposed to start simply would not, so the whole update process stopped before it could even begin.

This is why 0x80080005 is so stubborn. It is not a corrupted download you can fix by clicking "Retry," and it is not a storage problem you can fix by freeing space. Retrying downloads the same packages and runs into the same service that refuses to start. The error typically appears on the Windows Update screen in Settings with a message like "There were some problems installing updates" and the code 0x80080005 next to a failed update — sometimes for every single update, even small ones. In that case, the problem is almost never the update package itself. It is the update engine underneath.

The good news is that the root causes are a short list, and they are all repairable without losing anything. Nine times out of ten, 0x80080005 comes down to one of the update services being disabled or broken, a corrupted registration of the update components (which is what "server execution failed" literally describes — Windows cannot create the COM server the updater asked for), a corrupted download cache, or third-party security software blocking the services from starting. Work the steps below in order and you will find the culprit.

Common causes

• An update service is disabled or stuck: a system optimizer, debloat script, or group policy set Windows Update, BITS, or Cryptographic Services to Disabled, so they cannot start at all.
• Broken COM registration of update components: a failed install left the Windows Update DLLs unregistered, so Windows cannot create the component server the updater requests — the literal meaning of CO_E_SERVER_EXEC_FAILURE.
• Corrupted update cache: the SoftwareDistribution or catroot2 folders contain damaged packages or signatures that prevent the update engine from initializing.
• Third-party antivirus or firewall interference: security software quarantines update binaries or blocks the services from launching, especially right after its own update.
• Corrupted system files or registry damage: damaged protected system files or a corrupted service registration stop a required service from initializing, even when its startup type is correct.

How to fix error 0x80080005 — step by step

Work through these fixes in order. Step 2 is the most important for this particular error — watch the service start output carefully.

1. Run the Windows Update troubleshooter. Open Settings, go to System, then Troubleshoot, then Other troubleshooters. Click Run next to Windows Update and let the tool scan and repair common blockers, including services that are stopped or misconfigured. This occasionally fixes simple cases on its own, and it never hurts as a first move. When it is done, retry the update from Settings, then Windows Update, then Check for updates.
2. Restart the Windows Update services manually. Right-click Start and choose Terminal (Admin) or Command Prompt (Admin). Stop the four update-related services by running each command: net stop wuauserv, net stop cryptSvc, net stop bits, and net stop msiserver. Then start them again one at a time: net start wuauserv, net start cryptSvc, net start bits, and net start msiserver. Watch the output carefully — if one service reports that it could not be started, you have found your culprit. Also open services.msc and confirm that Windows Update, Background Intelligent Transfer Service, Cryptographic Services, and Windows Installer are not set to Disabled; set them to Manual or Automatic instead.
3. Re-register the Windows Update DLLs. In an admin Command Prompt, re-register the core update components with the regsvr32 command, running each line separately: regsvr32 atl.dll, regsvr32 wuapi.dll, regsvr32 wuaueng.dll, regsvr32 wuaueng1.dll, regsvr32 wucltui.dll, regsvr32 wups.dll, regsvr32 wups2.dll, and regsvr32 wuwebv.dll. Each one should respond with DllRegisterServer in the file succeeded. If one fails to register, note its name — it is usually the specific component whose COM registration is broken. Reboot after the last registration, then retry Windows Update.
4. Reset the Windows Update components. Right-click Start and choose Terminal (Admin) or Command Prompt (Admin). Stop the update services again: net stop wuauserv, net stop cryptSvc, net stop bits, and net stop msiserver. Then rename the cache folders so Windows rebuilds them from scratch: ren C:\Windows\SoftwareDistribution SoftwareDistribution.old and ren C:\Windows\System32\catroot2 Catroot2.old. Finally, start the services again: net start wuauserv, net start cryptSvc, net start bits, and net start msiserver. This clears a corrupted download cache that can prevent the update engine from initializing.
5. Repair system files with DISM and SFC. In the admin terminal, run DISM /Online /Cleanup-Image /RestoreHealth. This scans the component store for damage and replaces bad components with clean copies downloaded from Windows Update. It typically takes 10 to 30 minutes — let it run to the end and look for the message The restore operation completed successfully. Then run sfc /scannow, which checks every protected Windows system file against known-good copies and repairs anything still broken. Restart your PC when both are done, then retry Windows Update from Settings.
6. Do an in-place repair install of Windows. If nothing else works, download a Windows ISO matching your edition with the Media Creation Tool on the same PC, double-click the ISO to mount it, and run setup.exe. Choose the option to keep personal files and apps. This reinstalls Windows over itself, rebuilding every service registration and system component while keeping your files, programs, and settings exactly as they are. It is the definitive fix when a required update service is corrupted beyond what DISM can repair.

Did this fix it? Quick checklist

• The update installs from Windows Update without 0x80080005
• All four services start cleanly and stay running in services.msc
• Every regsvr32 call reported "DllRegisterServer succeeded"
• The previously failing update shows as installed under Update history

If 0x80080005 keeps coming back after all of this, open Event Viewer (press Win + R, type eventvwr), and look under Windows Logs, then System, for errors logged at the exact time you run Windows Update — the failing service name is often right there. Also temporarily disable third-party antivirus before retrying, since some suites re-block the update services on every reboot. On work PCs joined to a domain, a group policy may be forcing the services to Disabled; in that case your IT admin needs to change the policy, because local changes will be reverted.