If you manage devices and deployments with System Center Configuration Manager (SCCM), you know how critical smooth operations are. But sometimes errors interrupt software installations or updates. One of the more common ones is SCCM error 0x80080005, which often appears during application deployments, software updates, or operating system task sequences.
This article explains what the error means, the most common causes, and the exact steps you can take to fix it.
HelpDesk
What is SCCM Error 0x80080005?
The error code 0x80080005 translates to “CO_E_SERVER_EXEC_FAILURE”, meaning a required process or service failed to start. In SCCM, this typically surfaces when the Windows Update Agent or WMI (Windows Management Instrumentation) isn’t functioning properly.
You may see it logged in client logs like WUAHandler.log or UpdatesHandler.log.
Common Causes of Error 0x80080005
- Windows Update service not responding
- Corrupt or broken WMI repository
- Insufficient system or account permissions
- Damaged Windows Update components or cache
- System resource or DLL conflicts
How to Fix SCCM Error 0x80080005
Here are the most effective troubleshooting steps:
1. Restart Windows Update Services
Run the following commands in an elevated Command Prompt:
net stop wuauserv
net stop bits
net start wuauserv
net start bits
2. Repair the WMI Repository
Corrupted WMI is a frequent cause. Verify and repair with:
winmgmt /verifyrepository
winmgmt /salvagerepository
3. Reset Windows Update Components
Rename the update cache folders and restart services:
net stop wuauserv
net stop cryptSvc
net stop bits
net stop msiserver
ren C:\Windows\SoftwareDistribution SoftwareDistribution.old
ren C:\Windows\System32\catroot2 Catroot2.old
net start wuauserv
net start cryptSvc
net start bits
net start msiserver
4. Re-register Update DLL Files
Re-register essential Windows Update DLLs:
regsvr32 wuapi.dll
regsvr32 wuaueng.dll
regsvr32 wucltui.dll
regsvr32 wups.dll
regsvr32 wups2.dll
regsvr32 wuwebv.dll
5. Verify Permissions
Make sure the SYSTEM account and SCCM deployment accounts have the necessary permissions on the client machine.
6. Run a System File Check
Repair potential system file corruption:
sfc /scannow
Preventing Future Errors
- Keep SCCM clients updated with the latest patches
- Monitor WMI health regularly
- Ensure required services (BITS, Windows Update, Cryptographic Services) are running
- Periodically clean up the SoftwareDistribution folder
- Maintain correct Group Policy and account permissions
Final Thoughts
SCCM error 0x80080005 can be frustrating, but in most cases it’s tied to Windows Update services, WMI corruption, or permission issues. By following the steps above, you should be able to restore deployments quickly.
If problems persist, always check the logs (WUAHandler.log, UpdatesHandler.log) for deeper insight into what’s blocking the update or deployment. Proactive monitoring and client maintenance will also help reduce the likelihood of this error happening again.
