Error 0x80080005 is Windows Update failing at the starting line. Behind the friendly Settings page sits a COM server — the actual engine that scans, downloads, and installs updates — and this code means that engine would not start. The request was made, the launch was attempted, and the server never came up.

The usual reason is registration damage. COM servers live and die by their registry entries, and if the entries pointing to the update engine’s DLLs are broken, missing, or pointing at corrupted files, every launch attempt fails identically. Disk corruption, overzealous registry cleaners, and interrupted updates are the classic ways this damage happens.

Repairing it means rebuilding what the launch needs: correct registrations, intact binaries, and healthy services. The steps below do exactly that, from re-registration through full component repair.

It helps to picture the update engine as a program that Windows launches on demand, like any other. Error 0x80080005 means the launch itself is failing — the equivalent of double-clicking an application and having nothing happen. The repairs below fix the launch path: the registrations that point to the program, the files the program needs, and the services it runs inside.

Why this happens

  • Broken COM registration. The registry entries that tell Windows how to launch the update engine are damaged or missing.

  • Corrupted update engine DLLs. Files like wuaueng.dll that implement the engine are damaged, so the launched server crashes immediately.

  • Damaged servicing stack. The underlying CBS infrastructure the engine depends on is corrupted.

  • Windows Update service misconfiguration. The wuauserv service is disabled, set to the wrong account, or has broken dependencies.

  • Registry cleaner damage. Third-party registry cleaners are notorious for deleting COM registrations Windows actually needs.

  • Disk errors. Bad sectors hitting service binaries or registry hives produce launch failures.

  • Conflicting security software. Overprotective security products can block the engine’s processes from starting.

How to fix it

Work through these in order — diagnose first, then act.

Fix 1: Fix 1: Re-register the Windows Update DLLs

This is the signature fix for a COM launch failure. Re-registering rebuilds the registry entries the engine needs to start, directly addressing the most common cause. Run each regsvr32 command and wait for its success dialog before continuing; a failed registration tells you exactly which DLL is damaged and needs SFC’s attention.

  1. Open Terminal as administrator.
  2. Run these commands one by one: regsvr32 wuapi.dll, regsvr32 wuaueng.dll, regsvr32 wups.dll, regsvr32 wuwebv.dll, regsvr32 atl.dll, regsvr32 urlmon.dll, regsvr32 msxml3.dll. Confirm each succeeds.
  3. Restart the laptop and check for updates.

Fix 2: Fix 2: Verify the Windows Update service

If the service itself is disabled or misconfigured, the engine cannot start no matter how healthy its registration is. Check its state and dependencies directly. While in the Services console, glance at the Dependencies tab for Windows Update; the RPC service it depends on must be running or nothing downstream can start.

  1. Press Win + R, type services.msc, and press Enter.
  2. Double-click Windows Update and set Startup type to Manual (Trigger Start).
  3. On the Log On tab, confirm it uses the Local System account, then start the service and retry. If the service starts and then quietly stops again on its own, the dedicated Windows Update service not running guide digs into the dependency and corruption angles.

Fix 3: Fix 3: Reset the Windows Update components

Beyond registration, the engine needs healthy state folders. Resetting the components rebuilds the caches and restarts the services the engine coordinates with. This reset also clears the DataStore, which removes any corrupted state that might have been crashing the engine at launch.

  1. In an admin Terminal, run net stop wuauserv, net stop cryptSvc, net stop bits, net stop msiserver.
  2. Run ren C:\Windows\SoftwareDistribution SoftwareDistribution.old and ren C:\Windows\System32\catroot2 catroot2.old.
  3. Restart the four services and check for updates.

Fix 4: Fix 4: Run SFC to repair system files

If the engine’s binaries are corrupted on disk, re-registration points at broken files. SFC scans protected system files and restores damaged ones from the component store. SFC’s log at the CBS log path lists every file it repaired; a long list of update-engine files confirms you found the right problem.

  1. Open Terminal as administrator and run sfc /scannow.
  2. Let it reach 100 percent, restart, and retry the update.

Fix 5: Fix 5: Run DISM RestoreHealth

When SFC cannot repair because the store itself is damaged, DISM fixes the store first. This covers the deeper corruption that keeps the engine from launching. DISM’s online repair downloads clean copies, so keep the laptop connected and awake; sleep mid-repair is a classic way to interrupt it.

  1. In an admin Terminal, run DISM /Online /Cleanup-Image /RestoreHealth.
  2. Wait for completion, restart, then run sfc /scannow once more before retrying updates.

Fix 6: Fix 6: Clean-boot to rule out interference

Security software and system utilities can block the engine’s launch. A clean boot removes them from the equation for one test. If the engine starts clean-booted, the blocker is third-party; re-enable services in halves, testing the update check each time, to name it.

  1. Press Win + R, type msconfig, check Hide all Microsoft services, and click Disable all.
  2. Disable all startup items in Task Manager, restart, and check for updates.

Fix 7: Fix 7: Perform an in-place upgrade repair

For damage that resists every targeted repair, reinstalling Windows over itself rebuilds the engine, its registrations, and the servicing stack while keeping files and apps. An in-place repair is also the moment to image your drive afterward; with a fresh servicing stack, a system image gives you a clean restore point for the future.

  1. Download the installer from the Windows 11 download page .
  2. Run setup.exe from the mounted ISO with Keep personal files and apps.
  3. Finish the repair and run Windows Update. If the engine starts but downloads fail, our 0x80246007 guide is the next step.

Closing

Error 0x80080005 is the update engine failing to start, and re-registering its components plus repairing the underlying files brings it back in nearly every case. Work from the DLL re-registration through the component reset before considering the in-place repair. Once the engine runs again but downloads misbehave, the 0x80246007 download guide continues the journey, and Microsoft’s Windows support hub has the official service-repair documentation.

Frequently asked questions

What does error 0x80080005 mean?
It is a COM error, CO_E_SERVER_EXEC_FAILURE, meaning the Windows Update engine’s COM server failed to launch. In plain terms, Windows tried to start the update machinery and the machinery would not start, usually because its registration or supporting files are damaged.
Is 0x80080005 a virus symptom?
No. It is a system corruption or registration issue, not malware. That said, running a malware scan is reasonable general hygiene if system components are mysteriously damaged, since some infections do tamper with update services specifically to block security patches.
Can I fix 0x80080005 without reinstalling Windows?
Third-party registry cleaners are notorious for deleting COM registrations Windows actually needs. If you run one, exclude system and COM registrations from its cleaning, or better yet stop using registry cleaners entirely since they provide no measurable benefit on modern Windows.
Why did 0x80080005 appear suddenly?
Common triggers include interrupted updates, disk errors corrupting service binaries, registry cleaners damaging COM registrations, and failed third-party software installs that share the installer infrastructure with Windows Update. Any of these can damage the launch path silently, so the error often appears out of nowhere.