In this article, you will learn how to troubleshoot Failed to Install Update error 0X800705B4 and error 0X80004004 appearing in your SCCM console.
During the software update deployments, the updates fail to install and this is a common issue. Whenever an update deployed using SCCM fails to install, it fails with an error code. This error code should be used to troubleshoot the software update deployments.
Software Update Install Error 0X800705B4, Error 0X80004004
In this specific example, there are two errors that you see related to failed software updates deployments.
- Failed to install update(s) – Error Code 0X800705B4 (This operation returned because the timeout period expired.
- Failed to install update(s) Error 0X80004004 (Operation aborted).
Thanks to SCCM error lookup tools, you can translate the error codes to error messages. When you translate error 0X800705B4 using error lookup tool, here is what you see.
- Error 0X800705B4 = This operation returned because the timeout period expired.
- Error 0X80004004 = Operation aborted
You can use the same error lookup tool to translate error 0X80004004 which means Operation aborted.
Fix Failed to Install Update Error 0X800705B4, 0X80004004
Let’s look at the steps to fix failed to install update error 0X800705B4, error 0X80004004. You can fix the error 0X800705B4 by enabling the option “Allow clients to connect anonymously” under the SCCM distribution point properties.
- Open the Configuration Manager Console.
- Click on Administration > Overview > Distribution Points.
- Right-Click on the Distribution Point and then click Properties.
- In the General tab, click “Allow clients to connect anonymously.”
Logs that are beneficial to use when troubleshooting
The following list of SCCM log files are beneficial when you want to troubleshoot the software updates failed deployment issues.
- It is always recommended to check the locationservices.log on the client to ensure the client is detecting the correct Software Update Point (SUP). Also, it is always best practice to ensure that the ConfigMgr client is correctly reporting to the MECM server that the software update is enabled.
- The policy agent will trigger the software update deployment cycle, and then the scan result will then be compared with the catalog. It will then download only the required update and install it on the defined schedule. To get more details about the update, you can check the updatestore.log, updatesdeployment.log, and the windowsupdate.log.
Tracking software update deployment processes in MECM
You can use the following guide as reference for SCCM Software Updates Log Files. The below log files are useful for monitoring the software update deployments in SCCM.
| wsyncmgr.log | This file records information about the synchronization process. | Server machine |
| WCM.log | This log file records information about the SUP configuration, subscribed categories, classifications, and languages on the SUP server. Very important when you perform sync for the first time. | Server machine |
| wctrl.log | Records information about the configuration, database connectivity, and health of the WSUS server. | Server machine |
| WUAHandler.log | Records information about searching for updates. | Client machine |
| UpdatesDeployment.log | Records information about deployment, evaluations, and enforcements on the client. | Client machine |
| UpdatesHandler.log | Records information about compliance, scanning, and the download and installation of updates on the client. | Client machine |
| SoftwareDistribution.log | Contains information about the software updates that are synchronized from the update source to the WSUS database. | WSUS server – %programfiles%\Update Services\Logfiles |
| UpdateStore.log | This file contains information about the compliance of updates that are scanned as part of the compliance scanning. | Client machine |
| ruleengine.log | Records information about processing the automatic update rules. Useful when you are working with ADR’s. | Server machine |
| scup.log | Records information about downloading and synchronizing custom updates to WSUS. | %temp% on the computer with the SCUP console installed |
| patchdownloader.log | Records information about downloading software updates from the update source to the specified source location for the Update package | Client machine |
| windowsupdate.log | Logs activity about scanning and installing updates. | C:\Windows |
Recommended Reading
Some good references that you can use to troubleshoot and help track the software update deployment process:
