Windows 10 1703 Update Installation fails during MDT / ConfigMgr Task Sequence

UPDATE: I’ve added some ConfigMgr / SCCM related details at the end of the blog post.

Over the last few weeks, I had an interesting issue regarding Windows 10 1703 and the Installation of Windows Updating during a Capture MDT Task Sequence.

MDT was configured to install Updates from a locally installed WSUS, which worked for Windows 7 up to Windows 10 1511. I recently started working with Windows 10 1703 and used about the same Capture Task Sequence as for Windows 10 1511. Here I had the issue, that the Reference Computer reaches the first Windows Update Step and runs into a Timeout while searching for Updates. You can leave the Computer pretty much for hours in this state without it doing anything.

What I first tried was pre-applying the latest Cumulative Update before the Task Sequence reaches the Windows Update Step. This was necessary with Windows 10 1607, due to a broken Windows Update Agent in the Vanilla Image. However, here it didn’t change anything unfortunately.

During testing I also had limited success by connecting the Reference Machine directly to the Internet. In addition, when working in a large organization with a complex network, this isn’t really an easy thing to achieve.

The real solution here is to add the two Windows Update related Registry Keys to the Reference Machine, before the Task Sequence reaches the first Windows Update Step. After the last Windows Update Step, we can remove the Keys to restore the Initial Situation for Sysprep and Capture.

As you see, I created a new Group called ‘Add Windows Update Settings’ just before the first Windows Update Step. Add a new ‘Run Command Line’ Step in this Group, name it ‘Set DeliveryOptimization to Bypass’ and specify the following Command Line:

Add another ‘Run Command Line’ Step just below the previously created one and name it ‘Set DoNotConnectToWindowsUpdateInternetLocations to 1’. Specify the following Command Line:

Add a ‘Restart Computer’ Step after the above Step.

Create a second Group called ‘Remove Windows Update Settings’ just below the last Windows Update Step.

Add a new ‘Run Command Line’ Step in this Group, name it ‘Remove DeliveryOptimization Registry Value’ and specify the following Command Line:

Add another ‘Run Command Line’ Step just below the previously created one and name it ‘Remove DoNotConnectToWindowsUpdateInternetLocations Registry Value’. Specify the following Command Line:

Add a ‘Restart Computer’ Step after the above Step.

When now starting the Task Sequence, the Windows Update Step should run through without the above Timeout issue.

Update 2. August 2017: I recently tested the described behaviour with the updated 1703 Media from Late July 2017. I came to the conclusion that the updated media doesn’t change anything and the above described workaround is still needed.

Update 28. September 2017: The same behaviour occurs when using Configuration Manager. Here you can apply same logic as seen above. The Screenshot below is a working example of a Windows 10 1703 OSD Task Sequence in Configuration Manager current branch.

Windows 10 1703 Update Installation fails during MDT / ConfigMgr Task Sequence
5 (100%) 3 votes

14 Comments

  1. Rick 9. June 2017
  2. Lars 13. June 2017
  3. Sean 13. June 2017
  4. Jonathan Block 21. June 2017
  5. jamie whitehead 4. July 2017
  6. Arjan 12. July 2017
    • mm Simon Dettling 12. July 2017
  7. DaVinniCode 2. August 2017
  8. David 8. August 2017
    • mm Simon Dettling 21. August 2017
  9. Sid 14. October 2017

Leave a Reply