Applies to

Configuration Manager 1702


You have updated your custom BranchCache enabled Boot images on your Distribution Points and chose to “Reload this boot image with the current Windows PE version from the Windows ADK”

Your OSD Task Sequences are now failing due to being unable to run steps that call BCEnabler.exe.


The following Microsoft article gives an overview of Boot Image Management in Configuration Manager:-

As per the document :-

Beginning in version 1702, when you upgrade the Windows Assessment and Deployment Kit (ADK) version, and then use updates and servicing to install the latest version of Configuration Manager, the site regenerates the default boot images. This update includes the new WinPE version from the updated Windows ADK, the new version of the Configuration Manager client, drivers, and customizations. The site doesn't modify custom boot images.

So during the upgrade process any custom boot images are left untouched and while you are now unable to modify these through the CM console, they will work the same as before to boot your clients.

An issue arrises however  when you come to update your Distribution Points with your custom boot images. During this process you are presented with the option to “Reload this boot image with the current Windows PE version from the Windows ADK”.

You know where this is headed! This option will overwrite the 2Pint BranchCache enabled boot image customizations and you will no longer be able to enjoy the awesomeness of BranchCache enabled boot scenarios.


During the Update Distribution Point Wizard do not choose the option to update the PE version to the latest.