Fix SCCM Client-Side Patching or Software Updates Issues Troubleshooting Tips

In this post, we see how to Fix SCCM Client-Side Patching or Software Updates Issues and troubleshooting tips. Let’s go through ConfigMgr Software Updates Troubleshooting Tips, Fix Installation Issues, & Backend Process via the Update Deployment Agent component (UpdateDeployment.log).

I tried to give you an overview of the SCCM patching process using the Update Deployment Agent component. ConfigMgr also provides a solution to third-party application patching as well.

Software updates in SCCM provide a set of tools and resources along with WSUS that can help to manage the task of installing Microsoft patches on Windows 10 devices.

Patch My PC

The main topic that I’m going to cover is Servicing Stack Update (SSU) software update deployment mechanism for Windows 10. You can look into other ConfigMgr logs to get a similar kind of flow for each feature.

You need to configure Software Update Point (SUP) and infra setup before starting using the software update feature from ConfigMgr.

➡️SCCM Patch Software Update Deployment Process Guide.

Introduction – Troubleshoot SCCM Patching

In this post, I assume that you already have knowledge of how to configure and deploy software updates to Windows 10 devices. You can learn more about this here -> How to Create Deploy New Software Update Patch Package Using SCCM | ConfigMgr

I have already deployed the following software updates to Windows 10 device and now the client is trying to install the updates.

The following process of going through UpdateDeployment.log will help you to understand the background process. Also, this will help you to troubleshoot SCCM patching-related issues.

Troubleshooting Flow to Fix SCCM Client-Side Patching or Software Updates Issues

The flows which you need to check things from SCCM client-side – to Fix SCCM Client-Side Patching or Software Updates Issues.

Fix SCCM Client-Side Patching or Software Updates Issues Troubleshooting Tips
Fix SCCM Client-Side Patching or Software Updates Issues Troubleshooting Tips
  1. UpdateStore.log to know the status of the updates?
  2. Updatedeployment.log – % of Download completed? Status = ciStateInstalling, PercentComplete = 16,
    1. added to the targeted list of deployment
    2. Progress: Status = ciStateDownloading, PercentComplete = 0, Result = 0x0
    3. Progress: Status = ciStateWaitInstall, PercentComplete = 0, DownloadSize = 0, Result = 0x0
    4. Progress: Status = ciStateInstalling, PercentComplete = 89, DownloadSize = 0, Result = 0x0
    5. Progress: Status = ciStateInstalling, PercentComplete = 100, DownloadSize = 0, Result = 0x0
    6. Progress: Status = ciStatePendingSoftReboot, PercentComplete = 0, DownloadSize = 0, Result = 0x0
    7. Progress: Status = ciStateInstallComplete, PercentComplete = 0, DownloadSize = 0, Result = 0x0
    8.  Job completion received.
  3. CCMSDKProvider.log – Get client agent settings…Getting reboot setting whether to show dialog instead of notification

More Granular way of SCCM Client-Side Patching Issue Troubleshooting Options

Let’s seen the more granular way of troubleshooting SCCM Client-Side Patching Issue Troubleshooting Options. The SCCM client side log files are located at C:\Windows\CCM\Logs on Windows 11 or Windows 10 PCs.

1. Locationservices.log – Check whether it’s able to find WSUS Path= and Distribution Point with patches

2. WUAHandler.log to check whether the scan is completed or not

