Troubleshooting Failed Software Updates in ConfigMgr
Posted by Trevor Sullivan on 2009/11/02
I just wanted to take a few moments to share the thought process that I use to troubleshoot failing software updates in Configuration Manager. On several occasions for me, this has been the most straightforward method of figuring out why an update is failing, and determining how to resolve the issue.
How to Manually Troubleshoot a Software Update
- Identify the GUID or KB article number of the software update
- Find the update in the ConfigMgr console’s Update Repository
- Open the update’s property page
- Go to the Content Information tab
- Find the appropriate line item, click it, and Ctrl + C to copy it
- Open Notepad, paste the line into it, and parse out the URL
- Download the update with your web browser
- Extract the update file(s) from the CAB
- Manually execute the update with any command-line options for logging
- Examine the resulting log file to determine the failure reason
These steps have usually worked for me, and it is a more direct method of troubleshooting than examining the Configuration Manager log files, since you are manually executing the patch, and can enable additional logging. The SCCM client’s log files can help with initially identifying a failing update, but to dig deeper, you may want to follow the above steps.
ConfigMgr Client Software Update Log Files
- WindowsUpdate.log (located in the root of %WINDIR%)
Hope this helps!