Overview

You are attempting to install Feature update to Windows 10 workstation. The remediation job to install this service pack appears successful within Languard; however, the Windows OS does not upgrade on the target - the system never reboots to complete the update.

Solution

The most common root cause for such behavior is environmental issues on the target Windows machine, like not enough space or group policies restricting the deployment.

The patch deployment process with LanGuard involves downloading the needed patch and delivering it to the target machine. From there, Windows executes the update, and LanGuard monitors the execution of the patch. In the case of Windows Feature Updates, as they are deployed via .esd files, the system indicates that the remediation job is complete when the script to initiate the install is run. For more details, refer to Why do Windows Feature Updates Ignore the After Deployment Options and Reboot After Patching? article.

The absence of the errors in the remediation job details means that LanGuard successfully initiated the Feature Update installation, and you have to wait for it to complete. If there are any possible errors afterward, they are entirely related to the Windows environment and could be found only in the Windows event logs.

It has been reported that the Windows 10 2004 feature update can take more than one hour and normally requires two restarts to complete. A fresh scan of the target machine after allowing Windows to complete the update should show the updated status and no longer return this as a missing update on the console.

If, after allowing some time to elapse, you are not seeing that the machines have rebooted to complete the upgrade, it means that the environmental issues are disrupting the installation. The issue here can be anything, from not enough space (at least 32 GB of free disk space), group policy settings, or manual intervention preventing the machines from being rebooted to some device/drivers messing with update logic.

Such cases are out of the scope of the LanGuard support, still, we recommended to:

1. Check Windows Event logs for errors after the time LanGuard reported the successful initiation of the installation. Adress anything you find with the assistance of Microsoft technical support and forums. For example, a known issue is the Event ID 455 ESENT error in Windows 10.
2. Check the resultant group policies for the target computer.
3. Refer to external sources for known issues with Feature Update 2004 and solutions and verify if they can fix the issue for you.
4. Run the Windows Update Troubleshooter and fix the errors it finds.
5. Once the root cause is addressed, retry the Feature Update 2004 deployment. If the results would be the same, try to install the Feature Update manually and check whether it asks something during the installation. Adress the issues with the Microsoft support help.