Deploying Windows 10 Feature updates to clients older than 1803

Niall Murphy 1 Reputation point


We're trying to deploy feature updates, W10 1909 to clients 1803 and older via SCCM 1906.

The clients report as compliant but the update is not installed. We've deployed the latest Servicing Stack Update to the clients. This also reports as compliant without installing the update.

The clients aren't showing any errors in their update logs.

Any ideas?? Thanks

Microsoft Configuration Manager Updates
Microsoft Configuration Manager Updates
Microsoft Configuration Manager: An integrated solution for for managing large groups of personal computers and servers.Updates: Broadly released fixes addressing specific issue(s) or related bug(s). Updates may also include new or modified features (i.e. changing default behavior).
633 questions
{count} votes

1 answer

Sort by: Most helpful
  1. Amandayou-MSFT 10,941 Reputation points

    Since last SSU is not still installed on the client, there might be seven steps to troubleshoot the common issues. Step 1: We could check Policyagent.log. When policy is received, the following entry is logged in PolicyAgent.log: ![21436-831.png][1] We could check if Deployment Unique Id on the console is consistent with policy id displayed in PolicyAgent.log. ![21437-8311.png][2] Step 2: Software update would be checked if it is required by client , kindly check UpdatesStore.log. UpdateStore.log would record updates as missing if they are required. If it is not required or has been installed by client, there is no record in this log. Step 3: If the update is required, the content could be detected before downloading. We could refer to UpdatesDeploymentAgent.log. Step 4: The content could be downloaded. we could refer to UpdatesHandler.log, CAS.log, and ContentTransferManager.log. Here is a screenshot about ContentTransferManager.log. Step 5: After the download is completed, detection could be followed before installation. We could refer to UpdatesHandler.log,ScanAgent.log, UpdateStore.log, WindowsUpdate.log and WUAHandler.log. Step 6: Software update could be installed. We could refer to Windowsupdate.log and UpdatesDeployment.log. Step 7: After the updates are installed, Updates Deployment Agent checks whether any updates require a reboot, and then it notifies the user if client settings are configured to allow such notification. We could refer to UpdatesDeployment.log and UpdateStore.log. Here is an article about some detailed log screenshots. [Using log files to track the software update deployment process][3] ************************************************************************* If the response is helpful, please click "Accept Answer" and upvote it. [1]: /api/attachments/21436-831.png?platform=QnA [2]: /api/attachments/21437-8311.png?platform=QnA [3]: