This post covers details about Configuration Manager 1802 hotfix KB4339794. In my previous post I covered on Configuration Manager 1802 hotfix KB4163547. While this update appears in console, the question is whether to install it or not. Or what does this hotfix contain ?. The hotfix KB4339794 was released to address an issue where configuration manager clients fail to download express installation for updates. In addition this issue occurs after you update to Windows 10, version 1803. This is also known as the Windows 10 April 2018 Update.

The Configuration Manager product team has identified that this issue occurs in Configuration Manager current branch, version 1802. The error is observed in WUAHandler.log and one can see the line “Successfully canceled running content download”. More information about the hotfix KB4339794 is documented here. You can install this hotfix to fix the above mentioned issue. The update doesn’t require restart post installation.

Configuration Manager 1802 HotFix KB4339794 Update

To install configuration manager 1802 hotfix KB4163547, navigate to updates and servicing node. If you see the update status as ready to install, right click update and click Install Update Pack.

Configuration Manager 1802 HotFix KB4339794 Update

In the update wizard choose the client update settings. Click Next.

Configuration Manager 1802 HotFix KB4339794 Update

Click Next for remaining pages and on completion page click Close.

Configuration Manager 1802 HotFix KB4339794 UpdateMonitor the update installation status under Monitoring, Updates and Servicing status. In my lab setup i did notice that the hotfix KB4339794 showed installed successfully. However under the updates and servicing status, i saw that the installation was stuck on post-deployment tasks. I bounced the server and post-installation tasks showed all green (completed).

The hotfix doesn’t change site and console version. If you click the KB4339794, under the contents you see only Configuration Manager site server updates and Configuration Manager client updates. Probably that explains why console wasn’t updated. Note that the client agent version after installing this update should be 5.00.8634.1814. Do write in comments section if you have any questions related to this update.