Software update installations may stop responding or never return a completion status during task sequence execution or typical software updates management (SUM). This issue typically occurs when many updates are being installed, usually a mix of Office and Windows updates.
Different symptoms may be reported in the log files to indicate that this issue is being experienced.
For task sequence execution and the Install Software Updates task sequence step, the following message is repeated for the InstallSWUpdate component in the Smsts.log file:
Waiting for job status notification ...
Also, the WUAHandler.log file may indicate that the installation of all updates is successful. However, the completion status is never returned.
For typical SUM, different symptoms may be logged. The update installations may never start, and all updates may be stuck in a "ciStateDownloading" state. Additionally, entries that resemble the following for all updates may be logged in the UpdatesDeployment.log file:
Update (Site_73523994-7973-422C-A02B-F83A7A327F36/SUM_cca31bf2-b813-48d1-a4cd-ce317d024303) Progress: Status = ciStateDownloading, PercentComplete = 0, Result = 0x0 UpdatesDeploymentAgent
Note In some environments, the update installation process can stop responding later. Restarting the SMS Agent Host service (Ccmexec.exe). could enable the process to continue.
This issue most frequently occurs on Windows 10, version 1709. However, other versions of Windows may also be affected.
For more information about the symptoms that you might experience when this issue occurs, see the following Knowledge Base article:
4491117 Update installations to clients stop responding in Configuration Manager, version 1810 or 1806