I had the same issue. MS KB2769827 helps to explain the problem - it has to do with apps updating during the build process.
One fix is to disable Windows Store Updates and the Microsoft Consumer Experience before your VM hits the internet. Depending on how you create/deploy your vm, there are several ways to do this. I just created a vm without a NIC, installed Win10, disabled Windows Store Updates and the Microsoft Consumer Experience via a registry entry that comes from running a Powershell script that sets several configurations on the VM right after Windows loads (or you can use the local group policy editor), added a NIC to the VM, and proceeded with the build.
Powershell Reg entries in my script:
# Disable Microsoft Consumer Experience
New-Item -Path "HKLM:\Software\Policies\Microsoft\Windows" -Name CloudContent -Force
New-ItemProperty -Path "HKLM:\Software\Policies\Microsoft\Windows\CloudContent" -Name DisableWindowsConsumerFeatures -PropertyType DWORD -Value 1 -Force
# Disable Windows Store Updates
New-Item -Path "HKLM:\Software\Policies\Microsoft" -Name WindowsStore -Force
New-ItemProperty -Path "HKLM:\Software\Policies\Microsoft\WindowsStore" -Name AutoDownload -PropertyType DWORD -Value 2 -Force
A few good articles that helped me are:
Thank you PaulMurphyCO so much!! Would you say that this also applies to creating a template for Horizon Linked Clone deployment?
I will include your suggestions in my next development. By the way, I finally got something to work after running the "Kill it with Fire" commands from this article.
I did it on my template VMs, then created parent VMs for our linked clone pools. Sysprep ran successfully on creation of the parent vm.
Sorry for my delayed response. Excellent feedback. So helpful.
I did manage to get a Win10 1709 with the Horizon Win10 optimization sling utility.
It works, but for some reason IE is not in the start menu, therefore does not show up when typing in Search.
Its fine in the template.
Now I have to go back test it without the optimizations I guess.