With SCCM/MECM software update problems, separate the scan, policy, applicability, deployment and content stages from each other. An update that does not show up and an update that shows up but does not download or install are not the same problem.
All client logs mentioned below are in C:\Windows\CCM\Logs on the client.
Problem and symptoms
- Updates do not appear in Software Center.
- The client does not complete the software update scan.
- An update shows as required but installation does not start.
- A deployment exists but the client’s compliance state does not change.
1. ScanAgent.log
In ScanAgent.log, check that the software update scan was started and that the client can work with its scan source.
2. WUAHandler.log
WUAHandler.log is one of the key client logs for the scan between the Windows Update Agent and Configuration Manager. Do not read an error code on its own; read it together with the entries just before and after it.
3. UpdatesDeployment.log
Review deployment evaluation and the state of the updates targeted at the client in UpdatesDeployment.log. For the download and installation of a specific update, UpdatesHandler.log and UpdatesStore.log add detail.
4. Check the policy
If the software update deployment policy has not reached the client, the expected deployment behaviour will not happen even if the scan succeeds. Verify the policy logs and the collection targeting.
After a fix, you can trigger the scan and the deployment evaluation on the client instead of waiting for the next cycle:
# Software Updates Scan Cycle
Invoke-CimMethod -Namespace root\ccm -ClassName SMS_Client -MethodName TriggerSchedule -Arguments @{sScheduleID='{00000000-0000-0000-0000-000000000113}'}
# Software Updates Deployment Evaluation Cycle
Invoke-CimMethod -Namespace root\ccm -ClassName SMS_Client -MethodName TriggerSchedule -Arguments @{sScheduleID='{00000000-0000-0000-0000-000000000108}'}5. The SUP and WSUS layer
If several clients show the same scan problem, do not look for the cause only on the client. Check the health of the Software Update Point and WSUS, the result of the last synchronization and the update components on the site side. On the site server, wsyncmgr.log shows the synchronization and WCM.log and WSUSCtrl.log show the SUP and WSUS configuration.
6. The content layer
If the update is required and the deployment is active but the download does not start, move on to the Boundary Group, Distribution Point and content transfer chain. Review LocationServices.log, ContentTransferManager.log and the related content logs together.
My troubleshooting flow
- Verify the scan in ScanAgent.log.
- Review the Windows Update Agent result in WUAHandler.log.
- Check deployment evaluation in UpdatesDeployment.log.
- Verify the policy and the collection targeting.
- If the problem is widespread, check the SUP and WSUS layer.
- If the download fails, move on to the DP and content troubleshooting flow.
Best practice
With software update problems, do not reset the client cache or the Windows Update components right away. First use the logs to find out whether the problem is in the scan, policy, deployment or content layer.
Next layer
If the scan and deployment are healthy but the content does not download, continue with Distribution Point content troubleshooting. If the client cannot communicate with policy or the Management Point at all, go back to client health and Management Point troubleshooting.
Conclusion
The most efficient approach to SCCM software update troubleshooting is to follow the order scan → policy → deployment → content. WUAHandler.log, ScanAgent.log and UpdatesDeployment.log are the basis for making that distinction.
Related guides
- SCCM Client Not Installing? Troubleshooting with ccmsetup.log and Client Health
- SCCM Management Point Communication Problems: Client MP Troubleshooting
- SCCM Application Deployment Failed? Troubleshooting with AppDiscovery.log and AppEnforce.log
- Distribution Point content troubleshooting (Turkish)
- SCCM log files (Turkish)
- What is SCCM / MECM? Configuration Manager architecture (Turkish)