Error 0x80080005 means the Windows Update engine failed to start — the service could not launch, or its components could not register. On your Lenovo laptop this looks like updates that never begin: no download, no install attempt, just the error. The engine itself is broken, not any particular update.

This is a startup failure, which is a different animal from mid-process failures. If updates start but die partway, the 0x80240016 not-allowed guide covers those later-stage errors instead.

The fixes resuscitate the engine in stages: services, registrations, system files, and finally a full rebuild. Most cases resolve at the re-registration step.

Why this happens

  • Corrupted COM registration: The engine’s components register with COM at startup, and damaged registrations produce exactly this server-execution failure.
  • Update services disabled: If wuauserv is disabled — by a tool, a policy, or an accident — the engine cannot start.
  • Damaged service binaries: Corruption in the update client’s own files stops the service process from launching.
  • Permission problems: When the service account loses rights on its files or registry keys, startup fails with this code.
  • Conflicting security software: Some suites block the update service from launching, mistaking its behavior for something suspicious.
  • Corrupted shared libraries: System files the service depends on, if damaged, take the service down with them.
  • Disk errors: Bad sectors hitting the service’s files or registry hives prevent a clean startup.

How to fix it

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

Fix 1: Check whether the services can start at all

Like a car that will not turn over, the first question is whether the engine even tries. Windows Update depends on several background services, and if any is disabled or stuck, nothing launches. Tweaking utilities and debloat scripts sometimes turn them off. A minute in the Services console answers it.

  1. Use Win + R, type services.msc, then press Enter.
  2. Locate Windows Update, Background Intelligent Transfer Service, Cryptographic Services, and Windows Installer.
  3. Put each startup type on Automatic (Manual for Windows Installer) and start any that are stopped.
  4. Try the update again now that all four services run.

Fix 2: Re-register the update engine’s DLLs

If the service is enabled yet still will not start, its COM registration is the prime suspect. The update engine is a bundle of COM components, and when their registration breaks, the service cannot start or reach Microsoft’s servers. Re-registering the core DLLs rebuilds those registrations from nothing. The DLL sequence follows Microsoft’s official Windows support hub troubleshooting for update service failures.

  1. Open an elevated Command Prompt first.
  2. Halt the Windows Update service via net stop wuauserv.
  3. Re-register the core DLLs — regsvr32 wuaueng.dll, regsvr32 wucltux.dll, regsvr32 wuwebv.dll, regsvr32 wups2.dll — confirming each prompt.
  4. Restart the service via net start wuauserv, then retry the update.

Fix 3: Scan system files with SFC

The engine leans on shared system libraries, and damage there kills the service at birth. The System File Checker compares every protected file against a known-good copy and repairs what is broken, removing a whole class of failures in one sweep.

  1. Open a Command Prompt or Terminal with administrator rights.
  2. Type in sfc /scannow, press Enter, and wait for the scan to complete.
  3. Should it report repairs, reboot the laptop.
  4. Retry the update installation once the reboot is done.

Fix 4: Rule out antivirus interference

Security suites occasionally mistake the update service’s system-level behavior for something malicious and block its launch. The resulting errors never name the antivirus, so this is a legitimate diagnostic: pause real-time protection and attempt to start the service. Windows Defender keeps you covered meanwhile.

  1. Open the antivirus control panel and disable real-time protection.
  2. Try starting the Windows Update service and running the update while protection is paused.
  3. Re-enable protection immediately after the attempt finishes.
  4. If the service starts, add the update service executables to your suite’s exclusions.

Fix 5: Restore the update folders to a clean state

Stale state can jam the engine before it starts. Stopping the update services and renaming the SoftwareDistribution and catroot2 folders forces Windows to rebuild them cleanly — fresh permissions, no leftover operations, no corrupted bookkeeping for the service to choke on.

  1. Right-click the Start button, choose Terminal (Admin), and approve the elevation prompt.
  2. Issue the stop commands one by one: net stop wuauserv, net stop cryptSvc, net stop bits, net stop msiserver.
  3. Execute the renames — ren C:\Windows\SoftwareDistribution SoftwareDistribution.old and ren C:\Windows\System32\catroot2 catroot2.old.
  4. Start the services again using net start, then check for updates.

Fix 6: Scan the disk for bad sectors

When the service’s own files or registry hives sit on damaged sectors, startup fails no matter how healthy the software is. A disk check scans for physical defects and moves data away from bad areas, eliminating the hardware variable.

  1. Fire up an elevated Command Prompt.
  2. Type chkdsk C: /f /r and say yes to the next-restart check.
  3. Reboot the laptop and wait out the full scan — up to an hour on large drives.
  4. Attempt the update again following the clean disk check.

Fix 7: Reinstall Windows in place, keeping everything

When registrations, services, and files all check out yet the engine stays dead, escalate to the rebuild. A repair install reconstructs Windows around your files and apps, replacing every system file, service, and update component with fresh copies. Take a backup first anyway — repairs are safe, not risk-free. When the engine is damaged beyond repair, a repair install from the official Windows 11 download puts a clean one in its place.

  1. Pull the Windows 11 media creation tool from Microsoft’s official download page.
  2. Open it, choose Upgrade this PC now, and select Keep personal files and apps.
  3. Give the installer time to finish — the machine will restart several times.
  4. When setup completes, run Windows Update once more for anything the repair image lacked.

Closing

A dead update engine feels catastrophic, but it is usually a registration or service-state problem with a clean fix. Work the list in order and the engine almost always roars back to life — at which point pending updates install normally. Lenovo owners can follow up in Lenovo Vantage to confirm drivers and firmware are current once updates flow again. If the engine runs but the server conversation fails, the 0x80244010 server-trips guide picks up the trail.

Frequently asked questions

What does error 0x80080005 mean?
It means CO_E_SERVER_EXEC_FAILURE reaching you through Windows Update: the update engine’s server process failed to start or register its components. In practical terms, the Windows Update service cannot launch, so no update operation can even begin. Causes include corrupted COM registrations, disabled services, damaged service binaries, permission problems, and security software blocking the launch.
Why won't the Windows Update service start?
The usual suspects, in order: it is disabled (check services.msc), its COM registration is corrupted (re-register the DLLs), its files are damaged (SFC and DISM), or security software is blocking it. Work through those before assuming deeper damage. The Services console often shows the service stuck on Starting or immediately stopped, which confirms a startup failure rather than a mid-operation error.
Can antivirus block the update service?
Yes — behavior-based protection in some suites flags the update service’s system-level operations and blocks its launch, more often after antivirus updates that tighten heuristics. Temporarily disabling the suite’s real-time protection and trying to start the service is a conclusive test. If it starts, add the update service executables to the suite’s exclusions.
Is a repair install overkill for this?
Not if the earlier steps fail. When registrations, services, and system files all check out yet the engine still refuses to start, the damage sits beyond surgical repair — something in the servicing infrastructure is broken at a level the tools cannot reach. A repair install rebuilds all of it while preserving files and apps, making it the rational escalation rather than overkill.