Windows Fixes

Fix Windows Update Error 0x80080005

Issue type: Windows Update service and COM execution failure | Applies to: Windows 10, Windows 11

Windows update error 0x80080005 usually means Windows Update cannot start or control one of the internal components it needs to scan, download, or install updates. The practical fix is to repair Windows Update services, reset the update folders, re-register core update components, then run DISM and SFC if the error survives the service reset.

This error is often more stubborn than a normal download failure. Clicking Retry may show the same code again because the broken part is not the update package itself. The failure is usually in the local update engine, service registration, BITS transfer layer, COM registration, security software interference, or a damaged Windows image.

Before changing anything, check whether other updates are also failing. If every update fails with the same code, treat it as a Windows Update infrastructure problem. If only one KB fails, write down that KB number because a manual install may solve the issue later.

What to Do First: Fix Windows Update Error 0x80080005

  1. Restart the PC once and check whether windows update error 0x80080005 appears again.
  2. Open Settings → Windows Update → Update history and write down any failed KB number.
  3. Disconnect VPN software and pause third-party antivirus temporarily during the test.
  4. Run the Windows Update troubleshooter from Settings → System → Troubleshoot → Other troubleshooters.
  5. Open Command Prompt (Admin) and reset the update services if the troubleshooter does not fix it.
  6. Restart again, then check for updates before opening VPN, cleanup, optimizer, or security tools.

Fix 2: Run the Windows Update Troubleshooter

The troubleshooter is a safe first repair because it checks Windows Update configuration, restarts related services, and fixes common service state problems without deleting user files.

  1. Open Settings.
  2. Go to System → Troubleshoot → Other troubleshooters.
  3. Click Run next to Windows Update.
  4. Apply any suggested repairs.
  5. Restart when it finishes.

If the update then stays queued instead of installing, use the related TechRoke guide on Windows Update pending install because the problem has moved from a service launch error to a queue state issue.

Fix 3: Check Windows Update, BITS, RPC, and DCOM Services

Error 0x80080005 can appear when Windows Update cannot start one of the service layers it depends on. Check the services manually before running deeper repairs.

  1. Press Win + R, type services.msc, and press Enter.
  2. Find Windows Update and make sure it is not Disabled.
  3. Find Background Intelligent Transfer Service and make sure it is not Disabled.
  4. Find Remote Procedure Call (RPC) and confirm it is running.
  5. Find DCOM Server Process Launcher and confirm it is running.

Windows Update depends on service communication. If RPC or DCOM services are broken, Windows Update may fail before the download stage even starts.

Fix 4: Reset Windows Update Components

A full component reset rebuilds the main update folders and clears stale state data. This is stronger than clicking Retry because it resets the local update engine, not just the failed update attempt.

net stop wuauserv
net stop bits
net stop cryptSvc
net stop msiserver
ren C:\Windows\SoftwareDistribution SoftwareDistribution.old
ren C:\Windows\System32\catroot2 catroot2.old
net start msiserver
net start cryptSvc
net start bits
net start wuauserv

Restart after running the commands. Windows will create new update folders automatically. If updates do not download after the reset, check Windows Update not downloading.

Fix 5: Re-register Core Windows Update Components

If the service reset does not work, re-register the Windows Update components. This can help when update-related DLL registration is missing or damaged.

regsvr32.exe /s wuapi.dll
regsvr32.exe /s wuaueng.dll
regsvr32.exe /s wucltui.dll
regsvr32.exe /s wups.dll
regsvr32.exe /s wups2.dll
regsvr32.exe /s wuwebv.dll

Run these commands in Command Prompt (Admin). Then restart the PC and try Windows Update again.

Fix 6: Temporarily Remove VPN, Firewall, or Antivirus Interference