3. Updatedeployment.log – Check for the deadline of the assignment and Software Updates client configuration policy, DetectJob completion received for assignment, Added update (Site_, PercentComplete, etc…

4. Execmgr.log – Execution is complete for program Software Updates Program

5. RebootCoordinator.log – Reboot related things

Added to Targeted List of Deployment

This is the first step handled by the Update Deployment Agent component. You can find these details in the UpdateDeployment.log.

ConfigMgr Software Updates Troubleshooting Tips | Fix Installation Issues | SCCM
Introduction – Fix SCCM Client-Side Patching or Software Updates Issues

Update (Site_1074285A-82C7-474F-B242-1EE20F8C3CE5/SUM_774ec963-65e7-4c81-96e8-d229c10c3d00) Name (2021-01 Servicing Stack Update for Windows 10 Version 2004 for x64-based Systems (KB4598481)) ArticleID (4598481) added to the targeted list of deployment ({F7A0F5F8-689F-49BC-8EA3-966C43D8F867})

Start Downloading – Fix SCCM Client-Side Patching or Software Updates Issues

The SCCM Software Update (patching) is going into Downloading state as you can UpdateDeployment.log.

Fix SCCM Client-Side Patching or Software Updates Issues Troubleshooting Tips
Fix SCCM Client-Side Patching or Software Updates Issues Troubleshooting Tips

Update (Site_1074285A-82C7-474F-B242-1EE20F8C3CE5/SUM_774ec963-65e7-4c81-96e8-d229c10c3d00) Progress: Status = ciStateDownloading, PercentComplete = 0, Result = 0x0

Download Completed

The Configuration Manager Software Update (patching) is going into Download completed state as you can UpdateDeployment.log. The download percentage completed is 100% as per the log file.

Fix SCCM Client-Side Patching or Software Updates Issues Troubleshooting Tips
Fix SCCM Client-Side Patching or Software Updates Issues Troubleshooting Tips

Update (Site_1074285A-82C7-474F-B242-1EE20F8C3CE5/SUM_774ec963-65e7-4c81-96e8-d229c10c3d00) Progress: Status = ciStateDownloading, PercentComplete = 100, Result = 0x0

Waiting to Install

This is the next stage for patch installation using ConfigMgr (a.k.a) and WSUS. The update goes into the waiting to install stage or in the queue to get installed.

Fix SCCM Client-Side Patching or Software Updates Issues Troubleshooting Tips
Fix SCCM Client-Side Patching or Software Updates Issues Troubleshooting Tips

Update (Site_1074285A-82C7-474F-B242-1EE20F8C3CE5/SUM_774ec963-65e7-4c81-96e8-d229c10c3d00) Progress: Status = ciStateWaitInstall, PercentComplete = 0, DownloadSize = 0, Result = 0x0

Installing

Now, the patch/software update is getting into installing stage. It also gives the indication of the Percentage completed (11%) as you can in the UpdateDeployment.log.

Fix SCCM Client-Side Patching or Software Updates Issues Troubleshooting Tips
Fix SCCM Client-Side Patching or Software Updates Issues Troubleshooting Tips

Update (Site_1074285A-82C7-474F-B242-1EE20F8C3CE5/SUM_774ec963-65e7-4c81-96e8-d229c10c3d00) Progress: Status = ciStateInstalling, PercentComplete = 11, DownloadSize = 0, Result = 0x0

Installation Completed

Let’s check how to confirm whether one patch/software update got installed successfully or installation is completed successfully. You can refer to UpdateDeployment.log and check for the key word – Progress: Status = ciStateInstalling, PercentComplete = 100, DownloadSize = 0, Result = 0x0.

Fix SCCM Client-Side Patching or Software Updates Issues Troubleshooting Tips
Fix SCCM Client-Side Patching or Software Updates Issues Troubleshooting Tips

Update (Site_1074285A-82C7-474F-B242-1EE20F8C3CE5/SUM_774ec963-65e7-4c81-96e8-d229c10c3d00) Progress: Status = ciStateInstalling, PercentComplete = 100, DownloadSize = 0, Result = 0x0

Enforcement Message – Fix SCCM Client-Side Patching or Software Updates Issues

This message in the Update Deployment log file is important. The installation (enforcement state message for installation state) was successful and a Reboot is pending.

Fix SCCM Client-Side Patching or Software Updates Issues Troubleshooting Tips
Fix SCCM Client-Side Patching or Software Updates Issues Troubleshooting Tips

Raised update (TopicID) (Site_1074285A-82C7-474F-B242-1EE20F8C3CE5/SUM_774ec963-65e7-4c81-96e8-d229c10c3d00) enforcement state message successfully. TopicType = STATE_TOPICTYPE_SUM_CI_ENFORCEMENT, StateId = 9, StateName = CI_ENFORCEMENT_REBOOT_PENDING, StateCriticality = 0, TopicIdVersion = 200

Soft Reboot Pending

This is the message you can see in the updatedeployment.log file to confirm whether there is any reboot pending for the patch deployment using SCCM. The keyword that you can look for is Status = ciStatePendingSoftReboot.

Fix SCCM Client-Side Patching or Software Updates Issues Troubleshooting Tips 1

Update (Site_1074285A-82C7-474F-B242-1EE20F8C3CE5/SUM_774ec963-65e7-4c81-96e8-d229c10c3d00) Progress: Status = ciStatePendingSoftReboot, PercentComplete = 0, DownloadSize = 0, Result = 0x0

Get Assignment Priority

You can also check the assignment priority for a patch or software update from UpdateDeployment.log when you are using SCCM/WSUS for the installation of patches. The keyword that you have to look into is GetAssignmentPriority. The assignment priority for SSU is #1.

ConfigMgr Software Updates Troubleshooting Tips | Fix Installation Issues | SCCM
SCCM Patching issues

GetAssignmentPriority: update (Site_1074285A-82C7-474F-B242-1EE20F8C3CE5/SUM_774ec963-65e7-4c81-96e8-d229c10c3d00) is SSU, so that current assignment priority is 1

Successful Installation SCCM Software Update Client-Side Troubleshooting

This is the step after the restart of the Windows 10 device. The ConfigMgr patch installation got completed. The keywords are CI_ENFORCEMENT_SUCCESSFULL & Progress: Status = ciStateInstallComplete.

ConfigMgr Software Updates Installation Issues Troubleshooting Guide | SCCM Patching issues
ConfigMgr Software Updates Installation Issues Troubleshooting Guide | SCCM Patching issues

Raised update (TopicID) (Site_1074285A-82C7-474F-B242-1EE20F8C3CE5/SUM_774ec963-65e7-4c81-96e8-d229c10c3d00) enforcement state message successfully. TopicType = STATE_TOPICTYPE_SUM_CI_ENFORCEMENT, StateId = 10, StateName = CI_ENFORCEMENT_SUCCESSFULL, StateCriticality = 0, TopicIdVersion = 200

Update (Site_1074285A-82C7-474F-B242-1EE20F8C3CE5/SUM_774ec963-65e7-4c81-96e8-d229c10c3d00) Progress: Status = ciStateInstallComplete, PercentComplete = 0, DownloadSize = 0, Result = 0x0

Results – SCCM Client-Side Patching Troubleshooting

All the updates/patches will get disappeared from the software center after the restart and successful installation of patches/updates.

ConfigMgr Software Updates Installation Process via Update Deployment Log | SCCM
ConfigMgr Software Updates Installation Issues Troubleshooting Guide | SCCM Patching issues

Author

Anoop is Microsoft MVP! He is a Device Management Admin with more than 20 years of experience (calculation done in 2021) in IT. He is Blogger, Speaker, and Local User Group HTMD Community leader. His main focus is on Device Management technologies like SCCM 2012, Current Branch, and Intune. He writes about ConfigMgr, Windows 11, Windows 10, Azure AD, Microsoft Intune, Windows 365, AVD, etc.

Leave a Comment

This site uses Akismet to reduce spam. Learn how your comment data is processed.