Third-party security software can block update services, COM registration, or background transfers. Temporarily disabling it is a test, not a permanent fix.

  1. Disconnect any VPN.
  2. Temporarily pause third-party antivirus or firewall tools.
  3. Run Windows Update immediately.
  4. If the update works, add Windows Update and BITS to trusted rules.
  5. Turn protection back on after testing.

If you recently installed a cleanup utility, debloater, or optimizer, disable it and test again. Some tools disable services that Windows Update needs.

Fix 7: Repair Windows Image with DISM and SFC

If the update engine still fails, repair Windows itself. Run DISM first because it repairs the component store. Then run SFC because it uses that repaired store to restore protected system files.

DISM /Online /Cleanup-Image /CheckHealth
DISM /Online /Cleanup-Image /ScanHealth
DISM /Online /Cleanup-Image /RestoreHealth
sfc /scannow

Restart after both tools finish. If DISM pauses for several minutes, wait. Do not close the window while the repair is running.

Fix 8: Check Windows Update Logs and Event Viewer

If the error keeps returning, check the logs instead of repeating the same commands. Logs can show whether the failure is service startup, BITS transfer, access denied, COM, or component store damage.

Get-WindowsUpdateLog

Run that command in PowerShell as Administrator. Windows creates a readable log on the desktop. Search it for 0x80080005, wuauserv, BITS, COM, and access denied.

Also check Event Viewer → Windows Logs → System for Service Control Manager, DCOM, WindowsUpdateClient, or BITS errors at the same time as the failed update.

Fix 9: Install the Failed KB Manually

If only one KB fails after Windows Update is repaired, install that package manually from Microsoft Update Catalog. This bypasses part of the automatic queue.

  1. Copy the failed KB number from Update history.
  2. Search for the KB in Microsoft Update Catalog.
  3. Download the package that matches your Windows version and architecture.
  4. Run the package as Administrator.
  5. Restart after installation.

If the standalone installer fails, apply the package with DISM:

DISM /Online /Add-Package /PackagePath:"C:\Users\YourName\Downloads\update.msu"

Fix 10: Use an In-Place Repair If Windows Update Is Still Broken

If Windows Update fails for every KB and the repair tools do not fix the local update engine, use an in-place repair upgrade. This reinstalls Windows over itself while keeping files and apps.

This is not a clean install. It rebuilds Windows system files and servicing components while preserving your setup. Back up important files first, then use Microsoft’s Windows repair or installation media option.

If the error changes to 0x80070057 after repairs, follow Windows Update error 0x80070057 because the new code points to a different update store problem.

Common Mistake

The common mistake is only restarting the Windows Update service. Windows update error 0x80080005 often involves service registration, COM startup, BITS, or damaged update components. Restarting one service may reload the same broken state, so use the full component reset and repair path instead.

Best Next Step

If the error continues after the component reset, DLL re-registration, DISM, and SFC, use Microsoft’s official Windows Update troubleshooter and then consider an in-place repair if all updates fail. Start with Windows Update Troubleshooter — Microsoft Support.

Frequently Asked Questions

What does Windows Update error 0x80080005 mean?

It usually means Windows Update could not start or communicate with a required update component. The failure can involve Windows Update services, BITS, COM registration, security software, or damaged system files.

Can I fix 0x80080005 without reinstalling Windows?

Yes. Most cases can be fixed by running the troubleshooter, resetting update components, re-registering update DLLs, and repairing Windows with DISM and SFC.

Should I disable antivirus for this error?

Temporarily, yes, as a test. Antivirus or firewall software can block update services or registration operations. Turn protection back on after testing and add trusted rules if needed.

Why does error 0x80080005 come back after every retry?

The local update engine is still broken. Retrying the same update does not repair services, COM registration, update folders, or component store damage.

What should I do if the error changes after repair?

A changed error usually means progress. The original failure was fixed, and Windows Update is now reaching the next problem. Search for the new code and fix that specific issue.

Related Fixes

More useful answers in Windows Fixes

Keep solving the same topic without leaving the flow.